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 Tuesday, October 21, 2014, Alan Evangelista
wrote:
> Cobbler is a Linux installation server, based on Linux boot loaders, Linux
> initrd/kernel
> and Linux automated installation processes. Why is there a Windows breed?
> How would someone
> use this to install a Windows system? imho this shou
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
Let's send that stuff to Valhalla then. Indeed there are better facilities
to handle log files.
Cheers!
Jörgen
On Tue, Oct 21, 2014 at 5:49 AM, Alan Evangelista wrote:
> On 10/09/2014 12:06 AM, Alan Evangelista wrote:
>
>> I see that there is a Cobbler XML-RPC interface call to delete console
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
Cobbler is a Linux installation server, based on Linux boot loaders,
Linux initrd/kernel
and Linux automated installation processes. Why is there a Windows
breed? How would someone
use this to install a Windows system? imho this should be deleted.
Regards,
Alan Evangelista
___
