Modular L2 TypeDriver extra port information

Registered by Zang MingJie on 2013-07-19

Currently agent uses segment tuple (type,physical,segmentation_id) to decide how to setup the port, but sometimes extra information may be needed in order to setup the port. eg vxlan may need the multicast ip address.

This blueprint provides a mechanism where TypeDriver can provide extra information to agent when the agent is going to setup a port.

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Undefined
Drafter:
None
Direction:
Approved
Assignee:
Zang MingJie
Definition:
Obsolete
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
milestone icon next
Started by
Zang MingJie on 2013-07-19
Completed by
Armando Migliaccio on 2015-11-09

Related branches

Sprints

Whiteboard

If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1]

[1] http://docs.openstack.org/developer/neutron/policies/blueprints.html

3-Sep Moving I as the code was not finalized in time.

Gerrit topic: https://review.openstack.org/#q,topic:bp/ml2-typedriver-extra-port-info,n,z

Addressed by: https://review.openstack.org/37893
    Modular L2 TypeDriver extra port information (WIP)

Addressed by: https://review.openstack.org/61761
    Modular L2 TypeDriver refact (ovs-agent)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.