AFAIK most tabs of Host Groups are only used during host provisioning. Only a few tabs are later on used to configure already running hosts. In my point of view, only the tabs Puppet Classes, Ansible Roles, Salt States and Parameters are used after provisioning a host and take affect without rebuilding a host. In case a setting like “Network->Domain”, “Host Group -> Content View” or “Operating System -> Architecture” is changed, this change doesn’t affect already deployed host. Only if you rebuild them. Please, correct me if I’m wrong.
Therefore, wouldn’t it make sense to:
- Move Parameters, Puppet Classes, Ansible Roles and Salt States to something like “Config Sets”. The behaviour of Config Sets would be similar to the current Host Groups - including to have sub config sets etc.
- Rename Host Groups to “Host Templates” in which it is possible to select the Config Set which should be used if a host in this Host Template is provisioned
Afterwards, it would be crystal clear for evey user, that all settings of Host Templates are only used during provisioning and Config Sets take affect for already deployed hosts, too.
What’s your opinion?