
The request spec that is used for scheduling the instance should be persisted early in the boot process. This is to support cellsv2 where the instance is not going to be created in the db until scheduling has occurred. The persisted request spec is one of the pieces needed to respond to api list/show requests for unscheduled instances. The persisted request spec will also be used by resize/migration/live-migrate operations to ensure that the instance is scheduled to a host that fulfills the same constraints as the current host. Because there are a lot of tests that execute the boot path and are backed by a database a new fixture was added to test.TestCase to instantiate the api db if USE_DB is true. With this change the api db will be more frequently needed. NB: The request spec will not be persisted within a v1 cell and therefore not be available for later resize/migration operations when using cellsv1. Finally, a releasenote is being added explaining that the nova_api database needs to be setup at this point. RequestSpec.create() is the first piece of code, outside of nova-manage commands, that uses the api database. Partially-implements: bp cells-scheduling-interaction Change-Id: Idd4bbbe8eea68b9e538fa1567efd304e9115a02a
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