summaryrefslogtreecommitdiffstats
path: root/nova/openstack
diff options
context:
space:
mode:
authorDan Smith <danms@us.ibm.com>2013-02-06 17:48:49 -0500
committerDan Smith <danms@us.ibm.com>2013-02-06 21:45:11 -0500
commit32d6f568aedeee25cb9c0b093ee847459c091f7e (patch)
tree0671bb11349caf57a0f58b26016f4e3b7a96e09a /nova/openstack
parent749c3db3f63f70d9a71ff26e253b3eeda5d9d742 (diff)
downloadnova-32d6f568aedeee25cb9c0b093ee847459c091f7e.tar.gz
nova-32d6f568aedeee25cb9c0b093ee847459c091f7e.tar.xz
nova-32d6f568aedeee25cb9c0b093ee847459c091f7e.zip
Move security_groups refreshes to conductor
This moves the last bit of compute-initiated db accesses found during test runs to conductor. The quantum API was hitting the database directly while calling back to compute's API to trigger the refresh. This just makes the quantum API ask conductor to do that in a similar way to the usage notifications patch recently merged. Related to blueprint no-db-compute Change-Id: I44de7e1e12aec291b8319d45ec5975ad05b8e676
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions