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

Implements blueprint record-reason-for-disabling-service
We added a field to the service table to log a reason when a service has
been disabled.
We added a new API extension called os-extended-services. The new extension
will extend the os-services extension adding:
- A method for disabling a service and specify a reason for that.
PUT /v2/{tenant_id}/os-services/disable-log-reason
When the os-extended-extension is loaded the call:
GET /V2/{tenant_id}/os-services
will return the list of services with reason information it that exists.
DocImpact
Change-Id: I87a4affc45160796ff11c7b03e591e6aba73d62a

Change-Id: Ib268a66f5e17a7b96bed6a0d4e328f69c5481928

Previously if adding a security group to an instance it would fail
if the port did not contain port_security_enabled=True. This patch
also changes the unit tests so that networks by default are not
associated with port_security_enabled=True because this is only true
if a plugin is running the port_security extension.
Fixes bug 1189059
Change-Id: Ieebb7aafba01c18164b86a01a3c289a6957321e4

Second step in removing references to instance_types. Remove all
references to instance_type in nova.compute.flavors.
Also update compute devref to reflect changed name.
Partially implements bp flavor-instance-type-dedup
renamed: nova/tests/test_instance_types.py -> test_flavors.py
Change-Id: I7413bf832c61d04ab90ec8b1370d3f01372c4172

It is possible to use the agent, cloud-init and config drive
together on a single server. In this case we should still
be injecting the instance metadata.
The current code is inconsistent between spawn and migrations.
The correct approach is to always inject the data into xenstore.
fixes bug 1188618
Change-Id: I253b34234544cff353985a5b53ec084ea332535a

DB support for blueprint instance-group-api-extension
Change-Id: I615af9826ef61fd63d4cd8017908f943969bf177

Fixes Bug 1160078
Change-Id: Ic4d7ee0202ca15837f9dcab97e5502cbf82aa16f

This patch makes every boot create a block device mapping if the
instance was started with an image.
These block devices are not used anywhere at the moment but will be used
in the future as part of a more flexible block device API.
This patch also makes sure they are deleted once the instance is deleted
as well.
Change-Id: Ia89d531be71c460f1f82fcfce34b270639a23061
blueprint: improve-block-device-handling

This patch migrates the DB to the new data format. In addition it also
utilizes routines introduced in the change
I9370333059b8c9aaf92010470b8475a913d329b2 in a way that will allow us
to transition into using the new data in Nova logic one step at a time.
This is accomplished in a following manner in the DB/conductor layer,
which is supposed to allow for subsequent changes to be as granular as
possible:
* Read operations - data is always read as is found in the DB - meaning
in the new format, and transformed after every call. This will allow us
to make granular changes in the API/Compute layers.
* Data is converted inside the DB methods that do writes, and an
additional 'legacy' flag is added (set to True by default). It is up to
the calling method to make sure it supplies the DB layer with the format
it is intending to write, to avoid guessing.
An exception to the above is when using conductor due to rpcapi
versioning, so this patch adds a 'legacy' flag to the
block_device_mapping_get_all_by_instance conductor method and bumps the
version of the API.
This patch also fixes some of the block device fixtures in tests, when it was
required to be aware of the new data structure (mostly when mocking DB
methods that return the new data format).
This patch is not supposed to provide any new functionality to Nova.
blueprint: improve-block-device-handling
Change-Id: If30afdb59d4c4268b97d3d10270df2cc729a0c4c

This fixes an issue where not all of the LUNs are seen
by the kernel at attach time, but later become available.
We now rescan the list of devices seen by multipath at
detach time.
Also added another unit test case.
Fixes Bug: #1175366
Change-Id: Id5b313b17454ec32672373b7b564b9450466b7a2

Change-Id: Ifdb8136d1b90f5a2e1d37067fd33f75f2042f81f

There was no tests in test_db_api for s3_image_*
methods.
Add tests to ensure that all works.
blueprint db-api-tests
Change-Id: I906025f4c5178b26c222fb28d5c3b220e00ae79c

When there's 2 options with the same name, the script gets confused and
doesn't know in which group it goes. This fixes it, and fixes also the
template generation which is broken for various reasons:
- gettext.install was missing
- nova-rootwrap when imported calls exit() because it doesn't find a valid
 configuration file, so let's exclude it entirely anyway
- eventlet/greendns needs to be ignored for this
Change-Id: Iaa4e9a806e79032ce1675b46a6b7a7628c3eff89
Signed-off-by: Julien Danjou <julien@danjou.info>

Used inheritance to avoid logic duplication in conductor.api classes
Fixes: bug #1188577
Change-Id: Id0bedb974354177dc3c6f6562e836924bcaafb08

blueprint db-api-tests
Change-Id: I2fcfc50824de8965fe8521cde5f20d24e88eb8ae

DB models definition should be up-to-date with DB schema obtained after applying of
migrations. Currently, there are no tests enforcing this and it's really hard to
analyze what indexes should be added, and what indexes we have at the moment.
So the first step is it to fix all models, and add missing descriptions about
Indexes and UniqueConstraints in __table_args__ and use explicit 'nullable'
parameter in columns description.
Add missing 'nullable' parameters to all Columns
Add empty __table_args__ parameter to Table
There is no indexes and no unique constraints in this table at this moment.
blueprint db-sync-models-with-migrations
Change-Id: I9b31e8976f514e370d6b46076b469fe5e5c8e0f1