14cf5454fb
1) Child cell scheduling fails. The change to use Instance.create() in child cells broke things. The instance properties was being overwritten due to a typo. I also found a number of other things that need to be popped out before passing to create_db_entry_for_new_instance(). 2) Notification to the API cell was failing. We cannot pass an object to instance_update_at_top(). 3) When cells is enabled, deleting an instance hits the '_local_delete' part of code in the API because we don't see the compute node. There's a trap in cells_api.py to forward the delete on to child cells, but we need to make sure not to try to deallocate network in the API cell. Fixes bug 1216113 Change-Id: Ie989c22cb3b6a1359a0540e60e06fa4153e93476
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
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