0facd1f89e
Cinder change I03f8cae05cc117e14f7482115de685fc9f3fa54a sets the 'encrypted' key for all cinder volume drivers connection_info. When run through the encrypted volume tests in Tempest, this hits the encryption providers in Nova that fail for certain types of volume drivers, like file system and fibre channel, due to the rootwrap filter not matching. This change updates the symbolic link rootwrap filter so it works with file system and fibre channel type volume backends rather than just iSCSI. The /dev/mapper/ prefix is always set in the encryptor modules, so that can remain as before. The symbolic link path is a complete wildcard, however, because the file system volume backends all have a configurable option for the mount path prefix, which defaults to $state_path/mnt but may not be that value. An example call for NFS: ln --symbolic --force \ /dev/mapper/volume-f5684ecc-959f-4de8-8d62-a8adf4bdb4cc \ /opt/stack/data/nova/mnt/21dd48babac42ae884d1192b8697a041/\ volume-f5684ecc-959f-4de8-8d62-a8adf4bdb4cc An example call for fibre channel: ln --symbolic --force \ /dev/mapper/pci-0000:06:00.0-fc-0x5006016508603f9f-lun-151 \ /dev/disk/by-path/pci-0000:06:00.0-fc-0x5006016508603f9f-lun-151 This change also updates the sg_info and sgscan entries to reference the correct module since those are not called from nova.virt.libvirt.volume anymore. Closes-Bug: #1470142 Related-Bug: #1440227 Change-Id: I181b594a3119f7ad74c595fc7059d521079b1d74 |
||
|---|---|---|
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| nova | ||
| plugins/xenserver | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| openstack-common.conf | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements-py3.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast