15aa6f116d
This patch introduces a few new baremetal states, which are used to track the deploy process. Now, nova-baremetal-deploy-helper updates the bm_nodes record directly when it begins and finishes deploying an image to that node. The next patch will add a LoopingCall inside driver.spawn() to wait for the deploy to complete. Also, since there can not be >1 active deployment per node, there is no need to have a separate table for storing them. This patch drops the table bm_deployments and adds the important information it contained to bm_nodes. Since the previous behavior was to mark a deployment as deleted once it completed, there is no need to copy any data from bm_deployments prior to dropping the table -- assuming that no active deployments are in process when the migration is run. Since this is the first migration for the baremetal database, it also adds a new test class, TestBaremetalMigrations, and refactors the test_migrations.py file to allow for multiple test classes. partially implements fix for bug 1096723 Change-Id: Iad30b462d49c88fc19babed43a2fb8540b1fad30
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:
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:
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