|
|
471.
|
|
|
The administrators password. If "use_user_token" is not in effect, then admin credentials can be specified.
|
|
|
|
|
管理员密码。如果“use_user_token”没有生效，那么可指定管理凭证。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/__init__.py:78
|
|
|
472.
|
|
|
The tenant name of the administrative user. If "use_user_token" is not in effect, then admin tenant name can be specified.
|
|
|
|
|
管理用户的租户名称。如果“use_user_token”没有生效，那么可指定管理员租户名称。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/__init__.py:83
|
|
|
473.
|
|
|
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.
|
|
|
|
|
keystone 服务的 URL。如果“use_user_token”没有生效并且正在使用 keystone 认证，那么可指定 keystone 的 URL。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/__init__.py:88
|
|
|
474.
|
|
|
The strategy to use for authentication. If "use_user_token" is not in effect, then auth strategy can be specified.
|
|
|
|
|
要用于认证的策略。如果“use_user_token”没有生效，那么可指定认证策略。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/__init__.py:94
|
|
|
475.
|
|
|
The region for the authentication service. If "use_user_token" is not in effect and using keystone auth, then region name can be specified.
|
|
|
|
|
用于认证服务的区域。如果“use_user_token”没有生效并且正在使用 keystone 认证，那么可指定区域名称。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/__init__.py:99
|
|
|
476.
|
|
|
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.
|
|
|
|
|
向注册表进行请求时，是否传递包含用户和租户信息的头。这允许注册表使用上下文中间件而不使用 keystonemiddleware 的 auth_token 中间件，从而移除对 keystone 认证服务的调用。建议当使用此选项时，通过 auth_token 中间件以外的其他方式来确保 Glance api 与 Glance 注册表之间的通信安全。
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/scrubber.py:51 glance/registry/client/v1/api.py:34
|
|
|
477.
|
|
|
Configuration option was not valid
|
|
|
|
|
配置选项无效
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/v1/api.py:78 glance/registry/client/v2/api.py:60
|
|
|
478.
|
|
|
Could not find required configuration option
|
|
|
|
|
找不到必需的配置选项
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/registry/client/v1/api.py:82 glance/registry/client/v2/api.py:64
|
|
|
479.
|
|
|
location: %s data lost
|
|
|
|
|
位置：%s 数据已丢失
|
|
Translated by
openstackjenkins
|
|
|
|
Located in
glance/tests/unit/test_migrations.py:927
|
