e619354f7c
The mentality of being able to continuously deliver nova has been around since the beginning with Rackspace public cloud trying to CD openstack as close to master as possible. This has implications for how code series are structured, reviewed and merged. For the most part this seems to be tribal knowledge and we don't have anything very obvious in the nova docs about it, and not all projects in openstack necessarily subscribe to this mentality anymore, or do so grudgingly, but it's worth documenting it in nova while still applied here. Change-Id: Ieff87dbd748318f1b7f879a136ff25081dac321e
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: