Zen

Translation

English type: Plain text
provides customized {payg} product images for SLES, SLES for SAP, etc.
40/700 · 70

Only reviewers can change approved strings, please add a suggestion if you think the string should be changed.

English Chinese (China) (zh_CN) Actions
Clients use the versioning system of their underlying operating system. For clients using {suse} operating systems, you can perform upgrades within the {productname} {webui}.
客户端采用底层操作系统的版本控制系统。对于运行 {suse} 操作系统的客户端，可在 {productname} {webui} 中进行升级。
For more information about upgrading clients, see xref:client-configuration:client-upgrades.adoc[].
有关升级客户端的详细信息，请参见 xref:client-configuration:client-upgrades.adoc[]。
Supported Client Systems
支持的客户端系统
Supported operating systems for traditional and Salt clients are listed in this table.
下表列出了传统客户端和 Salt 客户端支持的操作系统。
In this table, {check} indicates that clients running the operating system are supported by {suse}, and {cross} indicates that it is not supported. Fields marked as {question} are under consideration, and may or may not be supported at a later date.
在此表格中，{check} 表示 {suse} 支持运行对应操作系统的客户端，{cross} 表示不支持。标有 {question} 的字段表示正在考核中，将来可能支持对应的操作系统，也可能不支持。
For {suse} operating systems, the version and SP level must be under general support (normal or LTSS) to be supported with {productname}. For details on supported product versions, see:
对于 {suse} 操作系统，版本和 SP 级别必须享受标准支持（常规或 LTSS）才受 {productname} 的支持。有关受支持产品版本的细节，请参见：
link:https://www.suse.com/lifecycle[]
link:https://www.suse.com/lifecycle[]
For non-{suse} operating systems, including {rhel}, {centos}, and {oracle}, only the latest available version is under general support.
对于非 {suse} 操作系统，包括 {rhel}、{centos} 和 {oracle}，只有最新可用版本才享受标准支持。
| Operating System
| Architecture
| Traditional Clients
| Salt Clients

| {sle} 15, 12
| {x86_64}, {ppc64le}, {ibmz}, {aarch64}
| {check}
| {check}

| {sles} for SAP 15, 12
| {x86_64}, {ppc64le}
| {check}
| {check}

| {micro}
| {x86_64}, {aarch64}, {s390x}
| {cross}
| {check}

| {opensuse} Leap 15
| {x86_64}, {aarch64}
| {check}
| {check}

| {sll} 9, 8, 7
| {x86_64}
| {cross}
| {check}

| {almalinux} 9, 8
| {x86_64}, {aarch64}
| {cross}
| {check}

| {amazon} 2
| {x86_64}, {aarch64}
| {cross}
| {check}

| {centos} 8, 7
| {x86_64}, {aarch64}
| {cross}
| {check}

| {debian} 12, 11, 10
| {x86_64}
| {cross}
| {check}

| {oracle} 9, 8, 7
| {x86_64}, {aarch64}
| {cross}
| {check}

| {rhel} 9, 8, 7
| {x86_64}
| {cross}
| {check}

| {rocky} 9, 8
| {x86_64}, {aarch64}
| {cross}
| {check}

| {ubuntu} 22.04, 20.04
| {amd64}
| {cross}
| {check}
| 操作系统
| 体系结构
| 传统客户端
| Salt 客户端

| {sle} 15、12
| {x86_64}、{ppc64le}、{ibmz}、{aarch64}
| {check}
| {check}

| {sles} for SAP 15、12
| {x86_64}、{ppc64le}
| {check}
| {check}

| {micro}
| {x86_64}、{aarch64}、{s390x}
| {cross}
| {check}

| {opensuse} Leap 15
| {x86_64}、{aarch64}
| {check}
| {check}

| {sll} 9 8、7
| {x86_64}
| {cross}
| {check}

| {almalinux} 9、8
| {x86_64}、{aarch64}
| {cross}
| {check}

| {amazon} 2
| {x86_64}、{aarch64}
| {cross}
| {check}

| {centos} 8、7
| {x86_64}、{aarch64}
| {cross}
| {check}

| {debian} 12、11、10
| {x86_64}
| {cross}
| {check}

| {oracle} 9、8、7
| {x86_64}、{aarch64}
| {cross}
| {check}

| {rhel} 9、8、7
| {x86_64}
| {cross}
| {check}

| {rocky} 9、8
| {x86_64}、{aarch64}
| {cross}
| {check}

