Comment 3 for bug 1460222

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

For completeness, one other mechanism that can be leveraged today (without any changes to Neutron) for these types of use cases is the binding:profile [1]. This is part of Neutron port binding extension [2], and it would allow you to address your use cases too. If you intend to use the ODL driver, then it should be a trivial change to have the binding profile be passed all the way down to the Neutron northbound endpoint.

Therefore at this point it's a matter of gauging interest as to whether we'd want to go with a fully fledged new tagging mechanism (potentially extended to other core resources), or settle for something that may fit the bill and have the lowest implementation cost.

[1] https://blueprints.launchpad.net/neutron/+spec/ml2-binding-profile
[2] https://blueprints.launchpad.net/neutron/+spec/ml2-portbinding