0.3.0 of cirros is a bit old. Let's switch to
what we test in our CI jobs which currently is 0.3.2
Change-Id: I999063dc0a86335b94376409ddd559e880c54bcc
Wikipedia's list of common misspellings [1] has a machine-readable
version. This patch fixes those misspellings mentioned in the list
which don't have multiple right variants (as e.g. "accension", which can
be both "accession" and "ascension"), such misspellings are left
untouched. The list of changes was manually re-checked for false
positives.
[1] https://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machines
Change-Id: I52a6f641a203185f9005bc0731d15166ad741161
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Currently v2 and v2.1 have separate functional tests and their
corresponding sample files. As v2 and v2.1 are supposed to be identical,
there is overhead to maintain two set of functional tests and sample files.
We can have one set of tests which can run for both v2 and v2.1.
This commit use the testscenearios to generate the tests one for v2 and one for v2.1
and make v2.1 tests to run against v2.1 plugins by redirecting /v2 endpoint to v2.1
plugins in api-paste.ini
As example this commit merge flavor APIs functional tests between v2 & v2.1.
In V2 flavor API has following extensions
- Flavor_swap
- Flavor_disabled
- Flavorextradata
In V2.1 above extensions have been merged together in flavor plugins
NOTE- As testscenarios is applied in base class. v2 tests will be generated
for all the existing tests but for tests which are not merged yet
their v2 generated tests will be skipped till they gets
merged. After merge, both version tests are expected to pass like
flavor tests in this patch. So you may see lot of skipped tests
which is expected and will gets disappear as tests gets merged.
Change-Id: I0e0262f818c7d7fb15528b16d3225b9578910996
Some sample files like server, images etc are kept under api_samples/
directory.
As plan is to create clean directory structure for sample files for
V2, V2.1 and microversion, moving these sample files to respective directory
will help to achieve that.
Change-Id: I284d035f6fadb26a94bcb3586f4a8c72942ee423
There are lot of duplicate sample files for server POST req/resp
in functional tests.
This patch reuse the server post req/resp sample file for V2
functional tests.
Change-Id: I4fc5771af9407b9e75cf07682ee1706935a87709
There are lot of duplicate sample files for server POST req/resp
in functional tests.
This patch reuse the server post req/resp sample file for V2.1
functional tests.
Change-Id: I5da924b78780eae64a40ee39ee4fbe1e5b8c3b1f
This change adds properties to v2.1
os-extended-server-properties and os-extended-volumes nova APIs
in order to expose information which is required for the standalone
EC2 API implementation (resides on stackforge/ec2-api) to use only
public APIs. Right now this information is taken by directly accessing
internal Nova DB.
It adds proposed microversion v2.3.
It implements the spec "Nova changes required for standalone EC2 API
implementation" in this review: https://review.openstack.org/#/c/153636/
APIImpact
Implements: blueprint ec2-api
Change-Id: I850e51e730c82906f68fddb14fb0004d7091eb91
X509 certificates are used by Windows for passwordless
authentication (WinRM) in a way which can be considered
consistent with the usage of SSH keys on Linux, as both
are based on public / private keypairs.
Enables nova-api to return the keypair type, updates
nova-api version to reflect the changes and updates the
unit and functional tests to validate the API changes.
Unit tests have been updated to ensure that the keypair
type is not being returned on previous API versions.
Note: x509 keypair implementation is added in the next
commit.
DocImpact - See nova/api/openstack/rest_api_version_history.rst
for details
APIImpact
Depends-On: Id5b210d7afe5c0a590abcbd42b9ff85b071a5c55
Co-Authored-By: Chris Yeoh <cyeoh@au1.ibm.com>
Partially implements: blueprint keypair-x509-certificates
Change-Id: I215662f2f92a01921a866c3218031787a9eaf915
V2.1 server update and rebuild response contain
'OS-EXT-IPS:type' & 'OS-EXT-IPS-MAC:mac_addr' in address field
which are new attributes compared to V2 response for those API.
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: Id5b210d7afe5c0a590abcbd42b9ff85b071a5c55
Adds new 'nova-manage api_db sync' and 'nova-manage api_db version'
commands for working with the new api database for cells.
DocImpact
bp: cells-v2-mapping
Change-Id: I00881db2ecbd559fdac7ad11ac452b0075ccc289
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
Adds information about how to manually compare the requested api version
with what behaviour to exhibit rather than rely on decorators.
Partially implements bp api-microversions
Change-Id: I69919bad4f267f27350df78e70d9fe3ed78b5520
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
Adds a first cut for some documentation on how to write an API plugin
for V2.1. Note that this is not meant to have exhaustive coverage, and I
will add more detail in future commits. I do welcome suggestions of
other areas which should be included in future doc patches.
Partially implements blueprint v2-on-v3-api
Change-Id: Ibe5a471af357ce21253efeb8beb9ade1c16396f5
Jenkins