The pci plugin was only ever merged into the v3 (now v2.1 microversions)
and never the v2 API. Since v2.1 i meant to be identical to v2 it should not
appear in v2 either.
This change disables the pci api functionality in v2.1. It will be renabled
soon after microversions is enabled using a microversion bump.
Related-Bug: 1426241
Partially implements blueprint v2-on-v3-api
Change-Id: Ifc1d6f24d5a637270154b996087a98b41133e014
Currently the following filters are written as though they support multiple values:
* aggregate_image_properties_isolation.py
* aggregate_instance_extra_specs.py
* aggregate_multitenancy_isolation_filter
* availability_zone_filter.py
This commit adds support to the underlying helper method to support
specifying multiple values separated by a comma.
This change for example allows operators to set multiple tenants by using a comma
separated list.
eg. filter_tenant_id: "tenantid1,tenantid2"
DocImpact:
Closes-Bug: #1413087
Change-Id: I010e85ff4c29171c4be6d7a7209dbf2d55da0b64
V2.1 must be identical with V2 and must not contain any new attributes
and new method. And those methods have same methods in the volumes
extensions. Those methods are added in the early stage of v3 works,
because the in early stage v3 works decides to delete any volume related
proxy API, then adds those method instead of them. This commit remove
these methods from V2.1 API.
Partially implements blueprint v2-on-v3-api
Change-Id: I20e0498ec187e9feafd2bfb1aa9646426b3609af
We have discussed how to allocate a microversion for each patch
on nova-api meeting and this patch adds the conclusion on the rst.
Partially implements blueprint api-microversions
Change-Id: I1f23294475d60b219d4167cad1650fd768f868a1
V2.1 server ips response contain 'OS-EXT-IPS:type' & 'OS-EXT-IPS-MAC:mac_addr'
also which are new attributes compared to V2 response.
These new attributes are found during tempest testing by blocking
additional properties in schema -https://review.openstack.org/#/c/156130/
V2.1 must be identical with V2 and must not contain any new attributes in
response. This commit removes these new attributes from V2.1 API.
Partially implements blueprint v2-on-v3-api
Change-Id: Id9fcce0c9629c3d325b87cf9b35f13f1ba15b13f
In case of v2.1, extended server status contain 'locked_by' which does
not match with V2 response.
These new attributes are found during tempest testing by blocking
additional properties in schema -https://review.openstack.org/#/c/156130/
V2.1 must be identical with V2 and must not contain any new attributes in
response. This commit removes this extra attributes from V2.1 API.
Partially implements blueprint v2-on-v3-api
Change-Id: I5c4f6851300510f8fc5342d3bfc596e0ac9f1800
In case of v2.1, update quota_set response contain 'id' which does
not match with V2 response.
These new attributes are found during tempest testing by blocking
additional properties in schema -
https://etherpad.openstack.org/p/Removal_new_attribute_V2_1
V2.1 must be identical with V2 and must not contain any new attributes in
response. This commit removes this extra attributes from V2.1 API.
Partially implements blueprint v2-on-v3-api
Change-Id: I7d1d03fadd1eaf90d9e37eb4f1dc330770f9ace9
In case of v2.1, if "os-access-ips" extension is enabled then server
POST response contain access ips attribute which does not match
with V2 response. V2 server POST response never have access ips attribute.
V2.1 must be identical with V2 and must not contain any new attributes in
response. This commit remove these extra attributes from V2.1 API.
V2 server POST response-
{
"server": {
"OS-DCF:diskConfig": "AUTO",
"adminPass": "ahW3PjQNAu6r",
"id": "e726f5ae-8179-44ba-bbfb-8a0c52b33095",
"links": [
{
"href": "http://openstack.example.com/v2/openstack/
servers/e726f5ae-8179-44ba-bbfb-8a0c52b33095",
"rel": "self"
},
{
"href": "http://openstack.example.com/openstack/
servers/e726f5ae-8179-44ba-bbfb-8a0c52b33095",
"rel": "bookmark"
}
],
"security_groups": [
{
"name": "default"
}
]
}
}
V2.1 server POST response-
{
"server": {
"OS-DCF:diskConfig": "AUTO",
"adminPass": "zPnp2GseTqG4",
"id": "8195065c-fea4-4d57-b93f-5c5c63fe90e8",
"links": [
{
"href": "http://openstack.example.com/v3/servers/
8195065c-fea4-4d57-b93f-5c5c63fe90e8",
"rel": "self"
},
{
"href": "http://openstack.example.com/servers/
8195065c-fea4-4d57-b93f-5c5c63fe90e8",
"rel": "bookmark"
}
],
"accessIPv4": "",
"accessIPv6": "",
"security_groups": [
{
"name": "default"
}
]
}
}
Partially implements blueprint v2-on-v3-api
Change-Id: Ib9197cc9061bbba0c040f237bb52d12a60a976d7
Currently the API sample get '?' for the cpu_info, this is really
confusing, it even does not tell the type of the return.
Change it to be more meaningful.
Change-Id: I791beb7502f47dff646a46c08e818c29f9e6cd79
Ironic has already implemented its own microversion mechanism, and
the header name is X-Ironic-API-Version, not X-Baremetal-API-Version.
Because Ida9f60d8cbd0dcf48669b82e619fc4016ee0bcb7 removed program
terminology from the governance repo.
The microversions of Nova is not used yet. And for consistency of
whole OpenStack projects, this patch changes microversion header
names on Nova side.
Partially implements blueprint api-microversions
Change-Id: I3ea2b2982c5f792c82832d772ae951b157da8b39
Depends-on: I1b43e2662107ad81e57b96f0c9430c61b795fdea
Currently, the headings in this section are all at top
level of the documentation. Move them to subsections.
Change-Id: I23f9bd4e617df7b84384f3a5ebd11b1ff575f3d5
floating-ips api missing floating-ips-get-resp sample file,
and the integrated test cases use a wrong sample file(algouth
the contents are same).
This patch addes missing api samples file and correct the
integrated test case.
Change-Id: Icadcabad369cb6a9c3270915aa3bc9545d5348e8
We've added support for Parallels Cloud Server
recently, so let's add it to hypervisor support
matrix. Since it allows to work with both container
and hypervisor technologies and at this point lists
of supported features are different, let's add two
separate columns.
Change-Id: I6b4f7aa6490819a84d820d68149181123cd7b7c3
Implements an API sample test for a GET request for os-baremetal-nodes
which was previously manually generated and wrong. Removes api samples
for add-interface, create, and remove-interface which were removed
for os-baremetal-nodes at some point.
This should bring the os-baremetal-nodes plugin in sync with reality
for both v2 and v2.1
Partially implements blueprint v2-on-v3-api
Change-Id: Ibd55b43368485b7f460ef6564f611df136275562
Looks like the api samples for os-baremetal-noes were added manually
and so either weren't correct in the first place or the api output
has changed since the first merge. This patch implements tests
for index method. More to follow in later patches
Partially implements bp v2-on-v3-api
Change-Id: I3bd421b9a8b9eb49d274c190d124aaac6fbd361f
The preserve ephemeral on rebuild functionality was merged into the servers plugin
code. This should never have happened and the hook for handling extra parameters
for the rebuild api used instead (otherwise we end up with monster functions).
This patch splits the relevant bits out to their own plugin.
Partially implements bp v2-on-v3-api
Change-Id: I0f35f897b9470039d509a97e6513c6cc806169b4
Most v2.1 API patches are merged and the v2.1 API gate jobs are stable
now. This patch changes v2.1 API status to CURRENT from EXPERIMENTAL,
and does v2 one to SUPPORTED for making developers concentrate on v2.1
API instead of v2 API.
We will replace /v2 endpoint with v2.1 code because users will be able
to continue using /v2 endpoint without any changes, and /v2 endpoint
status becomes
CURRENT -> SUPPORTED -> CURRENT
Partially implements blueprint v2-on-v3-api
Change-Id: I2c5e6612db4a792f1950f53c0bc69617e47b0fff
Depends-On: I8e63a684093dfe3a643c07b20e8080c1e950ed5a
Changes some extension names (not aliases) in the v2.1 api to match
what they are in v2. This is for compatibility between v2.1 and v2
to ensure /extensions output matches. Longer term the extension names
don't really matter as users should just be using the extension alias
and /extensions will be replaced by microversions and json HOME. So its not
worth adding extra infrastructure which is capable of translating just the
extension name like we do with other parts of the v2.1 /extension information
Partially implements bp v2-on-v3-api
Change-Id: I22227496aec51c5f523112cf49af92f0fa124a10
The V2.1 API implementation does not have a 1-1 mapping of extensions
compared to the V2 API. For example because many of the dummy
extensions were only originally added in order to be able to signal to
the API clients that new functionality was available these were not
ported and functionally hard coded into the original plugin.
However in order to retain complete backwards compatibility we need
to have an /extensions output which is identical to the original
V2 API. This patch implements that backwards compatibility including
fields such as XML namespaces, links and updated which are no
longer supported.
Some minor testcase changes to reflect no real xml support in v2.1
now
Part of blueprint v2-on-v3-api
Change-Id: I8e63a684093dfe3a643c07b20e8080c1e950ed5a
Two sections of the hypervisor support matrix refer readers to the
sections of the document dealing with the "pause" operation.
Although there is a section in the raw .ini file called
"[operation.pause]", this doesn't appear at all in the rendered
version of document since it's title is set to
"Stop instance CPUs". This renders readers of the rendered
document unable to find sections being referenced.
This patch clears up the confusion by changing the references
to refer to "Stop instance CPUs" rather than "pause".
Change-Id: Ia97d8e400db3a11291a715f6a630ea8bc638993e
Closes-bug: #1418641
Current v2.1 os-user-data extension only includes "v1.1" in the
description, but it confuses developers/users because of mismatching
versions. In addition, the other extensions doesn't contain version
number in their descriptions.
So this patch removes v1.1 from os-user-data extension's description.
Partially implements blueprint v2-on-v3-api
Change-Id: I6280a0633c0e416e4b1798a708035eaf8c979fba
Although os-user-data has an entry in nova.api.v3.extensions.server.create
in setup.cfg it is missing one in the general nova.api.v3.extensions list.
Without an entry the plugin does not appear in the extension list so this
patch adds an entry for it.
Partially implements blueprint v2-on-v3-api
Change-Id: I13fa049539b07ff901b36ae18eca59fbb1354794
Adds information about the -r flag for tox to refresh the venv when
running unitests as when this happens the failures can look odd or valid
failures can be missing when running on a local system but occur when running
in the gate.
Change-Id: Ie6f7f73dfdbd4e55e8ac0b8a66cf9661f5630a09
As patches are being added which use the new microversions
framework, it will be useful to have some guidance for developers
on how to use it.
Partially implements blueprint api-microversions
Change-Id: I6a118388a436e6ea0a3fdcb998f7a7ba4fbf6e8f
Add document to replace / obsolete the giant table on
https://wiki.openstack.org/wiki/HypervisorSupportMatrix
This initial draft is a fairly straightforward conversion of
that table. Over time, it needs much work to improve the coverage
of API operations and and coverage of important configuration
information that users will care about.
It is using the .ini file syntax in order to record the data in
an easily machine parsable format, while remaining human friendly
by avoiding the syntax heavy approach of XML / JSON / YAML
An extension is registered with sphinx that can convert the
.ini file content into docutils content that then gets rendered
into the developer docs, linked from the index page
Change-Id: I4d3db4bce5737dba30a026a11083a9ea64459cd4
