891abdff2f
* When execute `nvme connect`, "host-nqn" is needed in RSD environment. So add it as an optional parameter. * It is observed that the first `nvme list` can miss the newly connected nvme device, right after a success call of `nvme connect`. The solution is to add the retry&sleep logic back. * Sometimes there can be more than 10 nvme devices, e.g. "/dev/nvme10n10". Need to update the device re pattern. * In RSD environment, the connector needs additional information like "system uuid", to let cinder-volume know the nova-cpu service is running on which RSD node. * Add a new protocol "NVMEOF" mapping to allow both Cinder and Nova to identify and use the nvme connector. Implements: blueprint nvme-volume-driver Change-Id: I26e3dc140b2cf30a97665679fdc4d2f897cd4872
Team and repository tags
brick
OpenStack Cinder brick library for managing local volume attaches
Features
- Discovery of volumes being attached to a host for many transport protocols.
- Removal of volumes from a host.
Hacking
Hacking on brick requires python-gdbm (for Debian derived distributions), Python 2.7 and Python 3.4. A recent tox is required, as is a recent virtualenv (13.1.0 or newer).
If "tox -e py34" fails with the error "db type could not be determined", remove the .testrepository/ directory and then run "tox -e py34".
- For any other information, refer to the developer documents:
- OR refer to the parent project, Cinder:
- Release notes for the project can be found at:
- License: Apache License, Version 2.0
- Source: https://git.openstack.org/cgit/openstack/os-brick
- Bugs: https://bugs.launchpad.net/os-brick