uyuni/docs installation-and-upgrade-manager-4.3-MU-4.3.13 — Chinese (China) (zh_CN) @ openSUSE Weblate: Checking the credentials

Translation

English type: Labeled list

Chinese (China) (zh_CN)

Needs editing

Skip

	English	Chinese (China) (zh_CN)	Actions
	If the instance exists, but is stopped, the last known credentials will be used to try to connect to the instance.	如果实例存在但已停止，系统将使用最新的已知身份凭证尝试连接实例。
	How long the credentials remain valid depends on the cloud provider.	身份凭证的有效时长取决于云提供商。
	If the instance no longer exists, but is still registered with SUMA, its credentials are no longer valid and the authentication will fail.	如果实例不再存在，但在 SUMA 中仍保持注册状态，其身份凭证将不再有效，身份验证将会失败。
	The error message is shown in the column Status.	“状态”列中会显示错误消息。
	The error message only indicates that the instance is not available. Further diagnostics about the status of the instance needs to be done on the cloud provider.	错误消息只会指出实例不再可用。云提供商需要对实例的状态进行进一步诊断。
	Any of the following actions or changes in the {payg} instance will lead to credentials failing:	在 {payg} 实例中进行以下任意操作或更改都将导致身份凭证失效：
	removing zypper credentials files	去除 zypper 身份凭证文件
	removing the imported certificates	去除导入的证书
	removing cloud-specific entries from [path]``/etc/hosts``	从 [path]``/etc/hosts`` 中去除特定于云的条目
	Registering {payg} system as a client	将 {payg} 系统注册为客户端
	You can register a {payg} instance from where you harvest the credentials as a {salt} client. The instance needs to have a valid cloud connection registered, otherwise it will not have access to channels. If the user removes the cloud packages, the credentials harvesting may stop working.	您可以将从中收集身份凭证的 {payg} 实例注册为 {salt} 客户端。需要为实例注册有效的云连接，否则它将无法访问通道。如果用户去除相关云软件包，身份凭证收集可能会停止工作。
	First set up the {payg} instance to collect authentication data, so it can synchronize the channels.	首先，将 {payg} 实例设置为收集身份验证数据，以使其可以同步通道。
	The rest of the process is the same as for any non-public-cloud client and consists of synchronizing channels, automatic bootstrap script creation, activation key creation and starting the registration.	该过程的其余步骤与非公有云客户端的步骤相同，包括同步通道、自动创建引导脚本、创建激活密钥，以及启动注册。
	For more about registering clients, see xref:client-configuration:registration-overview.adoc[].	有关注册客户端的详细信息，请参见 xref:client-configuration:registration-overview.adoc[]。
	Troubleshooting	查错
	Checking the credentials	检查身份凭证
	If the script fails to collect the credentials, it should provide a proper error message in the logs and in the {webui}.	如果脚本无法收集身份凭证，将会在日志和 {webui} 中提供正确的错误消息。
	If the credentials are not working, [literal]``reposync`` should show the proper error.	如果身份凭证无法工作，[literal]``reposync`` 应该会显示正确的错误消息。
	Using [literal]``registercloudguest``	使用 [literal]``registercloudguest``
	Refreshing or changing the [literal]``registercloudguest`` connection to the public cloud update infrastructure should not interfere with the credentials usage.	刷新或更改 [literal]``registercloudguest`` 与公有云更新基础架构的连接不应影响身份凭证的使用。
	Running [literal]```registercloudguest --clean`` will cause problems if no new cloud connection is registered with the cloud guest command.	如果未使用 cloud guest 命令注册新的云连接，运行 [literal]``registercloudguest --clean`` 将会导致发生问题。
	Containerized proxy deployment using internal registry	使用内部注册表部署容器化代理
	It is possible to deploy containerized images in an environment without an internet connection. In such case, the images can be copied from {suse} registry to an internal registry, or saved to a [literal]``tar`` file.	您可以在未连接互联网的环境中部署容器化映像。在这种情况下，可以将映像从 {suse} 注册表复制到内部注册表，或保存到 [literal]``tar`` 文件。
	Image copying from {suse} registry to internal registry	将映像从 {suse} 注册表复制到内部注册表
	This example illustrates deployment of {salt} proxies only.	下面的示例仅说明 {salt} 代理的部署过程。
	Procedure: Deploying {salt} Proxy from an internal image registry	过程：从内部映像注册表部署 {salt} 代理
	On a machine with access to [literal]``registry.suse.com`` install [literal]``skopeo``:	在可访问 [literal]``registry.suse.com`` 的计算机上安装 [literal]``skopeo``：
	zypper in skopeo	zypper in skopeo
	This can be {productname} Server.	这可以是 {productname} 服务器。
	Copy images between registries:	在不同注册表之间复制映像：
	for image in httpd salt-broker squid ssh tftpd; do skopeo copy docker://registry.suse.com/suse/manager/4.3/proxy-$image:latest docker://<your_server>/registry.suse.com/suse/manager/4.3/proxy-$image done skopeo copy docker://k8s.gcr.io/pause:latest docker://<your_server>/k8s.gcr.io/pause:latest	for image in httpd salt-broker squid ssh tftpd; do skopeo copy docker://registry.suse.com/suse/manager/4.3/proxy-$image:latest docker://<your_server>/registry.suse.com/suse/manager/4.3/proxy-$image done skopeo copy docker://k8s.gcr.io/pause:latest docker://<your_server>/k8s.gcr.io/pause:latest

Loading…

None

String added in the repository

English

Chinese (China) (zh_CN) 6 characters edited Current translation Translated

3 weeks ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Chinese (China) (zh_CN)
No related strings found in the glossary.

String information

Source string description

type: Labeled list

Flags

no-wrap

Source string location

modules/installation-and-upgrade/pages/connect-payg.adoc:79

String age

3 weeks ago

Last updated

3 weeks ago

Source string age

3 weeks ago

Translation file

l10n-weblate/installation-and-upgrade/zh_CN.po, string 147