
There are a couple of issues with the test: 1. It doesn't consider both hosts from the two compute services during scheduling. 2. There is a race where sometimes claims.Claim.__init__ won't be called because if the RT instance_claim runs before update_available_resource has run, it will create a claims.NopClaim instead. This adds the RetryFilter to enabled_filters, adds set_nodes() calls to set the nodenames of each compute service to match its host, resulting in consideration of both hosts for scheduling, and stubs resource_tracker.ResourceTracker.instance_claim instead of claims.Claim.__init__. Related-Bug: #1671648 Change-Id: I541c03a7960b8f135b005c43cb5c7bcb0b63b9ae
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
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.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
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: