
This is a bus for all reno problems we see with the relnotes : * Change Id25bd4870c6e2fda08dc0177b7ed61a8a6091838 was having a formatting problem with not retaining the newlines, and also was mentioning "Nove" :-) * Change I43ddc5164f88fb049fe49ad4672fbf09b2b1987e was using a prelude section that is not needed because we will provide a general prelude section (and commenting that) in the next change. * Change I2dba71e71b1ed7cf8476e8bfe9481e84be5df128 was incorrectly using the upgrades section while it was a deprecation. * Change Ia6f1d8f9c7d700498b6441a6ba37fa25b2611ef8 is no longer valid because Id7936be290b6febd18deb4c2db8ea4d678d4d9b1 has been merged during Mitaka too. * Change I2465e1bee618a552132d659014ea96cdbda161d6 was reverting a reno file but due to a reno bug (see https://review.openstack.org/#/c/293078/), the release note is still kept in the output. Consequently, the workaround I found is to reintroduce the same reno file with an empty content to drop the previous content. Note that I used the prelude section for "dropping" notes, that prevents us to provide empty bullets for upgrade or features sections. Change-Id: I1535aff80850fa3666da739133fc43e8579aa19b
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