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,7 +3,7 @@
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
9
  "Last-Translator": "ohadlevy <ohadlevy@gmail.com>, 2019",
@@ -12,159 +12,153 @@
12
12
  "Content-Type": "text/plain; charset=UTF-8",
13
13
  "Content-Transfer-Encoding": "8bit",
14
14
  "Language": "he_IL",
15
- "Plural-Forms": "nplurals=4; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: (n % 10 == 0 && n % 1 == 0 && n > 10) ? 2 : 3;",
15
+ "Plural-Forms": "nplurals=3; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: 2;",
16
16
  "lang": "he_IL",
17
17
  "domain": "foreman_virt_who_configure",
18
- "plural_forms": "nplurals=4; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: (n % 10 == 0 && n % 1 == 0 && n > 10) ? 2 : 3;"
18
+ "plural_forms": "nplurals=3; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: 2;"
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.": [
53
+ "Actions": [
54
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.": [
65
+ "Configs": [
66
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.": [
78
- ""
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
- ""
82
- ],
83
- "Organization of the virt-who configuration": [
77
+ "Configuration interval in minutes": [
84
78
  ""
85
79
  ],
86
- "Select the Prism flavor you are connecting to": [
80
+ "Configuration name": [
87
81
  ""
88
82
  ],
89
- "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
83
+ "Configuration numeric identifier": [
90
84
  ""
91
85
  ],
92
- "Create a virt-who configuration": [
86
+ "Configuration script: ": [
93
87
  ""
94
88
  ],
95
- "Update a virt-who configuration": [
89
+ "Config|Interval": [
96
90
  ""
97
91
  ],
98
- "Configuration numeric identifier": [
92
+ "Config|Last Report": [
99
93
  ""
100
94
  ],
101
- "Delete a virt-who configuration": [
95
+ "Config|Name": [
102
96
  ""
103
97
  ],
104
- "Create Config": [
98
+ "Connection": [
105
99
  ""
106
100
  ],
107
- "New Config": [
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.": [
108
102
  ""
109
103
  ],
110
- "Help": [
104
+ "Copy to clipboard": [
111
105
  ""
112
106
  ],
113
- "VMware vCenter server’s fully qualified host name or IP address.": [
107
+ "Count": [
114
108
  ""
115
109
  ],
116
- "Microsoft Hyper-V fully qualified host name or IP address.": [
110
+ "Create Config": [
117
111
  ""
118
112
  ],
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": [
113
+ "Create a virt-who configuration": [
120
114
  ""
121
115
  ],
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.": [
116
+ "Delete a virt-who configuration": [
123
117
  ""
124
118
  ],
125
- "Nutanix AHV’s IP address.": [
119
+ "Delete virt-who configuration %s?": [
126
120
  ""
127
121
  ],
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.": [
122
+ "Deploy": [
129
123
  ""
130
124
  ],
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
- ""
125
+ "Details": [
126
+ "פרטים נוספים"
133
127
  ],
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.": [
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.": [
135
129
  ""
136
130
  ],
137
- "Account name by which virt-who is to connect to Nutanix AHV.": [
131
+ "Download the script": [
138
132
  ""
139
133
  ],
140
- "No Report Yet": [
134
+ "Edit": [
141
135
  ""
142
136
  ],
143
- "Unknown configuration status": [
137
+ "Edit Virt-who Config": [
144
138
  ""
145
139
  ],
146
- "Unlimited": [
140
+ "Enable AHV debug": [
147
141
  ""
148
142
  ],
149
- "Whitelist": [
143
+ "Enable debugging output": [
150
144
  ""
151
145
  ],
152
- "Blacklist": [
146
+ "Enable debugging output?": [
153
147
  ""
154
148
  ],
155
- "General information": [
149
+ "Every 12 hours": [
156
150
  ""
157
151
  ],
158
- "Schedule": [
152
+ "Every 2 days": [
159
153
  ""
160
154
  ],
161
- "Connection": [
155
+ "Every 2 hours": [
162
156
  ""
163
157
  ],
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,298 +167,301 @@
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": [
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.": [
189
183
  ""
190
184
  ],
191
- "No change": [
185
+ "Filter Hosts": [
192
186
  ""
193
187
  ],
194
- "Unknown": [
188
+ "Filter host parents": [
195
189
  ""
196
190
  ],
197
- "Unknown configuration status, caused by unexpected conditions": [
191
+ "Filter hosts": [
198
192
  ""
199
193
  ],
200
- "The configuration was not deployed yet or the virt-who was unable to report the status": [
194
+ "Filtering": [
201
195
  ""
202
196
  ],
203
- "The virt-who report arrived within the interval": [
197
+ "Foreman server FQDN": [
204
198
  ""
205
199
  ],
206
- "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
200
+ "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
207
201
  ""
208
202
  ],
209
- "Prism Central": [
203
+ "Fully qualified host name or IP address of the hypervisor": [
210
204
  ""
211
205
  ],
212
- "Prism Element": [
206
+ "General information": [
213
207
  ""
214
208
  ],
215
- "every %s hours": [
209
+ "HTTP Proxy": [
216
210
  ""
217
211
  ],
218
- "Success": [
219
- "הצלחה"
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
+ ""
220
214
  ],
221
- "Newer version of virt-who is required, minimum version is %s": [
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.": [
222
216
  ""
223
217
  ],
224
- "Unable to create virt-who config file": [
218
+ "Hammer command: ": [
225
219
  ""
226
220
  ],
227
- "Unable to create sysconfig file": [
221
+ "Help": [
228
222
  ""
229
223
  ],
230
- "Unable to enable virt-who service using systemctl": [
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.": [
231
225
  ""
232
226
  ],
233
- "Unable to start virt-who service, please see virt-who logs for more details": [
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.": [
234
228
  ""
235
229
  ],
236
- "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
230
+ "Hypervisor ID": [
237
231
  ""
238
232
  ],
239
- "Owner was not provided": [
233
+ "Hypervisor Password": [
240
234
  ""
241
235
  ],
242
- "Interval was not provided": [
236
+ "Hypervisor Server": [
243
237
  ""
244
238
  ],
245
- "Virt-who Configurations Status": [
239
+ "Hypervisor Type": [
246
240
  ""
247
241
  ],
248
- "Configuration Status": [
242
+ "Hypervisor Username": [
249
243
  ""
250
244
  ],
251
- "Count": [
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.": [
252
246
  ""
253
247
  ],
254
- "No Reports": [
248
+ "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
255
249
  ""
256
250
  ],
257
- "No Change": [
251
+ "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
258
252
  ""
259
253
  ],
260
- "Total Configurations": [
254
+ "Hypervisor type": [
261
255
  ""
262
256
  ],
263
- "Latest Configurations Without Change": [
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.": [
264
258
  ""
265
259
  ],
266
- "No configuration found": [
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.": [
267
261
  ""
268
262
  ],
269
- "Config|Name": [
263
+ "Ignore Proxy": [
270
264
  ""
271
265
  ],
272
- "Config|Last Report": [
266
+ "Ignore proxy": [
273
267
  ""
274
268
  ],
275
- "Config|Interval": [
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.": [
276
270
  ""
277
271
  ],
278
- "Edit Virt-who Config": [
272
+ "Interval": [
279
273
  ""
280
274
  ],
281
- "Virt-who Configurations": [
275
+ "Interval was not provided": [
282
276
  ""
283
277
  ],
284
- "Edit": [
278
+ "Latest Configurations Without Change": [
285
279
  ""
286
280
  ],
287
- "Status": [
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": [
288
282
  ""
289
283
  ],
290
- "Actions": [
284
+ "List of virt-who configurations": [
291
285
  ""
292
286
  ],
293
- "Delete virt-who configuration %s?": [
287
+ "List of virt-who configurations per organization": [
294
288
  ""
295
289
  ],
296
- "New Virt-who Config": [
290
+ "Microsoft Hyper-V fully qualified host name or IP address.": [
297
291
  ""
298
292
  ],
299
- "Virt-who Configuration %s": [
293
+ "Name": [
300
294
  ""
301
295
  ],
302
- "Overview": [
296
+ "Name of this configuration, e.g. the name of the hypervisor": [
303
297
  ""
304
298
  ],
305
- "Deploy": [
299
+ "New Config": [
306
300
  ""
307
301
  ],
308
- "Details": [
309
- "פרטים נוספים"
302
+ "New Virt-who Config": [
303
+ ""
310
304
  ],
311
- "Hypervisor ID": [
305
+ "Newer version of virt-who is required, minimum version is %s": [
312
306
  ""
313
307
  ],
314
- "Filtering": [
308
+ "No Change": [
315
309
  ""
316
310
  ],
317
- "Filter Hosts": [
311
+ "No Report Yet": [
318
312
  ""
319
313
  ],
320
- "Exclude Hosts": [
314
+ "No Reports": [
321
315
  ""
322
316
  ],
323
- "Enable debugging output?": [
317
+ "No change": [
324
318
  ""
325
319
  ],
326
- "HTTP Proxy": [
320
+ "No configuration found": [
327
321
  ""
328
322
  ],
329
- "Ignore Proxy": [
323
+ "Nutanix AHV’s IP address.": [
330
324
  ""
331
325
  ],
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:": [
326
+ "OK": [
333
327
  ""
334
328
  ],
335
- "Hammer command: ": [
329
+ "On the target virt-who host:": [
336
330
  ""
337
331
  ],
338
- "Copy to clipboard": [
332
+ "On this page you can define virt-who configurations for your hypervisors.": [
339
333
  ""
340
334
  ],
341
- "Configuration script: ": [
335
+ "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
342
336
  ""
343
337
  ],
344
- "On the target virt-who host:": [
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.": [
345
339
  ""
346
340
  ],
347
- "1. Copy this configuration script to a safe directory.": [
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.": [
348
342
  ""
349
343
  ],
350
- "2. Make the script executable and run it.": [
344
+ "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
351
345
  ""
352
346
  ],
353
- "3. Delete the script.": [
347
+ "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
354
348
  ""
355
349
  ],
356
- "Download the script": [
350
+ "Organization of the virt-who configuration": [
357
351
  ""
358
352
  ],
359
- "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
353
+ "Overview": [
360
354
  ""
361
355
  ],
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.": [
356
+ "Owner": [
363
357
  ""
364
358
  ],
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.": [
359
+ "Owner was not provided": [
366
360
  ""
367
361
  ],
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.": [
362
+ "Path to kubeconfig file": [
369
363
  ""
370
364
  ],
371
- "Filter hosts": [
365
+ "Prism Central": [
372
366
  ""
373
367
  ],
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.": [
368
+ "Prism Element": [
375
369
  ""
376
370
  ],
377
- "Exclude hosts": [
371
+ "Prism Flavor": [
378
372
  ""
379
373
  ],
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.": [
374
+ "Renders a deploy script for the specified virt-who configuration": [
381
375
  ""
382
376
  ],
383
- "Filter host parents": [
377
+ "Schedule": [
384
378
  ""
385
379
  ],
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.": [
380
+ "Select the Prism flavor you are connecting to": [
387
381
  ""
388
382
  ],
389
- "Exclude host parents": [
383
+ "Show a virt-who configuration": [
390
384
  ""
391
385
  ],
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.": [
386
+ "Specifies how the hypervisor will be identified.": [
393
387
  ""
394
388
  ],
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.": [
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.": [
396
390
  ""
397
391
  ],
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.": [
392
+ "Status": [
399
393
  ""
400
394
  ],
401
- "Ignore proxy": [
395
+ "Success": [
396
+ "הצלחה"
397
+ ],
398
+ "The configuration was not deployed yet or the virt-who was unable to report the status": [
402
399
  ""
403
400
  ],
404
- "Configuration file containing details about how to connect to the cluster and authentication details": [
401
+ "The virt-who report arrived within the interval": [
405
402
  ""
406
403
  ],
407
- "Path to kubeconfig file": [
404
+ "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
408
405
  ""
409
406
  ],
410
- "Prism Flavor": [
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.": [
411
408
  ""
412
409
  ],
413
- "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
410
+ "Total Configurations": [
414
411
  ""
415
412
  ],
416
- "Enable AHV debug": [
413
+ "Unable to create sysconfig file": [
417
414
  ""
418
415
  ],
419
- "Name of this configuration, e.g. the name of the hypervisor": [
416
+ "Unable to create virt-who config file": [
420
417
  ""
421
418
  ],
422
- "Name": [
419
+ "Unable to enable virt-who service using systemctl": [
423
420
  ""
424
421
  ],
425
- "Owner": [
422
+ "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
426
423
  ""
427
424
  ],
428
- "Hypervisor Type": [
425
+ "Unable to start virt-who service, please see virt-who logs for more details": [
429
426
  ""
430
427
  ],
431
- "Hypervisor Server": [
428
+ "Unknown": [
432
429
  ""
433
430
  ],
434
- "Hypervisor Username": [
431
+ "Unknown configuration status": [
435
432
  ""
436
433
  ],
437
- "Hypervisor Password": [
434
+ "Unknown configuration status, caused by unexpected conditions": [
438
435
  ""
439
436
  ],
440
- "Account password by which virt-who is to connect to the hypervisor instance.": [
437
+ "Unlimited": [
441
438
  ""
442
439
  ],
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.": [
440
+ "Update a virt-who configuration": [
444
441
  ""
445
442
  ],
446
- "Interval": [
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:": [
447
444
  ""
448
445
  ],
449
- "Configs": [
446
+ "VMware vCenter server’s fully qualified host name or IP address.": [
450
447
  ""
451
448
  ],
452
- "On this page you can define virt-who configurations for your hypervisors.": [
449
+ "Virt-who Configs Status": [
453
450
  ""
454
451
  ],
455
- "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
452
+ "Virt-who Configuration %s": [
456
453
  ""
457
454
  ],
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.": [
455
+ "Virt-who Configurations": [
459
456
  ""
460
457
  ],
461
- "Virt-who configurations": [
458
+ "Virt-who Configurations Status": [
462
459
  ""
463
460
  ],
464
- "Virt-who Configs Status": [
461
+ "Whitelist": [
465
462
  ""
466
463
  ],
467
- "A plugin to make virt-who configuration easy": [
464
+ "every %s hours": [
468
465
  ""
469
466
  ]
470
467
  }