@cloudtower/parrot 0.15.0-alpha.0 → 0.15.3-alpha.0

package/dist/locales/en-US/host.json

@@ -1,397 +0,0 @@
-{
-    "access_ip": "Access IP",
-    "already_copy": "IP address already copied",
-    "average_usage_over_last_15_min": "Average usage over the past 2 hours",
-    "current_usage_percent": "Current usage",
-    "binding": "Binding",
-    "block": "Block",
-    "capacity_and_zone": "Capacity and Partition",
-    "cluster": "Cluster",
-    "connected_error": "Error",
-    "compatibility_model": "CPU Compatibility Model",
-    "connected_healthy": "Healthy",
-    "connected_warning": "Unhealthy",
-    "connecting": "Connecting",
-    "session_expired": "Disconnected",
-    "initializing": "Initializing",
-    "copy": "Copy",
-    "count_cores": "{count} cores",
-    "cpu": "CPU",
-    "cpu_model": "CPU Model",
-    "cpu_brand": "CPU Model",
-    "data_ip": "Storage IP",
-    "datacenters": "Data Center",
-    "zone": "Availability Zone",
-    "edit_host_name": "Edit Hostname",
-    "edit_ipmi": "Edit IPMI Information",
-    "edit_nic_mtu": "Edit NIC MTU",
-    "edit_nic_mtu_warning": "The NIC will be disconnected for a few seconds after modifying its MTU value due to the reallocation of network resources.",
-    "filter_host": "Filter Hosts",
-    "hdd_data_capacity": "Total HDD Capacity",
-    "hdd_disk_count": "HDD Count",
-    "host_no_exists": "The host no longer exists.",
-    "idle_capacity": "Available Capacity",
-    "internet_access": "Network Port",
-    "count_internet_access": "{count} network ports",
-    "invalid_capacity": "Invalid Capacity",
-    "ip_address": "IP Address",
-    "ipmi_ip": "IPMI IP",
-    "main_frequency": "CPU Frequency",
-    "management_ip": "Management IP",
-    "memory": "Memory",
-    "migrate_ip": "Migration IP",
-    "monitor": "Monitoring",
-    "mtu_out_of_range": "The MTU value should be between 1500 and 9000",
-    "nic": "NIC",
-    "nic_mtu_confirm": "It is confirmed that the physical switch has enabled the jumbo frame function.",
-    "nic_mtu_confirm_desc": "When the MTU is not equal to 1500, you need to enable the jumbo frame function on the switch at the same time. Otherwise, the network transmission speed will decrease.",
-    "nics": "Network Port",
-    "no_nic": "No NIC",
-    "physical_disk": "Physical Disk",
-    "provisioned_cpu_cores": "Provisioned vCPU",
-    "provisioned_memory_bytes": "Provisioned Memory",
-    "sort_by_disk_character": "Sort by disk drive letter",
-    "sort_by_nic_character": "Sort by NIC name",
-    "ssd_data_capacity": "Total SSD Capacity",
-    "ssd_disk_count": "SSD Count",
-    "pmem_disk_count": "PMem Region Count",
-    "pmem_dimm_count": "PMem Count",
-    "pmem_dimm_capacity": "Total PMem Capacity",
-    "storage": "Storage",
-    "store_ip": "Storage IP",
-    "total_cache_capacity": "Cache Capacity",
-    "total_capacity": "Total Capacity",
-    "total_cpu_cores": "CPU Core Count",
-    "total_cpu_hz": "CPU Frequency",
-    "total_cpu_sockets": "CPU Socket",
-    "total_data_capacity": "Total Storage Capacity",
-    "total_memory_bytes": "Total Memory",
-    "total_with_num": "Total {num}",
-    "unhealthy": "Unhealthy",
-    "unmounted": "Unmounted",
-    "update_host": "Update host {host_name }",
-    "mount_disk": "Mount disk {disk_name} onto the host {host_name}",
-    "unmount_disk": "Unmount disk {disk_name} from the host {host_name}",
-    "used_capacity": "Used Capacity",
-    "used_cpu_hz": "Used CPU",
-    "used_data_space": "Used Storage Capacity",
-    "used_memory_bytes": "Used Memory",
-    "used": "Used",
-    "invalid": "Invalid",
-    "idle": "Available",
-    "serial": "Serial Number",
-    "serial2": "Serial Number: {serial}",
-    "can_not_edit_host_name": "Failed to edit hostname",
-    "scan_too_long": "It may take a while to scan for hosts that can be added. You can also <0>skip this step</0> and try to discover the host manually.",
-    "please_wait": "Please wait...",
-    "discovering": "Scanning for hosts that can be added to the cluster",
-    "not_found": "No available hosts found",
-    "not_found_tip": "Please try to <0>rescan</0> or <1>add hosts manually</1>.",
-    "has_discovered": "{count} hosts are discovered. Please select the hosts that need to be added.",
-    "no_discovered": "No available hosts are found. You may input the host information manually.",
-    "cancel_discover": "Cancel manually discovering host",
-    "select_host_tip": "Did not find the host you want to add?",
-    "manual_discover": "Discover Manually",
-    "discover_host": "Discover Host",
-    "select_host": "Select Host",
-    "set_host_config": "Configure Host",
-    "deploy_host": "Deploy",
-    "add_host_title": "Add Host",
-    "system_not_match": "The SMTX OS version or the host's hypervisor is inconsistent with that of the cluster.",
-    "rdma_not_match": "The cluster has RDMA enabled, but there is no network port that supports RDMA on the host",
-    "all_flash_not_match": "The host is configured with all SSDs but the license of the cluster does not support all-flash configuration.",
-    "size_not_match": "The host capacity exceeds the maximum capacity limit.",
-    "cpu_vendor_not_match": "The host cannot be added to the cluster because its CPU vendor is inconsistent with that of the cluster.",
-    "discovered_hosts_title": "Discovered Hosts",
-    "count": "",
-    "input_error": "Please fill in a valid IPv4, IPv6 or MAC address.",
-    "empty_input_error": "Please fill in the host address.",
-    "input_placeholder": "IPv4, IPv6 address or MAC address",
-    "manual_desc": "Use the host's IP address or MAC address to manually discover the host that needs to be added.",
-    "host_address": "Host IP Address",
-    "rescan": "Rescan",
-    "selected_hosts": "{count} hosts have been selected.",
-    "success_msg": "{inputs} hosts have been successfully discovered and selected.",
-    "please_select": "Please select at least one host.",
-    "set_host_config_desc": "Configure the {count} selected hosts",
-    "management_port": "Management Network port",
-    "storage_port": "Storage Network Port",
-    "vmware_access_port": "VMware access port",
-    "vmware_access_ip": "VMware access IP",
-    "access_port": "Access Network Port",
-    "labels": "Labels",
-    "go_to_host_detail": "Go to Host Details",
-    "power_name": "Power Supply Name",
-    "click_host_or_power_for_more_info": "Click the host or power for more information.",
-    "disk_layout_not_provided": "The server does not provide a hard disk layout.",
-    "disk_layout_not_provided_physical_slot": "Obtaining information about physical disk slots from this model of storage controller is not supported.",
-    "slot_number": "Slot Count",
-    "slot_number2": "Slot Count: {slot_number}",
-    "goto_disk_detail": "View hard disk details",
-    "slot_empty": "No disk inserted",
-    "click_disk_for_more_info": "Click the hard disk for more information",
-    "forward_view": "Front View",
-    "backward_view": "Backward View",
-    "power": "Power",
-    "unexpand_brick_info": "Collapse the chassis information",
-    "expand_brick_info": "Expand the chassis information",
-    "server_serial": "Server Model",
-    "memory_capacity": "Memory Capacity",
-    "host_info": "Host Information",
-    "license_checking_title": "Checking the license of the target cluster",
-    "adding_host_title": "Add a host to the current cluster",
-    "cannot_add_host_title": "Unable to Add Host",
-    "tower_and_cluster_full_desc": "The maximum number of licensed hosts has been reached, so no more hosts can be added.",
-    "tower_and_cluster_full_light_desc": "Please update the license before trying to add the host.",
-    "tower_full_desc": "The maximum number of licensed hosts ({count} in total) has been reached.",
-    "tower_full_light_desc": "Please update the license before trying to add the host.",
-    "cluster_full_desc": "There are {count} hosts in the cluster, which reaches the maximum number of licensed hosts.",
-    "cluster_full_light_desc": "Please update the cluster license before trying to add the host.",
-    "cannot_add_zero_hosts": "Please select at least one host.",
-    "add_too_many_hosts_to_tower": "{totalCount} licensed hosts and adding {count} hosts is not allowed.",
-    "add_too_many_hosts_to_cluster": "{totalCount} hosts licensed and adding {count} hosts is not allowed.",
-    "add_too_many_hosts_to_everoute": "There are {licenseCount} CPU sockets left in the Everoute license. Adding {count} CPU sockets is not allowed.",
-    "no_host_management_ports": "Please select the management network port.",
-    "no_host_management_ip": "Please fill in the management IP.",
-    "ip_address_not_in_management_network": "The IP address is not in the management network segment.",
-    "do_not_know_management_network": "The IP cannot be validated since the management network is unknown.",
-    "no_host_storage_ports": "Please select the storage network port.",
-    "no_host_storage_ip": "Please fill in the storage IP.",
-    "ip_address_not_in_storage_network": "The IP address is not in the storage network segment.",
-    "do_not_know_storage_network": "The IP cannot be validated because the storage network is unknown.",
-    "no_host_access_ports": "Please select the access network port.",
-    "no_host_access_ip": "Please fill in the access IP.",
-    "ip_address_not_in_access_network": "The IP address is not in the access network segment.",
-    "do_not_know_access_network": "The IP cannot be validated since access network is unknown.",
-    "no_esxi_ip": "Please fill the IP of ESXi server.",
-    "no_esxi_username": "Please fill the user ID of ESXi server.",
-    "no_esxi_password": "Please fill the password of ESXi server.",
-    "no_ipmi_ip": "Please fill the IP of IPMI.",
-    "no_ipmi_username": "Please fill the user id of IPMI.",
-    "no_ipmi_password": "Please fill the password of IPMI.",
-    "invalid_ip_address": "The IP address is invalid.",
-    "ip_address_conflict_within_cluster": "The IP address has been occupied.",
-    "ip_address_conflict_within_form": "The IP address has been occupied by another host.",
-    "no_disk_function": "Disk use is not specified.",
-    "has_disks_without_function": "The disks on the host have not been assigned a purpose of use.",
-    "meta_disks_not_enough": "There should be at least 2 disks containing a meta partition.",
-    "data_disks_not_enough": "There should be at least 1 disk for storage.",
-    "host_has_been_discovered": "This host has been discovered.",
-    "host_has_been_deployed": "This host has been added to another cluster.",
-    "host_cannot_be_discovered": "No available hosts found.",
-    "disk_function_tooltip1": "Specify a purpose for the disk without a metadata partition. It's recommended to specify a high-speed disk as the cache disk and a large-capacity yet relatively low-speed disk as the data disk.",
-    "disk_function_tooltip2": "The purpose of the disk requires considering whether the disk contains a metadata partition.",
-    "disk_function_tooltip3": "Manually specify a purpose for each disk. It's recommended to specify a high-speed disk as the cache disk and a large-capacity yet relatively low-speed disk as the data disk. Ensure that there are at least 2 cache disks containing metadata partitions.",
-    "disk_function_tooltip4": "Manually specify a purpose for each disk. Ensure that there are at least 2 cache disks containing metadata partitions.",
-    "disk_function_tooltip5": "For hosts that have enabled RAID1 for metadata partitions, select the use for disks that do not contain metadata partitions. Select high-speed disks as cache disks, and large-capacity and relatively low-speed physical disks as data disks. For metadata partitions For hosts that do not enable RAID1, manually select the purpose for each physical disk. Make sure that at least two cache disks contain metadata partitions.",
-    "disk_function_tooltip6": "For hosts that have enabled RAID1 for metadata partitions, their use has been determined based on whether the disks contain metadata partitions. For hosts that do not enable RAID1 for metadata partitions, manually select the use for each physical disk. Make sure at least Two cache disks contain metadata partitions.",
-    "deploy_in_progress": "The host is being added to the cluster according to the configuration...",
-    "deploy_completed": "Deployment Completed",
-    "deploy_fail_alert": "Failed to deploy {count} hosts. Please clear the configuration information of failed hosts and try again.",
-    "empty_as_not_set": "Leave blank to not set",
-    "host_log_title": "Deployment log of host {name}",
-    "check_log": "Check Log",
-    "select_nic": "Select network port",
-    "cluster_disconnect_no_data": "The connection to cluster is abnormal and data cannot be retrieved.",
-    "cluster_cannot_support_pmem": "The current cluster does not support the PMem mode.",
-    "host_dose_not_support_pmem": "The host does not contain a PMem and cannot be added to the cluster.",
-    "pmem_version_inconsistent": "The firmware version of PMem in the host is inconsistent.",
-    "pmem_not_healthy": "Contains an unhealthy PMem.",
-    "pmem_has_wrong_region": "The host contains a Region which is not in App Direct mode.",
-    "pmem_region_is_not_one": "The number of regions is not 1.",
-    "pmem_not_in_numa_node": "Contains a PMem that is not in NUMA Node0.",
-    "pmem_not_in_region": "There is a PMem that is not added to the region.",
-    "lack_of_rdma_iface": "The host does not contain a NIC that supports RDMA.",
-    "do_not_match_pmem_cluster_requirements": "The host does not meet the deployment requirements of the PMem mode: { reasons }",
-    "host_name_empty_validation": "Please fill in the host name",
-    "host_name_length_validation": "The length of a host name is within 2~64.",
-    "host_name_content_validation": "Only uppercase and lowercase English letters, numbers and hyphens (-) are supported.",
-    "host_name_beginning_validation": "A host name cannot start with hyphens (-) or numbers.",
-    "view_all": "To see all",
-    "unit_rpm": "Unit: RPM",
-    "edit_host_scvm_name": "Edit SCVM Hostname",
-    "scvm_name": "SCVM Hostname",
-    "can_not_edit_scvm_name": "Fail to edit SCVM hostname",
-    "not_support_edit_scvm_name": "The version of the cluster {cluster_name} to which the selected host {host_name} belongs is lower than 4.0.5 and does not support editing the SCVM hostname.",
-    "selectd_host_belongs_cluster_not_support_edit_host_name_yet": "The version of the cluster {cluster_name} to which the selected host {host_name} belongs is lower than 4.0.5 and does not support editing the hostname.",
-    "scvm_name_duplicated": "A SCVM host with the same name already exists in the cluster.",
-    "host_name_duplicated": "A host with the same name already exists in the cluster.",
-    "cluster__architecture": "CPU Architecture",
-    "select_all": "Select All",
-    "cancel_selected_items": "Unselect All",
-    "not_in_same_physical_nic": "Not belong to the same physical NIC",
-    "cpu_arch": "CPU Architecture",
-    "host_zone_placeholder": "Select the available zone to which the host belongs.",
-    "host_zone_validation": "The available zone for the host {name} cannot be left empty.",
-    "topo_invalid_desc": "The cluster is an active-active cluster. Make sure to configure racks for hosts in the primary and secondary available zones within the cluster before attempting to add a host.",
-    "topo_invalid_light_desc": "Add all hosts in the cluster to the rack in the Rack Configuration page.",
-    "deploy_success_alert": "A new host has been added successfully. Please configure the corresponding chassis and rack for the host on the Rack Configuration page.",
-    "deploy_success_alert_plural": "{count} hosts have been added successfully. Please configure the corresponding chassis and racks for the hosts on the Rack Configuration page.",
-    "deploy_success_with_vhost_alert": "A new host has been added successfully. Please restart the host to ensure that Boost mode takes effect. Then configure the corresponding chassis and rack for the host on the Rack Configuration page.",
-    "deploy_success_with_vhost_alert_plural": "{count} hosts have been added successfully. Please restart the hosts to ensure that Boost mode takes effect. Then configure the corresponding chassis and racks for the hosts on the Rack Configuration page.",
-    "reserved_cpu_cores_for_system_service": "CPU for System Services",
-    "vcpu_count_of_all_vms_nonexclusive": "CPU Allocation for All VMs",
-    "cpu_over_allocation_ratio_for_all_vms": "CPU Allocation Ratio for All VMs",
-    "vcpu_count_of_active_vms_nonexclusive": "CPU Allocation for Active VMs",
-    "cpu_over_allocation_ratio_for_active_vms": "CPU Allocation Ratio for Active VMs",
-    "allocable_cpu_cores_for_vm_exclusive": "Available Exclusive CPUs",
-    "canBeExclusive": "Available",
-    "exclusive": "Used",
-    "host_reserved_cpu_tip": "CPUs Reserved for System Services and VMs",
-    "logical_cpu": "Logical CPU",
-    "provisioned_cpu_cores_for_vm_exclusive": "Used Exclusive CPUs",
-    "reserved": "Reserved",
-    "total_cpu": "{num} CPU in total",
-    "esxi_host_cpu": "ESXi Host CPU",
-    "scvm_host_cpu": "SCVM Host CPU",
-    "esxi_host_memory": "ESXi Host Memory",
-    "scvm_host_memory": "SCVM Host Memory",
-    "cpu_usage": "CPU Usage",
-    "memory_usage": "Memory Usage",
-    "data_space_usage": "Storage Capacity Usage",
-    "all_cold_vms_cannot_move_back": "{count} virtual machine that was automatically cold migrated will not be migrated back.",
-    "all_cold_vms_cannot_move_back_plural": "All {count} virtual machines that were automatically cold migrated will not be migrated back.",
-    "all_hot_vms_cannot_move_back": "{count} virtual machine that was automatically hot migrated will not be migrated back.",
-    "all_hot_vms_cannot_move_back_plural": "All {count} virtual machines that were automatically hot migrated will not be migrated back.",
-    "all_vms_cannot_start": "All {count} virtual machines that were automatically shut down will not be powered on.",
-    "can_move_back_vm_count": "{count} virtual machine that can be migrated back",
-    "can_move_back_vm_count_plural": "{count} virtual machines that can be migrated back",
-    "can_start_vm_count": "{count} virtual machine that can be powered on",
-    "can_start_vm_count_plural": "{count} virtual machines that can be powered on",
-    "cannot_enter_maintenance_mode": "Unable to Enter Maintenance Mode",
-    "cannot_exit_maintenance_mode": "Unable to Exit Maintenance Mode",
-    "cannot_move_back_vm_count": "{count} virtual machine that cannot be migrated back",
-    "cannot_move_back_vm_count_plural": "{count} virtual machines that cannot be migrated back",
-    "cannot_start_vm_count": "{count} virtual machine that cannot be powered on",
-    "cannot_start_vm_count_plural": "{count} virtual machines that cannot be powered on",
-    "check_cluster_capacity": "Checking the available storage space in the cluster",
-    "check_cluster_quorum_services": "Checking the state of services",
-    "check_exists_one_replica_pextent": "Checking if the host has any data block with the replication factor of 1",
-    "check_exists_suspend_or_unknown_vms": "Checking if the host has any virtual machine in the suspended or unknown state",
-    "check_ha_enabled_vms_can_offline_migrate": "Checking if all virtual machines with high availability enabled on the host can be migrated",
-    "check_host_exists_maintenance_mode_host": "Checking if any hosts in the cluster are entering maintenance mode or already in maintenance mode",
-    "check_host_exists_maintenance_mode_scvm": "Checking if any SCVMs in the cluster are entering maintenance mode or already in maintenance mode",
-    "check_host_state_and_exist": "Check service state and exit",
-    "check_services_item": "The service state of the current host",
-    "check_services_item_error": "The following services of the current host have operational exceptions",
-    "check_services_item_success": "The service of the current host is running properly.",
-    "check_storage_need_recover": "The progress of data recovery in the cluster",
-    "check_storage_network_item": "The connection status of the current host's storage network",
-    "check_storage_network_item_error": "The storage network of the current host has connection exceptions",
-    "check_storage_network_item_success": "The storage network of the current host is connected properly",
-    "check_target_host_storage_network": "The connection state of the current host's storage network",
-    "check_vms_can_live_migrate": "Checking if all running virtual machines on the current host can be migrated",
-    "confirm_check_vms_can_live_migrate": "Shut down {count} virtual machines that cannot be migrated",
-    "session_expired_count": "Disconnected",
-    "connected_healthy_count": "Healthy",
-    "count_session_expired": "Disconnected {count}",
-    "count_in_maintenance": "{count} in maintenance mode",
-    "count_in_use": "{count} in use",
-    "count_initializing": "Initializing {count}",
-    "count_connected_error": "Error {count}",
-    "enter_maintenance_mode": "Enter Maintenance Mode",
-    "enter_maintenance_mode_alert_info1": "1. When entering maintenance mode, this host will not be available as a destination for scheduling virtual machines.",
-    "enter_maintenance_mode_alert_info2": "2. If data recovery occurs while entering maintenance mode, data recovery will be completed first and then continue into maintenance mode.",
-    "enter_maintenance_mode_alert_info3": "3. Cold data on the host will be recovered after 12 hours in maintenance mode.",
-    "enter_maintenance_mode_pre_check_host": "Checking if the host <1>{name}</1> can enter maintenance mode......",
-    "enter_maintenance_mode_pre_check_scvm": "Checking if the scvm <1>{name}</1> can enter maintenance mode......",
-    "enter_maintenance_mode_pre_check_error_host": "The host {name} failed to enter maintenance mode. Please address the following issues before trying entering the mode again.",
-    "enter_maintenance_mode_pre_check_error_scvm": "The SCVM {name} failed to enter maintenance mode. Please address the following issues before trying entering the mode again.",
-    "entering_maintenance_mode": "Entering Maintenance Mode",
-    "error_check_cluster_capacity": "Hosts in the cluster do not have sufficient storage capacity to recover all the data of the current host.",
-    "error_check_cluster_quorum_services": "The service operation state does not meet requirements. ",
-    "error_check_cluster_quorum_services_info1": "The zookeeper service of other nodes in the cluster has exceptions.",
-    "error_check_cluster_quorum_services_info2": "The mongodb service of other nodes in the cluster has exceptions.",
-    "error_check_cluster_quorum_services_info3": "The cluster has no other meta nodes except the current node.",
-    "error_check_cluster_quorum_services_info4": "The job-center-worker service on the current node is running abnormally.",
-    "error_check_cluster_quorum_services_info5": "The libvirt service on the current node is running abnormally.",
-    "error_check_exists_one_replica_pextent": "The current host has data blocks with a replication factor of 1.",
-    "error_check_exists_suspend_or_unknown_vms": "The current host has virtual machines in a Suspended or Unknown state.",
-    "error_check_ha_enabled_vms_can_offline_migrate": "Some high-availability-enabled virtual machines on the current host are unable to be migrated.",
-    "error_check_host_exists_maintenance_mode": "The cluster has one or more hosts in maintenance mode.",
-    "error_check_host_exists_maintenance_mode_info1": "The host {host_name} is entering maintenance mode. Please put the current host into maintenance mode after the host {host_name} has completed its maintenance tasks and exited maintenance mode.",
-    "error_check_host_exists_maintenance_mode_info2": "The host {host_name} is in storage maintenance mode. Please put the current host into maintenance mode after the host {host_name} has completed its maintenance tasks and exited maintenance mode.",
-    "error_check_host_exists_maintenance_mode_info3": "The {clusterTypeName} {host_name} is in maintenance mode. Please put the current host into maintenance mode after the host {host_name} has completed its maintenance tasks and exited maintenance mode.",
-    "error_check_storage_need_recover": "The cluster has data recovery in progress.",
-    "error_check_storage_need_recover_info": "Please try to enter maintenance mode after data recovery is complete.",
-    "error_check_target_host_storage_network": "The storage network of the current host has connection exceptions.",
-    "error_check_vms_can_live_migrate": "The virtual machine running system services on the current host is in the Running state and cannot be migrated.",
-    "error_enter_maintenance_mode_pre_check_host": "The host <1>{name}</1> cannot enter maintenance mode. Please address the following issues before trying entering the mode again.",
-    "error_enter_maintenance_mode_pre_check_scvm": "The SCVM <1>{name}</1> cannot enter maintenance mode. Please address the following issues before trying entering the mode again.",
-    "error_exit_maintenance_mode_pre_check_host": "The host <1>{name}</1> cannot exit maintenance mode. Please address the following issues before trying exiting the mode again.",
-    "error_exit_maintenance_mode_pre_check_scvm": "The SCVM <1>{name}</1> cannot exit maintenance mode. Please address the following issues before trying exiting the mode again.",
-    "exit_maintenance_mode": "Exit Maintenance Mode",
-    "exit_maintenance_mode_pre_check_host": "Checking if the host <1>{name}</1> can exit maintenance mode...",
-    "exit_maintenance_mode_pre_check_scvm": "Checking if the SCVM <1>{name}</1> can exit maintenance mode...",
-    "exit_maintenance_mode_pre_check_error_host": "The host <1>{name}</1> failed to exit maintenance mode. Please address the following issues before trying exiting the mode again.",
-    "exit_maintenance_mode_pre_check_error_scvm": "The SCVM <1>{name}</1> failed to exit maintenance mode. Please address the following issues before trying exiting the mode again.",
-    "healthy_in_use": "Working Properly",
-    "host_error": "The host reports an error.",
-    "host_health": "The host status is healthy.",
-    "host_initializing": "The host is initializing...",
-    "host_session_expired": "The host is disconnected.",
-    "in_maintenance": "In Maintenance",
-    "in_maintenance_mode": "The host is already in maintenance mode",
-    "in_maintenance_mode_for_time": "The host is already in maintenance mode for {time}.",
-    "in_use": "In Use",
-    "initializing_count": "Initializing",
-    "maintenance_mode": "Maintenance Mode",
-    "maintenance_mode_entering": "Entering Maintenance Mode",
-    "move_back_cold_migration_vm": "Migrate back cold-migrated virtual machines",
-    "move_back_cold_migration_vm_desc": "Virtual machines that were automatically cold-migrated during the process of entering maintenance mode will be moved back to this host. It is only supported for shutdown virtual machines.",
-    "move_back_hot_migration_vm": "Migrate back hot-migrated virtual machines",
-    "move_back_hot_migration_vm_desc": "Virtual machines that were automatically hot-migrated during the process of entering maintenance mode will be moved back to this host. It is only supported for running virtual machines.",
-    "no_auto_cold_migration_vm": "No virtual machines that were automatically cold-migrated",
-    "no_auto_hot_migration_vm": "No virtual machines that were automatically hot-migrated",
-    "no_auto_shutdown_vm": "No virtual machines that were automatically shutdown",
-    "notice_enter_maintenance_mode_pre_check1": "The host <1>{name}</1> can enter maintenance mode. Before that, please consider the following issues. Are you sure you want to migrate virtual machines on this host and then put it into maintenance mode?",
-    "notice_enter_maintenance_mode_pre_check2": "The host <1>{name}</1> can enter maintenance mode. Before that, please consider the following issues. Are you sure you want to migrate or shut down virtual machines on this host and then put it into maintenance mode?",
-    "connected_error_count": "Error",
-    "start_auto_shutdown_vm": "Power on the virtual machines that were automatically shut down",
-    "start_auto_shutdown_vm_desc": "Power on the virtual machines that were automatically shut down during the process of entering maintenance mode. It is only supported for shutdown virtual machines.",
-    "success_check_cluster_capacity": "Hosts in the cluster have sufficient storage capacity.",
-    "success_check_cluster_quorum_services": "The service is running properly.",
-    "success_check_exists_one_replica_pextent": "The current host does not have a data block with a replication factor of 1.",
-    "success_check_exists_suspend_or_unknown_vms": "The current host does not have a virtual machine in the Suspended or Unknown state.",
-    "success_check_ha_enabled_vms_can_offline_migrate": "Virtual machines with high availability enabled on the current host can be all migrated, or no virtual machines on the current host have enabled high availability.",
-    "success_check_host_exists_maintenance_mode": "The cluster has no hosts in maintenance mode.",
-    "success_check_storage_need_recover": "The cluster has no data recovery in progress.",
-    "success_check_target_host_storage_network": "The storage network of the current host is connected properly.",
-    "success_check_vms_can_live_migrate": "Running virtual machines on the current host can be all migrated, or there are no running virtual machines on the current host.",
-    "success_enter_maintenance_mode_pre_check": "The host <1>{name}</1> can enter maintenance mode. Are you sure you want to migrate the virtual machine on this host and put the host into maintenance mode?",
-    "success_exit_maintenance_mode_pre_check": " <1>Key services</1> of the {clusterTypeName} <0>{name}</0> <2>are now running properly</2>. Are you sure you want this host to exit maintenance mode?",
-    "vm_has_been_deleted": "The virtual machine has been deleted.",
-    "vm_has_host_devices": "The virtual machine has pass-through devices.",
-    "no_host_migration_ip": "Please fill in the migration IP.",
-    "add_host_vdses_desc": "Please associate at least one properly-connected physical network port with the following virtual distributed switches:",
-    "add_host_vdses_light_desc": "Network ports associated with the same virtual distributed switch need to be physically connected to each other. Each network port can be assigned to the only one virtual distributed switch.",
-    "add_host_vds_desc1": "It's already associated with {vlans}",
-    "add_host_vds_desc2": "Select a network port with a rate above 10GbE.",
-    "add_host_vds_desc3": "To select 2 or more RDMA network ports, the network ports should belong to the same physical NIC, and the rate should be higher than 10GBE.",
-    "mgt_type": "management network",
-    "storage_type": "storage network",
-    "access_type": "access network",
-    "migration_type": "migration network",
-    "rdma_storage_type": "storage network with RDMA enabled",
-    "rdma_access_type": "access network with NVMe over RDMA enabled",
-    "vm_status_changed": "The virtual machine is not in the \"Running\" state, or the host where it is located has been changed.",
-    "vm_usage_error_info": "{vm_usage}：{vms}.",
-    "vmware_check_exists_one_replica_pextent": "Checking if the current host has any data block with a replication factor of 1",
-    "vmware_enter_maintenance_mode_alert_info1": "1. Please put SMTX OS into maintenance mode first. Then shut down the SCVM and put this ESXi host into vSphere maintenance mode.",
-    "vmware_error_check_exists_one_replica_pextent": "The current host has data blocks with a replication factor of 1.",
-    "vmware_error_exit_maintenance_mode_pre_check": "The host <1>{name}</1> was unable to exit maintenance mode. Please address system service exceptions before trying exiting again.",
-    "vmware_exit_maintenance_mode_pre_check": "Checking the service operation status of the host <1>{name}</1>...",
-    "vmware_notice_enter_maintenance_mode_pre_check": "The {clusterTypeName} <1>{name}</1> can enter maintenance mode. Before that, please consider the following issues. Are you sure you want this host to enter maintenance mode?",
-    "vmware_success_check_exists_one_replica_pextent": "The current host does not have a data block with a replication factor of 1.",
-    "vmware_success_enter_maintenance_mode_pre_check": "The {clusterTypeName} <1>{name}</1> can enter maintenance mode. Are you sure you want to put this host into maintenance mode?",
-    "warning_check_vms_can_live_migrate": "You need to shut down the virtual machines that are unable to be migrated so that the host can enter maintenance mode.",
-    "warning_check_vms_can_live_migrate_info": "The following virtual machines cannot be migrated because the cluster has insufficient compute resources, or the virtual machines have been mounted with pass-through devices or cannot meet the <b>Must</b> requirements of the placement group policy after migration:",
-    "exist_host_entering_maintenance_mode": "The host {name} in the cluster is entering maintenance mode.",
-    "exist_host_in_maintenance_mode": "The host {name} in the cluster is already in maintenance mode.",
-    "exist_host_in_maintenance_mode_desc": "Please try adding the host again after the host exits maintenance mode.",
-    "inoperable_vm_reason": "{vm_name}: <0>{reason}</0>",
-    "vm_in_recycle_bin": "VM already moved to recycle bin",
-    "vm_status_changed_hot_migration": "The virtual machine is not in the <b>Running</b> state or its host is not undergoing changes.",
-    "warning_check_vms_can_live_migrate2": "The following virtual machines cannot be migrated and will be shut down when the host enters maintenance mode.",
-    "information": "Information"
-}

package/dist/locales/en-US/httpCode.json

@@ -1,16 +0,0 @@
-{
-    "Bad Request": "The client's request has a syntax error that the server cannot understand.",
-    "Unauthorized": "Request user authentication.",
-    "Forbidden": "The server understands the client's request, but refuses to execute the request.",
-    "Not Found": "The server cannot find the resource based on the client's request.",
-    "Method Not Allowed": "The method in the client request is forbidden.",
-    "Not Acceptable": "The server cannot fulfill the request based on the content characteristics of the client request.",
-    "Proxy Authentication Required": "Request proxy authentication.",
-    "Request Time-out": "The server has been waiting too long for a request from the client.",
-    "Internal Server Error": "The request could not be completed due to an internal server error.",
-    "Not Implemented": "The server does not support the requested function and cannot complete the request.",
-    "Bad Gateway": "A server acting as a gateway or proxy received an invalid response from the remote server when attempting to execute a request.",
-    "Service Unavailable": "Due to overloading or system maintenance, the server is temporarily unable to process the client's request.",
-    "Gateway Time-out": "The server acting as a gateway or proxy did not get the request from the remote server in time.",
-    "HTTP Version not supported": "The server does not support the requested version of the HTTP protocol and cannot complete processing."
-}

package/dist/locales/en-US/installer.json

@@ -1,67 +0,0 @@
-{
-    "step_IDLE": "Associate CloudTower",
-    "step_CONFIGURE": "Configure CloudTower Environment",
-    "step_INSTALL": "Install CloudTower",
-    "step_DONE": "Installation Completed",
-    "operation": "How to Operate",
-    "hint1": "1. Visit your CloudTower environment.",
-    "hint2": "2. On the \"Infrastructure > Cluster\" page, click the \"+\" button at the upper-right corner of the title area.",
-    "hint3": "3.  Select \"Add Cluster\" in the pop-up menu.",
-    "hint4": "4. Enter the connection information of the cluster. Follow the wizard to complete the addition.",
-    "hint5": "Use CloudTower to manage both SMTX OS and SMTX ZBS clusters and get a one-stop experience of infrastructure management.",
-    "connect_cluster": "Associate the cluster to: ",
-    "new_cluster": "New CloudTower Environment",
-    "guide": "The wizard will help you to install CloudTower in the current cluster.",
-    "existed_cluster": "Existing CloudTower Environment",
-    "connect_existed": "Associate the cluster to a new or an existing CloudTower environment: ",
-    "hint6": "1. Visit the vCenter to which the current cluster belongs.",
-    "hint7": "2. Install CloudTower according to User Manual.",
-    "hint8": "3. After completing installation and logging into CloudTower, click the \"+\" button at the upper-right corner of the title area to associate the current cluster to CloudTower.",
-    "upload_file_desc": "Drag and drop the file here, or <0> Select File </0> to upload.",
-    "validate_vm_ip": "Please set the IP address of CloudTower.",
-    "validate_vm_ip_format": "Please enter the correct IP address format.",
-    "validate_vm_netmask": "Please set the subnet mask of CloudTower.",
-    "validate_vm_gateway": "Please set the gateway of CloudTower.",
-    "validate_org_name": "Please set the organization name of CloudTower.",
-    "validate_root_password": "Please set the super administrator password of CloudTower.",
-    "validate_file": "Please select the installation image of CloudTower.",
-    "spec": "Select to Configure CloudTower Environment",
-    "spec_low": "Low Configurations",
-    "spec_low_desc": "It is recommended to manage up to 3 clusters, 30 hosts, and 300 VMs.",
-    "spec_low_content": "2 vCPU, 4 GiB memory, 50 GiB storage (logical)",
-    "spec_medium": "Medium Configurations",
-    "spec_medium_desc": "It is recommended to manage up to 10 clusters, 100 hosts, and 1000 VMs.",
-    "spec_medium_content": "4 vCPU, 8 GiB memory, 100 GiB storage (logical)",
-    "spec_high": "High Configurations",
-    "spec_high_desc": "It is recommended to manage up to 100 clusters, 1000 hosts, and 10000 VMs.",
-    "spec_high_content": "8 vCPU, 16 GiB memory, 400 GiB storage (logical)",
-    "vm_ip": "Set IP Address of CloudTower",
-    "vm_netmask": "Set Subnet Mask of CloudTower",
-    "vm_gateway": "Set Gateway of CloudTower",
-    "org_name": "Set Organization Name of CloudTower",
-    "root_password": "Set Super Administrator Password",
-    "start_install": "Start Installation",
-    "state_UPLOADING": "Uploading the installation image...",
-    "state_DECOMPRESSING": "Unzipping the installation image...",
-    "state_READY_TO_INSTALL": "Preparing to install...",
-    "state_INSTALLING": "Installing...",
-    "state_BOOTSTRAPPING": "Starting CloudTower...",
-    "state_DONE": "Installation Succeeded",
-    "state_FAILED": "Installation Failed",
-    "done_desc": "Click Finish, the page will jump to your CloudTower environment in {count} second(s).",
-    "done_desc2": "About to jump to CloudTower in {count} second(s)...",
-    "visit_cloudtower": "Visit CloudTower",
-    "set_vip": "Set Cluster Management Virtual IP Address",
-    "set_vip_guide": "Used to associate the newly deployed cluster to CloudTower.",
-    "missing_vip": "Please enter a management virtual IP.",
-    "finish": "Finish",
-    "finish_tip": "The deployment has been completed, now you can enter the corresponding environment for the subsequent operations.",
-    "back_to_configure": "Go back to the configuration steps",
-    "file": "Select a file",
-    "vhost_title": "Please reboot all the hosts in the cluster to complete the deployment.",
-    "vhost_desc": "The cluster has enabled Boost mode and all the hosts need to be rebooted. During the reboot process, this page will be invalid.",
-    "next_steps": "Next Steps",
-    "vhost_hint1": "1. Reboot all the hosts in the cluster.",
-    "vhost_hint2": "2. After the reboot is completed, refresh the current page.",
-    "vhost_hint3": "3. Follow the subsequent wizards to associate the cluster to a new or an existing CloudTower."
-}

package/dist/locales/en-US/iscsiConnection.json

@@ -1,12 +0,0 @@
-{
-    "host": "Host Connected",
-    "initiator_ip": "Client IP",
-    "client_port": "Client Port",
-    "access_ip": "Access IP",
-    "iscsi_target": "Connected Target",
-    "nvmf_subsystem": "Connected Subsystem",
-    "type": "Storage Object Type",
-    "connection_object": "Connected Storage Object",
-    "iscsi_target__name": "Connected Storage Object",
-    "tr_type": "Transport Type"
-}