It is observed that the api-ref has no doc support for
delete-from-store (/v2/stores/%(store)s/%(image)s) API.
This patch adds the doc support for delete-from-store in api-ref.
bp: delete-from-store
Closes-Bug: #1941038
Change-Id: I5e82ff9f979b80b5b1e06eebea84a1b2fb50c78e
This restricts all metadef resource manipulation to admin-only, but
still allow users to see everything. There are multiple low-grade
security issues with the metadef API, detailed in the related bug.
Restricting resource manipulation to admin-only solves most of these
concerns.
SecurityImpact
Depends-On: https://review.opendev.org/c/openstack/tempest/+/780108
Change-Id: I333c58e73c202c1f523030e54e03f2868459b595
Related-Bug: #1916926
This adds some words to the api-ref doc, as well as a release note
about the blanket reservation of os_glance* properties.
Change-Id: I0cd6f35296a647fdb1f2cb44a688b34c0382c556
Related-Bug: #1912001
Since this commit cfa9b6e8e8,
the visibility all is supported in the listing of images. However,
the documentation does not present it. This can make it hard for operators
to be aware of this option when listing images. Therefore, we propose to add
it in the documentation.
Change-Id: Iaa0ce6e1fde5c4c546b2f4a53969287b05d295de
Added new import method 'copy-image' which will copy existing image into
specified list of stores. Introduced additional task which will serve
as internal plugin which will allow copying existing image into staging
area and then this data will be uploaded to specified stores via regula
import flow.
NOTE: This new import method 'copy-image' is only supported if multiple
stores are enabled in deployment.
APIImpact
Implements: blueprint copy-existing-image
Change-Id: I13eaab7ab013f44ce18465bdbdbe8052942570ff
The import image api now supports a list of stores to import data into.
This list can be specified through a new "stores" field that has been
added to the request body.
During import stage, Glance iterates overs this list and send the data
to each store one by one.
If an invalid backend is requested by the user, an exception is raised.
If an errors occurs during verify, already pushed data is removed and
image state is unchanged.
Change-Id: Id3ac19488c0a693d7042be4a3c83f3b9f12313d0
Implements: blueprint import-multi-stores
The nova TrustedFilter scheduler filter was removed in the Queens
release [1] so the compute trust metadef is now just noise so we
should remove it.
[1] https://review.opendev.org/506864/
Change-Id: I71825cd5317d458fa30287b78cd1030cbc457dbd
Slight rewrite of the stores discovery section of the api-ref to
indicate which elements of the response are optional and to remove
mention of the store type from the descriptions.
Change-Id: I8261de878fcaff1e498f7a3e152df7d980d0560c
Made changes to discovery store to show 'http'
store as 'read-only' if it is configured under
'enabled_backends' cofiguration option.
Change-Id: If5d292bbb4cef1bd21a7e6cd4ef343a767eb91a4
Added documentation and modified api-ref documents to
reflect multiple stores support changes.
Related to blueprint multi-store
Change-Id: I932297df8149968d31a5367a9ca71a5629045445
Curly quotes(Chinese punctuation) usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I9b8830179fb98f3a6bef479bbaa12df70311269a
"List images" had been taken by the v1 API, but now that its
api reference has been removed, that's no longer a problem.
Can also remove the superfluous "an"s that were used in the
v2 titles to prevent sphinx conflicts.
Co-authored-by: Ha Van Tu <tuhv@vn.fujitsu.com>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Change-Id: I2c1ce3f5c1279a93a08855c554e156c4fc115f61
Closes-Bug: #1615899
Updates the schemas/image(s) responses and the api-ref. (The dev
docs are correct.) Adds a test so this won't happen again.
Closes-bug: #1762031
Change-Id: Ifb0a07fcdb1c8d91f1ad700329a208200222a2a6
In the metadefs section of the api-ref, the current example response
for the list-resource-type-associations call is incorrect. Add a
correct example response.
Change-Id: I10e92ce96b40563b3c4d02ac5c542960564837ec
Closes-bug: #1751208
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
Adds documentation of the interoperable image import process
introduced in Pike in the EXPERIMENTAL Image API v2.6.
Change-Id: Ifbedc2e5e566db084bc7028ed4239485f0d68b18
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
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
