Dan Smith
0daebe7272
Going forward with the early stages of no-db-compute, we will consistently hit cases where we need to eject some database usage from one virt driver up a few layers. Since those are not commonly used by all, some way of determining (and the higher layer) the properties of the virt driver being used will be useful. We have discussed using something like a mixin interface class and multiple inheritance. We have discussed tricks like detecting if the manage_image_cache() method has been overridden. We have discussed trying it once and catching NotImplementedError and then never trying again. Aside from the first, none of these are unsneaky enough to bite us later. This approach will provide us a way to declare such properties succinctly in the compute driver to help the higher layers know what we want them to do on our behalf. Change-Id: I74dea9322a5b4688319ebf5d9afe416e93401c58
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 <http://twitter.com/openstack>`_ on Twitter. To learn how to deploy OpenStack Nova, consult the documentation available online at: http://docs.openstack.org 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: http://bugs.launchpad.net/nova 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: http://github.com/openstack/nova Developers should also join the discussion on the mailing list, at: https://lists.launchpad.net/openstack/ 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: http://nova.openstack.org/ Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at: http://wiki.openstack.org/GerritWorkflow -- End of broadcast