This change set declares the nova.virt namespace per PEP420
(https://www.python.org/dev/peps/pep-0420/). This allows composing
nova.virt for drivers under test from separate packages.
Change-Id: I78c0ca85cb6ee2e370214a89a203f6f099748930
Partial-Bug: 1575335
According to policy change in HACKING:
http://docs.openstack.org/developer/hacking/#openstack-licensing
empty files should no longer contain copyright notices.
Please note, Oslo (nova/openstack/common) not changed!
Closes-bug: #1262424
Change-Id: I26b7d1eabb189f06219b70495d229389b9d3f260
We don't need to have the vi modelines in each source file,
it can be set in a user's vimrc if required.
Also a check is added to hacking to detect if they are re-added.
Change-Id: I347307a5145b2760c69085b6ca850d6a9137ffc6
Closes-Bug: #1229324
nova.compute and the hypervisor (i.e. libvirt).
compute.node is no longer coupled tightly with libvirt. Instead, hypervisor
connections are handled through a simple abstract interface. This has the
additional advantage that there is no need to riddle the code with
FLAGS.fake_libvirt checks, as we now have an interface behind which we can mock.
The libvirt-specific code, and the fakevirt code used for unit tests, have
moved into nova.virt.
The fake_libvirt flag has been replaced with a connection_type flag, that will
allow us to specify different connection types.
The disk image handling (S3 or local disk image fetch) has moved into
nova.virt.images, where it will be easier to share between connection types.
The power_state values (Instance.RUNNING etc) and the INSTANCE_TYPES dictionary
have moved into their own files (nova.compute.instance_types and
nova.compute.power_state) so that we can share them without mutual
dependencies between nova.compute.node and nova.virt.libvirt_conn.