Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 3. Configuration Options
The simplest configuration requiring virt-who consists of one hypervisor or virtualization manager, one organization and one hypervisor technology, with the virt-who instance reporting directly to the Satellite Server. Since most organizations are more complex than this, the installation and configuration of virt-who can be adapted to accommodate the following variables:
- Multiple organizations in Satellite
- Multiple hypervisors
- Multiple hypervisor technologies
- HTTP proxy
3.1. Multiple Organizations
A single virt-who instance can report to the Satellite Server virtual machines which are associated with multiple organizations. Individual configuration files are recommended for each organization.
3.2. Multiple Hypervisors
A single virt-who instance can connect to multiple hypervisors and report the virtual machines hosted by each. Individual configuration files are recommended for each hypervisor or virtualization manager as it makes troubleshooting easier. For example, if you suspect a hypervisor is causing a problem, you can move that hypervisor’s configuration file to another directory, stopping virt-who from querying it and so eliminating it from the problem’s scope.
If you have multiple hypervisors, virt-who queries each in parallel. This reduces the chance of virt-who’s queries being stopped or delayed because of an unresponsive hypervisor.
3.3. Multiple Hypervisor Technologies
A single virt-who instance can connect to virtualization platforms of multiple supported technologies. Individual configuration files are recommended for each platform.
3.4. HTTP Proxy
If you use HTTP proxy servers in your environment, additional configuration is required to use virt-who with HTTP proxy:
If there is an HTTP proxy between Satellite and the Content Delivery Network (CDN), by default, the virt-who traffic will attempt to go through the proxy server as well. This often fails if the HTTP proxy is configured to allow only external traffic and not internal traffic (virt-who traffic). It is also likely to fail if Satellite Server is on the same local network as the hypervisors.
To workaround these issues, you can configure virt-who to use no proxy, configure the HTTP proxy to allow local network traffic through, or configure an additional squid proxy. For further details, see Section 6.5.3, “Virt-who attempts to connect to virtualization manager or hypervisor via an HTTP proxy on the local network fails”.
- If you require virt-who to use a different proxy than what Satellite Server uses to connect to external networks, see Section 6.5.4, “Configure virt-who to use an internal proxy” for further details.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}