I would like to understand why Cobbler allows user to define several network interfaces in system object.
Netboot and automated installation processes only require 1 network interface and supporting multiple
network interfaces introduce complexity. Possible motivations I see:
1) allow user to quickly alternate between different network interfaces for testing purposes
2) automatically setup all network interfaces in a system
imho motivation 2 is a strong point, but it goes beyond the scope of network installation and automated
installation. I see in http://projects.theforeman.org/issues/2240 that people are
requesting the same feature in Foreman to support automatic setup of all network interfaces
using Puppet and its integration with Foreman. I think it makes more sense to delegate this
task (automatic setup of all network interfaces) to a config management tool (eg Puppet)
than do it in Cobbler, otherwise Cobbler ends up being a "do it all" tool.
Maybe I have a restricted view of how and how much this feature is used, so I'd like to get
some feedback from Cobbler community.
Regards,
Alan Evangelista
_______________________________________________
cobbler-devel mailing list
cobbler-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel