Setting up new Cobbler server from existing one
by petermity
If I have an existing Cobbler server all set up, is there an easy
way to copy all of the distros, profiles, and other Cobbler
aspects from it to a freshly created unit?
Could I just copy /etc/cobbler, /var/www/cobbler, and
/var/lib/cobbler to the new machine and then do cobbler sync?
12 years, 10 months
Allow multiple snippets directories
by petermity
Please allow multiple directories to be listed for "snippetsdir".
I like keeping my snippet files separate from the default Cobbler
ones.
Initially I added a symlink from the default snippets directory
to my snippets. But then I have to specify the directory path
for each snippet, and the hierarchy search method for per_profile
etc. doesn't work under that directory.
Then I changed the settings to point to my snippets directory
instead of the default, and copied Cobbler's default snippets to
my directory. Now I don't need to specify a path to snippets,
and the hierarchy works. But then everything is mixed up, and if
Cobbler's snippets change in a later release, it's easy to forget
to update them.
That's why it would be nice to be able to use a PATH or LIB style
method to allow multiple directories to be specified for
snippets. Then they don't need to be mixed up, yet the hierarchy
search could work in all directories.
12 years, 10 months
How to clear "cobbler status"?
by petermity
The "cobbler status" command is handy to see when builds are
running/finished. However, the display can be cluttered by units
that finished building (or hung/failed) days/weeks ago, even if
the Cobbler server is rebooted. Is there a way to start fresh?
Related: is there a wget command or some other method to tell
Cobbler that a failure occurred in the %post section? Something
analogous to the $kickstart_done, maybe a $kickstart_failed?
12 years, 10 months
How to force failure?
by petermity
How can I force a failure on a bad condition, so that "cobbler
profile getks" fails with a traceback (and the actual kickstart
fails, and validateks fails too)?
For instance, I don't want to proceed if some variable is not set:
#if $getVar('myvar','') != ''
# ... do something with $myvar
#else
# Somehow throw an error to abort, e.g.:
#error "The profile must define 'myvar'"
#end if
13 years
Cobbler 2.0.11-2
by Scott Henson
Some may have noticed that the Cobbler 2.0.11-1 release did not have a
change log update in the spec file. This release fixes that.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
13 years
cobbler db change from within a trigger may disappear
by Brano Zarnovican
Hi,
I have a python trigger on post system add hook. Sometimes the change
on Cobbler DB made
from within the trigger (via API) get lost. I would like to check with
you first if I'm allowed to
make changes within a trigger, before I open a ticket.
All looks as expected in 'cobbler system report', but the change may not be
in the JSON file and it is permanently gone after you do the next
cobblerd restart.
Regards,
BranoZ
13 years, 1 month
Yum Post Install Mirror
by Tom Murray
Cobbler Version 2.0.9
Cobbler Server Fedora 13
I have setup a Cobber Server with a local F13 repository. I can
successfully use PXE to install F13 using a kickstart file. According
to the documentation, it appears as though Cobbler will configure the
yum repositories on the newly installed system to match the repo's I
have locally. I have not been able to get the yum repos configured to
my local repos via the PXE/kickstart procedure. The standard F13 repos
are defined on the newly built system.
My /etc/cobbler/settings file has the option yum_post_install_mirror: 1
configured.
The kickstart file has the $yum_repo_stanza entry as well.
Thanks in advance for your help!!!
TM
[root@build kickstarts]# cobbler distro report
Name : P13-x86_64
Architecture : x86_64
Breed : redhat
Comment : fedora13.1
Initrd :
/var/www/cobbler/ks_mirror/P13-x86_64/images/pxeboot/initrd.img
Kernel :
/var/www/cobbler/ks_mirror/P13-x86_64/images/pxeboot/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree':
'http://@@http_server@@/cblr/links/P13-x86_64'}
Management Classes : []
OS Version : fedora13
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
[root@build kickstarts]# cobbler profile report
Name : P13-x86_64
Comment :
DHCP Tag : default
Distribution : P13-x86_64
Enable PXE Menu? : True
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/default.ks
Kickstart Metadata : {}
Management Classes : []
Name Servers : []
Name Servers Search Path : []
Owners : ['admin']
Parent Profile :
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos : ['F13-Updates', 'F13']
Server Override : <<inherit>>
Template Files : {}
Virt Auto Boot : 1
Virt Bridge : xenbr0
Virt CPUs : 1
Virt File Size(GB) : 5
Virt Path :
Virt RAM (MB) : 512
Virt Type : qemu
[root@build kickstarts]# cobbler repo report
Name : F13-Updates
Arch : x86_64
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror :
http://mirrors.kernel.org/fedora/updates/13/x86_64
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
Name : F13
Arch : x86_64
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror :
http://mirrors.kernel.org/fedora/releases/13/Fedora/x86_64/os/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
Kickstart file contents:
--------------------------------
#platform=x86, AMD64, or Intel EM64T
# Install OS instead of upgrade
install
# Use CDROM installation media
#cdrom
# Use network installation
url --url=$tree
# If any cobbler repo definitions were referenced in the kickstart
profile, include them here.
$yum_repo_stanza
# Reboot after installation
reboot
# Root password
rootpw --iscrypted \$1\$H.vYye/z$91xYx.U/2wqyzb.yu.4Tz1
# System authorization information
auth --useshadow --passalgo=md5
# Use text install
text
# System keyboard
keyboard us
# System language
lang en_US
# SELinux configuration
selinux --disabled
# Installation logging level
logging --level=info
firstboot --disable
network --device=eth0 --bootproto=query
# Firewall configuration
firewall --disabled
# System timezone
timezone America/New_York
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
%packages
@base
@admin-tools
@core
@editors
@kde-desktop
@graphical-internet
@base-x
firefox
@dial-up
@system-tools
# Keep dap off the install media, makes Eng & Sci show up
-dap-server-cgi
# filesystem stuff
@filesystems
# Removals
-gimp-help
-java-1.6.0-open*
-xorg-x11-docs
-kernel-doc
-java-1.5.0*
-sinjdoc*
-libgcj-src
-*javadoc*
-frysk
-*gcj*
-*openoffice*
-*games*
%post --interpreter=/bin/bash
chkconfig --levels 0123456 iptables off
chkconfig --levels 0123456 ip6tables off
chkconfig --levels 0123456 bluetooth off
chkconfig --levels 0123456 sendmail off
%end
13 years, 1 month
Extract iso from resulting files of livecd-iso-to-pxeboot
by hai wu
Does anyone know how to extract iso file from initrd.img file generated from
command 'livecd-creator'/'livecd-iso-to-pxeboot'? This livecd tools embed
the ISO file in initrd.img and hide it there, and there is not tool so far
to extract ISO file out of initrd.img file ..
13 years, 1 month
cobbler-register without kickstart
by Levente Lajko
Hello Guys,
I am working on a cobbler powered deployment environment to prepare hardware
for a specific deployment. Here is the scenario:
1. Multitude of bare-metal "off the truck" servers
2. Loading HP Scripting Toolkit image with some custom scripting via Cobbler
to update firmware, set iLO, configure RAID.
3. For this I use the default system with the Scripting Toolkit's profile
What I'm missing at this point is the ability to prevent pxe boot for the
default profile after the first boot + auto registration of the servers
using the Scripting Toolkit's profile.
My understanding is that these options are available only when deploying
RedHat/Fedora/Centos based images.
Any help would be appreciated.
Thanks in advance,
Levente
13 years, 1 month
Interactive RHEL installation
by Daniel Kertby
Hi all,
Anyone know how to setup a kickstart file to do an interactive RHEL 5 & 6
installation?
I can't get a minimal kickstart file to work, anaconda complains.
It was somewhere mentioned that Anaconda will not allow an interactive
installation in
RHEL 6. Interactive installation is really needed as a supplement for us and
it would
be great if a profile + kickstart file could fix it.
Thanks in advance,
Daniel
13 years, 1 month
