cf73bff104
The docs on create a volume-backed server from the command line were wrong in a few ways: * The openstack server create command does not currently allow booting from a volume where a source image is provided and nova creates the volume from the image and uses that volume as the root disk. The nova boot command supports that, so the docs are updated to call out the nova boot command since that is the appropriate command in this case (even the syntax with the openstack server create --block-device was wrong). * When creating a server from a bootable volume with the OSC CLI, either the --volume or --block-device options should be used for a single volume, but not both. The docs were using both, so the latter is dropped and a note is added which links to the CLI documentation for more details on --block-device option usage. Conflicts: doc/source/user/launch-instance-from-volume.rst NOTE(amodi): The conflict is due to not having Ifa2e2bbb4c5f51f13d1a5832bd7dbf9f690fcad7 in Pike Change-Id: I985b870759d6c21ef9357b04f39099c02354f135 Closes-Bug: #1794827 (cherry picked from commit |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref/source | ||
playbooks/legacy | ||
plugins/xenserver | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-functional-py3.txt | ||
tests-py3.txt | ||
tox.ini |
README.rst
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
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
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: