Security Group Trigger notifications not propagated to Quantum
Bug #933147 reported by
David Lapsley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
David Lapsley |
Bug Description
Nova allows security group information to be CRUD'd via both the ec2 and openstack APIs. Both of these APIs notify nova compute via three methods:
def trigger_
def trigger_
def trigger_
These indicate that the security group tables in the database have been modified so that nova can take appropriate action. Currently, quantum is not notified of these changes. A lightweight mechanism is required to ensure quantum is able to receive this notifications.
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/4218
Review: https:/