4bd8a4bd8e
Currently it is not possible to override an existing image block device by supplying the device with the same name at boot (see also Ib1ba130042aabbbe7bb8d60fc212c66e446c1d73). Even though we want to discourage usage of device names as much as possible in the Nova API (as not all hypervisors can honour them), EC2 API requires that this is possible. While we want to make sure we document that supplying device names at boot is only really desirable if you want to override some of the ones contained in the image, introducing a different labeling system just so that we don't use the device names seems like an overkill for a feature that does not seem to be very used. This patch adds a method that will do this deterministically when compiling all the block device information for the request. It is also worth noting that The EC2 API allows only subset of block device attributes to be overridden in this way (see [1]). This limitation did not exist previously in Nova, and there seems to be no reason why we would need that complexity, so it would be up to the EC2 compatibility code to deal with this. [1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html#Using_OverridingAMIBDM Doc-Impact Closes-bug: #1370250 Change-Id: I60ecdcae81ff5dec34f0fa0a39e0739759a6fa59 |
||
|---|---|---|
| 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 | ||
| bandit.yaml | ||
| openstack-common.conf | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| 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