Matt RiedemannandSean Dague
f2c1cfae53
In Id7936be290b6febd18deb4c2db8ea4d678d4d9b1 and I8bf7cbaa7015bb61656ab90ccc8f944aaeebb095 parts of the ec2 infrastructure were removed that had been deprecated and warned about in Liberty. However, changes were made to the metadata server in these changes as well, none of which had been warned about, and arguably should not be removed ever. The metadata server is an AWS construct, and given the implementation order of APIs in Nova (ec2 was the first API) it shares code with the ec2 base classes. But it's the ec2 API we were deprecating out and deleting. Removing these breaks anyone upgrading using the metadata server, as was seen by the neutron multinode job. In addition, paste filters should *never* return a response code directly. Doing so means they block processing the rest of the pipeline. Which means that the deprecation approach that was used here actually forcably broke anyone with existing deploys. Change-Id: I22eb3a3fcd8e74a1d9085acde15c25a927ae12cb Closes-Bug: #1545101
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