Þ•’¬Å< P 6Q )ˆ ² ÍÈ ,– <à ?X5uL«øÔÎÕ ¤®¶dËe0!–¸ Ëì & 2Ø=( .<\!|ž¥§­Uinƒ”¬Å Ô áï þ   ' 2@ Uc jw ‹ ˜¢N¶9? S‘^·ð¨¹É¾Hˆ! Ñ"¤ß"v„#Sû#O$¤_$T% Y& f&Îs&B'K'$e'Š'0ª':Û'(;( W(b(<v( ³( ½( Ë( Ö(à(÷())I3)™})ø*Ã,ŽÔ-c.*ó./'/-/D/ \/ j/ x/@…/Æ/-Ï/ý/00¹L03 3V3/l3jœ3*425G5%g515}¿5K=6‰6‘6=®6 ì6ö6ø7B8R8j8„8œ8»8 Ó8Ý8‰ì8Wv:NÎ:';>E;0„<Rµ<®=]·?’@“¨A{±_ ð_ý_U` j`$w`œ` »`È`"ç` a& aX4aÔa‘bbPôdÍEgÏhãhüh i' i#5i Yi giui]‹iéi(üi$%j<Jj¶‡j>nEnsLn.ÀnŠïnªzo%q.5q3dqJ˜qÖãqfºr!s(sHGs sšsj³sOunuu u°uÏußuõu!HƒŒ ’}w9uP5„cQ_‹^ #1Xy>3~Y@z ˆ‰WŠG]*NiIv"F.Ltlrog4f€ n†0)-BZO,p‡qd<E/&?ARx$V7:2ST'JU(86Ž`{=C aM\;[jD% bem‘+…|‚khsK1. 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 easyAccount 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.ActionsApplicable 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.BlacklistConfigsConfiguration 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 clipboardCountCreate ConfigCreate a virt-who configurationDelete a virt-who configurationDelete virt-who configuration %s?DeployDetailsDifferent 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.Download the scriptEditEdit Virt-who ConfigEnable AHV debugEnable debugging outputEnable debugging output?Every 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.Filter HostsFilter host parentsFilter hostsFilteringForeman server FQDNForeman server’s fully-qualified host name, for example: foreman.example.comFully qualified host name or IP address of the hypervisorGeneral informationHTTP 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.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.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.IntervalInterval was not providedLatest Configurations Without ChangeList of virt-who configurationsList of virt-who configurations per organizationMicrosoft Hyper-V fully qualified host name or IP address.NameName 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 providedPath to kubeconfig filePrism CentralPrism ElementPrism FlavorRenders a deploy script for the specified virt-who configurationScheduleSelect 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.StatusSuccessThe configuration was not deployed yet or the virt-who was unable to report the statusThe 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 conditionsUnlimitedUpdate a virt-who configurationUse 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.Virt-who Configs StatusVirt-who Configuration %sVirt-who ConfigurationsVirt-who Configurations StatusVirt-who configurationsWhitelistevery %s hoursProject-Id-Version: foreman_virt_who_configure 0.5.17 Report-Msgid-Bugs-To: PO-Revision-Date: 2017-05-03 11:59+0000 Last-Translator: Bryan Kearney , 2023 Language-Team: Japanese (https://app.transifex.com/foreman/teams/114/ja/) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: ja Plural-Forms: nplurals=1; plural=0; 1. ã“ã®è¨­å®šã‚¹ã‚¯ãƒªãƒ—トを安全ãªãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚³ãƒ”ーã—ã¾ã™ã€‚2. スクリプトを実行å¯èƒ½ãªçŠ¶æ…‹ã«ã—ã€ã“れを実行ã—ã¾ã™ã€‚3. スクリプトを削除ã—ã¾ã™ã€‚プロキシー設定を無視ã™ã‚‹ãƒ›ã‚¹ãƒˆåã€ãƒ‰ãƒ¡ã‚¤ãƒ³ã¾ãŸã¯ IP アドレスã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã€‚オプションã¨ã—ã¦ã€ã“れを * ã«è¨­å®šã—ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆåドメインã¾ãŸã¯ IP アドレスã®ãƒ—ロキシー設定をãƒã‚¤ãƒ‘スã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚virt-who 設定を容易ã«ã™ã‚‹ãƒ—ラグインvirt-who ã‚’ Nutanix AHV ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå。virt-who ã‚’ domain_name\account_name å½¢å¼ã§ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã™ã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå。å˜ä¸€ã®ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã®ã¿ãŒ domain_name ãŠã‚ˆã³ account_name ã®å€¤ã‚’区別ã™ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。ドメインアカウントãŠã‚ˆã³ã‚°ãƒ­ãƒ¼ãƒãƒ«è¨­å®šãƒ•ã‚¡ã‚¤ãƒ« /etc/virt-who.conf を使用ã—ã¦ã„ã‚‹å ´åˆã€2 㤠ã®ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚詳細ã¯ã€Red Hat ナレッジベースã®ã‚½ãƒªãƒ¥ãƒ¼ã‚·ãƒ§ãƒ³è¨˜äº‹ã€ŒHow to use a windows domain account with virt-whoã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。virt-who ã‚’ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå。virt-who ã‚’ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå。デフォルトã§ã€ã“れ㯠Administrator ã«ãªã‚Šã¾ã™ã€‚代替アカウントを使用ã™ã‚‹ã«ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚’作æˆã—ã€ãã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚’次ã®ã‚°ãƒ«ãƒ¼ãƒ—ã«å‰²ã‚Šå½“ã¦ã¾ã™ (Windows 2012 Server): Hyper-V 管ç†è€…ãŠã‚ˆã³ãƒªãƒ¢ãƒ¼ãƒˆç®¡ç†ãƒ¦ãƒ¼ã‚¶ãƒ¼ã€‚virt-who ã‚’ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå。Virt-who ã¯ãƒ‘スワードベースã®èªè¨¼ã‚’サãƒãƒ¼ãƒˆã—ãªã„ãŸã‚ã€SSH éµã‚’手動ã§è¨­å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚詳細ã¯ã€ã€ŒRed Hat Knowledgebase solution How to configure virt-who for a KVM hostã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。virt-who ã‚’ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«æŽ¥ç¶šã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¢ã‚«ã‚¦ãƒ³ãƒˆãƒ‘スワード。アクションesx プロãƒã‚¤ãƒ€ãƒ¼ã‚¿ã‚¤ãƒ—ã«ã®ã¿é©ç”¨ã§ãã¾ã™ã€‚親 (通常㯠ComputeResource) ã®åå‰ãŒã“ã®ã‚ªãƒ—ションã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã«æŒ‡å®šã•ã‚Œã¦ã„るホストã®å ´åˆã¯ レãƒãƒ¼ãƒˆã•ã‚Œã¾ã›ã‚“。ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚esx プロãƒã‚¤ãƒ€ãƒ¼ã‚¿ã‚¤ãƒ—ã«ã®ã¿é©ç”¨ã§ãã¾ã™ã€‚親 (通常㯠ComputeResource) ã®åå‰ãŒã“ã®ã‚ªãƒ—ションã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã«æŒ‡å®šã•ã‚Œã¦ã„るホストã®å ´åˆã«ã®ã¿ãƒ¬ãƒãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ブラックリスト設定設定ステータスクラスターã¸ã®æŽ¥ç¶šæ–¹æ³•ã¨èªè¨¼ã®è©³ç´°ã‚’å«ã‚€è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚¯ãƒ©ã‚¹ã‚¿ãƒ¼ã¸ã®æŽ¥ç¶šæ–¹æ³•ã¨èªè¨¼ã®è©³ç´°ã‚’å«ã‚€è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«è¨­å®šã®é–“éš” (分å˜ä½)設定å設定数値 ID設定スクリプト: 間隔最後ã®ãƒ¬ãƒãƒ¼ãƒˆåå‰æŽ¥ç¶šã‚³ãƒ³ãƒ†ãƒŠãƒ¼ãƒã‚¤ãƒ†ã‚£ãƒ–ã®ä»®æƒ³åŒ–ã®å®Œå…¨ä¿®é£¾ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ 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)。ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ホストã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ãƒ›ã‚¹ãƒˆã®è¦ªã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ãƒ›ã‚¹ãƒˆã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°Foreman サーãƒãƒ¼ã® FQDNForeman サーãƒãƒ¼ã®å®Œå…¨ä¿®é£¾ãƒ›ã‚¹ãƒˆå (例: foreman.example.com)ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®å®Œå…¨ä¿®é£¾ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ IP アドレス一般情報HTTP プロキシーvirt-who ãŒå®Ÿè¡Œã•ã‚Œã¦ã„るサーãƒãƒ¼ã¨ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ãŠã‚ˆã³ä»®æƒ³åŒ–マãƒãƒ¼ã‚¸ãƒ£ãƒ¼é–“ã®é€šä¿¡ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ã®ã‚ã‚‹ HTTP プロキシー。virt-who ãŒå®Ÿè¡Œã•ã‚Œã¦ã„るサーãƒãƒ¼ã¨ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ãŠã‚ˆã³ä»®æƒ³åŒ–マãƒãƒ¼ã‚¸ãƒ£ãƒ¼é–“ã®é€šä¿¡ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ã®ã‚ã‚‹ HTTP プロキシー。プロキシーãŒä½¿ç”¨ã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã“れを空白ã«ã—ã¾ã™ã€‚Hammer コマンド: ヘルプuuid (ã¾ãŸã¯ hypervisor_id ã«å¿œã˜ã¦ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ hwuuid) ãŒã“ã®ã‚ªãƒ—ションã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã«æŒ‡å®šã•ã‚Œã¦ã„るホスト㯠レãƒãƒ¼ãƒˆã•ã‚Œã¾ã›ã‚“。ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚接続済ã¿ã®ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«å¤‰æ›´ãŒãªã„ã‹ã€ã©ã®ã‚ˆã†ãªé »åº¦ã§ç¢ºèªã—ã¾ã™ã‹?ã¾ãŸã€ãƒžãƒƒãƒ”ングã®å ±å‘Šé »åº¦ã«ã‚‚影響ã—ã¾ã™ã€‚大åŠã®ç’°å¢ƒã§ã®æŽ¨å¥¨å€¤ã¯ã€2時間ã”ã¨ã§ã™ã€‚ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã”ã¨ã«ç•°ãªã‚‹é–“隔を設定ã§ãã‚‹ã®ã§ã€ã“ã®è¨­å®šã‚’デプロイã™ã‚‹ãƒ›ã‚¹ãƒˆã«è¨­å®šæ¸ˆã¿ã®ä»–ã®å…¨è¨­å®šã«å½±éŸ¿ãŒã‚ã‚Šã¾ã™ã€‚ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ IDフィルタリングモード㌠2 ã«è¨­å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã«ã®ã¿é©ç”¨ã§ãã‚‹ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ãƒ–ラックリストã§ã™ã€‚ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ãŠã‚Šã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ãƒ¢ãƒ¼ãƒ‰ã€‚%%{unlimited} ã¯ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ãŒãªã„ã“ã¨ã‚’æ„味ã—ã€%%{whitelist} ã¯ãƒ›ãƒ¯ã‚¤ãƒˆãƒªã‚¹ãƒˆã€%%{blacklist} ã¯ãƒ–ラックリストをæ„味ã—ã¾ã™ã€‚libvirt/kubevirt を除ãã™ã¹ã¦ã®ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ã‚¿ã‚¤ãƒ—ã«å¿…è¦ãªãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ãƒ‘スワードãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ã‚¿ã‚¤ãƒ—フィルタリングモード㌠1 ã«è¨­å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã«ã®ã¿é©ç”¨ã§ãã‚‹ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ãƒ›ãƒ¯ã‚¤ãƒˆãƒªã‚¹ãƒˆã§ã™ã€‚ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ãŠã‚Šã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚Red Hat Enterprise Linux ãŠã‚ˆã³ãã®ä»–ã®ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ ã‚’実行ã™ã‚‹ä»®æƒ³ãƒžã‚·ãƒ³ã§ãƒã‚¤ãƒ–リッド環境を実行ã™ã‚‹å ´åˆã¯ã€virt-who ã®ãƒ›ã‚¹ãƒˆã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã®ç¯„囲を制é™ã™ã‚‹ã“ã¨ã‚’ãŠå‹§ã‚ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€ä¸€éƒ¨ã®ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ãŒ Microsoft Windows Server インスタンスã®ã¿ã‚’ホストã™ã‚‹å ´åˆã€ã“れらã®ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã‚’ virt-who エージェントãŒå ±å‘Šã™ã‚‹åˆ©ç‚¹ã¯ã‚ã‚Šã¾ã›ã‚“。プロキシーを無視ã™ã‚‹ãƒ—ロキシーを無視プロキシーを無視ã—ã¾ã™ã€‚プロキシー設定を無視ã™ã‚‹ãƒ›ã‚¹ãƒˆåã€ãƒ‰ãƒ¡ã‚¤ãƒ³ã¾ãŸã¯ IP アドレスã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã§ã™ã€‚オプションã¨ã—ã¦ã€ã“れ㯠* ã«è¨­å®šã§ãã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆåドメインã¾ãŸã¯ IP アドレスã®ãƒ—ロキシー設定をãƒã‚¤ãƒ‘スã—ã¾ã™ã€‚間隔間隔ã¯æŒ‡å®šã•ã‚Œã¦ã„ã¾ã›ã‚“変更ã®ãªã„最新ã®è¨­å®švirt-who 設定一覧を表示ã—ã¾ã™ã€‚組織別㮠virt-who 設定ã®ä¸€è¦§Microsoft Hyper-V ã®å®Œå…¨ä¿®é£¾ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ IP アドレス。åå‰ã“ã®è¨­å®šã®åå‰ã€‚例: ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®åå‰æ–°è¦è¨­å®šæ–°è¦ Virt-who 設定virt-who ã®æ–°è¦ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒå¿…è¦ã§ã™ã€‚最å°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ %s ã§ã™å¤‰æ›´ãªã—レãƒãƒ¼ãƒˆã¯ã¾ã ã‚ã‚Šã¾ã›ã‚“レãƒãƒ¼ãƒˆãŒã‚ã‚Šã¾ã›ã‚“変更ãªã—設定ãŒè¦‹ã¤ã‹ã‚Šã¾ã›ã‚“Nutanix AHV ã® IP アドレス。OKターゲット virt-who ホスト上:ã“ã®ãƒšãƒ¼ã‚¸ã§ã€ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã® virt-who 設定を定義ã§ãã¾ã™ã€‚1 ã¤ã® virt-who 設定㯠/etc/virt-who.d ディレクトリー㮠1 ã¤ã®è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’表ã—ã€å˜ä¸€ã®ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã€çµ„ç¹”ãŠã‚ˆã³ãƒ©ã‚¤ãƒ•ã‚µã‚¤ã‚¯ãƒ«ç’°å¢ƒã«ãƒžãƒƒãƒ—ã•ã‚Œã¾ã™ã€‚クラスター ID ãŒã“ã®ã‚ªãƒ—ションã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã«æŒ‡å®šã•ã‚Œã¦ã„るホストã ã‘ãŒãƒ¬ãƒãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚PowerCLI コマンドを使用ã—㦠VMware ã§ãƒ‰ãƒ¡ã‚¤ãƒ³åを検索ã—ã¾ã™ (Get-Cluster “ClusterName†| Select ID)。ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚uuid (ã¾ãŸã¯ hypervisor_id ã«å¿œã˜ã¦ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ hwuuid) ãŒã“ã®ã‚ªãƒ—ションã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã«æŒ‡å®šã•ã‚Œã¦ã„るホストã®å ´åˆã«ã®ã¿ãƒ¬ãƒãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚ワイルドカードãŠã‚ˆã³æ­£è¦è¡¨ç¾ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã€è¤‡æ•°ã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚Œã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンマãªã©ã®ç‰¹æ®Šæ–‡å­—ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯å€¤ã‚’二é‡å¼•ç”¨ç¬¦ã§å›²ã¿ã¾ã™ã€‚ã™ã¹ã¦ã®æ”¹è¡Œæ–‡å­—ã¯ç”Ÿæˆã•ã‚Œã‚‹è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã§å‰Šé™¤ã•ã‚Œã€ç©ºç™½ã¯å…ˆé ­ãŠã‚ˆã³æœ«å°¾ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚AHV 内部デãƒãƒƒã‚°ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ã‚ªãƒ—ション Enable debugging output ãŒå¿…è¦ã§ã™ã€‚両方ã®ã‚ªãƒ—ションãŒæœ‰åŠ¹ãªå ´åˆã«è¿½åŠ ã® AHV デãƒãƒƒã‚°æƒ…報をæä¾›ã—ã¾ã™ã€‚AHV 内部デãƒãƒƒã‚°ã‚’有効ã«ã™ã‚‹ã«ã¯ã€Enable debugging output ã®ã‚ªãƒ—ションã¯å¿…é ˆã§ã™ã€‚両方ã®ã‚ªãƒ—ションãŒæœ‰åŠ¹ãªå ´åˆã«è¿½åŠ ã® AHV デãƒãƒƒã‚°æƒ…報をæä¾›ã—ã¾ã™ã€‚virt-who 設定ã®çµ„織概è¦æ‰€æœ‰è€…所有者ã¯æŒ‡å®šã•ã‚Œã¦ã„ã¾ã›ã‚“kubeconfig ファイルã¸ã®ãƒ‘スPrism CentralPrism ElementPrism フレーãƒãƒ¼æŒ‡å®šã—㟠virt-who 設定㮠deploy スクリプトã®ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ã‚’è¡Œã„ã¾ã™ã€‚スケジュール接続先㮠Prism フレーãƒãƒ¼é¸æŠžvirt-who 設定を表示ã—ã¾ã™ã€‚ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã®ç‰¹å®šæ–¹æ³•ã‚’指定ã—ã¾ã™ã€‚ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ãŒ hostnameã€uuid ã¾ãŸã¯ hwuuid ã§ç‰¹å®šã•ã‚Œã‚‹ã‚ˆã†ã«æŒ‡å®šã—ã¾ã™ã€‚ 一部ã®ä»®æƒ³åŒ–ãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰ã§ã¯ãれらã®ã™ã¹ã¦ãŒå®Ÿè£…ã•ã‚Œã¦ã„ã¾ã›ã‚“。 デフォルト㯠hostname ã§ã‚ã‚Šã€æ„味を付ã—ãŸãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼å ã‚’æä¾›ã—ã¾ã™ãŒã€ãƒ›ã‚¹ãƒˆåãŒå¤‰æ›´ã•ã‚Œã‚‹å ´åˆã¯ã€ãƒã‚¤ãƒ‘ーãƒãƒ¼ã‚¶ãƒ¼ç™»éŒ²ã®é‡è¤‡ãŒç”Ÿã˜ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã“れをé¿ã‘ã‚‹ã«ã¯ã€ä»£ã‚ã‚Šã« uuid を使用ã§ãã¾ã™ã€‚hwuuid 㯠esx ã®ã¿ã«é©ç”¨ã•ã‚Œã¾ã™ã€‚ ã“ã®ãƒ—ロパティーã¯ã€virt-who ã®åˆå›žã®å®Ÿè¡Œå‰ã«è¨­å®šã•ã‚Œã‚‹ã“ã¨ã«ãªã£ã¦ã„ã¾ã™ã€‚ã“れを後ã§å¤‰æ›´ã™ã‚‹ã¨ã€ã‚µãƒ–スクリプションマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã§ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã®é‡è¤‡ãŒç”Ÿã˜ã¾ã™ã€‚状態æˆåŠŸè¨­å®šãŒãƒ‡ãƒ—ロイã•ã‚Œã¦ã„ãªã„ã‹ã€ã¾ãŸã¯ virt-who ãŒã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’報告ã§ãã¾ã›ã‚“ã§ã—ãŸæœŸé–“内ã«ç€ä¿¡ã—㟠virt-who レãƒãƒ¼ãƒˆvirt-who レãƒãƒ¼ãƒˆã¯æœŸé–“内ã«ç€ä¿¡ã—ã¦ãŠã‚‰ãšã€ã“ã‚Œã¯ãƒã‚¤ãƒ‘ーãƒã‚¤ã‚¶ãƒ¼ã«å¤‰æ›´ãŒãªã„ã“ã¨ã‚’示ã—ã¦ã„ã¾ã™æ–°è¦è¨­å®šã‚’定義ã™ã‚‹ã«ã¯ã€æ–°è¦è¨­å®šãƒœã‚¿ãƒ³ã‚’クリックã—ã¦ãƒ•ã‚©ãƒ¼ãƒ ã«è¨˜å…¥ã—ã¾ã™ã€‚ã™ã¹ã¦ã®å¿…須情報を入力ã—ãŸå¾Œã«ã€virt-who 設定スクリプトãŒç”Ÿæˆã•ã‚Œã¾ã™ã€‚スクリプトをコピーã—ã¦ã“れを手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã‹ã€ã¾ãŸã¯ã“れをリモート実行ã«ã‚ˆã‚Šã€é¸æŠžã—ãŸã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒ›ã‚¹ãƒˆä¸Šã§ãƒ‡ãƒ—ロイã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚åˆè¨ˆã®è¨­å®šsysconfig ファイルを作æˆã§ãã¾ã›ã‚“virt-who 設定ファイルを作æˆã§ãã¾ã›ã‚“systemctl を使用ã—㦠virt-who サービスを有効ã«ã§ãã¾ã›ã‚“virt-who パッケージをインストールã§ãã¾ã›ã‚“。ホストãŒé©åˆ‡ã«ã‚µãƒ–スクライブã•ã‚Œã¦ãŠã‚Šã€katello-host-tools リãƒã‚¸ãƒˆãƒªãƒ¼ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ãŒã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚virt-who サービスを起動ã§ãã¾ã›ã‚“。詳細ã¯ã€virt-who ログをå‚ç…§ã—ã¦ãã ã•ã„ä¸æ˜Žä¸æ˜Žãªè¨­å®šã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹äºˆæœŸã—ãªã„状æ³ã«ã‚ˆã£ã¦ç”Ÿã˜ã‚‹ä¸æ˜Žãªè¨­å®šã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ç„¡åˆ¶é™virt-who 設定ã®æ›´æ–°ä»¥ä¸‹ã® Hammer コマンドã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トを使用ã—ã¦ã“ã®è¨­å®šã‚’デプロイã—ã¾ã™ã€‚ã„ãšã‚Œã‚‚ã€root 権é™ãŒå¿…è¦ã§ã™ã€‚katello-host-tools ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãるターゲットホスト㧠Hammer コマンドã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トを実行ã—ã€å¯èƒ½ãªå ´åˆã¯ Foreman ホスト㧠virt-who レãƒãƒ¼ãƒˆã‚’実行ã—ã¾ã™ã€‚VMware vCenter サーãƒãƒ¼ã®å®Œå…¨ä¿®é£¾ãƒ›ã‚¹ãƒˆåã¾ãŸã¯ IP アドレスVirt-who 設定ステータスVirt-who 設定 %sVirt-who 設定Virt-who 設定ステータスVirt-who 設定ホワイトリスト%s 時間ã”ã¨