On Tue, 2008-09-23 at 14:26 -0500, Dave Augustus wrote:
On Tue, 2008-09-23 at 14:46 -0400, Michael DeHaan wrote:
> Given the above "cobbler system edit" syntax can you sketch out what
> you
> think this might look like?
>
What about something like this?
for bonding interfaces:
cobbler system edit --name=foo --interface=bond0 --ip=10.10.10.10 --
mac_addr=00:11:22:33:44:55
for ethernet interfaces:
cobbler system edit --name=foo --interface=eth0 --mac=01:23:45:67:89:00
--master=bond0
cobbler system edit --name=foo --interface=eth1 --mac=99:99:77:66:55:44
--master=bond0
for ip addresses(aliases only)
cobbler system edit --name=foo --interface=bond0 --ipalias=192.168.100.2
Here are some revisions/additions to the above mentions with input from
IRC:
build the bonding interface:
cobbler system edit --name=foo --interface=bond0 --ip=10.10.10.10 --
netmask=255.255.255.0 --bondingopts="arp_interval=100
arp_ip_target=10.10.10.11,10.10.10.12,10.10.10.13"
add an ethernet interface to it:
cobbler system edit --name=foo --interface=eth0 --mac=01:23:45:67:89:00
--master=bond0 --hotplug=no
add an ip alias to bond0:
cobbler system edit --name=foo --interface=bond0 --addip --
ipalias=192.168.168.1 --netmask=255.255.255.0
add a second ip to bond0:
cobbler system edit --name=foo --interface=bond0 --addip --
ipalias=172.49.49.10 --netmask=255.255.255.0
By only putting the *master* parameter on the "eth" lines, the number of
"eths" used can be numerous. I realize that *slave* is needed for
configuring bonding but my idea was that the cheetah(or python- whatever
it is that does this) would handle that portion, scanning a system for
ETH interfaces FIRST, then BONDING interfaces. I am not sure if that is
possible but I would assume so.
Thanks,
Dave