The api-ref states that the both the key and value of a custom
property are limited to 255 chars. This limit applies only to
the key.
Change-Id: I3bacca8b25f2a8339f6d8758e45c690da9968555
Closes-bug: #1748900
Generalizes the discussion to include the new web-download import
method and includes a new sample import request.
Change-Id: Icb6cd920f31c6e8e4eecf17880dd3244e5d1a61b
Closes-bug: #1748229
The Nova project has added 'sata' as a valid disk bus for qemu and
kvm hypervisors, see https://review.openstack.org/#/c/459794/6
DocImpact: add to metadefs release note
Related-Bug: #1686136
Change-Id: If8e23756616e46391827ac3d85d287940862613f
Add deleting the only location or attempting to set the locations
to an empty list as another reason why a user might get a 403
response to a PATCH call.
Change-Id: I2edb072ded11d1b710af0309f0372d1b16042a54
Closes-bug: #1542724
Following apis are returning 500 error if user passes name with more
than 80 characters:
* md-tag-create
* md-tag-update
* md-object-create
* md-object-update
* md-property-create
* md-property-update
This happens because there is a discrepancy in db column length and
glance-api length check in schema validation. In database the 'name'
field for these API's is defined as of maximum 80 characters and in
schema it is defined as of maximum 255 characters. So if user passes
name with more than 80 characters and less than 255 characters
database fails to store that value and shouts with following error
which leads to 500 error to API user:
(pymysql.err.DataError) (1406, u"Data too long for column 'name' at
row 1")
Fixed this issue by changing the maximum allowed length for 'name'
from 255 to 80 in schema validation.
APIImpact
DocImpact
Closes-Bug: #1719252
Change-Id: I4ae67457c3e4f5a6bfc3c1db2d305a9b7587395f
The v1 API is deprecated, so moving that to be the last item in
the ToC. Also adding a search link to the top to make it easier
to find things within the API documentation.
Change-Id: Id558679ef9e7012ad4fbe8ea25e9bc544851d4c2
Adds documentation of the interoperable image import process
introduced in Pike in the EXPERIMENTAL Image API v2.6.
Change-Id: Ifbedc2e5e566db084bc7028ed4239485f0d68b18
The MVP of image import functionality will be introduced as an
EXPERIMENTAL 2.6 version of the Images API. The current version
will remain at 2.5.
This patch:
* Updates the version response
* Updates version negotiation code
* Updates unit and functional tests
* Updates the api-ref
* Adds a releasenote
Change-Id: Ied573897157e05f7b0438baeb1553326fb06613a
This patch updates the disk_format description to include "ploop"
(added in Ocata). It also rewrites the container_format description
to indicate that the actual values depend on how the API being queried
is configured.
This patch does not update the api-ref for the deprecated v1 API.
Change-Id: I3385b3f628b74b109c05108e331085c54b0126a1
Fix the Sphinx html_last_updated_fmt for Python3.
The html_last_updated_fmt option is interpeted as a
byte string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.
Change-Id: I2d79405579e55ae77c8f8e353a15c49474061e1e
This patch updates the api-ref to indicate that ``Range`` shall be
accepted in the request header and upon a successful serving of the
partial image data, the response headers would include ``Content-Range``.
Change-Id: I99ecc345793c7f3045400e57711f01cae2181f6f
Depends-On: b7ebc792c32995751744be3f36cbc9a0c1eead2a
Sphinx 1.5 fails with a warning that a code-block cannot be highlighted.
It's indeed not json, use 'none' to fix the build.
Change-Id: I02bfe805c419fcc49ac43b66f4f7b1a0d1d54755
Add text to the api-ref to document the changes introduced by
"Implement and Enable Community Images", whose change identifier
is I94bc7708b291ce37319539e27b3e88c9a17e1a9f.
Change-Id: Ib18c6ac226267ec15b399b71dbfefed33a1dbffd
Change [1] fixed partial downloads in glance and changed the
status codes to be more appropriate. Updating api-ref to reflect
what the v2 code will now do.
[1] I3cd47b998be79604511b3cd4879209820cf776b7
Change-Id: I70e3f60c3ce3d0eeb7b457496dbbe623b2ff473e
In most places, the api-ref refers to the 'namespace_name' in URLs,
but in two places in the metadefs-namespaces-properties file, the
term 'namespace_id' is used. This patch fixes those two occurrences
in the interest of consistency, but also because it is causing a
warning that's interpreted as an error in the latest version of
os_api_ref [0].
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-January/110606.html
Change-Id: I86435a216c9c8d8bd391fb662049662d7d303ae5
Change-Id I94bc7708b291ce37319539e27b3e88c9a17e1a9f (Community
Images) entails a minor version bump in the v2 API.
Change-Id: I2b7cd5ec9b974ebc738feb89ef22c428fbe3be06
Depends-On: I94bc7708b291ce37319539e27b3e88c9a17e1a9f
With the change [1] that went into Newton to disallow image location
updates except for 'queued' and 'active' states, this patch adds
appropriate api-ref documentation. Related change [2] bumps the minor
API version to 2.4.
[1] https://review.openstack.org/324012
[2] https://review.openstack.org/350809
Change-Id: I593ad2d3c7402c4fb87a475c8d44060baed5ff69
Closes-Bug: 1621236
Change all example urls in api-ref/source to
http://glance.openstack.example.org
and document about this standard URL format
Change-Id: I429c1e256fa3bfdc15adbee129b04ef9c028e82d
Closes-Bug: #1611490
This patch marks the Images v1 API as DEPRECATED in the api-ref.
The v1 API was deprecated in Newton by the following commit:
63e6dbb1eb006758fbcf7cae83e1d2eacf46b4ab
Change-Id: Ifa71b6375a63a9ddf182448a78192d6c76ed7fba
Partial-bug: #1618495
Images API reference is updated to reflect that the 'vhdx'
disk_format is now one of the default formats supported by Glance.
This change also introduces substitution of image parameter
description from a single source file in order to avoid copy and
paste errors. Only the disk_format parameter is affected in this,
other parameters may be consolidated in subsequent patch(es).
Co-Authored-By: Anne Gentle <agentle@cisco.com>
Co-Authored-By: Andreas Jaeger <jaegerandi@gmail.com>
Co-Authored-By: Alexander Bashmakov <alexander.bashmakov@intel.com>
Change-Id: Ib50b8e184364b6ee7d8af4ed3d4959ba76568049
Spec-Lite: https://review.openstack.org/#/c/347626
Closes-Bug: #1608643
The 'versions' response contains the status of the Images API versions,
but does not indicate the releases when the statuses went into effect.
This patch adds a Version History to the 'versions' api-ref page. The
language used (for example, "Bexar changes") is consistent with what's
been adopted for other parts of the images api-ref (see the discussion
on https://review.openstack.org/#/c/356693/ )
This patch is current for Newton:
- v1 deprecation: already merged as commit
63e6dbb1eb006758fbcf7cae83e1d2eacf46b4ab
- v2 minor version bump: the dependency stated below
Depends-On: I5d1c4380682efa4c15ff0f294f269c800fe6762a
Change-Id: Id920a3284a4be23032cc4a23e04726fab6d24361
Closes-bug: #1621161
Partial-bug: #1618495
OpenStack house style is no Latin, which includes "etc.".
This fixes the usage in the metadefs documentation.
Change-Id: Ic88bd2a9286b2647a927f2fb8ecdec480053a91c
Closes-Bug: 1610311
This patch corrects the versions response to be consistent with the
current (Mitaka) Images API versions.
Change-Id: I57f1caad34af17f9667d16e1574646f378e2c11a
Closes-bug: #1609795