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,
f Jeff
Schroeder
Sent: Tuesday, October 21, 2014 10:00 PM
To: cobbler development list
Subject: Re: [cobbler-devel] Support of several network interfaces in system
object
On Monday, October 20, 2014, Alan Evangelista
mailto:ala...@linux.vnet.ibm.com>> wrote:
I would like to understand why C
On 10/22/2014 12:00 AM, Jeff Schroeder wrote:
On Monday, October 20, 2014, Alan Evangelista
mailto:ala...@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 processe
On Monday, October 20, 2014, Alan Evangelista
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 introdu
On 10/21/2014 02:25 PM, Jörgen Maas wrote:
Hi Alan,
Here's some of the reasons i can think of why having support for
multiple interfaces would be useful:
- Not everybody is using configuration management tools (eg. small
environments)
- Configuration management integration is rather weak (a
Hi Alan,
Here's some of the reasons i can think of why having support for multiple
interfaces would be useful:
- Not everybody is using configuration management tools (eg. small
environments)
- Configuration management integration is rather weak (atm just Puppet)
- It could be that pxe/install in
