← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1393408] Re: hardcoded block device path for NBD server

 

I don't think this is a bug, nor a hardcoded openstack specific value. This is how linux implements sysFS. If nbd module is loaded, a sysfs entry will exist in /sys/block/nbd0
https://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf

** 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/1393408

Title:
  hardcoded block device path for NBD server

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  Nova uses hardcoded block device path for NBD server.
  See: https://github.com/openstack/nova/blob/master/nova/virt/disk/mount/nbd.py#L63

  For example, as deployer i want to pick my own path to NBD storage,
  but it's hardcoded. And not clear (no documentation) where should NBD
  storage be.

  Proper solution is to propose new configuration opt:
  Name: nbd_storage_path
  Type: String
  Default: /sys/blocl/nbd1

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


References