openstack/nova - nova - OpenDev: Free Software Needs Free Tools

Moves the lock/unlock server functionality out of admin_actions into
its own extension. This part of the larger
blueprint v3-api-admin-actions-split allows more selective enablement of
features contained in the admin actions extension.
Some setup work is done in the tests directory with an
admin_only_action_common.py file. This allows tests which are
split out from test_admin_actions (as their corresponding features
are separated from the admin_actions extension) can continue to
share code.
Note that XML api samples are no longer generated because
bp remove-v3-xml-api has been approved.
Partially implements bp v3-api-admin-actions-split
DocImpact: Adds os-lock-server extension and moves lock/unlock
functionality out of os-admin-actions into this new extension
Change-Id: Ie4b6e856c2f5c33de5575aa8666e0b2784b58d05

The method _generate_key_id was duplicated in
nova/keymgr/mock_key_mgr.py
This patchset removes one of the duplicates.
Change-Id: Idb30fca9d392fe5f5b4063ba1b22a967329987f6

This adds a warning log message to the administrators about libvirt
driver configurations that are not tested upstream. Things like
libvirt-lxc, libvirt-uml, and non-intel KVM architectures are the
primary target of this warning.
Change-Id: I17ee1e3c07510382254f45d99f557b227ac8470c

This adds a log message during the docker driver host init phase to
warn administrators that the driver currently does not meet the
requirements set out in:
https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan
Per the timeline above, this warning is being added in the Icehouse-2
milestone phase as a warning to anyone using it in the event that
the requirements are not met. While progress is being made towards
meeting the requirements, there is no visible indication that the
goal will be met. If it is, this is an easy revert.
Change-Id: I39318ed6544c77b4aa0f4614c16bc14a93734bf6

Removes the entry points defined in setup.cfg for
the V3 API XML. These are no longer called.
Partially implements blueprint remove-v3-xml-api
Change-Id: I1fd516b5a01f1ce2b4d42320594616a49b66952d

Removes all XML support from the V3 API admin_password
plugin.
Partially implements blueprint remove-v3-xml-api
Change-Id: Ib45a04d34704bc259ef6e457d6dfb6f79c929edf
DocImpact: XML no longer suported for the admin_password plugin

This patch removes XML support from certificates v3 API.
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: If34053c1dce851dc6b3fd2bd1b8ebd03849bae53

Remove XML support from the following v3 compute API plugins:
 - config_drive
 - services
 - simple_tenant_usage
 - versions
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: I58a29974253a5acfb04f42cf4712ba290203cb5a

Remove XML support from the following v3 compute API plugins:
 - extended_server_attributes
 - extended_status
 - extended_volumes
 - extension_info
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: I4f3785fbdac7257370458a3bdd859d46ef83f415

Remove XML support from the following v3 compute API plugins:
 - security_groups
 - server_diagnostics
 - server_metadata
 - server_password
 - server_usage
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: If3e8d82d6db2a2ff328ba477bffd5081f098be9a

Remove XML support from the following v3 compute API plugins:
 - quota_classes
 - quota_sets
 - scheduler_hints
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: I3ce2bcb1a7d7e152b0bfb96316ce8f1aab10061d

Remove XML support from the following v3 compute API plugins:
 - flavor_access
 - flavor_manage
 - flavor_rxtx
 - flavors
 - flavors_extraspecs
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: I9745285cb6053dcb634c23002f1f24412dc62021

This reverts commit 2593469103
This is a possible cause for bug #1273556
Change-Id: I675806a21bd2e2ab438913690438b2d25b145f7c

Remove XML support from the following v3 compute API plugins:
 - hosts
 - hypervisors
 - instance_actions
 - ips
 - keypairs
Part of blueprint remove-v3-xml-api
DocImpact
Change-Id: I49da82632c884cdac36ee37674a4d0fc360fdd83

