b1298cc990
There is a nova.virt.VIFDriver class which the hypervisor VIF drivers inherit from. None of the hypervisor subclasses pay any attention to the API contract defined to the parent class. Some of the hypervisors don't bother trying to use the VIFDriver class at all (hyperv, baremetal). It is not worth trying to make the hypervisor subclasses follow the same API contract, since the base parent class offers no re-usable functionality of its own. The hypervisor base classs nova.virt.ComputeDriver also has no need for the VIFDriver API to exist, since its integration point is the 'plug_vifs' method. As such the nova.virt.VIFDriver class serves no purpose other than to mislead reviewers into thinking there is a common API where none actually exists. It should thus be deleted Change-Id: Id287f7e66143a248a5f106e010510a3f09d2b1e7 Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
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:
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:
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