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.
Files changed (121) hide show
  1. checksums.yaml +4 -4
  2. data/app/assets/javascripts/foreman_virt_who_configure/locale/bn/foreman_virt_who_configure.js +155 -170
  3. data/app/assets/javascripts/foreman_virt_who_configure/locale/bn_IN/foreman_virt_who_configure.js +164 -179
  4. data/app/assets/javascripts/foreman_virt_who_configure/locale/ca/foreman_virt_who_configure.js +177 -213
  5. data/app/assets/javascripts/foreman_virt_who_configure/locale/cs_CZ/foreman_virt_who_configure.js +263 -392
  6. data/app/assets/javascripts/foreman_virt_who_configure/locale/de/foreman_virt_who_configure.js +273 -489
  7. data/app/assets/javascripts/foreman_virt_who_configure/locale/de_DE/foreman_virt_who_configure.js +157 -163
  8. data/app/assets/javascripts/foreman_virt_who_configure/locale/el/foreman_virt_who_configure.js +179 -239
  9. data/app/assets/javascripts/foreman_virt_who_configure/locale/en/foreman_virt_who_configure.js +2 -462
  10. data/app/assets/javascripts/foreman_virt_who_configure/locale/en_GB/foreman_virt_who_configure.js +161 -182
  11. data/app/assets/javascripts/foreman_virt_who_configure/locale/es/foreman_virt_who_configure.js +273 -489
  12. data/app/assets/javascripts/foreman_virt_who_configure/locale/fr/foreman_virt_who_configure.js +283 -529
  13. data/app/assets/javascripts/foreman_virt_who_configure/locale/gl/foreman_virt_who_configure.js +167 -185
  14. data/app/assets/javascripts/foreman_virt_who_configure/locale/gu/foreman_virt_who_configure.js +166 -184
  15. data/app/assets/javascripts/foreman_virt_who_configure/locale/he_IL/foreman_virt_who_configure.js +154 -157
  16. data/app/assets/javascripts/foreman_virt_who_configure/locale/hi/foreman_virt_who_configure.js +164 -179
  17. data/app/assets/javascripts/foreman_virt_who_configure/locale/it/foreman_virt_who_configure.js +175 -268
  18. data/app/assets/javascripts/foreman_virt_who_configure/locale/ja/foreman_virt_who_configure.js +282 -528
  19. data/app/assets/javascripts/foreman_virt_who_configure/locale/ka/foreman_virt_who_configure.js +280 -532
  20. data/app/assets/javascripts/foreman_virt_who_configure/locale/kn/foreman_virt_who_configure.js +164 -179
  21. data/app/assets/javascripts/foreman_virt_who_configure/locale/ko/foreman_virt_who_configure.js +291 -420
  22. data/app/assets/javascripts/foreman_virt_who_configure/locale/mr/foreman_virt_who_configure.js +164 -179
  23. data/app/assets/javascripts/foreman_virt_who_configure/locale/nl_NL/foreman_virt_who_configure.js +161 -176
  24. data/app/assets/javascripts/foreman_virt_who_configure/locale/or/foreman_virt_who_configure.js +164 -179
  25. data/app/assets/javascripts/foreman_virt_who_configure/locale/pa/foreman_virt_who_configure.js +164 -179
  26. data/app/assets/javascripts/foreman_virt_who_configure/locale/pl/foreman_virt_who_configure.js +167 -188
  27. data/app/assets/javascripts/foreman_virt_who_configure/locale/pt/foreman_virt_who_configure.js +150 -153
  28. data/app/assets/javascripts/foreman_virt_who_configure/locale/pt_BR/foreman_virt_who_configure.js +274 -490
  29. data/app/assets/javascripts/foreman_virt_who_configure/locale/ru/foreman_virt_who_configure.js +178 -307
  30. data/app/assets/javascripts/foreman_virt_who_configure/locale/sl/foreman_virt_who_configure.js +154 -163
  31. data/app/assets/javascripts/foreman_virt_who_configure/locale/sv_SE/foreman_virt_who_configure.js +167 -185
  32. data/app/assets/javascripts/foreman_virt_who_configure/locale/ta/foreman_virt_who_configure.js +155 -170
  33. data/app/assets/javascripts/foreman_virt_who_configure/locale/ta_IN/foreman_virt_who_configure.js +164 -179
  34. data/app/assets/javascripts/foreman_virt_who_configure/locale/te/foreman_virt_who_configure.js +164 -179
  35. data/app/assets/javascripts/foreman_virt_who_configure/locale/tr/foreman_virt_who_configure.js +152 -155
  36. data/app/assets/javascripts/foreman_virt_who_configure/locale/zh_CN/foreman_virt_who_configure.js +283 -529
  37. data/app/assets/javascripts/foreman_virt_who_configure/locale/zh_TW/foreman_virt_who_configure.js +176 -305
  38. data/lib/foreman_virt_who_configure/version.rb +1 -1
  39. data/locale/Makefile +12 -2
  40. data/locale/bn/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  41. data/locale/bn/foreman_virt_who_configure.po +5 -4
  42. data/locale/bn_IN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  43. data/locale/bn_IN/foreman_virt_who_configure.po +5 -4
  44. data/locale/ca/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  45. data/locale/ca/foreman_virt_who_configure.po +6 -5
  46. data/locale/cs_CZ/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  47. data/locale/cs_CZ/foreman_virt_who_configure.po +2 -1
  48. data/locale/de/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  49. data/locale/de/foreman_virt_who_configure.po +4 -3
  50. data/locale/de_DE/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  51. data/locale/de_DE/foreman_virt_who_configure.po +5 -4
  52. data/locale/el/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  53. data/locale/el/foreman_virt_who_configure.po +6 -5
  54. data/locale/en/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  55. data/locale/en/foreman_virt_who_configure.po +0 -468
  56. data/locale/en_GB/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  57. data/locale/en_GB/foreman_virt_who_configure.po +10 -9
  58. data/locale/es/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  59. data/locale/es/foreman_virt_who_configure.po +2 -1
  60. data/locale/foreman_virt_who_configure.pot +4 -4
  61. data/locale/fr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  62. data/locale/fr/foreman_virt_who_configure.po +10 -8
  63. data/locale/gl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  64. data/locale/gl/foreman_virt_who_configure.po +6 -5
  65. data/locale/gu/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  66. data/locale/gu/foreman_virt_who_configure.po +5 -4
  67. data/locale/he_IL/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  68. data/locale/he_IL/foreman_virt_who_configure.po +4 -3
  69. data/locale/hi/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  70. data/locale/hi/foreman_virt_who_configure.po +5 -4
  71. data/locale/it/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  72. data/locale/it/foreman_virt_who_configure.po +8 -8
  73. data/locale/ja/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  74. data/locale/ja/foreman_virt_who_configure.po +10 -7
  75. data/locale/ka/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  76. data/locale/ka/foreman_virt_who_configure.po +6 -5
  77. data/locale/kn/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  78. data/locale/kn/foreman_virt_who_configure.po +5 -4
  79. data/locale/ko/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  80. data/locale/ko/foreman_virt_who_configure.po +149 -141
  81. data/locale/mr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  82. data/locale/mr/foreman_virt_who_configure.po +5 -4
  83. data/locale/nl_NL/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  84. data/locale/nl_NL/foreman_virt_who_configure.po +7 -6
  85. data/locale/or/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  86. data/locale/or/foreman_virt_who_configure.po +5 -4
  87. data/locale/pa/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  88. data/locale/pa/foreman_virt_who_configure.po +5 -4
  89. data/locale/pl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  90. data/locale/pl/foreman_virt_who_configure.po +7 -6
  91. data/locale/pt/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  92. data/locale/pt/foreman_virt_who_configure.po +2 -1
  93. data/locale/pt_BR/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  94. data/locale/pt_BR/foreman_virt_who_configure.po +3 -2
  95. data/locale/ru/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  96. data/locale/ru/foreman_virt_who_configure.po +8 -7
  97. data/locale/sl/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  98. data/locale/sl/foreman_virt_who_configure.po +5 -4
  99. data/locale/sv_SE/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  100. data/locale/sv_SE/foreman_virt_who_configure.po +6 -5
  101. data/locale/ta/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  102. data/locale/ta/foreman_virt_who_configure.po +5 -4
  103. data/locale/ta_IN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  104. data/locale/ta_IN/foreman_virt_who_configure.po +5 -4
  105. data/locale/te/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  106. data/locale/te/foreman_virt_who_configure.po +5 -4
  107. data/locale/tr/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  108. data/locale/tr/foreman_virt_who_configure.po +2 -1
  109. data/locale/zh_CN/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  110. data/locale/zh_CN/foreman_virt_who_configure.po +14 -11
  111. data/locale/zh_TW/LC_MESSAGES/foreman_virt_who_configure.mo +0 -0
  112. data/locale/zh_TW/foreman_virt_who_configure.po +7 -6
  113. metadata +2 -10
  114. data/locale/cs_CZ/foreman_virt_who_configure.edit.po +0 -780
  115. data/locale/de/foreman_virt_who_configure.edit.po +0 -916
  116. data/locale/es/foreman_virt_who_configure.edit.po +0 -911
  117. data/locale/fr/foreman_virt_who_configure.edit.po +0 -936
  118. data/locale/ja/foreman_virt_who_configure.edit.po +0 -843
  119. data/locale/ka/foreman_virt_who_configure.edit.po +0 -894
  120. data/locale/pt_BR/foreman_virt_who_configure.edit.po +0 -903
  121. data/locale/zh_CN/foreman_virt_who_configure.edit.po +0 -825
