|
|
18.
|
|
|
Whether to pass through headers containing user and tenant information when making requests to the registry. This allows the registry to use the context middleware without keystonemiddleware's auth_token middleware, removing calls to the keystone auth service. It is recommended that when using this option, secure communication between glance api and glance registry is ensured by means other than auth_token middleware.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/scrubber.py:51 glance/registry/client/v1/api.py:34
|
|
|
203.
|
|
|
Date and time of namespace creation (READ-ONLY)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_namespaces.py:709
|
|
|
204.
|
|
|
Date and time of the last namespace modification (READ-ONLY)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_namespaces.py:715
|
|
|
209.
|
|
|
Resource type names should be aligned with Heat resource types whenever possible: http://docs.openstack.org/developer/heat/template_guide/openstack.html
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_resource_types.py:204
glance/tests/functional/v2/test_metadef_resourcetypes.py:199
|
|
|
210.
|
|
|
Specifies the prefix to use for the given resource type. Any properties in the namespace should be prefixed with this prefix when being applied to the specified resource type. Must include prefix separator (e.g. a colon :).
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_resource_types.py:212
glance/tests/functional/v2/test_metadef_resourcetypes.py:207
|
|
|
211.
|
|
|
Some resource types allow more than one key / value pair per instance. For example, Cinder allows user and image metadata on volumes. Only the image properties metadata is evaluated by Nova (scheduling or drivers). This property allows a namespace target to remove the ambiguity.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_resource_types.py:221
glance/tests/functional/v2/test_metadef_resourcetypes.py:216
|
|
|
212.
|
|
|
Date and time of resource type association (READ-ONLY)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_resource_types.py:233
glance/tests/functional/v2/test_metadef_resourcetypes.py:230
|
|
|
213.
|
|
|
Date and time of the last resource type association modification (READ-ONLY)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/metadef_resource_types.py:239
glance/tests/functional/v2/test_metadef_resourcetypes.py:236
|
|
|
268.
|
|
|
The format to which images will be automatically converted.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/async/flows/convert.py:36
|
|
|
308.
|
|
|
Work dir for asynchronous task operations. The directory set here will be used to operate over images - normally before they are imported in the destination store. When providing work dir, make sure enough space is provided for concurrent tasks to run efficiently without running out of space. A rough estimation can be done by multiplying the number of `max_workers` - or the N of workers running - by an average image size (e.g 500MB). The image size estimation should be done based on the average size in your deployment. Note that depending on the tasks running you may need to multiply this number by some factor depending on what the task does. For example, you may want to double the available size if image conversion is enabled. All this being said, remember these are just estimations and you should do them based on the worst case scenario and be prepared to act in case they were wrong.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/common/config.py:70
|
