On 10/22/2014 12:00 AM, Jeff Schroeder wrote:
On Monday, October 20, 2014, Alan Evangelista
<alanoe(a)linux.vnet.ibm.com <mailto:alanoe@linux.vnet.ibm.com>> wrote:
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.
At one of my previous employers, I used cobbler to dhcp a from scratch
Linux OS that ran in memory. It would come online and then run a small
script to connect to cobbler via the super simple xmlrpc api, get a
list of interfaces (set with the MAC address for each interface),
write out /etc/Iftar, and actually rename all of the interfaces and ip
them with cobbler as the authoritative source.
That might be a more advanced use case but is absolutely a valid one.
Please don't remove a feature like this. My take on config management
(puppet, salt, ansible, etc) is that you should setup the partitioning
and network bits before the config management runs. Please don't
alienate users just because you don't use a given feature.
Thanks for the feedback.
I'm not alienating anybody, I'm just trying to understand Cobbler use cases.
Do not worry, features which are useful and are being used by users will not
be removed.
Regards,
Alan Evangelista