yahoo-eng-team team mailing list archive

[Feodor Tersin <ftersin@xxxxxxxxxxxxxxxx>]

Public bug reported:

AWS allows to change block device attributes (such as volume size,
delete on termination behavior, existence) at instance launch.

For example, image xxx has devices:
vda, size 10, delete on termination
vdb, size 100, delete on termination
vdc, size 100, delete on termination
We can run an instance by
euca-run-instances ... xxx -b /dev/vda=:20 -b /dev/vdb=::false -b /dev/vdc=none
to get the instance with devices:
vda, size 20, delete on termination
vdb, size 100, not delete on termination

For Nova we get now:
$ euca-run-instances --instance-type m1.nano -b /dev/vda=::true ami-0000000a
euca-run-instances: error (InvalidBDMFormat): Block Device Mapping is Invalid: Unrecognized legacy format.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370250

Title:
  Can not set volume attributes at instance launch by EC2 API

Status in OpenStack Compute (Nova):
  New

Bug description:
  AWS allows to change block device attributes (such as volume size,
  delete on termination behavior, existence) at instance launch.

  For example, image xxx has devices:
  vda, size 10, delete on termination
  vdb, size 100, delete on termination
  vdc, size 100, delete on termination
  We can run an instance by
  euca-run-instances ... xxx -b /dev/vda=:20 -b /dev/vdb=::false -b /dev/vdc=none
  to get the instance with devices:
  vda, size 20, delete on termination
  vdb, size 100, not delete on termination

  For Nova we get now:
  $ euca-run-instances --instance-type m1.nano -b /dev/vda=::true ami-0000000a
  euca-run-instances: error (InvalidBDMFormat): Block Device Mapping is Invalid: Unrecognized legacy format.

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