Sphinx 1.6.x gained a cross-reference check warning that caused
the build to fail in "tox -e docs" environment. Removing underscores
from the citation reference identifier ensures that the cross references
are properly detected. Similarly missing references to footnotes are
now a warning (which is upgraded to an error in the docs tox
environment) so adjust references where it makes sense and is needed.
Closes-Bug: #1695127
Change-Id: I7e55dcf910e0ba6dd85b565db8cb1ecbdd39634a
TrivialFix:
"automaticly" should be "automatically"
"instnaces" should be "instances"
"verison" should be "version"
Change-Id: If470b65277718a4c6d1c56b4d215b565babe67d0
During the development of the placement API, some details ended
up being different than what was originally specified. The changes
herein attempt to make the spec reflect reality.
The changes include
* don't use $ when assigning shell variables in examples
* add GET allocations by consumer
* add GET allocations by resource provider
* fix URIs in link examples of resoure providers (they were shown as
relative links)
* correct "type": "uuid" jsonschema to use "type": "string" with a
"format" of "uuid".
* other minor jsonschema corrections here and there
* Correct inventory create and update response bodies from empty
responses to having a body
Change-Id: I47595a0a2353fdb58e1f7930a06b18312961433d
The original Nova specification for integrating Castellan
for key management has merged, but it was suggested that
alternate implementations to the original one may be preferred.
This addendum opens up other options for discussion.
Original specification change id:
I025995584e74c0b2df00841697714c10d1afb674
Change-Id: Ie9c686d9f1ee2e99d3c0b45f3b9b83e1f7ccb00b
At the end of the review for the generic resource pools spec, we agreed
to change the JSON structure of the inventory "records" to this:
{
"DISK_GB": {
"total": 0,
...
}, ...
}
instead of this:
[
{
"resource_class": "DISK_GB",
"total": 0,
...
}, ...
]
However, we forgot to make the PUT /r-p/{uuid}/inventories request
consistent with the GET response payload.
This corrects that oversight. The code in the placement API was written
to the spec and will need to be corrected as well.
Change-Id: I8eaef8d532d9e5d4917ede572000e3adc3149f73
This just amends the spec for the design change in the
server create request schema that went into the final
implementation for this blueprint.
Change-Id: Ide7f6126f8e8a4f47fad7dce55a820ada8426a00
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
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
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
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
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
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
Currently, no useful notification will be sent
for keypair state change.
This spec will transform legacy notification
to versioned notification about keypairs,
and at the same time extend contents of
notification with extra data.
Blueprint: keypair-notification
Change-Id: I05080afb8bd4249f8bea23512b25844fecbefeb9
The spec is describing the Nova side of the 'multiattach' feature.
The functionality targets to add support for attaching a Cinder
volume to multiple VM instances.
Previously-approved: mitaka
Implements: blueprint multi-attach-volume
Change-Id: I288f7140e3acd979b65734049fd42c2b3f3c5277
wanghui