Gateway Device extension API

Registered by Ryu Ishimoto

Implement gateway device management extension API for midonet neutron plugin
Gateway device is relevant for several use cases:
1. Connecting virtual network to Physical Servers (via HW VTEP)
2. Supporting Direct Connect between Peering Facility and Private Cloud
3. Supporting Router Peering, connecting multiple sites across WAN network.
All the above cases require physical or virtual gateway device to support connectivity.
We need a way to define and setup these devices. Gateway device management API is going to be used in order to manage the following:
-- Device type
-- Device name/uuid
-- Device management IP/Port
-- Device Tunneling Table
-- Device Tunnel IPs
Original JIRA: https://midonet.atlassian.net/browse/MNP-91

Blueprint information

Status:
Complete
Approver:
Ryu Ishimoto
Priority:
High
Drafter:
Ryu Ishimoto
Direction:
Approved
Assignee:
Kengo Hobo
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
None
Started by
Ryu Ishimoto
Completed by
Ryu Ishimoto

Related branches

Sprints

Whiteboard

To simplify the implementation, I suggest that we follow how L3 Service plugin is implemented. We want to keep everything in the networking-midonet package if possible. So I think we can do something like the following to keep consistent with the current codebase:

* Define the extension in midonet/neutron/extensions/gw_device.py
* Define the data models and add a migration script
* Implement the plugin in midonet/neutron/services/gw_device/plugin.py
* Write unit tests in midonet/neutron/tests/unit/test_extension_gw_device.py

Gerrit topic: https://review.openstack.org/#q,topic:bp/gw-device-api,n,z

Addressed by: https://review.openstack.org/243602
    Gateway device management API update spec

(?)

Work Items

Work items:
Extension: DONE
DB: DONE
Unit tests: DONE
Plugin: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.