foreman_virt_who_configure 0.5.25 → 0.5.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/app/assets/javascripts/foreman_virt_who_configure/locale/bn/foreman_virt_who_configure.js +155 -170
- data/app/assets/javascripts/foreman_virt_who_configure/locale/bn_IN/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ca/foreman_virt_who_configure.js +177 -213
- data/app/assets/javascripts/foreman_virt_who_configure/locale/cs_CZ/foreman_virt_who_configure.js +263 -392
- data/app/assets/javascripts/foreman_virt_who_configure/locale/de/foreman_virt_who_configure.js +273 -489
- data/app/assets/javascripts/foreman_virt_who_configure/locale/de_DE/foreman_virt_who_configure.js +157 -163
- data/app/assets/javascripts/foreman_virt_who_configure/locale/el/foreman_virt_who_configure.js +179 -239
- data/app/assets/javascripts/foreman_virt_who_configure/locale/en/foreman_virt_who_configure.js +2 -462
- data/app/assets/javascripts/foreman_virt_who_configure/locale/en_GB/foreman_virt_who_configure.js +161 -182
- data/app/assets/javascripts/foreman_virt_who_configure/locale/es/foreman_virt_who_configure.js +273 -489
- data/app/assets/javascripts/foreman_virt_who_configure/locale/fr/foreman_virt_who_configure.js +283 -529
- data/app/assets/javascripts/foreman_virt_who_configure/locale/gl/foreman_virt_who_configure.js +167 -185
- data/app/assets/javascripts/foreman_virt_who_configure/locale/gu/foreman_virt_who_configure.js +166 -184
- data/app/assets/javascripts/foreman_virt_who_configure/locale/he_IL/foreman_virt_who_configure.js +154 -157
- data/app/assets/javascripts/foreman_virt_who_configure/locale/hi/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/it/foreman_virt_who_configure.js +175 -268
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ja/foreman_virt_who_configure.js +282 -528
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ka/foreman_virt_who_configure.js +280 -532
- data/app/assets/javascripts/foreman_virt_who_configure/locale/kn/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ko/foreman_virt_who_configure.js +291 -420
- data/app/assets/javascripts/foreman_virt_who_configure/locale/mr/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/nl_NL/foreman_virt_who_configure.js +161 -176
- data/app/assets/javascripts/foreman_virt_who_configure/locale/or/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/pa/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/pl/foreman_virt_who_configure.js +167 -188
- data/app/assets/javascripts/foreman_virt_who_configure/locale/pt/foreman_virt_who_configure.js +150 -153
- data/app/assets/javascripts/foreman_virt_who_configure/locale/pt_BR/foreman_virt_who_configure.js +274 -490
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ru/foreman_virt_who_configure.js +178 -307
- data/app/assets/javascripts/foreman_virt_who_configure/locale/sl/foreman_virt_who_configure.js +154 -163
- data/app/assets/javascripts/foreman_virt_who_configure/locale/sv_SE/foreman_virt_who_configure.js +167 -185
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ta/foreman_virt_who_configure.js +155 -170
- data/app/assets/javascripts/foreman_virt_who_configure/locale/ta_IN/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/te/foreman_virt_who_configure.js +164 -179
- data/app/assets/javascripts/foreman_virt_who_configure/locale/tr/foreman_virt_who_configure.js +152 -155
- data/app/assets/javascripts/foreman_virt_who_configure/locale/zh_CN/foreman_virt_who_configure.js +283 -529
- data/app/assets/javascripts/foreman_virt_who_configure/locale/zh_TW/foreman_virt_who_configure.js +176 -305
- data/lib/foreman_virt_who_configure/version.rb +1 -1
- data/locale/Makefile +12 -2
- data/locale/bn/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/bn/foreman_virt_who_configure.po +5 -4
- data/locale/bn_IN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/bn_IN/foreman_virt_who_configure.po +5 -4
- data/locale/ca/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ca/foreman_virt_who_configure.po +6 -5
- data/locale/cs_CZ/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/cs_CZ/foreman_virt_who_configure.po +2 -1
- data/locale/de/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/de/foreman_virt_who_configure.po +4 -3
- data/locale/de_DE/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/de_DE/foreman_virt_who_configure.po +5 -4
- data/locale/el/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/el/foreman_virt_who_configure.po +6 -5
- data/locale/en/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/en/foreman_virt_who_configure.po +0 -468
- data/locale/en_GB/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/en_GB/foreman_virt_who_configure.po +10 -9
- data/locale/es/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/es/foreman_virt_who_configure.po +2 -1
- data/locale/foreman_virt_who_configure.pot +4 -4
- data/locale/fr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/fr/foreman_virt_who_configure.po +10 -8
- data/locale/gl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/gl/foreman_virt_who_configure.po +6 -5
- data/locale/gu/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/gu/foreman_virt_who_configure.po +5 -4
- data/locale/he_IL/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/he_IL/foreman_virt_who_configure.po +4 -3
- data/locale/hi/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/hi/foreman_virt_who_configure.po +5 -4
- data/locale/it/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/it/foreman_virt_who_configure.po +8 -8
- data/locale/ja/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ja/foreman_virt_who_configure.po +10 -7
- data/locale/ka/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ka/foreman_virt_who_configure.po +6 -5
- data/locale/kn/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/kn/foreman_virt_who_configure.po +5 -4
- data/locale/ko/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ko/foreman_virt_who_configure.po +149 -141
- data/locale/mr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/mr/foreman_virt_who_configure.po +5 -4
- data/locale/nl_NL/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/nl_NL/foreman_virt_who_configure.po +7 -6
- data/locale/or/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/or/foreman_virt_who_configure.po +5 -4
- data/locale/pa/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/pa/foreman_virt_who_configure.po +5 -4
- data/locale/pl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/pl/foreman_virt_who_configure.po +7 -6
- data/locale/pt/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/pt/foreman_virt_who_configure.po +2 -1
- data/locale/pt_BR/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/pt_BR/foreman_virt_who_configure.po +3 -2
- data/locale/ru/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ru/foreman_virt_who_configure.po +8 -7
- data/locale/sl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/sl/foreman_virt_who_configure.po +5 -4
- data/locale/sv_SE/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/sv_SE/foreman_virt_who_configure.po +6 -5
- data/locale/ta/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ta/foreman_virt_who_configure.po +5 -4
- data/locale/ta_IN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/ta_IN/foreman_virt_who_configure.po +5 -4
- data/locale/te/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/te/foreman_virt_who_configure.po +5 -4
- data/locale/tr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/tr/foreman_virt_who_configure.po +2 -1
- data/locale/zh_CN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/zh_CN/foreman_virt_who_configure.po +14 -11
- data/locale/zh_TW/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
- data/locale/zh_TW/foreman_virt_who_configure.po +7 -6
- metadata +2 -10
- data/locale/cs_CZ/foreman_virt_who_configure.edit.po +0 -780
- data/locale/de/foreman_virt_who_configure.edit.po +0 -916
- data/locale/es/foreman_virt_who_configure.edit.po +0 -911
- data/locale/fr/foreman_virt_who_configure.edit.po +0 -936
- data/locale/ja/foreman_virt_who_configure.edit.po +0 -843
- data/locale/ka/foreman_virt_who_configure.edit.po +0 -894
- data/locale/pt_BR/foreman_virt_who_configure.edit.po +0 -903
- data/locale/zh_CN/foreman_virt_who_configure.edit.po +0 -825
data/app/assets/javascripts/foreman_virt_who_configure/locale/zh_CN/foreman_virt_who_configure.js
CHANGED
@@ -3,10 +3,10 @@
|
|
3
3
|
"locale_data": {
|
4
4
|
"foreman_virt_who_configure": {
|
5
5
|
"": {
|
6
|
-
"Project-Id-Version": "foreman_virt_who_configure 0.5.
|
6
|
+
"Project-Id-Version": "foreman_virt_who_configure 0.5.25",
|
7
7
|
"Report-Msgid-Bugs-To": "",
|
8
8
|
"PO-Revision-Date": "2017-05-03 11:59+0000",
|
9
|
-
"Last-Translator": "
|
9
|
+
"Last-Translator": "Ewoud Kohl van Wijngaarden <ewoud+transifex@kohlvanwijngaarden.nl>, 2025",
|
10
10
|
"Language-Team": "Chinese (China) (https://app.transifex.com/foreman/teams/114/zh_CN/)",
|
11
11
|
"MIME-Version": "1.0",
|
12
12
|
"Content-Type": "text/plain; charset=UTF-8",
|
@@ -17,290 +17,107 @@
|
|
17
17
|
"domain": "foreman_virt_who_configure",
|
18
18
|
"plural_forms": "nplurals=1; plural=0;"
|
19
19
|
},
|
20
|
-
"
|
21
|
-
"
|
22
|
-
],
|
23
|
-
"List of virt-who configurations per organization": [
|
24
|
-
"每个机构的 virt-who 配置列表"
|
25
|
-
],
|
26
|
-
"Show a virt-who configuration": [
|
27
|
-
"显示 virt-who 配置"
|
28
|
-
],
|
29
|
-
"Renders a deploy script for the specified virt-who configuration": [
|
30
|
-
"为指定的 virt-who 配置提供部署脚本"
|
31
|
-
],
|
32
|
-
"Configuration name": [
|
33
|
-
"配置名称"
|
34
|
-
],
|
35
|
-
"Configuration interval in minutes": [
|
36
|
-
"以分钟为单位的配置间隔"
|
37
|
-
],
|
38
|
-
"Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
|
39
|
-
"Hypervisor 过滤模式 %{unlimited} 表示没有过滤,%{whitelist} 表示白名单,%{blacklist} 代表黑名单"
|
40
|
-
],
|
41
|
-
"Hypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
|
42
|
-
"Hypervisor 白名单,仅在过滤模式设置为 1 时适用。支持通配符和正则表达式,必须用逗号分隔多项记录。"
|
20
|
+
"1. Copy this configuration script to a safe directory.": [
|
21
|
+
"1. 将这个配置脚本复制到安全目录。"
|
43
22
|
],
|
44
|
-
"
|
45
|
-
"
|
23
|
+
"2. Make the script executable and run it.": [
|
24
|
+
"2. 使脚本可执行,并运行脚本。"
|
46
25
|
],
|
47
|
-
"
|
48
|
-
"
|
26
|
+
"3. Delete the script.": [
|
27
|
+
"3. 删除该脚本。"
|
49
28
|
],
|
50
|
-
"
|
51
|
-
"
|
29
|
+
"A comma-separated list of hostnames or domains or ip addresses to ignore proxy settings for. Optionally this may be set to <code>*</code> to bypass proxy settings for all hostnames domains or ip addresses.": [
|
30
|
+
"忽略代理服务器。忽略代理服务器设置的主机名、域或 ip 地址逗号分隔列表。可选择性地设置为 <code>*</code>,以便为所有主机名、域或 ip 地址跳过代理服务器设置。"
|
52
31
|
],
|
53
|
-
"
|
54
|
-
"
|
32
|
+
"A plugin to make virt-who configuration easy": [
|
33
|
+
"简化 virt-who 配置的插件"
|
55
34
|
],
|
56
|
-
"
|
57
|
-
"
|
35
|
+
"Account name by which virt-who is to connect to Nutanix AHV.": [
|
36
|
+
"virt-who 连接到 Nutanix AHV 的帐户名称。"
|
58
37
|
],
|
59
|
-
"
|
60
|
-
"
|
38
|
+
"Account name by which virt-who is to connect to the hypervisor, in the format <code>domain_name\\\\account_name</code>. Note that only a single backslash separates the values for domain_name and account_name. If you are using a domain account, and the global configuration file <code>/etc/virt-who.conf</code>, then <b>two</b> backslashes are required. For further details, see <a href=\\\"https://access.redhat.com/solutions/1270223\\\">Red Hat Knowledgebase solution How to use a windows domain account with virt-who</a> for more information.": [
|
39
|
+
"virt-who 用于连接 hypervisor 的帐户名,格式为 <code>domain_name\\\\account_name</code>。注意只使用单斜线来分离 domain_name 和 account_name 的值。如果您使用域帐户,以及全局配置文件 <code>/etc/virt-who.conf</code>,则需要使用 <b>双斜线</b>。有关进一步详情,请参见<a href=\\\"https://access.redhat.com/solutions/1270223\\\">红帽知识库解决方案 如何将 windows 域名帐户用于 在 virt-who</a> 了解更多信息。"
|
61
40
|
],
|
62
41
|
"Account name by which virt-who is to connect to the hypervisor.": [
|
63
42
|
"virt-who 用于连接 hypervisor 的帐户名。"
|
64
43
|
],
|
65
|
-
"Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
|
66
|
-
"Hypervisor 密码,除 libvirt/kubevirt 以外的所有 hypervisor 类型都需要"
|
67
|
-
],
|
68
|
-
"Foreman server FQDN": [
|
69
|
-
"Foreman 服务器 FQDN"
|
70
|
-
],
|
71
|
-
"Enable debugging output": [
|
72
|
-
"启用调试输出"
|
73
|
-
],
|
74
|
-
"Configuration file containing details about how to connect to the cluster and authentication details.": [
|
75
|
-
"配置文件,其中包含有关如何连接到集群的详细信息以及身份验证的详细信息。"
|
76
|
-
],
|
77
|
-
"HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.": [
|
78
|
-
"应当用于 virt-who 运行所在服务器和 hypervisor 及虚拟化管理器之间通信的 HTTP 代理服务器。"
|
79
|
-
],
|
80
|
-
"Ignore proxy. A comma-separated list of hostnames or domains or ip addresses to ignore proxy settings for. Optionally this may be set to * to bypass proxy settings for all hostnames domains or ip addresses.": [
|
81
|
-
"忽略代理服务器。忽略代理服务器设置的主机名、域或 ip 地址逗号分隔列表。可选择性地设置为 *,以便为所有主机名、域或 ip 地址跳过代理服务器设置。"
|
82
|
-
],
|
83
|
-
"Organization of the virt-who configuration": [
|
84
|
-
"virt-who 配置机构"
|
85
|
-
],
|
86
|
-
"Select the Prism flavor you are connecting to": [
|
87
|
-
"选择您要连接到的 Prism 类别"
|
88
|
-
],
|
89
|
-
"Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
|
90
|
-
"启用 AHV 内部故障排除需要 Option Enable debugging output。它会在两个选项都启用时提供额外的 AHV 调试信息"
|
91
|
-
],
|
92
|
-
"Create a virt-who configuration": [
|
93
|
-
"创建 virt-who 配置"
|
94
|
-
],
|
95
|
-
"Update a virt-who configuration": [
|
96
|
-
"更新 virt-who 配置"
|
97
|
-
],
|
98
|
-
"Configuration numeric identifier": [
|
99
|
-
"配置数字识别符"
|
100
|
-
],
|
101
|
-
"Delete a virt-who configuration": [
|
102
|
-
"删除 virt-who 配置"
|
103
|
-
],
|
104
|
-
"Create Config": [
|
105
|
-
"创建配置"
|
106
|
-
],
|
107
|
-
"New Config": [
|
108
|
-
"新建配置"
|
109
|
-
],
|
110
|
-
"Help": [
|
111
|
-
"帮助"
|
112
|
-
],
|
113
|
-
"VMware vCenter server’s fully qualified host name or IP address.": [
|
114
|
-
"VMware vCenter 服务器的完全限定主机名或 IP 地址。"
|
115
|
-
],
|
116
|
-
"Microsoft Hyper-V fully qualified host name or IP address.": [
|
117
|
-
"Microsoft Hyper-V fully 的完全限定主机名或 IP 地址。"
|
118
|
-
],
|
119
|
-
"Libvirt server’s fully qualified host name or IP address. You can also specify preferred schema, for example: <code>qemu+ssh://libvirt.example.com/system</code>. Make sure you setup root's SSH key on target host for a user specified at hypervisor username field": [
|
120
|
-
""
|
121
|
-
],
|
122
|
-
"Container-native virtualization’s fully qualified host name or IP address. In order to connect to the cluster it is required to provide path to kubeconfig which contains connection details and authentication token.": [
|
123
|
-
"容器原生虚拟化的标准主机名或 IP 地址。为了连接到集群,需要提供 kubeconfig 的路径,其中包含连接详细信息和身份验证令牌。"
|
124
|
-
],
|
125
|
-
"Nutanix AHV’s IP address.": [
|
126
|
-
"Nutanix AHV 的 IP 地址。"
|
127
|
-
],
|
128
|
-
"Account name by which virt-who is to connect to the hypervisor, in the format <code>domain_name\\\\account_name</code>. Note that only a single backslash separates the values for domain_name and account_name. If you are using a domain account, and the global configuration file <code>/etc/virt-who.conf</code>, then <b>two</b> backslashes are required. For further details, see <a href=\\\"https://access.redhat.com/solutions/1270223\\\">Red Hat Knowledgebase solution How to use a windows domain account with virt-who</a> for more information.": [
|
129
|
-
"virt-who 用于连接 hypervisor 的帐户名,格式为 <code>domain_name\\\\account_name</code>。注意只使用单斜线来分离 domain_name 和 account_name 的值。如果您使用域帐户,以及全局配置文件 <code>/etc/virt-who.conf</code>,则需要使用 <b>双斜线</b>。有关进一步详情,请参见<a href=\\\"https://access.redhat.com/solutions/1270223\\\">红帽知识库解决方案 如何将 windows 域名帐户用于 在 virt-who</a> 了解更多信息。"
|
130
|
-
],
|
131
44
|
"Account name by which virt-who is to connect to the hypervisor. By default this is <code>Administrator</code>. To use an alternate account, create a user account and assign that account to the following groups (Windows 2012 Server): Hyper-V Administrators and Remote Management Users.": [
|
132
45
|
"virt-who 连接 hypervisor 所用的帐户名。默认为 <code>Administrator</code>。要使用替换帐户,请创建用户帐户并将该帐户分配给以下组(Windows 2012 服务器):Hyper-V 管理员和远程管理用户。"
|
133
46
|
],
|
134
47
|
"Account name by which virt-who is to connect to the hypervisor. Virt-who does not support password based authentication, you must manually setup SSH key, see <a href=\\\"https://access.redhat.com/solutions/1515983\\\">Red Hat Knowledgebase solution How to configure virt-who for a KVM host</a> for more information.": [
|
135
48
|
"virt-who 连接 hypervisor 所用的帐户名。Virt-who 不支持基于密码的验证,您必须手动设置 SSH 密钥,有关更多信息,请参见 <a href=\\\"https://access.redhat.com/solutions/1515983\\\">红帽知识库解决方案 如何为 KVM 主机配置 virt-who</a>。"
|
136
49
|
],
|
137
|
-
"Account
|
138
|
-
"virt-who
|
139
|
-
],
|
140
|
-
"No Report Yet": [
|
141
|
-
"尚没有报告"
|
50
|
+
"Account password by which virt-who is to connect to the hypervisor instance.": [
|
51
|
+
"virt-who 用于连接 hypervisor 实例的帐户密码。"
|
142
52
|
],
|
143
|
-
"
|
144
|
-
"
|
53
|
+
"Actions": [
|
54
|
+
"操作"
|
145
55
|
],
|
146
|
-
"
|
147
|
-
"
|
56
|
+
"Applicable only for esx provider type. Hosts which parent (usually ComputeResource) name is specified in comma-separated list in this option will <b>NOT</b> be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
57
|
+
"仅适用于 esx 提供程序类型。在此选项中以逗号分隔的列表指定了父资源(通常是 ComputeResource)名称的主机<b>不会被</b>报告。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
148
58
|
],
|
149
|
-
"
|
150
|
-
"
|
59
|
+
"Applicable only for esx provider type. Only hosts which parent (usually ComputeResource) name is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
60
|
+
"仅适用于 esx 提供程序类型。仅报告在此选项中以逗号分隔的列表指定了父资源(通常是 ComputeResource)名称的主机。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
151
61
|
],
|
152
62
|
"Blacklist": [
|
153
63
|
"黑名单"
|
154
64
|
],
|
155
|
-
"
|
156
|
-
"
|
157
|
-
],
|
158
|
-
"Schedule": [
|
159
|
-
"调度"
|
160
|
-
],
|
161
|
-
"Connection": [
|
162
|
-
"连接"
|
163
|
-
],
|
164
|
-
"Every hour": [
|
165
|
-
"每小时"
|
166
|
-
],
|
167
|
-
"Every 2 hours": [
|
168
|
-
"每 2 小时"
|
169
|
-
],
|
170
|
-
"Every 4 hours": [
|
171
|
-
"每 4 小时"
|
172
|
-
],
|
173
|
-
"Every 8 hours": [
|
174
|
-
"每 8 小时"
|
175
|
-
],
|
176
|
-
"Every 12 hours": [
|
177
|
-
"每 12 小时"
|
178
|
-
],
|
179
|
-
"Every 24 hours": [
|
180
|
-
"每 24 小时"
|
181
|
-
],
|
182
|
-
"Every 2 days": [
|
183
|
-
"每 2 天"
|
184
|
-
],
|
185
|
-
"Every 3 days": [
|
186
|
-
"每 3 天"
|
187
|
-
],
|
188
|
-
"OK": [
|
189
|
-
"好"
|
190
|
-
],
|
191
|
-
"No change": [
|
192
|
-
"不更改"
|
193
|
-
],
|
194
|
-
"Unknown": [
|
195
|
-
"未知"
|
196
|
-
],
|
197
|
-
"Unknown configuration status, caused by unexpected conditions": [
|
198
|
-
"未知配置状态,由意外情况造成"
|
199
|
-
],
|
200
|
-
"The configuration was not deployed yet or the virt-who was unable to report the status": [
|
201
|
-
"尚未部署配置,或者 virt-who 无法报告状态"
|
202
|
-
],
|
203
|
-
"The virt-who report arrived within the interval": [
|
204
|
-
"在间隔期间收到 virt-who 报告"
|
205
|
-
],
|
206
|
-
"The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
|
207
|
-
"未在间隔期间收到 virt-who 报告,表示 hypervisor 无更改"
|
208
|
-
],
|
209
|
-
"Prism Central": [
|
210
|
-
"Prism Central"
|
211
|
-
],
|
212
|
-
"Prism Element": [
|
213
|
-
"Prism Element"
|
214
|
-
],
|
215
|
-
"every %s hours": [
|
216
|
-
"每 %s 小时"
|
217
|
-
],
|
218
|
-
"Success": [
|
219
|
-
"成功"
|
220
|
-
],
|
221
|
-
"Newer version of virt-who is required, minimum version is %s": [
|
222
|
-
"需要更高的 virt-who 版本,最低版本为 %s"
|
223
|
-
],
|
224
|
-
"Unable to create virt-who config file": [
|
225
|
-
"无法创建 virt-who 配置文件"
|
226
|
-
],
|
227
|
-
"Unable to create sysconfig file": [
|
228
|
-
"无法创建 sysconfig 文件"
|
229
|
-
],
|
230
|
-
"Unable to enable virt-who service using systemctl": [
|
231
|
-
"无法使用 systemctl 启用 virt-who 服务"
|
232
|
-
],
|
233
|
-
"Unable to start virt-who service, please see virt-who logs for more details": [
|
234
|
-
"无法开始 virt-who 服务,请查看 virt-who 日志了解详情"
|
235
|
-
],
|
236
|
-
"Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
|
237
|
-
"无法安装 virt-who 软件包,确保已正确订阅主机,且具备访问 katello-host-tools 的访问权限"
|
238
|
-
],
|
239
|
-
"Owner was not provided": [
|
240
|
-
"未提供所有者"
|
241
|
-
],
|
242
|
-
"Interval was not provided": [
|
243
|
-
"未提供间隔"
|
244
|
-
],
|
245
|
-
"Virt-who Configurations Status": [
|
246
|
-
"Virt-who 配置状态"
|
65
|
+
"Configs": [
|
66
|
+
"配置"
|
247
67
|
],
|
248
68
|
"Configuration Status": [
|
249
69
|
"配置状态"
|
250
70
|
],
|
251
|
-
"
|
252
|
-
"
|
71
|
+
"Configuration file containing details about how to connect to the cluster and authentication details": [
|
72
|
+
"配置文件,其中包含有关如何连接到集群的详细信息以及身份验证的详细信息"
|
253
73
|
],
|
254
|
-
"
|
255
|
-
"
|
74
|
+
"Configuration file containing details about how to connect to the cluster and authentication details.": [
|
75
|
+
"配置文件,其中包含有关如何连接到集群的详细信息以及身份验证的详细信息。"
|
256
76
|
],
|
257
|
-
"
|
258
|
-
"
|
77
|
+
"Configuration interval in minutes": [
|
78
|
+
"以分钟为单位的配置间隔"
|
259
79
|
],
|
260
|
-
"
|
261
|
-
"
|
80
|
+
"Configuration name": [
|
81
|
+
"配置名称"
|
262
82
|
],
|
263
|
-
"
|
264
|
-
"
|
83
|
+
"Configuration numeric identifier": [
|
84
|
+
"配置数字识别符"
|
265
85
|
],
|
266
|
-
"
|
267
|
-
"
|
86
|
+
"Configuration script: ": [
|
87
|
+
"配置脚本:"
|
268
88
|
],
|
269
|
-
"Config|
|
270
|
-
"
|
89
|
+
"Config|Interval": [
|
90
|
+
"配置|间隔"
|
271
91
|
],
|
272
92
|
"Config|Last Report": [
|
273
93
|
"配置|最新报告"
|
274
94
|
],
|
275
|
-
"Config|
|
276
|
-
"
|
277
|
-
],
|
278
|
-
"Edit Virt-who Config": [
|
279
|
-
"编辑 Virt-who 配置"
|
95
|
+
"Config|Name": [
|
96
|
+
"配置|名称"
|
280
97
|
],
|
281
|
-
"
|
282
|
-
"
|
98
|
+
"Connection": [
|
99
|
+
"连接"
|
283
100
|
],
|
284
|
-
"
|
285
|
-
"
|
101
|
+
"Container-native virtualization’s fully qualified host name or IP address. In order to connect to the cluster it is required to provide path to kubeconfig which contains connection details and authentication token.": [
|
102
|
+
"容器原生虚拟化的标准主机名或 IP 地址。为了连接到集群,需要提供 kubeconfig 的路径,其中包含连接详细信息和身份验证令牌。"
|
286
103
|
],
|
287
|
-
"
|
288
|
-
"
|
104
|
+
"Copy to clipboard": [
|
105
|
+
"复制到剪贴板"
|
289
106
|
],
|
290
|
-
"
|
291
|
-
"
|
107
|
+
"Count": [
|
108
|
+
"计数"
|
292
109
|
],
|
293
|
-
"
|
294
|
-
"
|
110
|
+
"Create Config": [
|
111
|
+
"创建配置"
|
295
112
|
],
|
296
|
-
"
|
297
|
-
"
|
113
|
+
"Create a virt-who configuration": [
|
114
|
+
"创建 virt-who 配置"
|
298
115
|
],
|
299
|
-
"
|
300
|
-
"
|
116
|
+
"Delete a virt-who configuration": [
|
117
|
+
"删除 virt-who 配置"
|
301
118
|
],
|
302
|
-
"
|
303
|
-
"
|
119
|
+
"Delete virt-who configuration %s?": [
|
120
|
+
"删除 virt-who 配置 %s?"
|
304
121
|
],
|
305
122
|
"Deploy": [
|
306
123
|
"部署"
|
@@ -308,407 +125,344 @@
|
|
308
125
|
"Details": [
|
309
126
|
"详情"
|
310
127
|
],
|
311
|
-
"
|
312
|
-
"
|
313
|
-
],
|
314
|
-
"Filtering": [
|
315
|
-
"过滤"
|
316
|
-
],
|
317
|
-
"Filter Hosts": [
|
318
|
-
"过滤主机"
|
319
|
-
],
|
320
|
-
"Exclude Hosts": [
|
321
|
-
"排除主机"
|
322
|
-
],
|
323
|
-
"Enable debugging output?": [
|
324
|
-
"启用调试输出?"
|
325
|
-
],
|
326
|
-
"HTTP Proxy": [
|
327
|
-
"HTTP 代理"
|
328
|
-
],
|
329
|
-
"Ignore Proxy": [
|
330
|
-
"忽略代理"
|
331
|
-
],
|
332
|
-
"Use either hammer command or the script below to deploy this configuration. Both require root privileges. Run one of them on the target host which has access to katello-host-tools repository and will run virt-who reporting, preferably Foreman host:": [
|
333
|
-
"使用 hammer 命令或下面的脚本来部署此配置。两者都需要 root 特权。在有权访问 Red Hat Satellite Tools 仓库的一个目标主机上运行其中一个,并运行 virt-who 报告,最好在 Foreman 主机上运行:"
|
334
|
-
],
|
335
|
-
"Hammer command: ": [
|
336
|
-
"Hammer 命令:"
|
337
|
-
],
|
338
|
-
"Copy to clipboard": [
|
339
|
-
"复制到剪贴板"
|
340
|
-
],
|
341
|
-
"Configuration script: ": [
|
342
|
-
"配置脚本:"
|
343
|
-
],
|
344
|
-
"On the target virt-who host:": [
|
345
|
-
"在目标 virt-who 主机上:"
|
346
|
-
],
|
347
|
-
"1. Copy this configuration script to a safe directory.": [
|
348
|
-
"1. 将这个配置脚本复制到安全目录。"
|
349
|
-
],
|
350
|
-
"2. Make the script executable and run it.": [
|
351
|
-
"2. 使脚本可执行,并运行脚本。"
|
352
|
-
],
|
353
|
-
"3. Delete the script.": [
|
354
|
-
"3. 删除该脚本。"
|
128
|
+
"Different debug value can't be set per hypervisor, therefore it will affect all other deployed configurations on the host on which this configuration will be deployed.": [
|
129
|
+
"不能为每个管理程序设置不同的调试值,因此它将影响将在其上部署此配置的主机上的所有其他已部署的配置。"
|
355
130
|
],
|
356
131
|
"Download the script": [
|
357
132
|
"下载脚本"
|
358
133
|
],
|
359
|
-
"
|
360
|
-
"
|
361
|
-
],
|
362
|
-
"Specifies that hypervisors will be identified by their <b>hostname</b>, <b>uuid</b> or <b>hwuuid</b>.\\n Note that some virtualization backends don't have all of them implemented.\\n Default is <b>hostname</b>, which provides more meaningful hypervisor\\n names, but can cause duplicated hypervisor registrations if the host is renamed. To avoid that, you can use <b>uuid</b> instead. <b>hwuuid</b> is applicable to esx only.\\n This property is meant to be set up before the initial run of virt-who. Changing it later will result in duplicated entries in the subscription manager.": [
|
363
|
-
"指定 hypervisor 由其 <b>hostname</b>、<b>uuid</b> 或 <b>hwuuid</b> 标识。\\n 注意某些虚拟化后端并未完全实施。\\n 默认为 <b>hostname</b>,它提供更具意义的 hypervisor \\n 名称,但如果主机重命名,则可能造成重复的 hypervisor 注册。为了避免这种情况,可使用 <b>uuid</b> 代替。<b>hwuuid</b> 仅适用于 esx。\\n 此特性应在首次运行 virt-who 之前设置。之后更改将导致订阅管理器中出现重复条目。"
|
364
|
-
],
|
365
|
-
"If you run a hybrid environment, with virtual machines running Red Hat Enterprise Linux and other operating systems, you may want to limit the scope of virt-who’s access to hosts. For example, if some hypervisors host only Microsoft Windows Server instances, there is no benefit in having those hypervisors reported by the virt-who agent.": [
|
366
|
-
"如果您运行混合环境,且虚拟机运行 Red Hat Enterprise Linux 和其他操作系统,您可能想要限制 virt-who 对主机的访问权限范围。例如,如果某些 hypervisor 只托管 Microsoft Windows Server 实例,那么让 virt-who agent 报告这些 hypervisor 没有任何意义。"
|
367
|
-
],
|
368
|
-
"Only hosts which uuid (or hostname or hwuuid, based on <code>hypervisor_id</code>) is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
369
|
-
"仅报告在此选项中以逗号分隔的列表指定了uuid(或主机名或 hwuuid,基于 <code>hypervisor_id</code>)的主机。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
370
|
-
],
|
371
|
-
"Filter hosts": [
|
372
|
-
"过滤主机"
|
373
|
-
],
|
374
|
-
"Hosts which uuid (or hostname or hwuuid, based on <code>hypervisor_id</code>) is specified in comma-separated list in this option will <b>NOT</b> be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
375
|
-
"<b>不报告</b>在此选项中以逗号分隔的列表指定了uuid(或主机名或 hwuuid,基于 <code>hypervisor_id</code>)的主机。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
376
|
-
],
|
377
|
-
"Exclude hosts": [
|
378
|
-
"排除主机"
|
379
|
-
],
|
380
|
-
"Only hosts which cluster ID is specified in comma-separated list in this option will be reported. PowerCLI command to find the domain names in VMware <code>Get-Cluster “ClusterName” | Select ID</code>. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
381
|
-
"只有集群 ID 在这个选项中列出(以逗号分隔的列表)的主机才会报告。PowerCLI 命令在 VMware <code>Get-Cluster \\\"ClusterName\\\" | Select ID</code> 中找到域名。支持通配符和正则表达式,以逗号分开多个记录。如果包含特殊字符(如逗号),则需要将值包括在括号中。在结果配置文件中,所有新行都将被删除,开头和结尾的空字符也会被删除。"
|
382
|
-
],
|
383
|
-
"Filter host parents": [
|
384
|
-
"过滤主机父系统"
|
134
|
+
"Edit": [
|
135
|
+
"编辑"
|
385
136
|
],
|
386
|
-
"
|
387
|
-
"
|
137
|
+
"Edit Virt-who Config": [
|
138
|
+
"编辑 Virt-who 配置"
|
388
139
|
],
|
389
|
-
"
|
390
|
-
"
|
140
|
+
"Enable AHV debug": [
|
141
|
+
"启用 AHV 故障排除"
|
391
142
|
],
|
392
|
-
"
|
393
|
-
"
|
143
|
+
"Enable debugging output": [
|
144
|
+
"启用调试输出"
|
394
145
|
],
|
395
|
-
"
|
396
|
-
"
|
146
|
+
"Enable debugging output?": [
|
147
|
+
"启用调试输出?"
|
397
148
|
],
|
398
|
-
"
|
399
|
-
"
|
149
|
+
"Every 12 hours": [
|
150
|
+
"每 12 小时"
|
400
151
|
],
|
401
|
-
"
|
402
|
-
"
|
152
|
+
"Every 2 days": [
|
153
|
+
"每 2 天"
|
403
154
|
],
|
404
|
-
"
|
405
|
-
"
|
155
|
+
"Every 2 hours": [
|
156
|
+
"每 2 小时"
|
406
157
|
],
|
407
|
-
"
|
408
|
-
"
|
158
|
+
"Every 24 hours": [
|
159
|
+
"每 24 小时"
|
409
160
|
],
|
410
|
-
"
|
411
|
-
"
|
161
|
+
"Every 3 days": [
|
162
|
+
"每 3 天"
|
412
163
|
],
|
413
|
-
"
|
414
|
-
"
|
164
|
+
"Every 4 hours": [
|
165
|
+
"每 4 小时"
|
415
166
|
],
|
416
|
-
"
|
417
|
-
"
|
167
|
+
"Every 8 hours": [
|
168
|
+
"每 8 小时"
|
418
169
|
],
|
419
|
-
"
|
420
|
-
"
|
170
|
+
"Every hour": [
|
171
|
+
"每小时"
|
421
172
|
],
|
422
|
-
"
|
423
|
-
""
|
173
|
+
"Exclude Hosts": [
|
174
|
+
"排除主机"
|
424
175
|
],
|
425
|
-
"
|
426
|
-
"
|
176
|
+
"Exclude host parents": [
|
177
|
+
"排除主机父系统"
|
427
178
|
],
|
428
|
-
"
|
429
|
-
""
|
179
|
+
"Exclude hosts": [
|
180
|
+
"排除主机"
|
430
181
|
],
|
431
|
-
"
|
432
|
-
""
|
182
|
+
"Exclude hosts which cluster ID is specified in comma-separated list in this option will <b>NOT</b> be reported. PowerCLI command to find the domain names in VMware <code>Get-Cluster “ClusterName” | Select ID</code>. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
183
|
+
"排除集群 ID 在这个选项中列出(以逗号分隔的列表)的主机,<b>不会</b>报告这些主机。PowerCLI 命令在 VMware <code>Get-Cluster \\\"ClusterName\\\" | Select ID</code> 中找到域名。支持通配符和正则表达式,以逗号分开多个记录。如果包含特殊字符(如逗号),则需要将值包括在括号中。在结果配置文件中,所有新行都将被删除,开头和结尾的空字符也会被删除。"
|
433
184
|
],
|
434
|
-
"
|
435
|
-
""
|
185
|
+
"Filter Hosts": [
|
186
|
+
"过滤主机"
|
436
187
|
],
|
437
|
-
"
|
438
|
-
""
|
188
|
+
"Filter host parents": [
|
189
|
+
"过滤主机父系统"
|
439
190
|
],
|
440
|
-
"
|
441
|
-
"
|
191
|
+
"Filter hosts": [
|
192
|
+
"过滤主机"
|
442
193
|
],
|
443
|
-
"
|
444
|
-
"
|
194
|
+
"Filtering": [
|
195
|
+
"过滤"
|
445
196
|
],
|
446
|
-
"
|
447
|
-
""
|
197
|
+
"Foreman server FQDN": [
|
198
|
+
"Foreman 服务器 FQDN"
|
448
199
|
],
|
449
|
-
"
|
450
|
-
"
|
200
|
+
"Foreman server’s fully-qualified host name, for example: foreman.example.com": [
|
201
|
+
"Foreman 服务器的完全限定主机名,例如:foreman.example.com"
|
451
202
|
],
|
452
|
-
"
|
453
|
-
"
|
203
|
+
"Fully qualified host name or IP address of the hypervisor": [
|
204
|
+
"Hypervisor 的完全限定主机名或 IP 地址"
|
454
205
|
],
|
455
|
-
"
|
456
|
-
"
|
206
|
+
"General information": [
|
207
|
+
"通用信息"
|
457
208
|
],
|
458
|
-
"
|
459
|
-
"
|
209
|
+
"HTTP Proxy": [
|
210
|
+
"HTTP 代理"
|
460
211
|
],
|
461
|
-
"
|
462
|
-
"
|
212
|
+
"HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.": [
|
213
|
+
"应当用于 virt-who 运行所在服务器和 hypervisor 及虚拟化管理器之间通信的 HTTP 代理服务器。"
|
463
214
|
],
|
464
|
-
"
|
465
|
-
"
|
215
|
+
"HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers. Leave this blank if no proxy is used.": [
|
216
|
+
"应当用于 virt-who 运行所在服务器和 hypervisor 及虚拟管理器之间通信的 HTTP 代理服务器。如果未使用代理服务器,则留空。"
|
466
217
|
],
|
467
|
-
"
|
468
|
-
"
|
218
|
+
"Hammer command: ": [
|
219
|
+
"Hammer 命令:"
|
220
|
+
],
|
221
|
+
"Help": [
|
222
|
+
"帮助"
|
469
223
|
],
|
470
|
-
"
|
471
|
-
"
|
224
|
+
"Hosts which uuid (or hostname or hwuuid, based on <code>hypervisor_id</code>) is specified in comma-separated list in this option will <b>NOT</b> be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
225
|
+
"<b>不报告</b>在此选项中以逗号分隔的列表指定了uuid(或主机名或 hwuuid,基于 <code>hypervisor_id</code>)的主机。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
472
226
|
],
|
473
|
-
"
|
474
|
-
"
|
227
|
+
"How often to check connected hypervisors for changes? Also affects how often a mapping is reported. The recommended value for most environments is every two hours. Different interval can't be set per hypervisor, therefore it will affect all other deployed configurations on the host on which this configuration will be deployed.": [
|
228
|
+
"检查连接的虚拟机管理程序是否有更改的频率?同时还影响报告映射的频率。对于大多数环境,建议值为每两个小时一次。不能为每个虚拟机管理程序设置不同的间隔,因此它将影响将在其上部署此配置的主机上的所有其他已部署的配置。"
|
475
229
|
],
|
476
|
-
"
|
477
|
-
"
|
230
|
+
"Hypervisor ID": [
|
231
|
+
"Hypervisor ID"
|
478
232
|
],
|
479
|
-
"
|
480
|
-
"
|
233
|
+
"Hypervisor Password": [
|
234
|
+
"Hypervisor 密码"
|
481
235
|
],
|
482
|
-
"
|
483
|
-
"
|
236
|
+
"Hypervisor Server": [
|
237
|
+
"Hypervisor 服务器"
|
484
238
|
],
|
485
|
-
"
|
486
|
-
"
|
239
|
+
"Hypervisor Type": [
|
240
|
+
"Hypervisor 类型"
|
487
241
|
],
|
488
|
-
"
|
489
|
-
"
|
242
|
+
"Hypervisor Username": [
|
243
|
+
"Hypervisor 用户名"
|
490
244
|
],
|
491
|
-
"
|
492
|
-
"
|
245
|
+
"Hypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
|
246
|
+
"Hypervisor 黑名单,仅在过滤模式设置为 2 时适用。支持通配符和正则表达式,必须用逗号分隔多项记录。"
|
493
247
|
],
|
494
|
-
"
|
495
|
-
"
|
248
|
+
"Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
|
249
|
+
"Hypervisor 过滤模式 %{unlimited} 表示没有过滤,%{whitelist} 表示白名单,%{blacklist} 代表黑名单"
|
496
250
|
],
|
497
|
-
"
|
498
|
-
"
|
251
|
+
"Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
|
252
|
+
"Hypervisor 密码,除 libvirt/kubevirt 以外的所有 hypervisor 类型都需要"
|
499
253
|
],
|
500
|
-
"
|
501
|
-
"
|
254
|
+
"Hypervisor type": [
|
255
|
+
"Hypervisor 类型"
|
502
256
|
],
|
503
|
-
"
|
504
|
-
"
|
257
|
+
"Hypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
|
258
|
+
"Hypervisor 白名单,仅在过滤模式设置为 1 时适用。支持通配符和正则表达式,必须用逗号分隔多项记录。"
|
505
259
|
],
|
506
|
-
"
|
507
|
-
"
|
260
|
+
"If you run a hybrid environment, with virtual machines running Red Hat Enterprise Linux and other operating systems, you may want to limit the scope of virt-who’s access to hosts. For example, if some hypervisors host only Microsoft Windows Server instances, there is no benefit in having those hypervisors reported by the virt-who agent.": [
|
261
|
+
"如果您运行混合环境,且虚拟机运行 Red Hat Enterprise Linux 和其他操作系统,您可能想要限制 virt-who 对主机的访问权限范围。例如,如果某些 hypervisor 只托管 Microsoft Windows Server 实例,那么让 virt-who agent 报告这些 hypervisor 没有任何意义。"
|
508
262
|
],
|
509
|
-
"
|
510
|
-
"
|
263
|
+
"Ignore Proxy": [
|
264
|
+
"忽略代理"
|
511
265
|
],
|
512
|
-
"
|
513
|
-
"
|
266
|
+
"Ignore proxy": [
|
267
|
+
"忽略代理服务器"
|
514
268
|
],
|
515
|
-
"
|
516
|
-
"
|
269
|
+
"Ignore proxy. A comma-separated list of hostnames or domains or ip addresses to ignore proxy settings for. Optionally this may be set to * to bypass proxy settings for all hostnames domains or ip addresses.": [
|
270
|
+
"忽略代理服务器。忽略代理服务器设置的主机名、域或 ip 地址逗号分隔列表。可选择性地设置为 *,以便为所有主机名、域或 ip 地址跳过代理服务器设置。"
|
517
271
|
],
|
518
|
-
"
|
519
|
-
"
|
272
|
+
"Interval": [
|
273
|
+
"间隔"
|
520
274
|
],
|
521
|
-
"
|
522
|
-
"
|
275
|
+
"Interval was not provided": [
|
276
|
+
"未提供间隔"
|
523
277
|
],
|
524
|
-
"
|
525
|
-
"
|
278
|
+
"Latest Configurations Without Change": [
|
279
|
+
"无更改的最新配置"
|
526
280
|
],
|
527
|
-
"
|
528
|
-
"
|
281
|
+
"Libvirt server’s fully qualified host name or IP address. You can also specify preferred schema, for example: <code>qemu+ssh://libvirt.example.com/system</code>. Make sure you setup root's SSH key on target host for a user specified at hypervisor username field": [
|
282
|
+
"Libvirt 服务器的完全限定主机名或 IP 地址。您也可以指定首选的方案,例如:<code>qemu+ssh://libvirt.example.com/system</code>。确保您在目标主机上为 hypervisor 用户名字段指定的用户设置根的 SSH 密钥"
|
529
283
|
],
|
530
|
-
"
|
531
|
-
"
|
284
|
+
"List of virt-who configurations": [
|
285
|
+
"virt-who 配置列表"
|
532
286
|
],
|
533
|
-
"
|
534
|
-
"
|
287
|
+
"List of virt-who configurations per organization": [
|
288
|
+
"每个机构的 virt-who 配置列表"
|
535
289
|
],
|
536
|
-
"
|
537
|
-
"
|
290
|
+
"Microsoft Hyper-V fully qualified host name or IP address.": [
|
291
|
+
"Microsoft Hyper-V fully 的完全限定主机名或 IP 地址。"
|
538
292
|
],
|
539
|
-
"
|
540
|
-
"
|
293
|
+
"Name": [
|
294
|
+
"名称"
|
541
295
|
],
|
542
|
-
"
|
543
|
-
"
|
296
|
+
"Name of this configuration, e.g. the name of the hypervisor": [
|
297
|
+
"此配置的名称,例如 hypervisor 的名称"
|
544
298
|
],
|
545
|
-
"
|
546
|
-
"
|
299
|
+
"New Config": [
|
300
|
+
"新建配置"
|
547
301
|
],
|
548
|
-
"
|
549
|
-
"
|
302
|
+
"New Virt-who Config": [
|
303
|
+
"新建 Virt-who 配置"
|
550
304
|
],
|
551
|
-
"
|
552
|
-
"
|
305
|
+
"Newer version of virt-who is required, minimum version is %s": [
|
306
|
+
"需要更高的 virt-who 版本,最低版本为 %s"
|
553
307
|
],
|
554
|
-
"
|
555
|
-
"
|
308
|
+
"No Change": [
|
309
|
+
"無變更"
|
556
310
|
],
|
557
|
-
"
|
558
|
-
"
|
311
|
+
"No Report Yet": [
|
312
|
+
"尚没有报告"
|
559
313
|
],
|
560
|
-
"
|
561
|
-
"
|
314
|
+
"No Reports": [
|
315
|
+
"没有报告"
|
562
316
|
],
|
563
|
-
"
|
564
|
-
"
|
317
|
+
"No change": [
|
318
|
+
"不更改"
|
565
319
|
],
|
566
|
-
"
|
567
|
-
"
|
320
|
+
"No configuration found": [
|
321
|
+
"找不到配置"
|
568
322
|
],
|
569
|
-
"
|
570
|
-
"
|
323
|
+
"Nutanix AHV’s IP address.": [
|
324
|
+
"Nutanix AHV 的 IP 地址。"
|
571
325
|
],
|
572
|
-
"
|
573
|
-
"
|
326
|
+
"OK": [
|
327
|
+
"好"
|
574
328
|
],
|
575
|
-
"
|
576
|
-
"
|
329
|
+
"On the target virt-who host:": [
|
330
|
+
"在目标 virt-who 主机上:"
|
577
331
|
],
|
578
|
-
"
|
579
|
-
"
|
332
|
+
"On this page you can define virt-who configurations for your hypervisors.": [
|
333
|
+
"在本页面,您可以为您的 hypervisor 定义 virt-who 配置。"
|
580
334
|
],
|
581
|
-
"
|
582
|
-
"
|
335
|
+
"One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
|
336
|
+
"一个 virt-who 配置代表 /etc/virt-who.d 目录中的一个配置文件,映射至单个 hypervisor、机构和生命周期环境。"
|
583
337
|
],
|
584
|
-
"
|
585
|
-
"
|
338
|
+
"Only hosts which cluster ID is specified in comma-separated list in this option will be reported. PowerCLI command to find the domain names in VMware <code>Get-Cluster “ClusterName” | Select ID</code>. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
339
|
+
"只有集群 ID 在这个选项中列出(以逗号分隔的列表)的主机才会报告。PowerCLI 命令在 VMware <code>Get-Cluster \\\"ClusterName\\\" | Select ID</code> 中找到域名。支持通配符和正则表达式,以逗号分开多个记录。如果包含特殊字符(如逗号),则需要将值包括在括号中。在结果配置文件中,所有新行都将被删除,开头和结尾的空字符也会被删除。"
|
586
340
|
],
|
587
|
-
"
|
588
|
-
"
|
341
|
+
"Only hosts which uuid (or hostname or hwuuid, based on <code>hypervisor_id</code>) is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.": [
|
342
|
+
"仅报告在此选项中以逗号分隔的列表指定了uuid(或主机名或 hwuuid,基于 <code>hypervisor_id</code>)的主机。支持通配符和正则表达式,多个记录必须用逗号分隔。如果该值包含逗号等特殊字符,则将其放在双引号中。所有新行字符将在生成的配置文件中删除,空格从开头和结尾删除。"
|
589
343
|
],
|
590
|
-
"
|
591
|
-
"
|
344
|
+
"Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
|
345
|
+
"启用 AHV 内部故障排除需要 Option Enable debugging output。它会在两个选项都启用时提供额外的 AHV 调试信息"
|
592
346
|
],
|
593
|
-
"
|
594
|
-
"
|
347
|
+
"Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
|
348
|
+
"启用 AHV 内部故障排除需要 Option Enable debugging output。它会在两个选项都启用时提供额外的 AHV 调试信息 "
|
595
349
|
],
|
596
|
-
"
|
597
|
-
"
|
350
|
+
"Organization of the virt-who configuration": [
|
351
|
+
"virt-who 配置机构"
|
598
352
|
],
|
599
|
-
"
|
600
|
-
"
|
353
|
+
"Overview": [
|
354
|
+
"概况"
|
601
355
|
],
|
602
|
-
"
|
603
|
-
"
|
356
|
+
"Owner": [
|
357
|
+
"所有者"
|
604
358
|
],
|
605
|
-
"
|
606
|
-
"
|
359
|
+
"Owner was not provided": [
|
360
|
+
"未提供所有者"
|
607
361
|
],
|
608
|
-
"
|
609
|
-
"
|
362
|
+
"Path to kubeconfig file": [
|
363
|
+
"到 kubeconfig 文件的路径"
|
610
364
|
],
|
611
|
-
"
|
612
|
-
"
|
365
|
+
"Prism Central": [
|
366
|
+
"Prism Central"
|
613
367
|
],
|
614
|
-
"
|
615
|
-
"
|
368
|
+
"Prism Element": [
|
369
|
+
"Prism Element"
|
616
370
|
],
|
617
|
-
"
|
618
|
-
"
|
371
|
+
"Prism Flavor": [
|
372
|
+
"Prism Flavor"
|
619
373
|
],
|
620
|
-
"
|
621
|
-
"
|
374
|
+
"Renders a deploy script for the specified virt-who configuration": [
|
375
|
+
"为指定的 virt-who 配置提供部署脚本"
|
622
376
|
],
|
623
|
-
"
|
624
|
-
"
|
377
|
+
"Schedule": [
|
378
|
+
"调度"
|
625
379
|
],
|
626
|
-
"
|
627
|
-
"
|
380
|
+
"Select the Prism flavor you are connecting to": [
|
381
|
+
"选择您要连接到的 Prism 类别"
|
628
382
|
],
|
629
|
-
"
|
630
|
-
"
|
383
|
+
"Show a virt-who configuration": [
|
384
|
+
"显示 virt-who 配置"
|
631
385
|
],
|
632
|
-
"
|
633
|
-
"
|
386
|
+
"Specifies how the hypervisor will be identified.": [
|
387
|
+
"指定如何识别 hypervisor。"
|
634
388
|
],
|
635
|
-
"
|
636
|
-
"
|
389
|
+
"Specifies that hypervisors will be identified by their <b>hostname</b>, <b>uuid</b> or <b>hwuuid</b>.\\n Note that some virtualization backends don't have all of them implemented.\\n Default is <b>hostname</b>, which provides more meaningful hypervisor\\n names, but can cause duplicated hypervisor registrations if the host is renamed. To avoid that, you can use <b>uuid</b> instead. <b>hwuuid</b> is applicable to esx only.\\n This property is meant to be set up before the initial run of virt-who. Changing it later will result in duplicated entries in the subscription manager.": [
|
390
|
+
"指定 hypervisor 由其 <b>hostname</b>、<b>uuid</b> 或 <b>hwuuid</b> 标识。\\n 注意某些虚拟化后端并未完全实施。\\n 默认为 <b>hostname</b>,它提供更具意义的 hypervisor \\n 名称,但如果主机重命名,则可能造成重复的 hypervisor 注册。为了避免这种情况,可使用 <b>uuid</b> 代替。<b>hwuuid</b> 仅适用于 esx。\\n 此特性应在首次运行 virt-who 之前设置。之后更改将导致订阅管理器中出现重复条目。"
|
637
391
|
],
|
638
|
-
"
|
639
|
-
"
|
392
|
+
"Status": [
|
393
|
+
"状态"
|
640
394
|
],
|
641
|
-
"
|
642
|
-
"
|
395
|
+
"Success": [
|
396
|
+
"成功"
|
643
397
|
],
|
644
|
-
"
|
645
|
-
"
|
398
|
+
"The configuration was not deployed yet or the virt-who was unable to report the status": [
|
399
|
+
"尚未部署配置,或者 virt-who 无法报告状态"
|
646
400
|
],
|
647
|
-
"
|
648
|
-
"
|
401
|
+
"The virt-who report arrived within the interval": [
|
402
|
+
"在间隔期间收到 virt-who 报告"
|
649
403
|
],
|
650
|
-
"
|
651
|
-
"
|
404
|
+
"The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
|
405
|
+
"未在间隔期间收到 virt-who 报告,表示 hypervisor 无更改"
|
652
406
|
],
|
653
|
-
"
|
654
|
-
"
|
407
|
+
"To define a new configuration, click the New Config button and fill in the form. After you provide all required information a virt-who configuration script will be generated. You could either install it manually by copying the script or deploy it on a selected target host through Remote Execution.": [
|
408
|
+
"如要定义新配置,请点击 New Config 按钮,填写表格。当您提供所有所需信息之后,会生成 virt-who 配置脚本。您可以通过复制脚本进行手动安装,也可以通过 Remote Execution 在选定的目标主机上部署。"
|
655
409
|
],
|
656
|
-
"
|
657
|
-
"
|
410
|
+
"Total Configurations": [
|
411
|
+
"全部配置"
|
658
412
|
],
|
659
|
-
"
|
660
|
-
"
|
413
|
+
"Unable to create sysconfig file": [
|
414
|
+
"无法创建 sysconfig 文件"
|
661
415
|
],
|
662
|
-
"
|
663
|
-
"
|
416
|
+
"Unable to create virt-who config file": [
|
417
|
+
"无法创建 virt-who 配置文件"
|
664
418
|
],
|
665
|
-
"
|
666
|
-
"
|
419
|
+
"Unable to enable virt-who service using systemctl": [
|
420
|
+
"无法使用 systemctl 启用 virt-who 服务"
|
667
421
|
],
|
668
|
-
"
|
669
|
-
"
|
422
|
+
"Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
|
423
|
+
"无法安装 virt-who 软件包,确保已正确订阅主机,且具备访问 katello-host-tools 的访问权限"
|
670
424
|
],
|
671
|
-
"
|
672
|
-
"
|
425
|
+
"Unable to start virt-who service, please see virt-who logs for more details": [
|
426
|
+
"无法开始 virt-who 服务,请查看 virt-who 日志了解详情"
|
673
427
|
],
|
674
|
-
"
|
675
|
-
"
|
428
|
+
"Unknown": [
|
429
|
+
"未知"
|
676
430
|
],
|
677
|
-
"
|
678
|
-
"
|
431
|
+
"Unknown configuration status": [
|
432
|
+
"未知配置状态"
|
679
433
|
],
|
680
|
-
"
|
681
|
-
"
|
434
|
+
"Unknown configuration status, caused by unexpected conditions": [
|
435
|
+
"未知配置状态,由意外情况造成"
|
682
436
|
],
|
683
|
-
"
|
684
|
-
"
|
437
|
+
"Unlimited": [
|
438
|
+
"无限制"
|
685
439
|
],
|
686
|
-
"Update
|
687
|
-
"
|
440
|
+
"Update a virt-who configuration": [
|
441
|
+
"更新 virt-who 配置"
|
688
442
|
],
|
689
|
-
"
|
690
|
-
"
|
443
|
+
"Use either hammer command or the script below to deploy this configuration. Both require root privileges. Run one of them on the target host which has access to katello-host-tools repository and will run virt-who reporting, preferably Foreman host:": [
|
444
|
+
"使用 hammer 命令或下面的脚本来部署此配置。两者都需要 root 特权。在有权访问 Red Hat Satellite Tools 仓库的一个目标主机上运行其中一个,并运行 virt-who 报告,最好在 Foreman 主机上运行:"
|
691
445
|
],
|
692
|
-
"
|
693
|
-
"
|
446
|
+
"VMware vCenter server’s fully qualified host name or IP address.": [
|
447
|
+
"VMware vCenter 服务器的完全限定主机名或 IP 地址。"
|
694
448
|
],
|
695
|
-
"
|
696
|
-
"
|
449
|
+
"Virt-who Configs Status": [
|
450
|
+
"Virt-who 配置状态"
|
697
451
|
],
|
698
|
-
"
|
699
|
-
"
|
452
|
+
"Virt-who Configuration %s": [
|
453
|
+
"Virt-who 配置 %s"
|
700
454
|
],
|
701
|
-
"
|
702
|
-
"
|
455
|
+
"Virt-who Configurations": [
|
456
|
+
"Virt-who 配置"
|
703
457
|
],
|
704
|
-
"
|
705
|
-
"
|
458
|
+
"Virt-who Configurations Status": [
|
459
|
+
"Virt-who 配置状态"
|
706
460
|
],
|
707
|
-
"
|
708
|
-
"
|
461
|
+
"Whitelist": [
|
462
|
+
"白名单"
|
709
463
|
],
|
710
|
-
"
|
711
|
-
"
|
464
|
+
"every %s hours": [
|
465
|
+
"每 %s 小时"
|
712
466
|
]
|
713
467
|
}
|
714
468
|
}
|