2cf846e1e7
Following objects were added: * CpuDiagnostics * NicDiagnostics * DiskDiagnostics * MemoryDiagnostics * Diagnostics These objects will be used to transmit data via RPC. They are based on same objects from nova.virt.diagnostics. But old objects were used only for storing data. During RPC transmission they are transform into dictionaries. It is not right approach. We will have some problems in case of adding new diagnostics fields. New nova objects will allow us to have a good control of objects versioning. It will force contributors to dump objects version in case of any changes. Also some new fields were added/modified to be in accordance with updated diagnostic spec Ibcc2b98ae5b3731a9e5a1a3f28fc7ce4655c8ea6 blueprint: restore-vm-diagnostics Change-Id: I6b15001e6f4e649df983071464ec8642bfc89b61
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:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://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:
https://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: