Description of problem: At the present time spacewalk uses an in house mechanism to generate the network boot line for a static network instead of using cobbler's network_config snippet. Which means we are not using the full power of the cobbler snippets.. We should move to that
Commenting from a Satellite user perspective, it's vitally important that the same methods are used to provision machines regardless of how Spacewalk/Satellite manages that. Current problem with Satellite 5.3 is that cobbler network config is used when doing a re-provision, but not if I CD boot a machine and point it at the same kickstart file on the Satellite. But would cobbler network_config snippets be as flexible as doing network config inside Activation Keys? We currently have a fairly straightforward default network config, but it depends on machine type: Physical: eth0 & eth1 are bonded (bond0) Virtual: Only eth0 exists on VMware machines However, certain (normally physical) machine types then have eth2 & eth3 configurations depending on usage. Is cobbler the best place to be configuring all this? Would this not mean I have to have different kickstarts for each network type?
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
Changes have happened since this was reported. I wonder if things have improved.
Partha, is there a patch available, or at least reproducer steps that would show what/how things differ when used one method over the other one? Where to start at all?
I'm affraid we don't have a working patch, closing.