On 10/22/2014 11:21 AM, Mann, Owen wrote:
I use it a lot. I consider it a “basic minimum’, since kickstart
supports it. We don’t use configuration management tools at this time
(all built into Cobbler!), and it’s really convenient to have each
machine’s 6 or so interfaces in there. Besides, if PXEing from a bond
or a VLAN needs to be supported, is it that much more work to keep the
rest?
I am not sure what you meant with "if PXEing from a bond or a VLAN needs
to be supported".
If you are talking about netboot, Cobbler does not do any network setup
in the client before or
during netboot, it only answers DHCP/TFTP requests. If you are talking
about *static*
network setup after netboot and before Linux installation starts,
Cobbler does not handle that
either, it supposes network setup is retrieved from DHCP at that time.
Maybe you meant
*static* network setup during and after Linux installation; those are
the only ones Cobbler
do, but they have nothing to do with PXE. Automatic Linux installation
via netboot and
full automatic network setup (all network interfaces, gateway, domain
name servers, etc)
during/after Linux installation are independent features.
It is already clear people like the full automatic network setup feature
and want to keep it, so
that's what we will do.
Regards,
Alan Evangelista
_______________________________________________
cobbler-devel mailing list
cobbler-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel
