Dave Hatton wrote:
> This would mean --interface=X would either take ethN or bondN, if
we
> also support the bonding case, as opposed to a freeform string.
>
>
>
If you allow for --interface=X:Y then this would allow for the IPalias
support discussed yesterday
(eg: --interface=eth0:1 --ip=x.x.x.x --netmask=x.x.x.x)
this should generate a standard ifcfg file under
/etc/sysconfig/network-scripts but with a name like ifcfg-eth0:1
dave
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
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.
(Also regarding my earlier web comments, this interface change may prove
a reason enough to clean up the webapp in general --- adding
multi-interface support is going to be hand without making it more ajaxy
anyway. This might make it a little longer between releases but could
make for some interesting things. Still evaluating -- I'll chase this
while everyone is looking at the networking details, we need them both)
--Michael