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

Add the following notifications when swapping volumes.
* instance.volume_swap.start
* instance.volume_swap.end
* instance.volume_swap.error
Change-Id: I84c1c536a6e5a94f22443b9fbc934aeed48e327a
Implements: blueprint add-swap-volume-notifications

Change-Id: If6386cdfda9c8f1048902318982cf4beb3c85042

This spec describe the deprecation of image-metadata API
APIImpact
Implement blueprint deprecate-image-meta-proxy-api
Change-Id: Ie532bfde231b783d7d0cfc3d76e2c3a8cace5831

This was introduced in Newton but didn't land any
changes, so re-proposed for Ocata.
blueprint cells-quota-api-db
Previously-approved: Newton
Change-Id: I0a29a4df368975699a1c42eacdbbb50d252423c7

This will provide a mechanism for the user to tag a device they
have assigned to their guest with a specific role. The tag will
be matched to the hardware address of the device and this mapping
exposed to the guest OS via metadata service/cloud-init
Spec for bp/virt-device-tagged-attach-detach
APIImpact
Previously-approved: Newton
Change-Id: Idcac1506b61c29f02e335200fb18d394243098e2

Previously-approved: Newton
Change-Id: I426e5f32ddb0737f393d78bbf24c83e811c0560f
Implements: blueprint hyperv-storage-qos

Previously-approved: Newton
Change-Id: Ib46ac5b3dfbb90adcdeda56e02865e62ef76ea0f
Implements: blueprint hyper-v-uefi-secureboot

This uses the mova-implemented-specs script to move
completed newton specs to the implemented directory
and populate the redirects file.
Change-Id: I0511f2c32f7fe85ace8d035b07342ce628491e1b

The filename of the spec should match the blueprint
in launchpad, this is what the move-implemented-specs
script works with and needs, and our template/review process
should enforce. This change fixes the newton specs that
had busted names and updates the redirects file to preserve
any links to the old names.
You can test this by running:
tox -r -e move-implemented-specs -- -n -v newton
And there won't be any warnings at the end.
Change-Id: I806bdebde1c5bf8e48dfdbf4813342a9c4de5ad3

This adds a script and tox target to automatically process and
move approved specs for a given release into the related implemented
directory for the same release. It uses launchpadlib to check the
status on the spec (blueprint) and only moves those that are
complete.
For example, to run this:
tox -r -e move-implemented-specs -- -n -v newton
Change-Id: Ib431f62101b90abecce86f60ba7acbba11e09533

Previously-approved: Newton
Change-Id: I03b7e801f8cf06465bd260fe8aade2e995882ac8
Implements: blueprint hyper-v-vnuma-enable

This feature adds the possibility to define a flavor,
that does not create any ephemeral disks locally on the hypervisor.
If the new flavor key 'local_disks' is set to 'False', users are
"forced" to create a bootable volume to launch an instance from
that flavor.
Change-Id: I428b26a88bb6df500ad4a3daab158875e59050be
Previously-Approved: Newton
Implements: blueprint flavor-root-disk-none

Because this spec didn't have a title it messed up the
links in the specs/newton/approved list in the docs.
Change-Id: I8a630592eecce88709d3adf35573911e0bdb3c1f
Closes-Bug: #1625322 

In I2a178966b65f628d5752c5327aeda8b625f190ba,
the blueprints and specs link was fixed in mitaka-template.rst.
It should also be applied for ocata-template.rst
TrivialFix
Change-Id: Idfdbaf732e46b94f11650e714ca439812bcd83cf

This was a feature from Nova legacy API codebase that had 0 testing,
and only hints of documentation. This proposes to bring it back in a
very limited (and deprecated way) for the current code.
Change-Id: I70a8c8e76f234611f4b2972b3adae86ca09da012

This removes the portgroups functionality, as we didn't/won't get to
that this cycle. This will be proposed as a separate blueprint in a
future cycle.
Change-Id: Ic97c172c72245ffa9fe8c2544639a1cb7a898e4d

Modify 'filtering/cliaming' to 'filtering/claiming'
Change-Id: Idec6297e62543a90cf3e0b5a3730544cbd644389
Closes-Bug: #1610092 

Populates the allocations table in the API database with usage
information by calling the new placement API from the Nova resource
tracker.
Change-Id: Ia90ddb7d148f5ec9cb67cf378b93784371af82c7
blueprint: resource-providers-allocations

Currently, Nova does not check the validity of what the user provides for the
project id value in quota and flavor management activities. This leads to
inaccurate quota entries in the database, causing the user to think Nova isn't
reporting quota information accurately. The solution proposed in this blueprint
is to add project id validation specifically to quota and flavor management
through Keystone, to provide the user with an error if their specified project
id is invalid, and to ensure quota and flavor management data is not incorrectly
modified.
bp validate-project-with-keystone
Previously-approved: newton
Change-Id: Ib5d22b2c52d04114d91bf5313e72f7e9a13abe92

This re-writes the ironic-multiple-compute-hosts spec to use a hash
ring, rather than messing around with how we schedule.
Change-Id: I51de94e3fbe301aeed35a6456ed0b7350aefa317

Not sure how or why we forgot to include an ability for a caller to set
and delete allocation records against resource providers, but we did.
This amendment to the spec adds two additional REST API calls for
setting and deleting allocation records in an atomic fashion (atomic
operation for a set of resources consumed by a single consumer against
one or more resource providers). These REST API calls will be made from
the Nova resource tracker when instances claim or free resources on the
compute nodes.
The endpoint is /allocations/{consumer_uuid} accepting PUT and DELETE
methods.
Co-Authored-By: Chris Dent <cdent@anticdent.org>
Change-Id: I5ef70ae2e13b1dd0c0ef1fa5821b3ee5a3265ca7
Blueprint: generic-resource-pools

In-development work has shown that an additional method is
needed in the resource providers API to allow the setting
of multiple inventories on one resource provider, in one
request.
This has been added as
 PUT /resource_provideres/{uuid}/inventories
with a body of one or more inventories.
Change-Id: I81f1b26579e8c2b1aa4afce3a90979ea7a925008
Blueprint: generic-resource-pools

A bug was found where passing an invalid status to the server listing
API would return an empty list for a regular user, but would raise an
exception and return a 500 error for admin users. In the discussions
about that bug it was felt that while fixing the exception was certainly
correct, the list of valid status values is small and well-defined, so
returning an empty list was not the desired behavior; instead, the user
should get a 400 Bad Request instead.
Blueprint response-for-invalid-status
APIImpact
Change-Id: Id5a9b6708b39530ca6f53e9c576305d01f211c78

Clearly it doesn't make sense to have a blank line in the middle of a
paragraph.
Change-Id: I962c8abdd8a3e73291c5863bb2b4b96d458c58d0
Signed-off-by: Adam Spiers <aspiers@suse.com>

This is rendering poorly, fix it up so I can read it. :)
Change-Id: I3584c3067d3f8da9be821cf10579ca91959e2d61

This tries to put down the complete arc of API extensions use in Nova,
and how we will be tearing down the infrastructure over the next 2
cycles.
Change-Id: Ic44397fbaf142816091eb1817dcbea249b3528b0

Amends the generic-resource-pools spec with the following changes:
* Change terminology from "resource pool" to "resource provider"
* Change the REST API proposal to have /resource_providers endpoints
instead of /resource_pools endpoints
* Change the `openstack resource-pool` CLI commands to `openstack
resource-provider` CLI commands
* Adds a generation field to the output of the resource provider dicts
and update operations along with a note as to how the generation field
shall be used
Change-Id: Iefe28041fa9e81558ebac9f47016c4db43a92723