foreman_virt_who_configure 0.5.25 → 0.5.26

data/app/assets/javascripts/foreman_virt_who_configure/locale/sl/foreman_virt_who_configure.js

@@ -3,10 +3,10 @@
   "locale_data": {
     "foreman_virt_who_configure": {
       "": {
-        "Project-Id-Version": "foreman_virt_who_configure 0.5.17",
+        "Project-Id-Version": "foreman_virt_who_configure 0.5.25",
         "Report-Msgid-Bugs-To": "",
         "PO-Revision-Date": "2017-05-03 11:59+0000",
-        "Last-Translator": "Barbara Krasovec <barbarak@arnes.si>, 2019",
+        "Last-Translator": "Barbara Krasovec <barbarak@arnes.si>, 2023",
         "Language-Team": "Slovenian (https://app.transifex.com/foreman/teams/114/sl/)",
         "MIME-Version": "1.0",
         "Content-Type": "text/plain; charset=UTF-8",
@@ -17,154 +17,148 @@
         "domain": "foreman_virt_who_configure",
         "plural_forms": "nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3);"
       },
-      "List of virt-who configurations": [
+      "1. Copy this configuration script to a safe directory.": [
         ""
       ],
-      "List of virt-who configurations per organization": [
+      "2. Make the script executable and run it.": [
         ""
       ],
-      "Show a virt-who configuration": [
+      "3. Delete the script.": [
         ""
       ],
-      "Renders a deploy script for the specified virt-who configuration": [
+      "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.": [
         ""
       ],
-      "Configuration name": [
+      "A plugin to make virt-who configuration easy": [
         ""
       ],
-      "Configuration interval in minutes": [
+      "Account name by which virt-who is to connect to Nutanix AHV.": [
         ""
       ],
-      "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
+      "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.": [
         ""
       ],
-      "Hypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
+      "Account name by which virt-who is to connect to the hypervisor.": [
         ""
       ],
-      "Hypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
+      "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.": [
         ""
       ],
-      "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.": [
+      "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.": [
         ""
       ],
-      "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.": [
+      "Account password by which virt-who is to connect to the hypervisor instance.": [
         ""
       ],
-      "Specifies how the hypervisor will be identified.": [
+      "Actions": [
         ""
       ],
-      "Hypervisor type": [
+      "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.": [
         ""
       ],
-      "Fully qualified host name or IP address of the hypervisor": [
+      "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.": [
         ""
       ],
-      "Account name by which virt-who is to connect to the hypervisor.": [
+      "Blacklist": [
         ""
       ],
-      "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
+      "Configs": [
         ""
       ],
-      "Foreman server FQDN": [
+      "Configuration Status": [
         ""
       ],
-      "Enable debugging output": [
+      "Configuration file containing details about how to connect to the cluster and authentication details": [
         ""
       ],
       "Configuration file containing details about how to connect to the cluster and authentication details.": [
         ""
       ],
-      "HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.": [
+      "Configuration interval in minutes": [
         ""
       ],
-      "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.": [
+      "Configuration name": [
         ""
       ],
-      "Organization of the virt-who configuration": [
+      "Configuration numeric identifier": [
         ""
       ],
-      "Select the Prism flavor you are connecting to": [
+      "Configuration script: ": [
         ""
       ],
-      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
+      "Config|Interval": [
         ""
       ],
-      "Create a virt-who configuration": [
+      "Config|Last Report": [
         ""
       ],
-      "Update a virt-who configuration": [
+      "Config|Name": [
         ""
       ],
-      "Configuration numeric identifier": [
+      "Connection": [
         ""
       ],
-      "Delete a virt-who configuration": [
+      "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.": [
         ""
       ],
-      "Create Config": [
+      "Copy to clipboard": [
         ""
       ],
-      "New Config": [
+      "Count": [
         ""
       ],
-      "Help": [
+      "Create Config": [
         ""
       ],
-      "VMware vCenter server’s fully qualified host name or IP address.": [
+      "Create a virt-who configuration": [
         ""
       ],
-      "Microsoft Hyper-V fully qualified host name or IP address.": [
+      "Delete a virt-who configuration": [
         ""
       ],
-      "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": [
+      "Delete virt-who configuration %s?": [
         ""
       ],
-      "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.": [
+      "Deploy": [
         ""
       ],
-      "Nutanix AHV’s IP address.": [
-        ""
+      "Details": [
+        "Podrobnosti"
       ],
-      "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.": [
+      "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.": [
         ""
       ],
-      "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.": [
+      "Download the script": [
         ""
       ],
-      "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.": [
+      "Edit": [
         ""
       ],
-      "Account name by which virt-who is to connect to Nutanix AHV.": [
+      "Edit Virt-who Config": [
         ""
       ],
-      "No Report Yet": [
+      "Enable AHV debug": [
         ""
       ],
-      "Unknown configuration status": [
+      "Enable debugging output": [
         ""
       ],
-      "Unlimited": [
-        "Neomejeno"
-      ],
-      "Whitelist": [
+      "Enable debugging output?": [
         ""
       ],
-      "Blacklist": [
+      "Every 12 hours": [
         ""
       ],
-      "General information": [
+      "Every 2 days": [
         ""
       ],
-      "Schedule": [
-        "Urnik"
-      ],
-      "Connection": [
+      "Every 2 hours": [
         ""
       ],
-      "Every hour": [
+      "Every 24 hours": [
         ""
       ],
-      "Every 2 hours": [
+      "Every 3 days": [
         ""
       ],
       "Every 4 hours": [
@@ -173,305 +167,302 @@
       "Every 8 hours": [
         ""
       ],
-      "Every 12 hours": [
+      "Every hour": [
         ""
       ],
-      "Every 24 hours": [
+      "Exclude Hosts": [
         ""
       ],
-      "Every 2 days": [
+      "Exclude host parents": [
         ""
       ],
-      "Every 3 days": [
+      "Exclude hosts": [
         ""
       ],
-      "OK": [
+      "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.": [
         ""
       ],
-      "No change": [
+      "Filter Hosts": [
         ""
       ],
-      "Unknown": [
+      "Filter host parents": [
         ""
       ],
-      "Unknown configuration status, caused by unexpected conditions": [
+      "Filter hosts": [
         ""
       ],
-      "The configuration was not deployed yet or the virt-who was unable to report the status": [
+      "Filtering": [
         ""
       ],
-      "The virt-who report arrived within the interval": [
+      "Foreman server FQDN": [
         ""
       ],
-      "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
+      "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
         ""
       ],
-      "Prism Central": [
+      "Fully qualified host name or IP address of the hypervisor": [
         ""
       ],
-      "Prism Element": [
+      "General information": [
         ""
       ],
-      "every %s hours": [
+      "HTTP Proxy": [
         ""
       ],
-      "Success": [
+      "HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.": [
         ""
       ],
-      "Newer version of virt-who is required, minimum version is %s": [
+      "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.": [
         ""
       ],
-      "Unable to create virt-who config file": [
+      "Hammer command: ": [
         ""
       ],
-      "Unable to create sysconfig file": [
+      "Help": [
         ""
       ],
-      "Unable to enable virt-who service using systemctl": [
+      "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.": [
         ""
       ],
-      "Unable to start virt-who service, please see virt-who logs for more details": [
+      "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.": [
         ""
       ],
-      "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
+      "Hypervisor ID": [
         ""
       ],
-      "Owner was not provided": [
+      "Hypervisor Password": [
         ""
       ],
-      "Interval was not provided": [
+      "Hypervisor Server": [
         ""
       ],
-      "Virt-who Configurations Status": [
+      "Hypervisor Type": [
         ""
       ],
-      "Configuration Status": [
+      "Hypervisor Username": [
         ""
       ],
-      "Count": [
+      "Hypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
         ""
       ],
-      "No Reports": [
+      "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
         ""
       ],
-      "No Change": [
+      "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
         ""
       ],
-      "Total Configurations": [
+      "Hypervisor type": [
         ""
       ],
-      "Latest Configurations Without Change": [
+      "Hypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
         ""
       ],
-      "No configuration found": [
+      "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.": [
         ""
       ],
-      "Config|Name": [
+      "Ignore Proxy": [
         ""
       ],
-      "Config|Last Report": [
+      "Ignore proxy": [
         ""
       ],
-      "Config|Interval": [
+      "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.": [
         ""
       ],
-      "Edit Virt-who Config": [
+      "Interval": [
         ""
       ],
-      "Virt-who Configurations": [
+      "Interval was not provided": [
         ""
       ],
-      "Edit": [
+      "Latest Configurations Without Change": [
         ""
       ],
-      "Status": [
+      "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": [
         ""
       ],
-      "Actions": [
+      "List of virt-who configurations": [
         ""
       ],
-      "Delete virt-who configuration %s?": [
+      "List of virt-who configurations per organization": [
         ""
       ],
-      "New Virt-who Config": [
+      "Microsoft Hyper-V fully qualified host name or IP address.": [
         ""
       ],
-      "Virt-who Configuration %s": [
-        ""
+      "Name": [
+        "Ime"
       ],
-      "Overview": [
+      "Name of this configuration, e.g. the name of the hypervisor": [
         ""
       ],
-      "Deploy": [
+      "New Config": [
         ""
       ],
-      "Details": [
-        "Podrobnosti"
-      ],
-      "Hypervisor ID": [
+      "New Virt-who Config": [
         ""
       ],
-      "Filtering": [
+      "Newer version of virt-who is required, minimum version is %s": [
         ""
       ],
-      "Filter Hosts": [
+      "No Change": [
         ""
       ],
-      "Exclude Hosts": [
+      "No Report Yet": [
         ""
       ],
-      "Enable debugging output?": [
+      "No Reports": [
         ""
       ],
-      "HTTP Proxy": [
+      "No change": [
         ""
       ],
-      "Ignore Proxy": [
+      "No configuration found": [
         ""
       ],
-      "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:": [
+      "Nutanix AHV’s IP address.": [
         ""
       ],
-      "Hammer command: ": [
+      "OK": [
         ""
       ],
-      "Copy to clipboard": [
+      "On the target virt-who host:": [
         ""
       ],
-      "Configuration script: ": [
+      "On this page you can define virt-who configurations for your hypervisors.": [
         ""
       ],
-      "On the target virt-who host:": [
+      "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
         ""
       ],
-      "1. Copy this configuration script to a safe directory.": [
+      "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.": [
         ""
       ],
-      "2. Make the script executable and run it.": [
+      "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.": [
         ""
       ],
-      "3. Delete the script.": [
+      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
         ""
       ],
-      "Download the script": [
+      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
         ""
       ],
-      "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
+      "Organization of the virt-who configuration": [
         ""
       ],
-      "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.": [
+      "Overview": [
         ""
       ],
-      "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.": [
+      "Owner": [
         ""
       ],
-      "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.": [
+      "Owner was not provided": [
         ""
       ],
-      "Filter hosts": [
+      "Path to kubeconfig file": [
         ""
       ],
-      "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.": [
+      "Prism Central": [
         ""
       ],
-      "Exclude hosts": [
+      "Prism Element": [
         ""
       ],
-      "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.": [
+      "Prism Flavor": [
         ""
       ],
-      "Filter host parents": [
+      "Renders a deploy script for the specified virt-who configuration": [
         ""
       ],
-      "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.": [
-        ""
+      "Schedule": [
+        "Urnik"
       ],
-      "Exclude host parents": [
+      "Select the Prism flavor you are connecting to": [
         ""
       ],
-      "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.": [
+      "Show a virt-who configuration": [
         ""
       ],
-      "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.": [
+      "Specifies how the hypervisor will be identified.": [
         ""
       ],
-      "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.": [
+      "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.": [
         ""
       ],
-      "Ignore proxy": [
+      "Status": [
         ""
       ],
-      "Configuration file containing details about how to connect to the cluster and authentication details": [
+      "Success": [
         ""
       ],
-      "Path to kubeconfig file": [
+      "The configuration was not deployed yet or the virt-who was unable to report the status": [
         ""
       ],
-      "Prism Flavor": [
+      "The virt-who report arrived within the interval": [
         ""
       ],
-      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
+      "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
         ""
       ],
-      "Enable AHV debug": [
+      "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.": [
         ""
       ],
-      "Name of this configuration, e.g. the name of the hypervisor": [
+      "Total Configurations": [
         ""
       ],
-      "Name": [
+      "Unable to create sysconfig file": [
         ""
       ],
-      "Owner": [
+      "Unable to create virt-who config file": [
         ""
       ],
-      "Hypervisor Type": [
+      "Unable to enable virt-who service using systemctl": [
         ""
       ],
-      "Hypervisor Server": [
+      "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
         ""
       ],
-      "Hypervisor Username": [
+      "Unable to start virt-who service, please see virt-who logs for more details": [
         ""
       ],
-      "Hypervisor Password": [
+      "Unknown": [
         ""
       ],
-      "Account password by which virt-who is to connect to the hypervisor instance.": [
+      "Unknown configuration status": [
         ""
       ],
-      "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.": [
+      "Unknown configuration status, caused by unexpected conditions": [
         ""
       ],
-      "Interval": [
-        ""
+      "Unlimited": [
+        "Neomejeno"
       ],
-      "Configs": [
+      "Update a virt-who configuration": [
         ""
       ],
-      "On this page you can define virt-who configurations for your hypervisors.": [
+      "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:": [
         ""
       ],
-      "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
+      "VMware vCenter server’s fully qualified host name or IP address.": [
         ""
       ],
-      "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.": [
+      "Virt-who Configs Status": [
         ""
       ],
-      "Virt-who configurations": [
+      "Virt-who Configuration %s": [
         ""
       ],
-      "Virt-who Configs Status": [
+      "Virt-who Configurations": [
         ""
       ],
-      "A plugin to make virt-who configuration easy": [
+      "Virt-who Configurations Status": [
         ""
       ],
-      "Disable": [
-        "Onemogoči"
+      "Whitelist": [
+        ""
       ],
-      "Enable": [
-        "Omogoči"
+      "every %s hours": [
+        ""
       ]
     }
   }