yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

** Changed in: nova
       Status: New => Opinion

-- 
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/1333971

Title:
  Block device usage is overly restrictive

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  Version in use: Havana, but I believe the issue exists in IceHouse

  As per https://www.mail-archive.com/openstack-
  dev@xxxxxxxxxxxxxxxxxxx/msg25179.html, I'd like to be able to specify
  multiple --image options (or rather the equivalent --block-device
  options). Further, I'd like to be able to specify a --image other than
  the first as the initial boot disk.

  The documentation for the "nova boot" command makes no reference to
  the number of --image/--block-device options being limited to 1, and
  indeed describes a --boot-index option to allow a non-first disk to be
  booted. However, using multiple options simply does not work. What
  seems to happen is that the last option specified is used.

  I suggest the following implementation:

      - an arbitrary number of --block-device (or equivalent --image,
  --sawp, --ephemeral or --block-device-mapping) options be allowed.

      - any --block-device of type image be allowed to take a boot-index
  option. The boot-index option(s) must start at 0, and must not exceed
  the number of block-devices of type images. Duplicate values are not
  allowed.

      - if no --block-device has a boot-index option, then the first
  such option shall default to --boot-index=0.

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