- 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.