Removes some trace bits of XML test classes
from the unitests
Part of blueprint remove-v3-xml-api
Change-Id: I8d87cc1e3331c5ea135702ae4e03788ff2841642

this change is the beginning of the tear down of the xml v3 code.
removing xml from servers.py and still passing unit tests means
that we're done with the unit test tear down we need, as nothing
can be touching xml anywhere, as the root controller is no longer
there.
one additional test had to be removed to make this pass.
Part of blueprint remove-v3-xml-api
Change-Id: I7f04255ecc91f2aba045dc0c38992bc6d8a5b82a

Remove a bunch of unit tests for XML support in v3 compute API plugins.
This is another step towarding removing XML support completely from this
API.
Part of blueprint remove-v3-xml-api
Change-Id: Ibc35791cd8593b523ff21d9f604d0263e6da2b0a

This is a step toward removing XML support from the v3 compute API.
First, we need to remove all of the tests that would fail once we start
ripping out the real code.
Part of blueprint remove-v3-xml-api
Change-Id: Ie2c280d5ea1e6b8756535deb05982a92561552db

Patch adds a module for manipulating dmcrypt devices.
Implements: blueprint encrypt-ephemeral-storage
Change-Id: I308b9f26c382b332c02f13aa1d5f0a830e9ef277

Patch adds a field to instance for storing the uuid of
the key used to encrypt instance's ephemeral storage.
Implements: blueprint encrypt-ephemeral-storage
Change-Id: Id5b1e272d4461875bb231839e4714d3ed0899d3f

Docker has named container since 0.7. In order to make it easier for the
admin to troubleshoot and find container set the container name to the nova
instance UUID. Addtional the name is prefixed with nova.
Example: nova-d7553842-2424-4471-98a7-92a1db70033b
DocImpact - Docker driver requires Docker 0.7 or newer.
Change-Id: I4f12734663e726b08f53400fdfcfb8d31401490d
Blueprint:
https://blueprints.launchpad.net/nova/+spec/docker-name-instance-id 

Currently the driver includes all hosts connected to VC
(including disconnected hosts) when calculating available
vcpus. The patch enforces that the reported available stats
only include resources of hosts that are connected to the
VC.
Note: A host can be connected to a VC, but have a disconnected
host state
Change-Id: Iba9d80f894cc2b7471a7f9c87b7367fd93bacb48
Closes-Bug: 1257998

The method extend does not log any information if there is a
problem during the resize with "resize2fs".
This patch refactor extend and adds missing tests.
Change-Id: I81079a79e0449381440f202f6143b48f96453a11
Related-Bug: #1270086 

This makes nova-network manager use the Network.create() method
to do the work of creating networks. It also makes the rpcapi
use the NovaObjectSerializer since this is the first change that
makes nova-network return or take an object via RPC.
Related to blueprint nova-network-objects
Change-Id: Ida9a05ac249ff168075f87e5dbdad6bc23e69561

This makes base.obj_to_primitive() handle netaddr.IPAddress() and
netaddr.IPNetwork() objects so that they properly become strings
in the primitive format, which provides compatibility with existing
network dicts.
Related to blueprint nova-network-objects
Change-Id: I098d775a2a792073b2777495d665846f399ecf3e

This adds a Network object to provide services and modeling
for nova-network and its use of the current SQLAlchemy Network
model.
Related to blueprint nova-network-objects
Change-Id: I7f943cda32fc98b3b03cdbb5d68e0c741053afaa

Right now, service workers can race to create their service record
in the database. This makes a NotFound...Exists pattern not fail
when the service record shows up due to a successful sibling.
Change-Id: I3e912beeb953c85189f44171d958e9402abc01ae

the previous mocks made some very specific assumptions about the
behavior of an internal private method in stevedore, which changed
in 0.14. Make the mocks more flexible so they work regardless.
Change-Id: I5063c652c705fd512f90ff3897a4c590f7ba7c02

