414bdd21cd
This is the second patch set in a series refactoring code that uses ResourceTracker.compute_node so that it can later be changed to be a ComputeNode object. Note that in this patch compute_node is still a dict. The methods that calculate resource usage in the ResourceTracker take a parameter called (variously) resources, values or stats. Sometimes these are called passing self.compute_node as the value for this parameter and sometimes a dict data structure obtained from the virt driver by the get_available_resources() method. The result of the changes are always copied into the self.compute_node. This mixing of data structures won't work if self.compute_node is converted to be a ComputeNode object instead of a dict. The previous patch in this series initialises self.compute_node at the start of _update_available_resources() so it has a value at the outset. This patch copies the resources data into self.compute_node and uses only that data structure in the methods that calculate resource usage. As a consequence it is no longer necessary to pass this in as a parameter in those methods or to copy the result into self.compute_node at the end of the calculations. This step will allow us, in following patches, to convert the code in the update methods to object notiation when self.compute_node is changed to be an object instread of a dict. Minor changes included are removal the final copy into compute_node and moving initialisation of the stats plugin into _init_compute_node(). Change-Id: Ia79b34aa9e6aad5cabe63bb7545c545b952b2b3a
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