|
|
475.
|
|
|
The URL to the keystone service. If "use_user_token" is not in effect and using keystone auth, then URL of keystone can be specified.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/registry/client/__init__.py:88
|
|
|
476.
|
|
|
The strategy to use for authentication. If "use_user_token" is not in effect, then auth strategy can be specified.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/registry/client/__init__.py:94
|
|
|
477.
|
|
|
The region for the authentication service. If "use_user_token" is not in effect and using keystone auth, then region name can be specified.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/registry/client/__init__.py:99
|
|
|
478.
|
|
|
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
|
|
|
479.
|
|
|
Configuration option was not valid
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/registry/client/v1/api.py:78 glance/registry/client/v2/api.py:60
|
|
|
480.
|
|
|
Could not find required configuration option
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/registry/client/v1/api.py:82 glance/registry/client/v2/api.py:64
|
|
|
481.
|
|
|
location: %s data lost
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/tests/unit/test_migrations.py:927
|
