|
|
465.
|
|
|
Registry service can't use %s
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Registry service can't use %s
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
glance/registry/api/v2/rpc.py:42
|
|
|
474.
|
|
|
The tenant name of the administrative user. If "use_user_token" is not in effect, then admin tenant name can be specified.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
The tenant name of the administrative user. If "use_user_token" is not in effect, then admin tenant name can be specified.
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
glance/registry/client/__init__.py:83
|
|
|
476.
|
|
|
The strategy to use for authentication. If "use_user_token" is not in effect, then auth strategy can be specified.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
The strategy to use for authentication. If "use_user_token" is not in effect, then auth strategy can be specified.
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
glance/registry/client/__init__.py:94
|
|
|
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)
|
| In Ubuntu: |
|
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.
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
glance/scrubber.py:51 glance/registry/client/v1/api.py:34
|
