yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

The description of this option is confusing:

https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.block_device_allocate_retries

"Number of times to retry block device allocation on failures. Starting
with Liberty, Cinder can use image volume cache. This may help with
block device allocation performance. Look at the cinder
image_volume_cache_enabled configuration option."

The "on failures" part doesn't make sense. The option is used during
boot from volume where nova-compute is waiting for volumes it created to
be "available" before attaching them to the server.

The mention of Liberty can also probably go away and just link to the
cinder docs:

https://docs.openstack.org/cinder/latest/admin/blockstorage-image-
volume-cache.html

It should also mention the related
block_device_allocate_retries_interval option.

Following up, a min=0 value could be added so the code doesn't need to
handle values less than 0.

** Affects: nova
     Importance: Low
     Assignee: Matt Riedemann (mriedem)
         Status: In Progress


** Tags: config docs volumes

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

Title:
  block_device_allocate_retries help needs work

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The description of this option is confusing:

  https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.block_device_allocate_retries

  "Number of times to retry block device allocation on failures.
  Starting with Liberty, Cinder can use image volume cache. This may
  help with block device allocation performance. Look at the cinder
  image_volume_cache_enabled configuration option."

  The "on failures" part doesn't make sense. The option is used during
  boot from volume where nova-compute is waiting for volumes it created
  to be "available" before attaching them to the server.

  The mention of Liberty can also probably go away and just link to the
  cinder docs:

  https://docs.openstack.org/cinder/latest/admin/blockstorage-image-
  volume-cache.html

  It should also mention the related
  block_device_allocate_retries_interval option.

  Following up, a min=0 value could be added so the code doesn't need to
  handle values less than 0.

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