yahoo-eng-team team mailing list archive

[Nikola Đipanov <ndipanov@xxxxxxxxxx>]

It is enough to specify --boot-volume option, (see
https://wiki.openstack.org/wiki/BlockDeviceConfig for more details about
the block device mapping syntax).

Setting max_local_block_devices to 0 means that any request that
attempts to create a local disk will fail. This option is meant to limit
the number of local discs (so root local disc that is the result of
--image being used, and any other ephemeral and swap disks).

AFAIK Tempest by it's very nature will test both booting instances from
volumes and from images downloaded to hypervisor local storage, so it
makes very little sense to me to attempt to limit the environment
tempest runs against to allow only boot from volume and then expect to
be able to run tests that spawn instances from images.

 max_local_block_devices set to 0 does not mean that nova will
automatically convert --images to volumes and boot instances from
volumes - it just means that all request that attempt to create a local
disk will fail.

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

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

Title:
  Option to boot VM only from volume is not available

Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  New

Bug description:
  Issue:
  When service provider wants to use only boot from volume option for booting a server then the integration tests fails. No option in Tempest to use only boot from volume for booting the server.

  Expected :

  a parameter in Tempest.conf for option of boot_from_volume_only for
  all the tests except for image tests.

  
  $ nova boot --flavor FLAVOR_ID [--image IMAGE_ID] / [ --boot-volume BOOTABLE_VOLUME]

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