1b5f9f8203
If 'connection' is set in the 'placement_database' conf group use that as the connection URL for the placement database. Otherwise if it is None, the default, then use the entire api_database conf group to configure a database connection. This works by: * adding a 'placement sync' and 'placement version' command to nova-manage * adding placement_migrations that that sync will run * adding a placement_database config group with the relevant database configuration settings * adding a placement_context_manager. If CONF.placement_database.connection is None this is the same as the api_context_manager, otherwise it is a new one from its own config * adjust nova/tests/fixtures to be aware of a 'placement' database and the placement_context_manager This version of this change differs from others by not requiring separate placement commands for migration, instead using existing tooling, which makes the size of the change a bit smaller and also addresses problems with the test fixtures needing to be too aware of what migration code to run. Now it runs the same code. This functionality is being provided to allow deployers to choose between establishing a new database now or requiring a migration later. The default is migration later. This is a modification of Id93cb93a0f4e8667c8e7848aa8cff1d994c2c364 and I3290e26d0a212911f8ef386418b9fa08c685380b. Change-Id: Ice03144376c9868c064e4393d531510615fc6fc1 Co-Authored-By: Chris Dent <cdent@anticdent.org> Partially-Implements: blueprint generic-resource-pools |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| nova | ||
| plugins/xenserver | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bandit.yaml | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
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