| {ubuntu} 22.04、20.04
| {amd64}
| {cross}
| {check}
Salt SSH is using [path]``/var/tmp`` to deploy Salt Bundle to and execute Salt commands on the client with the bundled Python. Therefore you must not mount [path]``/var/tmp`` with the [option]``noexec`` option. It is not possible to bootstrap the clients, which have [path]``/var/tmp`` mounted with [option]``noexec`` option, with the {webui} because the bootstrap process is using Salt SSH to reach a client.
Salt SSH 使用 [path]``/var/tmp`` 在安装了绑定 Python 的客户端上部署 Salt 捆绑包和执行 Salt 命令。因此，切勿使用 [option]``noexec`` 选项挂载 [path]``/var/tmp``。无法通过 {webui} 引导使用 [option]``noexec`` 选项挂载 [path]``/var/tmp`` 的客户端，因为引导过程是使用 Salt SSH 来访问客户端的。
When you are setting up your client hardware, you need to ensure you have enough for the operating system and for the workload you want to perform on the client, with these additions for {productname}:
设置客户端硬件时，需确保为操作系统以及您要在客户端上执行的工作负载提供足够的空间；对于 {productname}，需按如下所述提供额外的资源：
Client Additional Hardware Requirements
客户端的额外硬件要求
| Hardware | Additional Size Required
| RAM | 512{nbsp}MB
| Disk Space: | 200{nbsp}MB
| 硬件 | 额外所需大小
| RAM | 512{nbsp}MB
| 磁盘空间： | 200{nbsp}MB
Connect {payg} instance
连接 {payg} 实例
In the three major public cloud providers (AWS, GCP and Azure), SUSE:
在三大主流公有云提供商（AWS、GCP 和 Azure）中，SUSE：
provides customized {payg} product images for SLES, SLES for SAP, etc.
提供 SLES、SLES for SAP 等产品的自定义 {payg} 产品映像
operates per-region RMT Servers mirroring repositories for products available as {payg}
为以 {payg} 形式提供的产品操作按区域 RMT 服务器镜像储存库
This document describes how to connect existing {payg} instance to {productname} server, and gives basic information about credentials collection from the instance. The goal of this connection is to extract authentication data so the {productname} Server can connect to a cloud RMT host. Then the {productname} Server has access to products on the RMT host that are not already available with the {scc} organization credentials.
本文介绍如何将现有 {payg} 实例连接到 {productname} 服务器，并提供了有关从实例收集身份凭证的基本信息。此类连接是为了提取身份验证数据，以使 {productname} 服务器能够连接到云 RMT 主机。之后，{productname} 服务器便可以访问 RMT 主机上尚未提供 {scc} 组织身份凭证的产品。
Before using {payg} feature make sure that:
在使用 {payg} 功能之前，请确保：
The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories
{payg} 实例是从正确的 SUSE 产品映像（例如 SLES、SLES for SAP、SLE HPC）启动的，以便能够访问所需储存库
{productname} Server has connectivity to the {payg} instance (ideally in the same region) either directly or via a bastion
{productname} 服务器可以直接或通过堡垒连接到 {payg} 实例（最好位于同一区域）
A basic {scc} account is required. Enter your valid {scc} credentials in menu:Admin[Setup Wizard > Organization Credentials]. This account is required for accessing the {productname} client tools for boostrapping regardless of {payg} instances.
需要基本的 {scc} 帐户。请在menu:管理[安装向导 > 组织身份凭证]中输入您的有效 {scc} 身份凭证。无论要引导的是哪个 {payg} 实例，都需要使用此帐户来访问 {productname} 客户端工具。
If you bootstrap the {payg} instance to SUSE Manager, SUSE Manager will disable its {payg} repositories then add repositories from where it mirrored the data from the RMT server. The final result will be {payg} instances acquiring the same repositories from the RMT servers but through the SUSE Manager server itself. Of course repositories can still be setup primarily from SCC.
如果您引导 SUSE Manager 的 {payg} 实例，SUSE Manager 将禁用其 {payg} 储存库，然后从其镜像 RMT 服务器中数据的地方添加储存库。最终结果是，{payg} 实例会获得与通过 RMT 服务器添加这种方式相同的储存库，只不过是通过 SUSE Manager 服务器自身获得的。当然，设置储存库的主要方式仍是通过 SCC。
Connecting {payg} instance
连接 {payg} 实例
Procedure: Connecting new {payg} instance
过程：连接新的 {payg} 实例
In the {productname} {webui}, navigate to menu:Admin[Setup Wizard > {payg}], and click btn:[Add {payg}].
在 {productname} {webui} 中，导航到menu:管理[安装向导 > {payg}]，然后单击 btn:[添加 {payg}]。
Start with the page section [guimenu]``{payg} connection Description``.
从页面的 [guimenu]``{payg} 连接说明``部分开始。
In the [guimenu]``Description`` field, add the description.
在[guimenu]``说明``字段中添加说明。
Move to the page section [guimenu]``Instance SSH connection data``.
转移到页面的[guimenu]``实例 SSH 连接数据``部分。
In the [guimenu]``Host`` field, enter the instance DNS or IP address to connect from {productname}.
在[guimenu]``主机``字段中，键入要从 {productname} 连接的实例 DNS 或 IP 地址。
In the [guimenu]``SSH Port`` field, enter the port number or use default value 22.
在 [guimenu]``SSH 端口``字段中输入端口号或使用默认值 22。

Loading…

User avatar graceyu

Translation approved

  1. uyuni
  2. docs installation-and-upgrade-manager-4.3-MU-4.3.11
  3. Chinese (China) (zh_CN)
provides customized {payg} product images for SLES, SLES for SAP, etc.
提供 SLES、SLES for SAP 等产品的自定义 {payg} 产品映像
4 months ago
Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: SLES

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

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

String information

Source string description
type: Plain text
Source string location
modules/installation-and-upgrade/pages/connect-payg.adoc:3
String age
5 months ago
Last updated
a month ago
Source string age
5 months ago
Translation file
l10n-weblate/installation-and-upgrade/zh_CN.po, string 70