ff4a290f05
There is a reno bug (https://review.openstack.org/#/c/293078/) that leaves reno files to be shown as release notes even if the file was deleted later. This change aims to reintroduce a couple of reno files but emptied in order to remove their previous content from the HTML output. This is a workaround and those empty YAML files will be deleted once the latest reno version is having the bugfix. * Change I11bde778e9fe1f3a70d9fac213b40f05f07e7e47 was removing lock_policy * Change Ic9f70dae037d32980a5a252bdd08eff02ba27120 was removing a filter * Change I817b8d0f6c6fa71dc56b031c717bd7a63193f847 was removing report opts There was one last revert, but it has already been fixed in I1535aff80850fa3666da739133fc43e8579aa19b Change-Id: I945ded1eceeac49f50a5fff7ebece040f8c8b632
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