With the support of both RHEL 6 and RHEL 7, we should add either a configuration option for which base hostgroup to be created or preferably, configure multiple base hostgroups for both RHEL 6 and RHEL 7 (and possibly CentOS and Fedora). +++ This bug was initially created as a clone of Bug #1102391 +++ Description of problem: For RHELOSP 5, we should start by configuring staypuft to use RHEL 7 in the Base Hostgroup. This includes a RHEL 7 kickstart and RHEL 7 options. Actual results: Currently a RHEL 6 OS is configured in Foreman Expected results: We should do RHEL 7 Additional info:
In the 'multiple base hostgroups' case, we'll also need to modify the staypuft wizard to add an OS selection component on the first screen -- the result of this selection will be to choose the parent hostgroup for the deployment (which will set the OS-specific bits for the deployment).
I think better than current attitude (to create two hostgroups) we should still have only one but user should specify desired operating system. Otherwise we'll have to have hostgroup for every OS and version combination.
That could work too -- if I understand correctly, the modification would be that installer would, instead of setting up hostgroups with everything needed for provisioning, everything non-OS-specific would be set on the base hostgroup, and the deployment hostgroup would set the OS. I guess my question is how many hostgroup params are OS-specific? Are we just adding an OS choice that gets set at deploy time on the deployment hostgroup, or are there a number of params that must be set? I think in addition to OS we'll also need to set the Installation medium, and possibly the kickstart/templates. If we're needing to set 2 or more parameters, the multi-hostgroup approach may be best. If we really only need to set the OS (and not template/kickstart, install medium, etc), then the single hostgroup, override OS on deployment approach would be better.
So operating system also defines partition table, installation media and provisioning templates but for a given os family it's usually the same. Installation media URL can be dynamic using $arch and version so can be reused for multiple systems. I think it depends whether we'll want to support deployment only on same OS or we want heterogeneous deployments. Also if you later decide to add something to the base hostgroup, e.g. some puppet module, you'll have to do it for all hostgroups. Since we'd have hostgroup for all RHEL version (6.5,7.0,7.1...) it can become a pain quite easily.
Anyway we create 2 hostgroups, one for each RHEL. RHEL7 is set by default but user can change base hostgroup using Setting. If you think we should rather set operating system, please open a new BZ. Setting this to POST, it's in upstream since 0.0.18
Hmm, I'm not sure if this is the best approach, or if we need a setting that provides an array of valid base hostgroups (with some sort of identifier "RHEL 6" vs. "RHEL 7" etc.). My thinking was that the 'create deployment' page would have a radio button selection for choosing either RHEL6 or RHEL7 -- the question is how this maps to the back end.
I think I agree with Scott. A radio button on the create deployment screen that lets you choose a valid OS. If that maps in the backend to different hostgroups, I think that's fine, but the selection should happen at the create deployment page, IMO.
We currently only suport RHEL 7. You can see both RHEL 7 and RHEL 6 under hostgroups, but when creating a new deployment the only option is to choose RHEL 7 as a platform.
Fixed as a part of https://github.com/theforeman/foreman-installer-staypuft/pull/66
RHEL 6 is not supported any more and was removed from the host groups.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html