This change moves existing files, updates a few of the cross-references
and paths, and fixes some formatting. It is not meant to be the final
word on how the main page looks or how the other files are organized,
but it gets everything roughly into shape. If the glance team wants to
make changes, please do those as follow-up patches
This change depends on the spec and on a feature of pbr that allows us
to move where the auto-generated class reference documentation ends up
in the tree.
Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
Depends-On: I2bd5652bb59cbd9c939931ba2e7db1b37d2b30bb
Change-Id: I9dde267793a5913acb5b1ec028cfb66bc5189783
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch consists of changes to the Glance developer docs to
indicate that the Images API v1 has been deprecated in Newton.
Change-Id: Idf62cf86cd402b2f39a7233f7159ba81dad02bb9
Partial-bug: #1618495
As we are removing the s3 driver from source tree per change
I032b0fc16400cbd2112687d38e010128be699221 , it seems right to remove the
references of the same in the glance tree.
Updated here are files that referenced s3; these files include:
* documentation files
* documentation of the glance architecture (source and png files)
* config help text
* stores associated with location strategy
* tests
UpgradeImpact
Change-Id: I680ee2baf39b49156d173e2ae108ae5d0221eca7
Depends-On: I032b0fc16400cbd2112687d38e010128be699221
Depends-On: I5d2da0611365b838f41285b64cdcfef9adf50e85
Change all example urls in doc/source to
http://glance.openstack.example.org
Change-Id: If7a5ccd31f6892de441d2acb6213bf15d1be3e64
Closes-Bug: #1611489
Co-Authored-By: Jin Li <jl7351@att.com>
Co-Authored-By: Hemanth Makkapati <hemanth.makkapati@rackspace.com>
This patch adds the Hyper-V 'vhdx' disk format to the Glance
configuration. This allows users to upload 'vhdx' images by default.
'vhdx' disks can have much larger storage capacity than the older 'vhd'
format [1]. (Plus, anything with 'x' in the name is awesome.)
DocImpact: Docs will need to be updated to indicate that the 'vhdx'
disk_format is now one of the default disk formats supported by Glance.
UpgradeImpact: Adds 'vhdx' to the default list of disk_formats. Operators
will no longer need to configure specifically to use 'vhdx' disks.
[1] https://technet.microsoft.com/en-us/library/hh831446(v=ws.11).aspx
Spec-Lite: https://review.openstack.org/#/c/347626
Change-Id: I4e172c78d7afeb8be5a0123238efe3d8e4b044c9
Add 'ova' as a container_format in glanceapi.rst
because the format is missed.
Change-Id: Ifa52d6ca8a6f81fd8c07aa59c171ba47ad8f798c
Closes-Bug: #1606573
As per the comments and agreement on
Iede37e61784b6a8a974ce0ae29ccfab510d8cc53 , this patch proposes the
concerned changes. The former patch was merged as the consensus on the
idea of the Images API future section was converged. This is merely a
simplification to the grammatical tone on the respective sections.
Change-Id: Iefbdeadb78b2a7b866495d4a8f3e7a84cee46fe2
Adds a section to the Glance docs clarifying the relations between
Glance and the OpenStack Images APIs, as well as Glare and why there
is no current intention to create an Images v3 API.
Change-Id: Iede37e61784b6a8a974ce0ae29ccfab510d8cc53
There are many warnings and errors that occur when the docs are
generated.
Co-Author-By: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
Closes-Bug: 1556818
Change-Id: Ifebeb3904f136a56bd6fe6877220b279a1f98354
Gridfs was marked as deprecated some releases go and now it has
been removed from Glance_store. So Glance should not support this
driver anymore.
Change-Id: Ia81e109c3919ad8ee8336f9051fa7920780f5bbd
A Docker image is a tar archive typically containing a container
filesystem. In order to use the nova-docker compute driver nova and boot
docker instances glance support of the docker container format is
required.
This patch adds the Docker container format to the Glance configuration.
DocImpact: Docs will need to be updated to indicate that the docker
container_format is now one of the default container formats supported
by Glance.
UpgradeImpact: Adds 'docker' to the default list of container_formats.
Operators will no longer need to configure specifically to use docker
containers.
Closes-Bug: #1519402
Change-Id: Ifa206686086232a5599e7bc27a852bc5f3186ebc
Adds conceptual overview of tasks and documents the tasks API calls.
This is a partial fix (parts 1 & 2) for bug #1484566.
Change-Id: If295c35d3cfa2f39d9f6bac8f02947bce3552d0a
Partial-bug: #1484566
This patch:
- addresses grammar comments from commit
https://review.openstack.org/207510
- fixes small grammar/syntax errors in Using Glance’s
Image Public APIs section of the guide.
Change-Id: I6b5339a7680c3ccd3ce9bb156f10acad9f47daa3
- Rename resource_type to resource_type_
associations in namespace API input/output
- Add created_at/updated_at in resource_
type_associations block of namespace API
input/output.
- Fix minor nits
Closes-bug: 1367908
Change-Id: Ie74bfb36a7023abb346852f5b863f19d0d7bc4ff
This patch will add document about how to use the
API message localization.
Partially implements bp i18n-messages
Change-Id: I389103574fc52feed96c592cbafbb52faccda939
Customers using a VMware environment with OpenStack should be able to
store their Glance images in VMware datastores. This is a first step to solve
the problem where Nova needs to copy the bits over the network
from Glance to the datastore when spawning an instance.
Also, this give the ability to provide some optimizations for specific
image formats in the future (fast cloning for example).
This patch contains a 'glance/store/vmware/' folder with the code
to manage the connection with vCenter or an ESX(i) host.
This code will go away as soon as it is merged to Olso:
see review https://review.openstack.org/#/c/65075/
The current implementation give this ability to specify the vCenter or
ESX(i) IP. In case of a vCenter IP, there is no optimization to reduce
the datapath (no host selected).
Consequently, it is recommended to specify an ESX IP if the ESX host
API endpoint is accessible from Glance.
docImpact
Implements bp vmware-datastore-storage-backend
Change-Id: I3837912e0d1614b9c31a689f71c2e34d453e2dc3
corrected request body for POST to /v2/.../members
removed GET /v2/images/{imageId}/members/{memberId} (call not implemented)
Change-Id: Iafbba48c7d5e8b8b38e77b7ead216d0e7e235cb2
Closes-Bug: #1229351
These are some text fixes in document, scripts and functions,
including variable usage, text aligning, adding new store class in
document
Change-Id: I98e226969d86698972870a7b3a042cb00c2206e9
This lets us refer to the fact that some optional headers are in fact
required unless reserving an image.
Fixes bug 1124224
Change-Id: I5646d4dc130efecf991573b363eb1a665012b7df
Patchset addresses reviewer's comments, rebase against master,
and follows new guidance from Foundation:
http://wiki.openstack.org/Documentation/Copyright
Change-Id: I94367461505778973528eb8835d991f4fb796dab
* Drop image sharing blurb from authentication docs.
* Link to authentication page from api page
Related to bp glance-folsom-docs-cleanup
Change-Id: Idac46a78f79fac0c673f6a9b91c1f44df7b705b4
* Add bit about images api vs glance
* Explain how to send auth token
* Prepend '/v1' to example URIs
Related to bp glance-folsom-docs-cleanup
Change-Id: I2c3b568e463f62033268573f50f2d8a74d053965
Fixes lp 933702
For images created via the glance CLI, the container and disk formats
were previously defaulted if not explicitly set. However if created via
the python or REST APIs, these attributes were not defaulted if unset.
There is no real sensible default for these formats, so now an image
create fails with 400 "Bad Request" if the format metadata are missing.
Also we ensure unset image metadata are not reported in x-image-meta-*
headers in order to disambiguate None and empty string values.
Change-Id: I8189383f5f9adf42a8cdac7f8dc7e9327baf46da
This just changes the value of image.id, leaving the key name alone. We also
enforce image ids provided on an image create be a uuid. Implements
blueprint uuid-image-identifiers
Change-Id: I22ba69550ccbc04a24d680748d60414d2d0f1a99
Removes the Location field from the return of the
API server's GET /images/detail and GET /images/<ID>
calls. The Registry server API was unchanged, as the API
server needs to call the Registry server in order to
find location information...
Change-Id: I914456ad3879f19fa0b55c8a89b8217c193193d8
When adding an image (or uploading an image during PUT operations),
you may now supply an optional X-Image-Meta-Checksum header. When
storing the uploaded image, the backend image stores now are required
to return a checksum of the data they just stored. The optional
X-Image-Meta-Checksum header is compared against this generated checksum
and returns a 409 Bad Request if there is a mismatch.
The ETag header is now properly set to the image's checksum now
for all GET /images/<ID>, HEAD /images/<ID>, POST /images and
PUT /images/<ID> operations.
Adds unit tests verifying the checksumming behaviour in the API, and
in the Swift and Filesystem backend stores.
properly with invalid or mismatched disk and container formats.
Adds documentation on disk and container formats. Updates
existing documentation to remove references to the now-gone
type column and replaces these references with disk_format
and container_format.
Reworked the validates_image() method in the registry.db.api
to be like what Rick was describing in reviews.
Doug Hellmann