L3|H6I),<)?A5L!7 ?L! %)Ogode!Oq      ! ! ,!:!P!f!{!!!!!! ""!8"Z"a" i""""O#W#`#t#y##### ## # # $ $ )$ 7$ E$ P$^$ s$$&&&& && && ''N#'9r'''!' ' ((S)d)i)H3+ |,,v/-S-- . ..T. #0 00=0 11/1K1a1 s11/1 1 1112"222$L2q2303:3;4 Q4\4<p4 4 4 4 444 55I-5w56 89]:*:;!;';>;U; m; {; ;;;;;*; ;<0<?< N<o<<@<<<==-=I=0g==R@Y@ a@n@ ~@@V@?@/9AjiA*ABC%4C1ZC}CK DVD^D={D DDDDEEGVGpGGG GGG0jI*IIIJJJJ1K5K0MHM6N9OOOO OODQ RR RRS*S 1Sf>SiS!T 1T>TTT dTrT TTTEUXUtU{UU UUUU$UV&V-V=VVV iVvVVVVVVVV|WW WWWWWWW W X X "X /X =X GX TX aX kXxX XXeZ lZ vZZ ZZ ZZZZHZ0E[ v[[[ [v[2\\\z\;f^ __u:`S`aa aa5a bccccdd /d mKmRmbmimmm m mmm m.n0n7nGn]n%dnn nbn%q,q3qBqRqYq7uqCq%qFr^r bsos"s-srsDQttt*t tttuu'u>uOubuuuuuu uu@vw(w>wQwawww w wC&zg"m`/ AL29RVZEYG  Dj)sU>l.I13fd^nT[7;M q5?k+eHyvF_xXu =~P|SwW6\i,bc}-toa%Qr]N$@Bh{J48!:< '(*O0pK#1. Copy this configuration script to a safe directory.2. Make the script executable and run it.3. Delete the script.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.A plugin to make virt-who configuration easyAHV update intervalAbstractAbstract async taskAccount name by which virt-who is to connect to Nutanix AHV.Account name by which virt-who is to connect to the hypervisor, in the format domain_name\account_name. 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 /etc/virt-who.conf, then two backslashes are required. For further details, see Red Hat Knowledgebase solution How to use a windows domain account with virt-who for more information.Account name by which virt-who is to connect to the hypervisor.Account name by which virt-who is to connect to the hypervisor. By default this is Administrator. 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.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 Red Hat Knowledgebase solution How to configure virt-who for a KVM host for more information.Account password by which virt-who is to connect to the hypervisor instance.Action with sub plansActionsAgent actionApplicable only for esx provider type. Hosts which parent (usually ComputeResource) name is specified in comma-separated list in this option will NOT 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.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.Attach subscriptionsAuto attach subscriptionsBlacklistBulk generate applicability for hostsCombined Profile UpdateConfigsConfiguration StatusConfiguration file containing details about how to connect to the cluster and authentication detailsConfiguration file containing details about how to connect to the cluster and authentication details.Configuration interval in minutesConfiguration nameConfiguration numeric identifierConfiguration script: Config|IntervalConfig|Last ReportConfig|NameConnectionContainer-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.Copy to clipboardCopy version units to libraryCountCreateCreate Alternate Content SourceCreate ConfigCreate Export HistoryCreate Import HistoryCreate Package GroupCreate Syncable Export HistoryCreate a virt-who configurationDeleteDelete Activation KeyDelete Lifecycle EnvironmentDelete Package GroupDelete ProductDelete a virt-who configurationDelete virt-who configuration %s?DeployDestroyDestroy Alternate Content SourceDestroy Content HostDetailsDifferent 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.DisableDiscoverDownload the scriptEditEdit Virt-who ConfigEnableEnable AHV debugEnable debugging outputEnable debugging output?Errata mailEvery 12 hoursEvery 2 daysEvery 2 hoursEvery 24 hoursEvery 3 daysEvery 4 hoursEvery 8 hoursEvery hourExclude HostsExclude host parentsExclude hostsExclude hosts which cluster ID is specified in comma-separated list in this option will NOT be reported. PowerCLI command to find the domain names in VMware Get-Cluster “ClusterName” | Select ID. 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.ExportExport LibraryExport RepositoryFetch pxe filesFilter HostsFilter host parentsFilter hostsFiltered index contentFilteringForeman server FQDNForeman server’s fully-qualified host name, for example: foreman.example.comFully qualified host name or IP address of the hypervisorGeneral informationGenerate host applicabilityGenerate repository applicabilityHTTP ProxyHTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.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.Hammer command: HelpHosts which uuid (or hostname or hwuuid, based on hypervisor_id) is specified in comma-separated list in this option will NOT 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.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.Hypervisor IDHypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklistHypervisor password, required for all hypervisor types except for libvirt/kubevirt.Hypervisor typeHypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.HypervisorsHypervisors updateIf 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.Ignore ProxyIgnore proxyIgnore 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.ImportImport Content View VersionImport Default Content ViewImport Puppet classesImport RepositoryImport factsIncremental UpdateIncremental Update of Content View Version(s) Index contentIndex errataIndex module streamsIndex package groupsInstall Applicable ErrataInstance updateInterval was not providedLatest Configurations Without ChangeLibvirt server’s fully qualified host name or IP address. You can also specify preferred schema, for example: qemu+ssh://libvirt.example.com/system. If you use SSH, make sure you setup root's SSH key on target host for a user specified at hypervisor username fieldList of virt-who configurationsList of virt-who configurations per organizationMicrosoft Hyper-V fully qualified host name or IP address.Name of this configuration, e.g. the name of the hypervisorNew ConfigNew Virt-who ConfigNewer version of virt-who is required, minimum version is %sNo ChangeNo Report YetNo ReportsNo changeNo configuration foundNutanix AHV’s IP address.OKOn the target virt-who host:On this page you can define virt-who configurations for your hypervisors.One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.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 Get-Cluster “ClusterName” | Select ID. 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.Only hosts which uuid (or hostname or hwuuid, based on hypervisor_id) 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.Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabledOption Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled Organization of the virt-who configurationOverviewOwnerOwner was not providedPackage Profile UpdatePath to kubeconfig filePrism CentralPrism ElementPrism FlavorProduct CreatePromotePromotion to EnvironmentPublishPublish Lifecycle Environment RepositoriesRefresh Alternate Content SourceReindex subscriptionsRemove ContentRemove VersionRemove Versions and AssociationsRemove from EnvironmentRemove subscriptionsRenders a deploy script for the specified virt-who configurationReportRepublish Version RepositoriesRun Sync Plan:ScheduleSelect the Prism flavor you are connecting toShow a virt-who configurationSpecifies how the hypervisor will be identified.Specifies that hypervisors will be identified by their hostname, uuid or hwuuid. Note that some virtualization backends don't have all of them implemented. Default is hostname, which provides more meaningful hypervisor names, but can cause duplicated hypervisor registrations if the host is renamed. To avoid that, you can use uuid instead. hwuuid is applicable to esx only. 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.StatusSuccessSync capsuleSyncable exportSynchronizeSynchronize smart proxyThe configuration was not deployed yet or the virt-who was unable to report the statusThe frequency of VM-to-host mapping updates for AHV(in seconds)The virt-who report arrived within the intervalThe virt-who report has not arrived within the interval, which indicates there was no change on hypervisorTo 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.Total ConfigurationsUnable to create sysconfig fileUnable to create virt-who config fileUnable to enable virt-who service using systemctlUnable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repositoryUnable to start virt-who service, please see virt-who logs for more detailsUnknownUnknown configuration statusUnknown configuration status, caused by unexpected conditionsUnlimitedUpdateUpdate Alternate Content SourceUpdate CDN ConfigurationUpdate Content OverridesUpdate a virt-who configurationUpdate content urlsUpdate for hostUpdate http proxyUpdate http proxy detailsUpdate redhat repositoryUpdate release version for hostUpdating System Purpose for hostUpload intoUse 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:VMware vCenter server’s fully qualified host name or IP address.Verify checksumVirt-who Configs StatusVirt-who Configuration %sVirt-who ConfigurationsVirt-who Configurations StatusVirt-who configurationsWhitelistevery %s hoursProject-Id-Version: foreman_virt_who_configure 0.5.11 Report-Msgid-Bugs-To: PO-Revision-Date: 2017-05-03 11:59+0000 Last-Translator: Amit Upadhye , 2022 Language-Team: Chinese (China) (https://www.transifex.com/foreman/teams/114/zh_CN/) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: zh_CN Plural-Forms: nplurals=1; plural=0; 1. 将这个配置脚本复制到安全目录。2. 使脚本可执行，并运行脚本。3. 删除该脚本。忽略代理服务器。忽略代理服务器设置的主机名、域或 ip 地址逗号分隔列表。可选择性地设置为 *，以便为所有主机名、域或 ip 地址跳过代理服务器设置。简化 virt-who 配置的插件AHV 更新间隔摘要抽象 async 任务virt-who 连接到 Nutanix AHV 的帐户名称。virt-who 用于连接 hypervisor 的帐户名，格式为 domain_name\account_name。注意只使用单斜线来分离 domain_name 和 account_name 的值。如果您使用域帐户，以及全局配置文件 /etc/virt-who.conf，则需要使用 双斜线。有关进一步详情，请参见红帽知识库解决方案 如何将 windows 域名帐户用于 在 virt-who 了解更多信息。virt-who 用于连接 hypervisor 的帐户名。virt-who 连接 hypervisor 所用的帐户名。默认为 Administrator。要使用替换帐户，请创建用户帐户并将该帐户分配给以下组（Windows 2012 服务器）：Hyper-V 管理员和远程管理用户。virt-who 连接 hypervisor 所用的帐户名。Virt-who 不支持基于密码的验证，您必须手动设置 SSH 密钥，有关更多信息，请参见 红帽知识库解决方案 如何为 KVM 主机配置 virt-who。virt-who 用于连接 hypervisor 实例的帐户密码。有子计划的操作操作代理操作仅适用于 esx 提供程序类型。在此选项中以逗号分隔的列表指定了父资源（通常是 ComputeResource）名称的主机不会被报告。支持通配符和正则表达式，多个记录必须用逗号分隔。如果该值包含逗号等特殊字符，则将其放在双引号中。所有新行字符将在生成的配置文件中删除，空格从开头和结尾删除。仅适用于 esx 提供程序类型。仅报告在此选项中以逗号分隔的列表指定了父资源（通常是 ComputeResource）名称的主机。支持通配符和正则表达式，多个记录必须用逗号分隔。如果该值包含逗号等特殊字符，则将其放在双引号中。所有新行字符将在生成的配置文件中删除，空格从开头和结尾删除。附加订阅自动附加订阅黑名单批量生成主机的适用性组合的配置集更新配置配置状态配置文件，其中包含有关如何连接到集群的详细信息以及身份验证的详细信息配置文件，其中包含有关如何连接到集群的详细信息以及身份验证的详细信息。以分钟为单位的配置间隔配置名称配置数字识别符配置脚本：配置|间隔配置|最新报告配置|名称连接容器原生虚拟化的标准主机名或 IP 地址。为了连接到集群，需要提供 kubeconfig 的路径，其中包含连接详细信息和身份验证令牌。复制到剪贴板将版本单位复制到库计数创建创建备用内容源创建配置创建导出历史记录创建导入历史记录创建软件包组创建可同步的导出历史记录创建 virt-who 配置刪除删除激活码删除生命周期环境删除软件包组删除产品删除 virt-who 配置删除 virt-who 配置 %s？部署销毁销毁备用内容源销毁内容主机详情不能为每个管理程序设置不同的调试值，因此它将影响将在其上部署此配置的主机上的所有其他已部署的配置。禁用发现下载脚本编辑编辑 Virt-who 配置启用启用 AHV 故障排除启用调试输出启用调试输出？勘误邮件每 12 小时每 2 天每 2 小时每 24 小时每 3 天每 4 小时每 8 小时每小时排除主机排除主机父系统排除主机排除集群 ID 在这个选项中列出（以逗号分隔的列表）的主机，不会报告这些主机。PowerCLI 命令在 VMware Get-Cluster "ClusterName" | Select ID 中找到域名。支持通配符和正则表达式，以逗号分开多个记录。如果包含特殊字符（如逗号），则需要将值包括在括号中。在结果配置文件中，所有新行都将被删除，开头和结尾的空字符也会被删除。导出导出库导出仓库获取 pxe 文件过滤主机过滤主机父系统过滤主机已过滤的索引内容过滤Foreman 服务器 FQDNForeman 服务器的完全限定主机名，例如：foreman.example.comHypervisor 的完全限定主机名或 IP 地址通用信息产生主机适用性生成仓库适用性HTTP 代理应当用于 virt-who 运行所在服务器和 hypervisor 及虚拟化管理器之间通信的 HTTP 代理服务器。应当用于 virt-who 运行所在服务器和 hypervisor 及虚拟管理器之间通信的 HTTP 代理服务器。如果未使用代理服务器，则留空。Hammer 命令：帮助不报告在此选项中以逗号分隔的列表指定了uuid（或主机名或 hwuuid，基于 hypervisor_id）的主机。支持通配符和正则表达式，多个记录必须用逗号分隔。如果该值包含逗号等特殊字符，则将其放在双引号中。所有新行字符将在生成的配置文件中删除，空格从开头和结尾删除。检查连接的虚拟机管理程序是否有更改的频率？同时还影响报告映射的频率。对于大多数环境，建议值为每两个小时一次。不能为每个虚拟机管理程序设置不同的间隔，因此它将影响将在其上部署此配置的主机上的所有其他已部署的配置。Hypervisor IDHypervisor 黑名单，仅在过滤模式设置为 2 时适用。支持通配符和正则表达式，必须用逗号分隔多项记录。Hypervisor 过滤模式 %{unlimited} 表示没有过滤，%{whitelist} 表示白名单，%{blacklist} 代表黑名单Hypervisor 密码，除 libvirt/kubevirt 以外的所有 hypervisor 类型都需要Hypervisor 类型Hypervisor 白名单，仅在过滤模式设置为 1 时适用。支持通配符和正则表达式，必须用逗号分隔多项记录。HypervisorHypervisor 更新如果您运行混合环境，且虚拟机运行 Red Hat Enterprise Linux 和其他操作系统，您可能想要限制 virt-who 对主机的访问权限范围。例如，如果某些 hypervisor 只托管 Microsoft Windows Server 实例，那么让 virt-who agent 报告这些 hypervisor 没有任何意义。忽略代理忽略代理服务器忽略代理服务器。忽略代理服务器设置的主机名、域或 ip 地址逗号分隔列表。可选择性地设置为 *，以便为所有主机名、域或 ip 地址跳过代理服务器设置。导入导入内容视图版本导入默认内容视图导入 Puppet 类导入仓库导入事实增量更新内容视图版本的增量更新索引內容索引勘误索引模块流索引软件包组安装适用的勘误实例更新未提供间隔无更改的最新配置Libvirt 服务器的完全限定主机名或 IP 地址。您也可以指定首选的方案，例如：qemu+ssh://libvirt.example.com/system。如果您使用 SSH，确保您在目标主机上为 hypervisor 用户名字段指定的用户设置根的 SSH 密钥virt-who 配置列表每个机构的 virt-who 配置列表Microsoft Hyper-V fully 的完全限定主机名或 IP 地址。此配置的名称，例如 hypervisor 的名称新建配置新建 Virt-who 配置需要更高的 virt-who 版本，最低版本为 %s無變更尚没有报告没有报告不更改找不到配置Nutanix AHV 的 IP 地址。好在目标 virt-who 主机上：在本页面，您可以为您的 hypervisor 定义 virt-who 配置。一个 virt-who 配置代表 /etc/virt-who.d 目录中的一个配置文件，映射至单个 hypervisor、机构和生命周期环境。只有集群 ID 在这个选项中列出（以逗号分隔的列表）的主机才会报告。PowerCLI 命令在 VMware Get-Cluster "ClusterName" | Select ID 中找到域名。支持通配符和正则表达式，以逗号分开多个记录。如果包含特殊字符（如逗号），则需要将值包括在括号中。在结果配置文件中，所有新行都将被删除，开头和结尾的空字符也会被删除。仅报告在此选项中以逗号分隔的列表指定了uuid（或主机名或 hwuuid，基于 hypervisor_id）的主机。支持通配符和正则表达式，多个记录必须用逗号分隔。如果该值包含逗号等特殊字符，则将其放在双引号中。所有新行字符将在生成的配置文件中删除，空格从开头和结尾删除。启用 AHV 内部故障排除需要 Option Enable debugging output。它会在两个选项都启用时提供额外的 AHV 调试信息启用 AHV 内部故障排除需要 Option Enable debugging output。它会在两个选项都启用时提供额外的 AHV 调试信息 virt-who 配置机构概况所有者未提供所有者软件包配置集更新到 kubeconfig 文件的路径Prism CentralPrism ElementPrism Flavor产品创建升级升级到环境发布发布生命周期环境仓库刷新备用内容源重新索引订阅删除内容移除版本删除版本和关联从环境中移除删除订阅为指定的 virt-who 配置提供部署脚本报告发布版本库运行同步计划：调度选择您要连接到的 Prism 类别显示 virt-who 配置指定如何识别 hypervisor。指定 hypervisor 由其 hostname、uuid 或 hwuuid 标识。 注意某些虚拟化后端并未完全实施。 默认为 hostname，它提供更具意义的 hypervisor 名称，但如果主机重命名，则可能造成重复的 hypervisor 注册。为了避免这种情况，可使用 uuid 代替。hwuuid 仅适用于 esx。 此特性应在首次运行 virt-who 之前设置。之后更改将导致订阅管理器中出现重复条目。状态成功同步 capsule可同步导出同步同步智能代理服务器尚未部署配置，或者 virt-who 无法报告状态AHV 的虚拟机到主机映射更新的频率（以秒为单位）在间隔期间收到 virt-who 报告未在间隔期间收到 virt-who 报告，表示 hypervisor 无更改如要定义新配置，请点击 New Config 按钮，填写表格。当您提供所有所需信息之后，会生成 virt-who 配置脚本。您可以通过复制脚本进行手动安装，也可以通过 Remote Execution 在选定的目标主机上部署。全部配置无法创建 sysconfig 文件无法创建 virt-who 配置文件无法使用 systemctl 启用 virt-who 服务无法安装 virt-who 软件包，确保已正确订阅主机，且具备访问 katello-host-tools 的访问权限无法开始 virt-who 服务，请查看 virt-who 日志了解详情未知未知配置状态未知配置状态，由意外情况造成无限制更新更新备用内容源更新 CDN 配置更新内容覆盖更新 virt-who 配置更新内容 url对主机的更新更新 HTTP 代理更新 http 代理详情更新 redhat 仓库为主机更新发行版本主机更新系统目的上传到使用 hammer 命令或下面的脚本来部署此配置。两者都需要 root 特权。在有权访问 Red Hat Satellite Tools 仓库的一个目标主机上运行其中一个，并运行 virt-who 报告，最好在 Foreman 主机上运行：VMware vCenter 服务器的完全限定主机名或 IP 地址。验证校验和Virt-who 配置状态Virt-who 配置 %sVirt-who 配置Virt-who 配置状态Virt-who 配置白名单每 %s 小时