`_parse_block_device_mapping` method was design to support both
bdm v1 and v2. The implementation is based on the fact that API side
ignores unknown/incorrect parameters, so `_parse_block_device_mapping` compose
equal parameter for bdm v1 and bdm v2. Since Nova V2.1 contains schema checks,
such implementation stoped working.
Despite the fact that novaclient.v2.servers contains separate logic for bdm v2,
we can make `_parse_block_device_mapping` works only with legacy bdm and
in future patches make it works for both bdm v1 and bdm v2.
Reviewed: https:/ /review. openstack. org/221525 /git.openstack. org/cgit/ openstack/ python- novaclient/ commit/ ?id=5153dcda807 c554769081626c1 0c43d16adea671
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5153dcda807c554 769081626c10c43 d16adea671
Author: Andrey Kurilin <email address hidden>
Date: Wed Sep 9 01:04:45 2015 +0300
[BugFix] Change parameters for legacy bdm
`_parse_ block_device_ mapping` method was design to support both block_device_ mapping` compose v2.servers contains separate logic for bdm v2, block_device_ mapping` works only with legacy bdm and
bdm v1 and v2. The implementation is based on the fact that API side
ignores unknown/incorrect parameters, so `_parse_
equal parameter for bdm v1 and bdm v2. Since Nova V2.1 contains schema checks,
such implementation stoped working.
Despite the fact that novaclient.
we can make `_parse_
in future patches make it works for both bdm v1 and bdm v2.
Change-Id: I37c00ac77b1a3b 500221d77953353 2e9f43e5277
Closes-Bug: #1491737