6a7b7a3a78
The OpenStack os-brick library uses hardcoded paths to binary files to interact with the VxFlexOS SDC. This leads to problems when using containerized OpenStack (Kolla & Red Hat). Due to the fact that VxFlexOS SDC binary files has to be used inside containers (nova, cinder, etc.) the overcloud deployment must be performed in 3 stages: 1) deploy overcloud without additional volume mounts 2) install the VxFlexOS client on the controller and compute nodes 3) update overcloud with additional volume mounts Using these changes overcloud can be deployed without update step after initial deployment since os-brick does not have external dependencies and uses python built-in libraries. The scini device through which the VxFlexOS client interacts is presented in the containers by default because /dev directory from the host is mounted in all containers. Change-Id: Ifc4dee0a51bafd6aa9865ec66c46c10087daa667 Closes-Bug: #1846483 (cherry picked from commit 2d694361fe66736c59ca96a2a54c368638445de6)
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://opendev.org/openstack/os-brick
- Bugs: https://bugs.launchpad.net/os-brick