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
On 11/5/16 7:59 PM, Kevin Benton wrote:
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 AM, zhuna <juno....@huawei.com
<mailto:juno....@huawei.com>> wrote:
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
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
