yahoo-eng-team team mailing list archive

[Hong Hui Xiao <honghui_xiao@xxxxxxxx>]

Public bug reported:

In the notification of AFTER_DELETE event for SECURITY_GROUP_RULE, the
security group rule is actually deleted from DB. There is no way for
subscriber to know the latest information of related security group.

To be specific, dragonflow will maintain the security group version, and
we are using revision_number in dragonflow now. The sg_rule_delete will
bump the sg revision, which will only happen after the db transaction.
dragonflow stores security group rule as part of security group. So, in
the AFTER_DELETE event of SECURITY_GROUP_RULE, we don't know which
security group is updated, if neutron don't pass the security group id.

We can query all security group and iterate their security group rules.
But that is inefficient and it will be nice if neutron just pass the
related security group id.

** Affects: neutron
     Importance: Undecided
     Assignee: Hong Hui Xiao (xiaohhui)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Hong Hui Xiao (xiaohhui)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1621698

Title:
  AFTER_DELETE event for SECURITY_GROUP_RULE should contain sg_id

Status in neutron:
  New

Bug description:
  In the notification of AFTER_DELETE event for SECURITY_GROUP_RULE, the
  security group rule is actually deleted from DB. There is no way for
  subscriber to know the latest information of related security group.

  To be specific, dragonflow will maintain the security group version,
  and we are using revision_number in dragonflow now. The sg_rule_delete
  will bump the sg revision, which will only happen after the db
  transaction. dragonflow stores security group rule as part of security
  group. So, in the AFTER_DELETE event of SECURITY_GROUP_RULE, we don't
  know which security group is updated, if neutron don't pass the
  security group id.

  We can query all security group and iterate their security group
  rules. But that is inefficient and it will be nice if neutron just
  pass the related security group id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1621698/+subscriptions