Description of problem: IfI am currently deploying RHEL OSP using the foreman automation utility, I first must manually configure any NICs and BONDs including associating them with any VLANs before apply a RHEL OSP host group. I believe (also heard from Dell Partner) that it may be expected that this configuration should be handled by the automation tool Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
If we want bonded NIC's, it feels a configuration that should take place in provisioning mode, in a provisioning template. Does that align with expectations?
Wouldn't the proposal limit the use of bonds to only when the Operating Systems is provisioned? That would mean a user who wants to install a HA RHOS environment, must use Foreman bare metal provioning, and would require them to re-install the system. Say someone has a different baremetal provisioning system (cobbler) we would say our autoamted RHOS HA installed requires you to manually configure you bonds? Just to clarify, you request is just for bonds. Do you agree tht configuring NICs with/without VLANs is something that is not a baremetal time operation?
>Wouldn't the proposal limit the use of bonds to only when the Operating Systems >is provisioned? That would mean a user who wants to install a HA RHOS >environment, must use Foreman bare metal provioning, and would require them to >re-install the system. Well, I guess it would require they have some way of configuring bonded nic's. Right now in our host groups general, we assume that IP addresses are already up on interfaces already decided by the user. I have to admit I'm getting lost in the VLAN wrinkle. But, I think one alternative would be to take MAC addresses as parameters in our host groups instead of nic's and IP's.
Unclear at this time. Dell has started to test and initially saw issues were the name of vlan devices are getting mangled. (eth0.100 is being translated to eth0_100) whic failes to come up. Believe they have BZ'd this. I beleive this will be an issue with staypuft. If they have success using foreman, I will update.
Bonding moved to bug 1139328
User can configure different subnet to different NIC, per host including VLAN per subnet rhel-osp-installer-0.3.6-1.el6ost.noarch ruby193-rubygem-staypuft-0.3.9-1.el6ost.noarch
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-1350.html