Plugins » virt-who configure

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1525930

Description of problem:
When virt-who configuration is modified, manual action to alter the config files is needed.
Also when entry from satellite webui is deleted, virt-who config file from /etc/virt-who.d/ is not deleted and configuration not altered, so the config file needs to be deleted manually.

Version-Release number of selected component (if applicable):
6.3.0

How reproducible:
100%

Steps to Reproduce:
1.create virt-who config and apply it
2.delete the profile fom satellite
3.check filesystem in /etc/virt-who.d/

Actual results:
config file of deleted profile is still present

Expected results:
config file deleted or modified to configname.config.backup to prevent accidental total deletions, with everything commented out

Additional info:
This should be possible to achieve by adding a drop-down menu or check-boxes which will allow to choose where the config will be deployed.
If on satellite than hammer can be called, if on content host, than it would be possible to use either puppet or job to create the required configs, or if just config script is needed.

Marek:

It would definitely use the same deploy mechanism for both Satellite host or other host. Note that Satellite can't simply run hammer, we need root permissions but Satellite web process runs under non-root user. I guess we'd use REX for all such operations. There's a parameter in installer that one could use to have Satellite ready for managing using REX. It configures internal capsule SSH key so user run jobs against Satellite host right after installation. It's disabled by default as we don't want to open this channel without user knowing.