Enable UEFI Red Hat support on Cobbler (2.6.7) - HOW?
by Ž D
Hallo. I was successful in UEFI boot and install, here are details:
1) Cobbler server : 2.6.9
source: ?, ?
build time: Fri Jun 12 07:42:24 2015
Cobbler is installed on Oracle Linux 6.6
2) I am installing Oracle Linux R6-U6-x86_64 on the Oracle Server x3-2
3) DHCP service is provided by another box, the config is:
host my-hostname.domain.com {
hardware ethernet 00:10:e0:aa:aa:aa;
fixed-address 10.xx.xx.xx;
next-server 10.yy.yy.yy; # my cobbler server
filename "/grub/BOOTX64.efi";
}
4) How to find proper BOOTX64.efi file, read the doc:
http://docs.oracle.com/cd/E37670_01/E41137/E41137.pdf
See the paragraph 1.4.7 (starts on page 9), the page 10 talks about
UEFI-based PXE client.
This is the key: UEFI-based PXE clients can use the BOOTX64.efi boot
loader, which is available as EFI/BOOT/BOOTX64.efi from the Oracle Linux
6 Update 6 Media Pack DVD image.
So I placed BOOTX64.efi in <my_cobbler_server>:/var/lib/tftpboot/grub/
5) I also have the file splash.xpm.gz in
<my_cobbler_server>:/var/lib/tftpboot/grub/
6) The file /var/lib/tftpboot/grub/00:10:e0:aa:aa:aa looks like
timeout=10
splashimage=(nd)/splash.xpm.gz
title OL-R6-U6-x86_64-UEFI
root (nd)
kernel /images/OL-R6-U6-x86_64/vmlinuz ksdevice=bootif lang= text
ks=http://my_cobbler_server/cblr/svc/op/ks/system/host_name
initrd /images/OL-R6-U6-x86_64/initrd.img
7) The kickstart file is
# ks for OL 6.6 UEFI
install
text
url --url=http://10.yy.yy.yy/cobbler/links/OL-R6-U6-x86_64
lang en_US.UTF-8
keyboard us
rootpw --iscrypted $1$zw2wh8P1$zZMsVBx4.HbZNxM8p1uPX1
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Los_Angeles
reboot
bootloader --location=partition
clearpart --all --initlabel
part /boot/efi --fstype=vfat --size=200 --asprimary --ondisk=sda
part /boot --fstype=ext4 --size=500 --label=/boot --asprimary --ondisk=sda
part / --fstype=ext4 --size=8192 --grow --maxsize=51200 --label=/
--ondisk=sda
part /var --fstype=ext4 --size=4096 --label=/var --ondisk=sda
part /u01 --fstype=ext3 --size=4096 --label=/u01 --ondisk=sda
part swap --size=16384 --label=swap --ondisk=sda
%packages
@base
@core
device-mapper-multipath
kexec-tools
net-tools
pciutils
sysfsutils
system-config-kickstart
wget
lsscsi
nfs-utils
8) Works for me. Let me know if you need any other detail?
--
Thanks,
Zarko
7 years, 9 months
Calling snippets from ksmeta
by Antonio Sebastian Salles M.
Hi there,
I'm looking the way for call a list of SNIPPETs using an array of
ksmeta variables, but finally cheeta doesn't like it. Something like
this:
cobbler ... --ksmeta="machinetype=kvm machineenv=db"
...
#set $machinetype = $getVar('$machinetype')
#set $machineenv = $getVar('$machineenv')
$SNIPPET('spacewalk/1/$machinetype')
$SNIPPET('spacewalk/1/$machineenv')
Is possible do this?
Thanks a lot.
Antonio
8 years, 6 months
Re: [cobbler] Provisioning a cluster
by Waldron, Michael H
Andre,
That did the trick, I also had to install python-ethtool in addition to koan, and now it works. One additional question, do you have a method for it to also register the desired hostname or do you just rename it after it's registered?
Vielen dank!
Mike
Date: Fri, 6 Nov 2015 09:36:36 +0100 (CET)
From: André Gemünd <andre.gemuend(a)scai.fraunhofer.de>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: Re: [cobbler] Provisioning a cluster
Message-ID:
<316657621.782597.1446798996731.JavaMail.zimbra(a)scai.fraunhofer.de>
Content-Type: text/plain; charset=utf-8
Hi Mike,
you need to enable EPEL and install koan in your kickstart. I forgot to mention that as we have it in our default package list (handy for reinstalls).
We mirror EPEL with cobbler repo and then add it to the profile repos field for nearly all of our profiles (except the bare minimal). If you have the $yum_repo_stanza in your kickstart, this will enable it for installs.
Cheers
Andre
Mike Waldron
Systems Specialist
ITS - Research Computing Center
University of North Carolina at Chapel Hill
8 years, 6 months
Cobbler 2.6.9 does not generate add_on_product
by Diep, Minh
Hi,
I am running v2.6.9 and found that cobbler does not generate the add on product in suse kickstart xml file even I have the repos listed. The same profile and repo works on v2.4.4.
cobbler system getks --name wolf-38 | head –20
<?xml version="1.0" ?><!DOCTYPE profile><profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
<!--
THIS FILE IS MANAGED BY CHEF
DO NOT EDIT DIRECTLY
Your changes will be lost the next time Chef runs
-->
<add-on>
<add_on_products config:type="list">
</add_on_products>
</add-on>
<bootloader>
[root@mgmt-1 kickstarts]# cobbler profile report --name test-sles11sp4-x86_64 | grep Repos
Repos : ['local-toolkit_sles11sp4-x86_64', 'sdk-sles11.4-x86_64']
[root@mgmt-1 kickstarts]#
8 years, 6 months
DHCP with custom MAC Addresses?
by Sam Sen
I generated a handful of valid MAC Addresses using a Python script I created. For whatever reason, my Vms won't pick up a DHCP address from my cobbler server (Cobbler managed DHCP). I finally realized that unless I have Cobbler generate the MAC addresses, my Vms wont PXEBoot. I ended up using the MAC generated via the Cobbler web, but I prefer to use different ranges within our network. Is there a setting somewhere that Cobbler only accepts a certain range?
8 years, 6 months
Re: [cobbler] Provisioning a cluster
by Waldron, Michael H
Andre,
I am running a default installation and the kickstart does have the $SNIPPET('cobbler_register') entry, however it's not working. The system doesn't get registered and just installs again when rebooted. I do have register_new_installs set also. I see that after installation the cobbler-register command is not installed on the worker. Am I missing something?
Mike
Date: Thu, 5 Nov 2015 10:14:21 +0100 (CET)
From: André Gemünd <andre.gemuend(a)scai.fraunhofer.de>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: Re: [cobbler] Provisioning a cluster
Message-ID:
<1369099692.750496.1446714861962.JavaMail.zimbra(a)scai.fraunhofer.de>
Content-Type: text/plain; charset="utf-8"
> I am new to Cobbler, and am wondering if anyone uses it to provision a large cluster? Rather than having to collect a lot of MAC addresses and manually create all the system records, I'd like to be able to have systems register themselves when they are first booted.
Assuming the Cobbler server sits in an internal cluster network, when we are provisioning the (uniform) worker nodes for the first time, we simply set the default entry for PXE boots to provision the correct distro, depending on your paths e.g. in /var/lib/tftpboot/pxelinux.cfg/default. You can enable menu in cobbler settings to let cobbler sync generate you a file showing the available profiles with the correct params. In the kickstart we use cobbler_register.
> I've seen the snippet 'cobbler_register' which seems intended for this purpose, but I can't figure out how to use it. Is anyone doing this? If so can you provide specifics on how to do so?
The snippet should just work when its used in a kickstart with $SNIPPET('cobbler_register'). Be sure to set register_new_installs in cobbler settings. We also have pxe_just_once set to 1.
--
André Gemünd
Fraunhofer-Institute for Algorithms and Scientific Computing
andre.gemuend(a)scai.fraunhofer.de
Tel: +49 2241 14-2193
/C=DE/O=Fraunhofer/OU=SCAI/OU=People/CN=Andre Gemuend
8 years, 7 months
Provisioning a cluster
by Waldron, Michael H
I am new to Cobbler, and am wondering if anyone uses it to provision a large cluster? Rather than having to collect a lot of MAC addresses and manually create all the system records, I'd like to be able to have systems register themselves when they are first booted.
I've seen the snippet 'cobbler_register' which seems intended for this purpose, but I can't figure out how to use it. Is anyone doing this? If so can you provide specifics on how to do so?
Mike Waldron
8 years, 7 months
