cobbler May 2011

cobbler@lists.fedorahosted.org

19 participants
19 discussions

Vote for a Cobbler/ESXi session at VMworld
by Jonathan Sabo 17 May '11

17 May '11

Hello List, In an attempt at gaining a free trip to Vegas where I will no doubt win millions and millions of dollars playing slots and an opportunity to spread the love for automated Cobbler installs, I submitted a session outline to VMworld titled "Bare Metal to Business Ready with ESXi, ViJava, and Cobbler". You have to log in to vote for the sessions and there are lots of cool sessions to vote on but you can find the one I submitted just by searching for "Cobbler". Check it out! Thanks, Jonathan

2 2

Putting generated.iso on a usb stick
by Ole Ersoy 15 May '11

15 May '11

Hi, I'm attempting to put generated.iso on a USB stick. I tried this: [root@ole ole]# livecd-iso-to-disk /home/ole/generated.iso /dev/sdb1 Verifying image... /home/ole/generated.iso: Could not get pvd data Unable to read the disc checksum from the primary volume descriptor. This probably means the disc was created without adding the checksum.Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort ERROR: /home/ole/generated.iso does not appear to be a Live image or DVD installer. Cleaning up to exit... Any suggestions on how to go about doing this? Also once the iso is on the stick can I just plug it in and go or are there other steps that must be performed before I'll get a menu? TIA, - Ole

3 6

tftp: client does not accept options
by Ole Ersoy 13 May '11

13 May '11

Hi, I'm trying to pxe boot a machine, and I get the following in /var/log/messages May 13 15:18:54 ole in.tftpd[3913]: tftp: client does not accept options The client machine just hangs on the line: Trying to Load: pxelinux.cfg/default Thoughts? TIA, - Ole

4 6

cobbler kickstart and filesystem labels
by Tony Schreiner 13 May '11

13 May '11

I'm new to cobbler.... I've succeeded in creating a PXE + kickstart environment, but something odd is happening I've run an installation (CentOS 5.6) many times now on a machine and each time it alternates creating labeling the disks as LABEL=/ LABEL=/boot etc... and then next time LABEL=/1 LABEL=/boot1 etc.. alternating with whatever it was before. If I change it manually after the system comes up, the next kickstart will label it the other way. If I change one of the file system labels and leave the others, it will still label with the name other to what it was. Here is my kickstart snippet for the disks #System bootloader configuration bootloader --location=mbr ##Clear the Master Boot Record #zerombr yes #Disk partitioning information clearpart --linux --drives=sda part /boot --fstype ext3 --ondisk=sda --size 300 part / --fstype ext3 --ondisk=sda --size 25000 part swap --size 2048 --ondisk=sda part /var --fstype ext3 --ondisk=sda --size 2000 part /tmp --fstype ext3 --ondisk=sda --size 2000 part /scratch --fstype ext3 --ondisk=sda --size 1 --grow It's a Dell PowerEdge and I wish to preserve the Diagnostics partition, hence the clearpart --linux am I missing something? I have not run into this before with kickstart, outside of cobbler. Thanks, Tony Schreiner

3 3

Cobbler Build Hostname issue
by Jaganathan, Selvakumar 11 May '11

11 May '11

Hi, I building some vsphere 4.1 using cobbler where we mention fqdn name for hostname but after the installation I see shortname for HOSTNAME in /etc/sysconfig/network file. How we can fix this, below is cobber ks config info related to network and host. We want HOSTNAME to be fully qualified domain name. # --- Cobbler Details --- # name = test1 # distro = vsphere4-update1 # profile_name = vsphere4_server # http_server = x.x.x.x # hostname = test1.labdomain.net # system_name = test1 # interfaces = ['vmnic0'] # ks_meta = "$ks_meta" # source_repos = [] # snippetsdir = /var/lib/cobbler/snippets # kickstart = /var/lib/cobbler/kickstarts/jpmc-ks.cfg # arch = x86_64 # initrd = /var/lib/cobbler/pxeboot/vsphere4/initrd.img # kernel = /var/lib/cobbler/pxeboot/vsphere4/vmlinuz # kernel_options = "ksdevice=vmnic0 lang= mem=512M ip=x.x.x.x quiet netmask=255.255.255.0 dns=x.x.x.x vmkopts=debugLogToSerial:1 kssendmac gateway=x.x.x.x " # Using "old" style networking config. Make sure all MAC-addresses are in cobbler to use the new-style config network --bootproto=static --ip=x.x.x.x --netmask=x.x.x.x --gateway=x.x.x.x--nameserver=x.x.x.x --hostname= test1.labdomain.net --onboot=on Sorry I mentioned x.x.x.x just to avoid real ip address. Thanks, Selva This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

