f8a81807e0
Update the documents, making the following changes: * Reference Fedora 24 instead of the outdated Fedora 21 * Don't reference the removed 'rejoin-stack' script * Let devstack do as much work for us as possible (NUMATopologyFilter) * Don't overcomplicate anything (installing emacs, using non-standard devstack install dir) * Use '$' prefix for non-root commands * Update XML with latest examples * Use the 'openstack' client, rather than the 'nova' client * Random formatting fixes ...and, finally, stop hating on poor, innocent vi. Change-Id: Idc89a5c0617ccf7044e1cfc2b5d7f5ff4004b5bf
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 and OpenStack Ironic.
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.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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: