Public bug reported:
when a security group members or rules change, if it just notify the l2 agents
with 'security_groups_member_updated' or 'security_groups_rule_updated', the
all related l2 agents need to get the security group details through RPC from
neutron-server, when the number of l2 agents is large, the load of
neutron-server is heavy.
we can use fanout RPC message with the changed sg details to notify the l2
agents, then l2 agents which has the related devices update the sg information
in their memory, they do not need to get the sg details through RPC.
** Affects: neutron
Importance: Undecided
Assignee: shihanzhang (shihanzhang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => shihanzhang (shihanzhang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1463375
Title:
Use fanout RPC message to nofity the security group's change
Status in OpenStack Neutron (virtual network service):
New
Bug description:
when a security group members or rules change, if it just notify the l2
agents with 'security_groups_member_updated' or 'security_groups_rule_updated',
the all related l2 agents need to get the security group details through RPC
from
neutron-server, when the number of l2 agents is large, the load of
neutron-server is heavy.
we can use fanout RPC message with the changed sg details to notify the l2
agents, then l2 agents which has the related devices update the sg information
in their memory, they do not need to get the sg details through RPC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1463375/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
