646151ff1b
In virtuozzo 7 we have changed disk bus from sata to scsi. Sata is not supported in virtuozzo 7. We don't need to support sata bus for virtuozzo in nova. Virtuozzo 6 may work with python 2.6 only and it's not possible to run upstream nova on virtuozzo 6. We always use this patch in our internal infrastructure to run openstack on virtuozzo 7. Also in this patch we have changed tests for hypervisor version. We don't need to check libvirt version in case of Virtuozzo hypervisor. Because Virtuozzo 7 always has libvirt with support of 'parallels' virt type. Docs have already been updated: If3d2f402bb1b21bec360693a6c1e9d73e998d167 Change-Id: If3d5e39bd745c0df74316a90159fffb3221864cc
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: