Jasper Capel wrote: > Michael DeHaan wrote: > > >> Right now the interface name could be arbitrary, so it seems it would >> only depend on the magic to set things up right in %post. Does anyone >> care to take a shot at cleaning up the "post-network-system-config" >> snippet on the Wiki now? We should make it account for mutliple >> interfaces first, add it to %post in the default templates, and then we >> can teach it about bonding once that is established. >> >> > If we're gonna do some %post magic anyway, why not add adding custom > routes on an interface as well? It would be a small effort to write the > route-<ifname> files as well. > > something like this: > --interface=eth0 --gateway=10.1.1.254 --routes="10.0.0.0/24 via > 10.1.1.1,10.0.2.0/24 via 10.1.1.2" > --gateway would write the default gateway (as it is now) and --routes > would add anything there to routes-eth0 (but with a newline instead of a > comma) > > Just a thought. :) > > Jasper > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
There's a fine line between this and a config managment tool, though networking /does/ have to be set up properly before that. This seems reasonable, though the syntax maybe could be cleaner. "10.0.0.0/24=10.1.1.1 10.0.2.0/24=10.1.1.2" would allow the python code in utils.py to parse it just like any other --ks-meta or --kernel option. I can see a big Wiki page on "advanced networking topics" building up now :) --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