@@ -3,11 +3,11 @@
3
3
  "locale_data": {
4
4
  "foreman_virt_who_configure": {
5
5
  "": {
6
- "Project-Id-Version": "foreman_virt_who_configure 0.5.17",
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": "KotUchoniy <yosho1@yandex.ru>, 2021",
10
- "Language-Team": "Russian (https://www.transifex.com/foreman/teams/114/ru/)",
9
+ "Last-Translator": "Bryan Kearney <bryan.kearney@gmail.com>, 2023",
10
+ "Language-Team": "Russian (https://app.transifex.com/foreman/teams/114/ru/)",
11
11
  "MIME-Version": "1.0",
12
12
  "Content-Type": "text/plain; charset=UTF-8",
13
13
  "Content-Transfer-Encoding": "8bit",
@@ -17,154 +17,148 @@
17
17
  "domain": "foreman_virt_who_configure",
18
18
  "plural_forms": "nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);"
19
19
  },
20
- "List of virt-who configurations": [
20
+ "1. Copy this configuration script to a safe directory.": [
21
21
  ""
22
22
  ],
23
- "List of virt-who configurations per organization": [
23
+ "2. Make the script executable and run it.": [
24
24
  ""
25
25
  ],
26
- "Show a virt-who configuration": [
26
+ "3. Delete the script.": [
27
27
  ""
28
28
  ],
29
- "Renders a deploy script for the specified virt-who configuration": [
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
30
  ""
31
31
  ],
32
- "Configuration name": [
32
+ "A plugin to make virt-who configuration easy": [
33
33
  ""
34
34
  ],
35
- "Configuration interval in minutes": [
35
+ "Account name by which virt-who is to connect to Nutanix AHV.": [
36
36
  ""
37
37
  ],
38
- "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
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
39
  ""
40
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.": [
41
+ "Account name by which virt-who is to connect to the hypervisor.": [
42
42
  ""
43
43
  ],
44
- "Hypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
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.": [
45
45
  ""
46
46
  ],
47
- "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.": [
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.": [
48
48
  ""
49
49
  ],
50
- "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.": [
50
+ "Account password by which virt-who is to connect to the hypervisor instance.": [
51
51
  ""
52
52
  ],
53
- "Specifies how the hypervisor will be identified.": [
54
- ""
53
+ "Actions": [
54
+ "Действия"
55
55
  ],
56
- "Hypervisor type": [
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
57
  ""
58
58
  ],
59
- "Fully qualified host name or IP address of the hypervisor": [
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
60
  ""
61
61
  ],
62
- "Account name by which virt-who is to connect to the hypervisor.": [
62
+ "Blacklist": [
63
63
  ""
64
64
  ],
65
- "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
66
- ""
65
+ "Configs": [
66
+ "Конфигурация"
67
67
  ],
68
- "Foreman server FQDN": [
68
+ "Configuration Status": [
69
69
  ""
70
70
  ],
71
- "Enable debugging output": [
71
+ "Configuration file containing details about how to connect to the cluster and authentication details": [
72
72
  ""
73
73
  ],
74
74
  "Configuration file containing details about how to connect to the cluster and authentication details.": [
75
75
  ""
76
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.": [
77
+ "Configuration interval in minutes": [
78
78
  ""
79
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.": [
80
+ "Configuration name": [
81
81
  ""
82
82
  ],
83
- "Organization of the virt-who configuration": [
83
+ "Configuration numeric identifier": [
84
84
  ""
85
85
  ],
86
- "Select the Prism flavor you are connecting to": [
86
+ "Configuration script: ": [
87
87
  ""
88
88
  ],
89
- "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
89
+ "Config|Interval": [
90
90
  ""
91
91
  ],
92
- "Create a virt-who configuration": [
92
+ "Config|Last Report": [
93
93
  ""
94
94
  ],
95
- "Update a virt-who configuration": [
95
+ "Config|Name": [
96
96
  ""
97
97
  ],
98
- "Configuration numeric identifier": [
99
- ""
98
+ "Connection": [
99
+ "Соединение"
100
100
  ],
101
- "Delete a virt-who configuration": [
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
102
  ""
103
103
  ],
104
+ "Copy to clipboard": [
105
+ "Скопировано в буфер обмена"
106
+ ],
107
+ "Count": [
108
+ "Счётчик"
109
+ ],
104
110
  "Create Config": [
105
111
  ""
106
112
  ],
107
- "New Config": [
113
+ "Create a virt-who configuration": [
108
114
  ""
109
115
  ],
110
- "Help": [
111
- "Справка"
112
- ],
113
- "VMware vCenter server’s fully qualified host name or IP address.": [
116
+ "Delete a virt-who configuration": [
114
117
  ""
115
118
  ],
116
- "Microsoft Hyper-V fully qualified host name or IP address.": [
119
+ "Delete virt-who configuration %s?": [
117
120
  ""
118
121
  ],
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": [
122
+ "Deploy": [
120
123
  ""
121
124
  ],
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
- ""
125
+ "Details": [
126
+ "Свойства"
124
127
  ],
125
- "Nutanix AHV’s IP address.": [
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.": [
126
129
  ""
127
130
  ],
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.": [
131
+ "Download the script": [
129
132
  ""
130
133
  ],
131
- "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
- ""
134
+ "Edit": [
135
+ "Правка"
133
136
  ],
134
- "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.": [
137
+ "Edit Virt-who Config": [
135
138
  ""
136
139
  ],
137
- "Account name by which virt-who is to connect to Nutanix AHV.": [
140
+ "Enable AHV debug": [
138
141
  ""
139
142
  ],
140
- "No Report Yet": [
143
+ "Enable debugging output": [
141
144
  ""
142
145
  ],
143
- "Unknown configuration status": [
146
+ "Enable debugging output?": [
144
147
  ""
145
148
  ],
146
- "Unlimited": [
147
- "Не ограничено"
148
- ],
149
- "Whitelist": [
149
+ "Every 12 hours": [
150
150
  ""
151
151
  ],
152
- "Blacklist": [
152
+ "Every 2 days": [
153
153
  ""
154
154
  ],
155
- "General information": [
155
+ "Every 2 hours": [
156
156
  ""
157
157
  ],
158
- "Schedule": [
159
- "Расписание"
160
- ],
161
- "Connection": [
162
- "Соединение"
163
- ],
164
- "Every hour": [
158
+ "Every 24 hours": [
165
159
  ""
166
160
  ],
167
- "Every 2 hours": [
161
+ "Every 3 days": [
168
162
  ""
169
163
  ],
170
164
  "Every 4 hours": [
@@ -173,425 +167,302 @@
173
167
  "Every 8 hours": [
174
168
  ""
175
169
  ],
176
- "Every 12 hours": [
170
+ "Every hour": [
177
171
  ""
178
172
  ],
179
- "Every 24 hours": [
173
+ "Exclude Hosts": [
180
174
  ""
181
175
  ],
182
- "Every 2 days": [
176
+ "Exclude host parents": [
183
177
  ""
184
178
  ],
185
- "Every 3 days": [
179
+ "Exclude hosts": [
186
180
  ""
187
181
  ],
188
- "OK": [
189
- "OK"
190
- ],
191
- "No change": [
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.": [
192
183
  ""
193
184
  ],
194
- "Unknown": [
195
- "Неизвестно"
185
+ "Filter Hosts": [
186
+ ""
196
187
  ],
197
- "Unknown configuration status, caused by unexpected conditions": [
188
+ "Filter host parents": [
198
189
  ""
199
190
  ],
200
- "The configuration was not deployed yet or the virt-who was unable to report the status": [
191
+ "Filter hosts": [
201
192
  ""
202
193
  ],
203
- "The virt-who report arrived within the interval": [
194
+ "Filtering": [
204
195
  ""
205
196
  ],
206
- "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
197
+ "Foreman server FQDN": [
207
198
  ""
208
199
  ],
209
- "Prism Central": [
200
+ "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
210
201
  ""
211
202
  ],
212
- "Prism Element": [
203
+ "Fully qualified host name or IP address of the hypervisor": [
213
204
  ""
214
205
  ],
215
- "every %s hours": [
206
+ "General information": [
216
207
  ""
217
208
  ],
218
- "Success": [
219
- "Успешно"
209
+ "HTTP Proxy": [
210
+ "HTTP-прокси"
220
211
  ],
221
- "Newer version of virt-who is required, minimum version is %s": [
212
+ "HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.": [
222
213
  ""
223
214
  ],
224
- "Unable to create virt-who config file": [
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.": [
225
216
  ""
226
217
  ],
227
- "Unable to create sysconfig file": [
218
+ "Hammer command: ": [
228
219
  ""
229
220
  ],
230
- "Unable to enable virt-who service using systemctl": [
231
- ""
221
+ "Help": [
222
+ "Справка"
232
223
  ],
233
- "Unable to start virt-who service, please see virt-who logs for more details": [
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.": [
234
225
  ""
235
226
  ],
236
- "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
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.": [
237
228
  ""
238
229
  ],
239
- "Owner was not provided": [
230
+ "Hypervisor ID": [
240
231
  ""
241
232
  ],
242
- "Interval was not provided": [
233
+ "Hypervisor Password": [
243
234
  ""
244
235
  ],
245
- "Virt-who Configurations Status": [
236
+ "Hypervisor Server": [
246
237
  ""
247
238
  ],
248
- "Configuration Status": [
239
+ "Hypervisor Type": [
249
240
  ""
250
241
  ],
251
- "Count": [
252
- "Счётчик"
253
- ],
254
- "No Reports": [
242
+ "Hypervisor Username": [
255
243
  ""
256
244
  ],
257
- "No Change": [
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.": [
258
246
  ""
259
247
  ],
260
- "Total Configurations": [
248
+ "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
261
249
  ""
262
250
  ],
263
- "Latest Configurations Without Change": [
251
+ "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
264
252
  ""
265
253
  ],
266
- "No configuration found": [
254
+ "Hypervisor type": [
267
255
  ""
268
256
  ],
269
- "Config|Name": [
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.": [
270
258
  ""
271
259
  ],
272
- "Config|Last Report": [
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.": [
273
261
  ""
274
262
  ],
275
- "Config|Interval": [
263
+ "Ignore Proxy": [
276
264
  ""
277
265
  ],
278
- "Edit Virt-who Config": [
266
+ "Ignore proxy": [
279
267
  ""
280
268
  ],
281
- "Virt-who Configurations": [
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.": [
282
270
  ""
283
271
  ],
284
- "Edit": [
285
- "Правка"
286
- ],
287
- "Status": [
288
- "Состояние"
272
+ "Interval": [
273
+ "Интервал"
289
274
  ],
290
- "Actions": [
291
- "Действия"
275
+ "Interval was not provided": [
276
+ ""
292
277
  ],
293
- "Delete virt-who configuration %s?": [
278
+ "Latest Configurations Without Change": [
294
279
  ""
295
280
  ],
296
- "New Virt-who Config": [
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": [
297
282
  ""
298
283
  ],
299
- "Virt-who Configuration %s": [
284
+ "List of virt-who configurations": [
300
285
  ""
301
286
  ],
302
- "Overview": [
303
- "Обзор"
287
+ "List of virt-who configurations per organization": [
288
+ ""
304
289
  ],
305
- "Deploy": [
290
+ "Microsoft Hyper-V fully qualified host name or IP address.": [
306
291
  ""
307
292
  ],
308
- "Details": [
309
- "Свойства"
293
+ "Name": [
294
+ "Имя"
310
295
  ],
311
- "Hypervisor ID": [
296
+ "Name of this configuration, e.g. the name of the hypervisor": [
312
297
  ""
313
298
  ],
314
- "Filtering": [
299
+ "New Config": [
315
300
  ""
316
301
  ],
317
- "Filter Hosts": [
302
+ "New Virt-who Config": [
318
303
  ""
319
304
  ],
320
- "Exclude Hosts": [
305
+ "Newer version of virt-who is required, minimum version is %s": [
321
306
  ""
322
307
  ],
323
- "Enable debugging output?": [
308
+ "No Change": [
324
309
  ""
325
310
  ],
326
- "HTTP Proxy": [
327
- "HTTP-прокси"
328
- ],
329
- "Ignore Proxy": [
311
+ "No Report Yet": [
330
312
  ""
331
313
  ],
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:": [
314
+ "No Reports": [
333
315
  ""
334
316
  ],
335
- "Hammer command: ": [
317
+ "No change": [
336
318
  ""
337
319
  ],
338
- "Copy to clipboard": [
339
- "Скопировано в буфер обмена"
320
+ "No configuration found": [
321
+ ""
340
322
  ],
341
- "Configuration script: ": [
323
+ "Nutanix AHV’s IP address.": [
342
324
  ""
343
325
  ],
326
+ "OK": [
327
+ "OK"
328
+ ],
344
329
  "On the target virt-who host:": [
345
330
  ""
346
331
  ],
347
- "1. Copy this configuration script to a safe directory.": [
332
+ "On this page you can define virt-who configurations for your hypervisors.": [
348
333
  ""
349
334
  ],
350
- "2. Make the script executable and run it.": [
335
+ "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
351
336
  ""
352
337
  ],
353
- "3. Delete the script.": [
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.": [
354
339
  ""
355
340
  ],
356
- "Download the script": [
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.": [
357
342
  ""
358
343
  ],
359
- "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
344
+ "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
360
345
  ""
361
346
  ],
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.": [
347
+ "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
363
348
  ""
364
349
  ],
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.": [
350
+ "Organization of the virt-who configuration": [
366
351
  ""
367
352
  ],
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
- ""
353
+ "Overview": [
354
+ "Обзор"
370
355
  ],
371
- "Filter hosts": [
372
- ""
356
+ "Owner": [
357
+ "Владелец"
373
358
  ],
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.": [
359
+ "Owner was not provided": [
375
360
  ""
376
361
  ],
377
- "Exclude hosts": [
362
+ "Path to kubeconfig file": [
378
363
  ""
379
364
  ],
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.": [
365
+ "Prism Central": [
381
366
  ""
382
367
  ],
383
- "Filter host parents": [
368
+ "Prism Element": [
384
369
  ""
385
370
  ],
386
- "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.": [
371
+ "Prism Flavor": [
387
372
  ""
388
373
  ],
389
- "Exclude host parents": [
374
+ "Renders a deploy script for the specified virt-who configuration": [
390
375
  ""
391
376
  ],
392
- "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.": [
393
- ""
377
+ "Schedule": [
378
+ "Расписание"
394
379
  ],
395
- "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.": [
380
+ "Select the Prism flavor you are connecting to": [
396
381
  ""
397
382
  ],
398
- "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.": [
383
+ "Show a virt-who configuration": [
399
384
  ""
400
385
  ],
401
- "Ignore proxy": [
386
+ "Specifies how the hypervisor will be identified.": [
402
387
  ""
403
388
  ],
404
- "Configuration file containing details about how to connect to the cluster and authentication details": [
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.": [
405
390
  ""
406
391
  ],
407
- "Path to kubeconfig file": [
408
- ""
392
+ "Status": [
393
+ "Состояние"
409
394
  ],
410
- "Prism Flavor": [
411
- ""
395
+ "Success": [
396
+ "Успешно"
412
397
  ],
413
- "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
398
+ "The configuration was not deployed yet or the virt-who was unable to report the status": [
414
399
  ""
415
400
  ],
416
- "Enable AHV debug": [
401
+ "The virt-who report arrived within the interval": [
417
402
  ""
418
403
  ],
419
- "Name of this configuration, e.g. the name of the hypervisor": [
404
+ "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
420
405
  ""
421
406
  ],
422
- "Name": [
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.": [
423
408
  ""
424
409
  ],
425
- "Owner": [
426
- "Владелец"
427
- ],
428
- "Hypervisor Type": [
410
+ "Total Configurations": [
429
411
  ""
430
412
  ],
431
- "Hypervisor Server": [
413
+ "Unable to create sysconfig file": [
432
414
  ""
433
415
  ],
434
- "Hypervisor Username": [
416
+ "Unable to create virt-who config file": [
435
417
  ""
436
418
  ],
437
- "Hypervisor Password": [
419
+ "Unable to enable virt-who service using systemctl": [
438
420
  ""
439
421
  ],
440
- "Account password by which virt-who is to connect to the hypervisor instance.": [
422
+ "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
441
423
  ""
442
424
  ],
443
- "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.": [
425
+ "Unable to start virt-who service, please see virt-who logs for more details": [
444
426
  ""
445
427
  ],
446
- "Interval": [
447
- ""
428
+ "Unknown": [
429
+ "Неизвестно"
448
430
  ],
449
- "Configs": [
450
- "Конфигурация"
431
+ "Unknown configuration status": [
432
+ ""
451
433
  ],
452
- "On this page you can define virt-who configurations for your hypervisors.": [
434
+ "Unknown configuration status, caused by unexpected conditions": [
453
435
  ""
454
436
  ],
455
- "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
437
+ "Unlimited": [
438
+ "Не ограничено"
439
+ ],
440
+ "Update a virt-who configuration": [
456
441
  ""
457
442
  ],
458
- "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.": [
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:": [
459
444
  ""
460
445
  ],
461
- "Virt-who configurations": [
446
+ "VMware vCenter server’s fully qualified host name or IP address.": [
462
447
  ""
463
448
  ],
464
449
  "Virt-who Configs Status": [
465
450
  ""
466
451
  ],
467
- "A plugin to make virt-who configuration easy": [
452
+ "Virt-who Configuration %s": [
468
453
  ""
469
454
  ],
470
- "Abstract async task": [
471
- "Абстрактная асинхронная задача"
472
- ],
473
- "Action with sub plans": [
474
- "Действия с подпланами"
475
- ],
476
- "Attach subscriptions": [
477
- "Выделить подписки"
478
- ],
479
- "Auto attach subscriptions": [
480
- "Выбрать подписки автоматически"
481
- ],
482
- "Create": [
483
- "Создать"
484
- ],
485
- "Delete": [
486
- "Удалить"
487
- ],
488
- "Delete Activation Key": [
489
- "Удалить ключ активации"
490
- ],
491
- "Delete Lifecycle Environment": [
492
- "Удалить окружение"
493
- ],
494
- "Delete Product": [
495
- "Удалить продукт"
496
- ],
497
- "Destroy": [
498
- "Удалить"
499
- ],
500
- "Destroy Content Host": [
501
- "Удалить узел"
502
- ],
503
- "Disable": [
504
- "Отключить"
505
- ],
506
- "Discover": [
507
- "Поиск"
508
- ],
509
- "Enable": [
510
- "Включить"
511
- ],
512
- "Errata mail": [
513
- "Почта"
514
- ],
515
- "Export": [
516
- "Экспорт"
517
- ],
518
- "Filtered index content": [
519
- "Содержимое фильтруемого индекса"
520
- ],
521
- "Hypervisors": [
522
- "Гипервизоры"
523
- ],
524
- "Hypervisors update": [
525
- "Обновление гипервизоров"
526
- ],
527
- "Import": [
528
- "Импорт"
529
- ],
530
- "Import Puppet classes": [
531
- "Импорт классов Puppet"
532
- ],
533
- "Import facts": [
534
- "Импорт фактов"
535
- ],
536
- "Incremental Update": [
537
- "Инкрементное обновление"
538
- ],
539
- "Index content": [
540
- "Индексировать содержимое"
541
- ],
542
- "Index errata": [
543
- "Индексировать исправления"
544
- ],
545
- "Index package groups": [
546
- "Индексировать группы пакетов"
547
- ],
548
- "Install Applicable Errata": [
549
- "Установить исправления"
550
- ],
551
- "Package Profile Update": [
552
- "Обновление профиля пакетов"
553
- ],
554
- "Product Create": [
555
- "Создать продукт"
556
- ],
557
- "Promote": [
558
- "Продвижение"
559
- ],
560
- "Publish": [
561
- "Опубликовать"
562
- ],
563
- "Reindex subscriptions": [
564
- "Повторно индексировать подписки"
565
- ],
566
- "Remove Content": [
567
- "Удалить содержимое"
568
- ],
569
- "Remove Version": [
570
- "Удалить версию"
571
- ],
572
- "Remove Versions and Associations": [
573
- "Удалить версии и связи"
574
- ],
575
- "Remove from Environment": [
576
- "Удалить из окружения"
577
- ],
578
- "Remove subscriptions": [
579
- "Удалить подписки"
580
- ],
581
- "Report": [
582
- "Сообщить"
583
- ],
584
- "Synchronize": [
585
- "Синхронизировать"
455
+ "Virt-who Configurations": [
456
+ ""
586
457
  ],
587
- "Update": [
588
- "Обновить"
458
+ "Virt-who Configurations Status": [
459
+ ""
589
460
  ],
590
- "Update for host": [
591
- "Обновление узла"
461
+ "Whitelist": [
462
+ ""
592
463
  ],
593
- "Upload into": [
594
- "Добавить в"
464
+ "every %s hours": [
465
+ ""
595
466
  ]
596
467
  }
597
468
  }