bfe52542f5
This patch is making the Nova ironic driver to try to unprovision the node even if it's in DEPLOYING state. Current Ironic will not accept aborting the deployment when it's in DEPLOYING state but with the retry mechanism it may work once the state is moved to ACTIVE or DEPLOYWAIT. Prior to this patch the logic was to not even try to unprovision the node if it's in DEPLOYING and just go ahead and clean the instance but that behavior is dangerous and could leave orphan active instances in Ironic. With this patch at least if the unprovision fails in Ironic we can make sure that the instance won't be deleted from Nova. The tests for the destroy() method were refactored to extend testing destroy() being called with all provision state methods in Ironic instead of picking certain ones; A helper function was created to avoid code duplication on the tests. Partial-Bug: #1477490 Change-Id: I227eac73a9043dc242b7a0908bc27b628b830c3c
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