Operational Status for OVS plugin

Registered by dan wendlandt

This milestone has a blueprint to add an "operational status" attribute to API entities, including quantum networks and ports (https://blueprints.launchpad.net/quantum/+spec/api-operational-status).

The OVS plugin will need to be updated to expose operational status.

Likely this status will be "up" for a network as long as a underlying resources (e.g., a VLAN) was successfully allocated for the network.

For a port, the agent will need to "phone home" indicating whether it currently sees a particular VIF.

Blueprint information

Status:
Complete
Approver:
dan wendlandt
Priority:
Medium
Drafter:
dan wendlandt
Direction:
Needs approval
Assignee:
dan wendlandt
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2012.1
Started by
dan wendlandt
Completed by
dan wendlandt

Related branches

Sprints

Whiteboard

Am targeting this for essex-2, though if it takes a while to define the API changes themselves (also slotted for essex-2), we may have to bump this to essex-3.

Gerrit topic: https://review.openstack.org/#q,topic:bp/operational-status-ovs-plugin,n,z

Addressed by: https://review.openstack.org/2281
    blueprint operational-status-ovs-plugin

Addressed by: https://review.openstack.org/2097
    blueprint api-operational-status

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.