John Eckersberg's recent patches allow cobbler to support multiple
arbitrary interfaces, each having their own name:
cobbler system edit --name=foo --interface=foosball
--mac=AA:BB:CC:DD:EE:FF --ip=192.168.10.50 #etc
In order to support this, I've had to overhaul the webapp some. The
new interface presents a select box ("drop down") of all of your interfaces
and lets you edit them one at a time. There is also a button to delete
the selected interface and to add one (after providing the name).
Testing on this would be much appreciated, though it seems pretty solid
at the moment.
This now opens up the possibility of adding additional parameters, such
as in support of the bonding use cases, as we can now support interfaces
with arbitrary names. If this is still desired we need (A) a list of
new parameters to "cobbler system add" that we would require, and (B)
upgrades to the $post_network_config snippet modification (on top of
what we already have in /var/lib/cobbler/snippets on the devel branch)
that understands these additional per-interface variables.
Also note that in the new editor there is a checkbox (and there is a CLI
field as well) for editing static interface details. This is leveraged
by the network_config snippet in $pre so your kickstart templates no
longer have to mention the networking details for which interfaces are
dhcp and which are static.
Longer term, we're going to have a first-class "network" object in
Cobbler, where we can make addition of new interfaces even easier by
assigning them to a network and have Cobbler manage their reservations
(optional) and/or static info. Of course the existing method will
still work.
Comments/questions?
After testing this feature, let's move forward with the other network
details, starting with the bonding options (still need input/consensus
on this, I think) and then moving towards the (optional) network object.
--Michael
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
