Public bug reported:
in neutron.db.db_base_plugin_v2,
def update_subnetpool(self, context, id, subnetpool):
....
if address_scope_changed:
# Notify about the update of subnetpool's address scope
kwargs = {'context': context, 'subnetpool_id': id}
registry.notify(resources.SUBNETPOOL_ADDRESS_SCOPE,
events.AFTER_UPDATE,
self.update_subnetpool,
**kwargs)
This kwargs ONLY includes subnetpool_id, in some cases, we want to know
the subnetpool old address scope id.
Here is the use case,
To develop bgp vpn in neutron-dynamic-routing, each bgpvpn is associated to
address scope, bgpvpn routes only include the subnets of same address scope.
If the subnetpool change its address scope, for some bgpvpnvs associated to old
address scope, it should delete the routes; for some bgpvpns associated to new
address scope, it should add new routes.
If this event does not include old address_scope_id, bgpvpn can not
delete old routes.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1598735
Title:
subnetpool address scope change event should include the old address
scope id
Status in neutron:
New
Bug description:
in neutron.db.db_base_plugin_v2,
def update_subnetpool(self, context, id, subnetpool):
....
if address_scope_changed:
# Notify about the update of subnetpool's address scope
kwargs = {'context': context, 'subnetpool_id': id}
registry.notify(resources.SUBNETPOOL_ADDRESS_SCOPE,
events.AFTER_UPDATE,
self.update_subnetpool,
**kwargs)
This kwargs ONLY includes subnetpool_id, in some cases, we want to
know the subnetpool old address scope id.
Here is the use case,
To develop bgp vpn in neutron-dynamic-routing, each bgpvpn is associated to
address scope, bgpvpn routes only include the subnets of same address scope.
If the subnetpool change its address scope, for some bgpvpnvs associated to
old address scope, it should delete the routes; for some bgpvpns associated to
new address scope, it should add new routes.
If this event does not include old address_scope_id, bgpvpn can not
delete old routes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1598735/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
