Actions
Feature #14859
open
Enable virt-who content host to register hypervisors under different env/CV than its own
Description
Currently in Katello 2.4.1 (and perhaps newer, I have not had the opportunity to check), all hypervisors registered by a content host running virt-who are assigned the same environment and content view as the host that is registering them.
As virt-who now support user credentials, it would be beneficial to allow a content host to remain in its current environment/CV (and thus be patched, etc, along with other systems) while hypervisors can be placed in a 'Dummy' environment if so desired. This is especially useful when the ESX infrastructure is maintained by a different team than the Linux systems that Katello is maintaining and the only interaction with the hosts whatsoever is the hypervisor/guest UUID mapping.
Updated by Eric Helms almost 8 years ago
- translation missing: en.field_release set to 114
Actions