1 0

Allowing for --profiles and --system when creating standalone iso?
by Jan Hedström 10 May '11

10 May '11

Hi, I have a question on the buildiso --standalone capabilities. When making a standalone ISO, it is not possible to define a certain --profile and/or --system. Instead, the ISO will be created for each and every possible system using a certain --distro. For a project I work on, it would be useful to limit the amount of configurations copied onto that ISO. But before I start trying to patch the buildiso script, I would like to ask whether there is a logical, firm reason not to do this? Will something break if we try building standalone ISOs for individual profiles? Thanks, /Jan Hedström

1 0

[PATCH] plugin to auto-alloc IP with cobbler
by Brano Zarnovican 09 May '11

09 May '11

Hi, I wrote a small plugin that I would like to share.. It allows cobbler to auto-allocate IP from a pool, rather than user explicitly specifying the IP at host creation time. This is mostly useful for VMs with statically assigned IP, where you don't care too much what the IP is (other than it is not used in that VLAN). How to use? In the /etc/cobbler/settings you configure a pool for each VLAN.. ip_auto_alloc: true ip_pool: vlan100: 10.10.100.20 - 10.10.100.250 vlan101: 10.10.101.20 - 10.10.101.250 There is only one pool allowed on each vlan. Pool name must match the vlan/bridge name (from --virt-bridge option). Then you can create a VM as follows.. cobbler system add --name $host --hostname $host --profile Fedora14-kvm --gateway=10.10.100.1 cobbler system edit --name $host --interface=eth0 --virt-bridge=vlan100 \ --ip=0.0.0.0 --subnet=255.255.255.0 --dns-name=${host}.example.com --static=yes cobbler system edit --name $host --interface=eth1 --virt-bridge=vlan101 \ --ip=0.0.0.0 --subnet=255.255.255.0 --dns-name=${host}-mgmt.example.com --static=yes The code above can be wrapped into a script, which will allow you to add VM just by specifying the hostname. How it works? When the new host/interface is added to cobbler, plugin is triggered. If it finds an IP address 0.0.0.0 on an interface, it will select a pool associated with the interface's VLAN (--virt-bridge). Then it finds the first unused IP in the pool. The check if the IP is used is made against Cobbler DB, therefore Cobbler must be the only authority to assign IP from that pool. Lastly, the dummy IP 0.0.0.0 is replaced with real IP. To install.. Install package python-IPy (yum install python-IPy) Copy the attached file "system_post_ip_alloc.py" to /usr/lib/pythonX.X/site-packages/cobbler/modules/. Add the config snippet from above to /etc/cobbler/settings. Restart cobblerd I have also attached the same plugin in a form of a patch file against stable branch. Regards, BranoZ

1 0

cobbler db change from within a trigger may disappear
by Brano Zarnovican 06 May '11

06 May '11

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

2 3

Confused, multiple vlans and http_server ip per each VLAN
by Daniel Kertby 04 May '11

04 May '11

Hi, I have setup Cobbler to use DHCP and the cobbler itself resides on multiple VLANs (over a Bond). My intention is to get the ks=http://<server>/cblr/svc.. to point at the interface if of the Cobbler server for that VLAN. When adding a system, --server-override=string can be used but I don't want this to be put on the cobbler users -- or additional code for fixing that. My understanding is that the /etc/cobbler/dhcp.template file can be updated to provide the correct installation server. Is this correct? My /etc/cobbler/dhcp.template today contains network definitions, such as (masked): subnet aa.bb.cc.dd netmask 255.255.254.0 { option routers aa.bb.cc.1; option domain-name-servers xxx,yyy; option subnet-mask 255.255.254.0; filename "/pxelinux.0"; default-lease-time 21600; max-lease-time 43200; next-server aa.bb.cc.YY; (the IP of the cobbler server for that VLAN) } EVERYTHING below: #for dhcp_tag in $dhcp_tags.keys(): ... ... IS unmodified. I would appreciate the simpliest and cleanest way to keep the traffic within the VLAN without user intervention. Best Regards, Daniel

3 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

cobbler May 2011