Cobbler 2.8
by Alan Evangelista
Jörgen, when do you plan to release Cobbler 2.8? You already know what
will be on it
(bug fixes, new features, doc improvements, refactorings)?
Regards,
Alan Evangelista
8 years, 11 months
Cobbler's TFTP server
by Alan Evangelista
Question 1: From the user perspective, what is the benefit of using
Cobbler's own TFTP server,
implemented in Python, over using inet TFTP server or another TFTP
server ? I see it generates
templates in RAM instead of creating files (eg boot loader configuration
file), but I dont
know if this translates in a performance gain.
Question 2: Cobbler TFTP server supports Linux automated installation?
Automated installation
related kernel options are built in tftpgen.py and Cobbler TFTP server
does not use it,
it just renders the boot loader configuration file with system blended data.
Question 3: is it worth it to keep Cobbler TFTP server?
Regards,
Alan Evangelista
9 years, 4 months
ESXi and boot loader conf file templates
by Alan Evangelista
Hi
Cobbler has boot loader conf file templates for mboot.c32
(bootcfg_esxi*) and gpxe (gpxe_system_esxi*)
which are used on ESXi installation. Why do we need to support both boot
loaders? gpxe doesnt support
all ESXi use cases?
Regards,
Alan Evangelista
9 years, 4 months
Boot loader configuration files and system's network interfaces
by Alan Evangelista
Current one boot loader configuration file is written for each system's
network interface.
afaik usually user uses only one network interface in the system to
netboot it, so writing the
other boot loader configuration files are useless. I suggest either:
(1) add a netboot_interface attribute to system, restricting generation of
one single boot loader configuration per system
(2) add a netboot_enabled attribute for each system's network_interface,
restricting generation
of boot loader configuration for enabled network interfaces in a system
Alternative 2 is more flexible, but I do not know if we have any use
case that requires it.
What do you think?
Regards,
Alan Evangelista
9 years, 4 months
Windows breed
by Alan Evangelista
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
9 years, 5 months
dev platform
by J's Mail
I'm stumbling and am looking for some guidance. I did this once
successfully, but have since wiped that environment (vagrant). In a new
instance (CentOS 6.5) I can get a 'make install' to complete successfully,
but after that, I get odd behaviour (cobbler import fails, cobbler system
add fails); the errors are odd and glaring, such that I suspect my
environment rather than the code.
I want to help out with some basic bugs, but I can't seem to get a copy of
Cobbler running from source. Thus, I ask: is there a recommended build
environment?
Thanks,
-- Jess
9 years, 5 months
Support of several network interfaces in system object
by Alan Evangelista
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
9 years, 5 months
pxe_just_once setting default value
by Alan Evangelista
Why pxe_just_once default value is 0 in Cobbler? It seems to me that
most users
would like to have this setting enabled so that netboot is disabled in
system
object (and system entry is removed from DHCP server configuration file)
after
OS installation is done.
Often I see beginner users having problem with this in IRC.
Regards,
Alan Evangelista
9 years, 5 months
