This change will make possible to enable/disable both v1 and v2 Registry APIs
either individually or together from glance-registry.conf.
DocImpact
Closes bug: #1290432
Change-Id: Ib2458b3312bdb552975b1e42485086a1c3aa6d3f
This patch will add document about how to use the
API message localization.
Partially implements bp i18n-messages
Change-Id: I389103574fc52feed96c592cbafbb52faccda939
An OVA package is a tar archive usually containing an OVF directory
inside it. Nova needs to be able to differentiate OVF and OVA based on
the container format in order to extract the relevant information from
it.
This patch adds the OVA container format to the Glance configuration.
Closes-Bug: #1286375
Change-Id: I5034d2943907823a9296e7a5fb41a28f2d92ec5a
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
Finish updating the glance manpages:
- Update and modernize all files and references
- Add a new manpage for glance-replicator
- Move the common configuration options to common files for
easier maintenance and less redundancy
Change-Id: If2cbcc30f2761b187038f39324c7698de4eb2ab9
Closes-Bug: #1238366
Currently to configure multiple nfs server as a backend
using filesystem store, you cannot mount all disks to a single directory.
Filesystem store allows administrator to configure only single directory with
filesystem_store_datadir parameter in the glance-api.conf.
With multifilesystem store, administrators can configure multiple directories
to store the glance image with help of filesystem_store_datadirs option.
Each directory can be coupled with its priority.
Format for filesystem_store_datadirs in glance-api.conf:
--------------------------------------------------------
filesystem_store_datadirs = </path/to/store>:<priority>
...
filesystem_store_datadirs = </path/to/store>:<priority>
Example:
filesystem_store_datadirs = /var/glance/store
filesystem_store_datadirs = /var/glance/store1:100
filesystem_store_datadirs = /var/glance/store2:200
Note:
-----
1. Either filesystem_store_datadir or filesystem_store_datadirs option
must be specified in glance-api.conf
2. Store with priority 200 has precedence over store with priority 100
3. If no priority is specified, default priority '0' is associated with it.
4. If two filesystem stores have same priority store with maximum free space
will be chosen to store the image.
5. If same store is specified multiple times then BadStoreConfiguration
exception will be raised.
blueprint: glance-multifilesystem-store
DocImpact: Multifilesystem support can be used by specifying multiple
directory paths to filesystem_store_datadirs param in glance-api.conf as
discussed above.
Change-Id: Ibb04ac14c472cd863c5e285b6dc6a08c69014fe8
If a request to Swift for an image fails before the full image is
downloaded, this will reconnect to Swift and download the remainder of
the image without having to start from scratch.
DocImpact
blueprint retry-swift-download
Change-Id: Ifde68415707506b56ffac1939c6750b216b87a87
In roles based property protection, if '@' and '!' are in the same rule then the
glance api will not start considering this an Invalid Configuration.
DocImpact
Closes-bug: #1260333
Change-Id: I1d304f5c505ae9e2486ff653dda205fc2d851c2b
The current policy.json file is missing the copy_from policy in order
to be exhaustive.
DocImpact
Change-Id: Ibc0d1fa7626629c28c514514a985a6b89db2ac69
Closes-bug: #1258999
Add documentation for some parameters which can
be present in glance-api.conf:
* use_user_token
* admin_user
* admin_password
* admin_tenant_name
* auth_url
* auth_region
* auth_strategy
Fix for bug 1256952.
DocImpact
Change-Id: Ia5b731cabaec961f3a4226d30abd3bca9bd87651
There was no policy to control data upload.
Up until today, the add_image policy was a all or nothing, from metadata
to the actual data. Now, with the combination of add_image and upload_image
an administrator will have finer control over the whole chain.
Change-Id: I1a7966ffb5c63dd8239a54fe2963b031d9fe1f9a
Closes-bug: #1254521
Related to bug 1250918
There currently exists no check in set_data function for glance
api v2 in the policy layer. This patch adds upload_image policy.
DocImpact
Change-Id: Ibccc78f8bccff3baa5aca574cf17bd14c5403ca2
Now there is no image status transition diagram in the dev
doc, this patch will add one and keep the image source as
a dot file so that it can be updated easily in the future.
See http://www.graphviz.org to get more info about .dot file.
Fixes bug 1244995
Change-Id: I076c461f688be93eab8d3d1fa541990d7b79da5e
nova-manage supports subcommands of db, for nova-manage,
eg) 'nova-manage db sync',
glance manage however has individual commands like db_sync, db_version
etc. This patch aims at adding the db operations as subcommands to db in
glance-manage similar to nova and refactoring this bit of code in
cmd/manage.py
Fixes: bug 1213197
Change-Id: I6fad31766bc1cec2a666a7ebc8df5c732007c5f1
This patch replaces `qpid_host` with `qpid_hostname` in both the
documentation and the config file sample. `qpid_host` has been shipped
as the parameter to specify qpid's hostname, although the correct one is
`qpid_hostname`.
DocImpact
Closes-bug 1242715
Change-Id: I25f2d0e505560e1762f7f059728c33c47a23439e
Includes an example to limit all property interactions to admin only using policy rule
context_is_admin defined in policy.json
Change-Id: I22dddc06a84312b3b1cbd195cb84839e0321a9f0
Closes-Bug: #1243945
Add documentation for using policies to describe
property protections.
Related to bp api-v2-property-protection
Change-Id: Ic1fc4d3d69dee7ba65462a5bda6cdbe1a266077e
Fixes bug 1233303
Specified conditions under which glance api will not start
successfully.
DocImpact
Change-Id: I8498e9e51f5c7e0d411379c0574c0b8e300f77c2
corrected request body for POST to /v2/.../members
removed GET /v2/images/{imageId}/members/{memberId} (call not implemented)
Change-Id: Iafbba48c7d5e8b8b38e77b7ead216d0e7e235cb2
Closes-Bug: #1229351
Add a new glance-api.conf parameter 'swift_store_ssl_compression',
which allows disabling SSL layer compression for https swift requests.
This can increase performance when transferring compressed images (eg
qcow2) to/from swift.
Addresses bug 1190666.
DocImpact.
Change-Id: Ic26dba9dce5ea7e5c09fdd531746b93cec54fc5c
This patch adds a storage quota that is applied against the sum total
of a users storage consumption against all configured storage systems.
A single quota is applied to all users via the configuration option
'total_storage_quota'. Most of the patch is about enforcement so
when a separate service for quota management emerges in OpenStack the
per user value to enforce can be obtained from that service but the
enforcement code will remain the same.
blueprint glance-basic-quotas
docImpact
Change-Id: I251832f7372c70942be6f0c6aa12285145dd7c18