We've had a number of gating failures resulting from
attach failures. Looking through past gate logs it
seems we've had a pretty wide variance in how long it
takes the actual iscsi attach and mount to complete
before being available in dev/disk-by-id.
This patch simply bumps the retry count from 3 to 5,
the result will be going from a max of 14 seconds to wait
for attach to 55 seconds total before failing.
Change-Id: Ib46da71c964da977471cc6635adc5d92ff3beb9c
Closes-Bug: 1270608

Compacts the pre-Icehouse database migrations into a
single migration (216_havana.py).
Pre-Icehouse users will now need to upgrade to Havana before
running any Icehouse migrations.
Tested on MySQL and PostgreSQL schemas on Fedora 19 to ensure the
new compacted migration generates an identical schema to the
previous migrate scripts in Havana.
Specific changes include:
 1) Add aggregate metadata unique constraint.
 2) Fix migrations index (add deleted column).
 3) Add pci_devices table.
 4) fix migrations_instance_uuid_and_status_idx index.
Implements: blueprint compact-havana-db-migrations
Change-Id: Id96e13b0ed65837761bd173c9e32ebcc1ff5f376

Compacts the pre-Icehouse database migrations <= 210 into a
single migration (210_havana.py).
Pre-Icehouse users will now need to upgrade to Havana before
running any Icehouse migrations.
Tested on MySQL and PostgreSQL schemas on Fedora 19 to ensure the
new compacted migration generates an identical schema to the
previous migrate scripts in Havana.
Specific changes include:
 1) Add more indexes for SQLite DB (per 201).
 2) Add unique constraint on instance_type_extra_specs.
 3) Add project_user_quotas, indexes, and constraints.
 4) Add indexes to reservations.
 5) Add locked by to instances.
 6) Add cleaned column to instances.
 7) Add host_ip/supported_instances to compute_nodes.
 8) Add missing Fkeys.
 9) Fix project_user_quotas_user_id_deleted index.
Implements: blueprint compact-havana-db-migrations
Change-Id: I63e00cd29eb4c26717b5ebd7a1ff11a01c0085de

Compacts the pre-Icehouse database migrations <= 200 into a
single migration (200_havana.py).
Pre-Icehouse users will now need to upgrade to Havana before
running any Icehouse migrations.
Tested on MySQL and PostgreSQL schemas on Fedora 19 to ensure the
new compacted migration generates an identical schema to the
previous migrate scripts in Havana.
Specific changes include:
 1) Add unique constraint on quotas.
 2) cleanup virtual_interfaces unique constraints
 3) Remove a bunch of volume tables (cinder cleanup)
 4) Indexes cleanup per 194_fix_152_migration_indexes.py
 5) Add unique constraint on fixed_ips.address.
 6) Add unique constraint on services columns.
 7) Add unique constraint on agent_builds columns.
 8) Add unique constraint on console_pools columns.
 9) Add unique constraint on aggregate_hosts columns.
 10) Add transport_url column to cells. (removes RPC columns)
Implements: blueprint compact-havana-db-migrations
Change-Id: Ie14e9e5de6d7d43ebabfc4680ed6434d08ecee49

Compacts the pre-Icehouse database migrations <= 190 into a
single migration (190_havana.py).
Pre-Icehouse users will now need to upgrade to Havana before
running any Icehouse migrations.
Tested on MySQL and PostgreSQL schemas on Fedora 19 to ensure the
new compacted migration generates an identical schema to the
previous migrate scripts in Havana.
Specific changes include:
 1) Drop migrations 181 - 184 which synced up shadow table changes.
 We now accomodate these changes in the base migration.
 2) Rename unique contraints per 185_rename_unique_constraints.py
 3) Add a new BDM table format.
 4) Add instance groups tables.
 5) add reason column to service
 6) add cells unique constraint
 7) add security groups unique constraint
Change-Id: Ibf2289f37c2376f3bd564728db5400859523c619
Implements: blueprint compact-havana-db-migrations