foreman_virt_who_configure 0.5.25 → 0.5.26

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

@@ -3,11 +3,11 @@
   "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": "Robert Antoni Buj i Gelonch <rbuj@fedoraproject.org>, 2022",
-        "Language-Team": "Catalan (https://www.transifex.com/foreman/teams/114/ca/)",
+        "Last-Translator": "Robert Antoni Buj i Gelonch <rbuj@fedoraproject.org>, 2023",
+        "Language-Team": "Catalan (https://app.transifex.com/foreman/teams/114/ca/)",
         "MIME-Version": "1.0",
         "Content-Type": "text/plain; charset=UTF-8",
         "Content-Transfer-Encoding": "8bit",
@@ -17,154 +17,148 @@
         "domain": "foreman_virt_who_configure",
         "plural_forms": "nplurals=2; plural=(n != 1);"
       },
-      "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": [
+        "Accions"
       ],
-      "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": [
+        "Llista negra"
       ],
-      "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": [
-        "Configuració nova"
-      ],
-      "Help": [
-        "Ajuda"
-      ],
-      "VMware vCenter server’s fully qualified host name or IP address.": [
+      "Count": [
         ""
       ],
-      "Microsoft Hyper-V fully qualified host name or IP address.": [
+      "Create Config": [
         ""
       ],
-      "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": [
+      "Create 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.": [
+      "Delete a virt-who configuration": [
         ""
       ],
-      "Nutanix AHV’s IP address.": [
+      "Delete virt-who configuration %s?": [
         ""
       ],
-      "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.": [
+      "Deploy": [
         ""
       ],
-      "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.": [
-        ""
+      "Details": [
+        "Detalls"
       ],
-      "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.": [
+      "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 Nutanix AHV.": [
+      "Download the script": [
         ""
       ],
-      "No Report Yet": [
-        ""
+      "Edit": [
+        "Edita"
       ],
-      "Unknown configuration status": [
+      "Edit Virt-who Config": [
         ""
       ],
-      "Unlimited": [
-        "Il·limitat"
+      "Enable AHV debug": [
+        ""
       ],
-      "Whitelist": [
-        "Llista blanca"
+      "Enable debugging output": [
+        ""
       ],
-      "Blacklist": [
-        "Llista negra"
+      "Enable debugging output?": [
+        ""
       ],
-      "General information": [
-        "informació general"
+      "Every 12 hours": [
+        ""
       ],
-      "Schedule": [
+      "Every 2 days": [
         ""
       ],
-      "Connection": [
+      "Every 2 hours": [
         ""
       ],
-      "Every hour": [
+      "Every 24 hours": [
         ""
       ],
-      "Every 2 hours": [
+      "Every 3 days": [
         ""
       ],
       "Every 4 hours": [
@@ -173,332 +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": [
-        "D'acord"
-      ],
-      "No change": [
+      "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.": [
         ""
       ],
-      "Unknown": [
-        "Desconegut"
-      ],
-      "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": [
+      "Filter host parents": [
         ""
       ],
-      "The virt-who report arrived within the interval": [
+      "Filter hosts": [
         ""
       ],
-      "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
+      "Filtering": [
+        "Filtratge"
+      ],
+      "Foreman server FQDN": [
         ""
       ],
-      "Prism Central": [
+      "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
         ""
       ],
-      "Prism Element": [
+      "Fully qualified host name or IP address of the hypervisor": [
         ""
       ],
-      "every %s hours": [
-        "cada %s hores"
+      "General information": [
+        "informació general"
       ],
-      "Success": [
-        "Correcte"
+      "HTTP Proxy": [
+        "Servidor intermediari HTTP"
       ],
-      "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.": [
         ""
       ],
-      "Unable to create virt-who config file": [
+      "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 sysconfig file": [
+      "Hammer command: ": [
         ""
       ],
-      "Unable to enable virt-who service using systemctl": [
-        ""
+      "Help": [
+        "Ajuda"
       ],
-      "Unable to start virt-who service, please see virt-who logs for more details": [
+      "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 install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
+      "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.": [
         ""
       ],
-      "Owner was not provided": [
+      "Hypervisor ID": [
         ""
       ],
-      "Interval was not provided": [
+      "Hypervisor Password": [
         ""
       ],
-      "Virt-who Configurations Status": [
+      "Hypervisor Server": [
         ""
       ],
-      "Configuration Status": [
+      "Hypervisor Type": [
         ""
       ],
-      "Count": [
+      "Hypervisor Username": [
         ""
       ],
-      "No Reports": [
+      "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 Change": [
+      "Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklist": [
         ""
       ],
-      "Total Configurations": [
+      "Hypervisor password, required for all hypervisor types except for libvirt/kubevirt.": [
         ""
       ],
-      "Latest Configurations Without Change": [
+      "Hypervisor type": [
         ""
       ],
-      "No configuration found": [
+      "Hypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.": [
         ""
       ],
-      "Config|Name": [
+      "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|Last Report": [
+      "Ignore Proxy": [
         ""
       ],
-      "Config|Interval": [
+      "Ignore proxy": [
         ""
       ],
-      "Edit Virt-who Config": [
+      "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.": [
         ""
       ],
-      "Virt-who Configurations": [
+      "Interval": [
         ""
       ],
-      "Edit": [
-        "Edita"
-      ],
-      "Status": [
-        "Estat"
-      ],
-      "Actions": [
-        "Accions"
+      "Interval was not provided": [
+        ""
       ],
-      "Delete virt-who configuration %s?": [
+      "Latest Configurations Without Change": [
         ""
       ],
-      "New Virt-who Config": [
+      "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": [
         ""
       ],
-      "Virt-who Configuration %s": [
+      "List of virt-who configurations": [
         ""
       ],
-      "Overview": [
-        "Apreciació global"
+      "List of virt-who configurations per organization": [
+        ""
       ],
-      "Deploy": [
+      "Microsoft Hyper-V fully qualified host name or IP address.": [
         ""
       ],
-      "Details": [
-        "Detalls"
+      "Name": [
+        "Nom"
       ],
-      "Hypervisor ID": [
+      "Name of this configuration, e.g. the name of the hypervisor": [
         ""
       ],
-      "Filtering": [
-        "Filtratge"
+      "New Config": [
+        "Configuració nova"
       ],
-      "Filter Hosts": [
+      "New Virt-who Config": [
         ""
       ],
-      "Exclude Hosts": [
+      "Newer version of virt-who is required, minimum version is %s": [
         ""
       ],
-      "Enable debugging output?": [
+      "No Change": [
         ""
       ],
-      "HTTP Proxy": [
-        "Servidor intermediari HTTP"
-      ],
-      "Ignore Proxy": [
+      "No Report Yet": [
         ""
       ],
-      "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:": [
+      "No Reports": [
         ""
       ],
-      "Hammer command: ": [
+      "No change": [
         ""
       ],
-      "Copy to clipboard": [
+      "No configuration found": [
         ""
       ],
-      "Configuration script: ": [
+      "Nutanix AHV’s IP address.": [
         ""
       ],
+      "OK": [
+        "D'acord"
+      ],
       "On the target virt-who host:": [
         ""
       ],
-      "1. Copy this configuration script to a safe directory.": [
+      "On this page you can define virt-who configurations for your hypervisors.": [
         ""
       ],
-      "2. Make the script executable and run it.": [
+      "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
         ""
       ],
-      "3. Delete the script.": [
+      "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.": [
         ""
       ],
-      "Download the script": [
+      "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.": [
         ""
       ],
-      "Foreman server’s fully-qualified host name, for example: foreman.example.com": [
+      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled": [
         ""
       ],
-      "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.": [
+      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
         ""
       ],
-      "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.": [
+      "Organization of the virt-who configuration": [
         ""
       ],
-      "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.": [
-        ""
+      "Overview": [
+        "Apreciació global"
       ],
-      "Filter hosts": [
-        ""
+      "Owner": [
+        "Propietari"
       ],
-      "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.": [
+      "Owner was not provided": [
         ""
       ],
-      "Exclude hosts": [
+      "Path to kubeconfig file": [
         ""
       ],
-      "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 Central": [
         ""
       ],
-      "Filter host parents": [
+      "Prism Element": [
         ""
       ],
-      "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.": [
+      "Prism Flavor": [
         ""
       ],
-      "Exclude host parents": [
+      "Renders a deploy script for the specified virt-who configuration": [
         ""
       ],
-      "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.": [
+      "Schedule": [
         ""
       ],
-      "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.": [
+      "Select the Prism flavor you are connecting to": [
         ""
       ],
-      "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.": [
+      "Show a virt-who configuration": [
         ""
       ],
-      "Ignore proxy": [
+      "Specifies how the hypervisor will be identified.": [
         ""
       ],
-      "Configuration file containing details about how to connect to the cluster and authentication details": [
+      "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.": [
         ""
       ],
-      "Path to kubeconfig file": [
-        ""
+      "Status": [
+        "Estat"
       ],
-      "Prism Flavor": [
-        ""
+      "Success": [
+        "Correcte"
       ],
-      "Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled ": [
+      "The configuration was not deployed yet or the virt-who was unable to report the status": [
         ""
       ],
-      "Enable AHV debug": [
+      "The virt-who report arrived within the interval": [
         ""
       ],
-      "Name of this configuration, e.g. the name of the hypervisor": [
+      "The virt-who report has not arrived within the interval, which indicates there was no change on hypervisor": [
         ""
       ],
-      "Name": [
+      "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.": [
         ""
       ],
-      "Owner": [
-        "Propietari"
-      ],
-      "Hypervisor Type": [
+      "Total Configurations": [
         ""
       ],
-      "Hypervisor Server": [
+      "Unable to create sysconfig file": [
         ""
       ],
-      "Hypervisor Username": [
+      "Unable to create virt-who config file": [
         ""
       ],
-      "Hypervisor Password": [
+      "Unable to enable virt-who service using systemctl": [
         ""
       ],
-      "Account password by which virt-who is to connect to the hypervisor instance.": [
+      "Unable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repository": [
         ""
       ],
-      "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 start virt-who service, please see virt-who logs for more details": [
         ""
       ],
-      "Interval": [
-        ""
+      "Unknown": [
+        "Desconegut"
       ],
-      "Configs": [
+      "Unknown configuration status": [
         ""
       ],
-      "On this page you can define virt-who configurations for your hypervisors.": [
+      "Unknown configuration status, caused by unexpected conditions": [
         ""
       ],
-      "One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.": [
+      "Unlimited": [
+        "Il·limitat"
+      ],
+      "Update a virt-who configuration": [
         ""
       ],
-      "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.": [
+      "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:": [
         ""
       ],
-      "Virt-who configurations": [
+      "VMware vCenter server’s fully qualified host name or IP address.": [
         ""
       ],
       "Virt-who Configs Status": [
         ""
       ],
-      "A plugin to make virt-who configuration easy": [
+      "Virt-who Configuration %s": [
         ""
       ],
-      "Create": [
-        "Crea"
-      ],
-      "Delete": [
-        "Suprimeix"
-      ],
-      "Destroy": [
-        "Destrueix"
-      ],
-      "Disable": [
-        "Inhabilita"
-      ],
-      "Enable": [
-        "Habilita"
-      ],
-      "Export": [
-        "Exporta"
-      ],
-      "Import": [
-        "Importa"
-      ],
-      "Remove Version": [
-        "Suprimeix la versió"
+      "Virt-who Configurations": [
+        ""
       ],
-      "Report": [
-        "Informe"
+      "Virt-who Configurations Status": [
+        ""
       ],
-      "Synchronize": [
-        "Sincronitza"
+      "Whitelist": [
+        "Llista blanca"
       ],
-      "Update": [
-        "Actualitza"
+      "every %s hours": [
+        "cada %s hores"
       ]
     }
   }