Bases: object
Indexable for file-like objs iterators
Wrapper that allows an iterator or filelike be treated as an indexable data structure. This is required in the case where the return value from Store.get() is passed to Store.add() when adding a Copy-From image to a Store where the client library relies on eventlet GreenSockets, in which case the data to be written is indexed over.
Implemented by subclasses to return the next element.
Return entire string value… used in testing
Registers all store modules and all schemes from the given config. Duplicates are not re-registered.
Removes chunks of data from backend specified by uri.
Yields chunks of data from backend specified by uri.
Returns list of known schemes.
Retrieves image size from backend specified by uri.
Given a location (assumed to be a URL), attempt to determine the store from the location. We use here a simple guess that the scheme of the parsed URL is the store…
uri – Location to check for the store
Given a scheme, return the appropriate store object for handling that scheme.
Given a URI, return the store object that would handle operations on the URI.
uri – URI to analyze
A wrapper around a call to each stores add() method. This gives glance a common place to check the output
image_id – The image add to which data is added
data – The data to be stored
size – The length of the data in bytes
store – The store to which the data is being added
context – The request context
verifier – An object used to verify signatures for images
The url location of the file, the size amount of data, the checksum of the data the storage systems metadata dictionary for the location
A wrapper around a call to each store’s add() method that requires a hashing_algo identifier and returns a 5-tuple including the “multihash” computed using the specified hashing_algo. (This is an enhanced version of store_add_to_backend(), which is left as-is for backward compatibility.)
image_id – The image add to which data is added
data – The data to be stored
size – The length of the data in bytes
store – The store to which the data is being added
hashing_algo – A hashlib algorithm identifier (string)
context – The request context
verifier – An object used to verify signatures for images
The url location of the file, the size amount of data, the checksum of the data, the multihash of the data, the storage system’s metadata dictionary for the location
glance_store.exceptions.BackendException
glance_store.exceptions.UnknownHashingAlgo
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.