diff options
| author | Dan Smith <danms@us.ibm.com> | 2013-01-02 10:59:42 -0800 |
|---|---|---|
| committer | Dan Smith <danms@us.ibm.com> | 2013-01-04 08:10:41 -0800 |
| commit | 10daa81057b2cfc0a3e21624b50b0b5d610b4db2 (patch) | |
| tree | 036decd2a534f377db737b7cf0130b50e44a71c9 /nova/exception.py | |
| parent | 1bf89924ba6eafc394612f9d62c1b52251825b2b (diff) | |
| download | nova-10daa81057b2cfc0a3e21624b50b0b5d610b4db2.tar.gz nova-10daa81057b2cfc0a3e21624b50b0b5d610b4db2.tar.xz nova-10daa81057b2cfc0a3e21624b50b0b5d610b4db2.zip | |
Move block_device_mapping destroy operations to conductor
This patch moves the compute/manager's use of block_device_mapping_destroy
operations to the conductor. Specifically:
- block_device_mapping_destroy()
- block_device_mapping_destroy_by_instance_and_device()
- block_device_mapping_destroy_by_instance_and_volume()
Once again, this just adds a single destroy operation to the conductor's
RPC API and replicates the older interfaces in the public API. Further,
the first now takes a list of bdms to be destroyed (unlike the db
operation it mirrors) so that multiple RPC calls can be avoided for
bulk delete operations.
Related to blueprint no-db-compute-manager
Change-Id: Ib93184ee6d32fcda90f75a26b579787e4625e9ae
Diffstat (limited to 'nova/exception.py')
0 files changed, 0 insertions, 0 deletions