True. I think if you just want to add segments, making use of the new
segments API added as part of the routed networks work would be the way to
go.
On Mon, Nov 7, 2016 at 9:19 AM, Robert Kukura
wrote:
> I'm not sure unbinding ports is necessary unless the segment that a port
> has bound is remo
I'm not sure unbinding ports is necessary unless the segment that a port
has bound is removed or modified. A reasonable compromise might be for
ML2 to allow adding new segments, which should not require
unbinding/rebinding ports, but not allow removing or modifying existing
segments.
-Bob
O
To allow that we would have to unbind every port in the network and then
rebind it with the new segment info generated from changing the provider
attributes. This requires quite a bit of orchestration code in ML2 (to
handle failures, etc) that doesn't exist right now.
On Sat, Nov 5, 2016 at 7:50 A
Dear,
Neutron RESTful API support update network provider attributes, but ML2 raises
error when update network provider attributes (in function
_raise_if_updates_provider_attributes), can anyone tell me why ML2 does not
support it?
BR
Juno
__
