inheriting static network config
by Dick Davies
I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname
--profile='centos-53-i386-puppet' \
--static=true --gateway=1.2.1.254 --subnet=255.255.128.0
--ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \
--name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded
into the machines
after they're built.
Tried setting 'default_name_servers' in cobbler/settings
and it seemed to be a null-op; certainly had no effect on existing
systems, even if I re-created their
definitions.
Am I missing something? Thanks!
14 years, 11 months
koan xenpv installation goes interactive and asks for installation method
by Msquared
Hi!
When I try to install a xenpv using koan the installation goes interactive
and asks for the installation method, instead of just using cobbler's HTTP
files.
I'm sure this worked with cobbler/koan 1.4.x, but now that I've rebuilt my
host machine with CentOS 5.3 and installed cobbler 1.6.2 and koan 1.6.1
from EPEL, it doesn't work any more. (I'm sure I've missed something
else, but I can't work out what!)
My koan install command is:
koan --virt --server=cobbler --system=testweb2
Do I have to tell Koan or Cobbler where the install tree is, or something?
I thought that was handled automatically by Koan? What else could I be
missing? What else might I have to do to get koan to perform a
non-interactive install?
Things I've checked:
* Made sure that
* Selected a xen profile
* Run: cobbler sync
* Restarted cobblerd
Anything else I should check?
Here is /var/lib/cobbler/config/systems.d/testweb2.json
{"comment": "", "kickstart": "<<inherit>>", "name_servers_search": [],
"ks_meta": {}, "kernel_options_post": {}, "image": "",
"redhat_management_key": "~", "virt_path": "<<inherit>>", "power_user":
"", "kernel_options": {}, "name_servers": ["192.168.1.10"], "mtime":
1243412603.745317, "template_files": {}, "gateway": "192.168.1.254",
"uid": "MTI0MzQxMTY3OC4wODQxNjc3OTguODI0MDI", "power_type": "virsh",
"virt_cpus": 1, "hostname": "testweb2", "mgmt_classes": [], "power_pass":
"", "netboot_enabled": true, "profile": "centos-5.3-xen-x86_64",
"virt_bridge": "<<inherit>>", "parent": "", "virt_type": "<<inherit>>",
"interfaces": {"eth0": {"dhcp_tag": "", "subnet": "255.255.255.0",
"virt_bridge": "xenbr0", "static_routes": [], "dns_name": "testweb2",
"ip_address": "192.168.1.16", "bonding": "", "static": true,
"bonding_opts": "", "mac_address": "00:16:3e:76:95:36", "bonding_master":
""}}, "power_address": "", "virt_file_size": 10, "ctime":
1243411678.079283, "owners": ["cobbler"], "name": "testweb2", "virt_ram":
512, "power_id": "", "random_id": "9Yyj", "server": "<<inherit>>",
"redhat_management_server": "~", "depth": 2}
Regards, Msquared...
14 years, 11 months
Cobbler 1.6.5 release plan
by Michael DeHaan
Currently there are three things enqueued for 1.6.5
- Don't use simplejson on RHEL 4 and before since it can lead to unicode
problems
- Jasper Capel's fix for koan to not add virtual interfaces for vlan
tagged interface names
- Allow F-11 imports and also create distros that correctly pair PAE and
non-PAE kernel/initrds (creating one distro/profile for each combo).
If there is anything else that needs to be included, let me know.
Otherwise we'll release this after the third item is all polished and
done with testing. (So this makes 2 fixes for cobbler, technically,
and 1 for koan).
(Meanwhile we're working on the devel branch, primarily focusing on
Django features and underlying code simplification to enable that.)
--Michael
14 years, 11 months
cobbler reposync pulling dependencies from host machine's repo list
by David Jablonski
When I run a cobbler reposync of a mirrored repo and the sync needs to
pull dependencies the reposync pulls those dependencies from the
system's yum.repos.d list.
e.g.:
Cobbler Server: CentOS 5.3
Cobbler repos: fedora10, rpmfusion
If I try to sync an rpmfusion mirror and some of those files are
dependent on core dependency files then cobbler will download those
CentOS dependencies instead of from the fedora repositories so I get a
mix of el5 and fc10 packages.
The current way I've been getting around this is to symlink the
yum.repos.d file to the repos for fedora10 when I run a cobbler reposync
and then unlink and re-link for updates to the host OS.
My question is: Is there a better way to do this?
Thanks for any pointers...
--
David W. Jablonski
Systems Administrator
INOC
608.204.0202
608.663.4555 fax
djablonski(a)inoc.com
www.inoc.com
*** DELIVERING UPTIME ***
14 years, 11 months
Re: Fedora 11 preview cobbler-1.6.4-1 sync wont rebuild tftpboot
by Lester M.
OK, did a lil bit of troubleshooting on this matter. I turned off SELinux (I
do not think this was a factor at all) and I tried the following versions:
cobbler-1.4.3-4.fc11.noarch.rpm
cobbler-1.6.2-1.fc11.noarch.rpm
These test pxeboot tests took place on an IBM Lenovo Thinkpad T60, and all
of the above versions actually worked! I can pxeboot a virtual machine on
Fedora 11 preview.
the following versions did not work: (the same problem exists in these
versions)
cobbler-1.6.3-1.fc11.i586
cobbler-1.6.4-1.fc11.i586
So now I know that with the latest version of cobbler, there is a strange
issue there. When I rebuild my machine with fedora 11 preview, the same
results happen with the latest version of cobbler. Also, I can reproduce
this on an old toshiba tecra M2 laptop.
Where do I go now with my troubleshooting? I really want to use the latest
version of cobbler, on Fedora 11 preview, but obviously no being able to
pxeboot a vm is a big issue.
Where do I go on from here?
14 years, 11 months
Koan, KVM and PXE
by Fabien Dupont
Hi all.
Maybe I'm not posting on the right mailing list, but I know you'll point me
the right place...
I am on Fedora 10 with Cobbler 1.6.4 and Koan 1.6.3 (latest available from
stable repos). I would like to create VMs using KVM thus I have imported
FC10 DVD, added Everything and Updates repos and created a host using the
profile created during import. The system has the following properties :
root# cobbler system report vmtest
system : vmtest
profile : fedora-core-10-x86_64
comment :
created : Fri May 8 13:43:40 2009
gateway : 192.168.1.254
hostname : vmtest
image :
kernel options : {}
kernel options post : {}
kickstart : <<inherit>>
ks metadata : {}
mgmt classes : []
modified : Sat May 23 18:42:59 2009
name servers : []
name servers search : []
netboot enabled? : True
owners : ['admin']
redhat mgmt key : <<inherit>>
redhat mgmt server : <<inherit>>
server : <<inherit>>
template files : {}
virt cpus : <<inherit>>
virt file size : <<inherit>>
virt path : <<inherit>>
virt ram : <<inherit>>
virt type : <<inherit>>
power type : ipmitool
power address :
power user :
power password :
power id :
interface : eth0
mac address : ff:00:00:01:00:00
bonding :
bonding_master :
bonding_opts :
is static? : True
ip address : 192.168.1.201
subnet : 255.255.255.0
static routes : []
dns name : vmtest.local
dhcp tag :
virt bridge : br0
As you can see, I use a bridged network with a real bridge create with the
method described on the wiki (eth0 is the real interface and br0 the
bridge).
Then I create the VM using : koan --server=cobbler.evenit.info --virt
--system=vmtest
The VM is correctly created and started : kernel and initrd are correctly
set, virtual hard drive is right and network interface seems right.
root# ps -edf | grep kvm
root 19484 23655 67 21:54 ? 00:00:06 /usr/bin/qemu-kvm -S -M pc
-m 256 -smp 1 -name vmtest -monitor pty -no-reboot -boot c -kernel
/var/lib/libvirt/boot/virtinst-vmlinuz.omv9yr -initrd
/var/lib/libvirt/boot/virtinst-initrd.img.Ufj-qc -append ks=
http://cobbler.evenit.info/cblr/svc/op/ks/system/vmtest ksdevice=link
kssendmac lang= text method=
http://cobbler.evenit.info:80/cblr/links/fedora-core-10-x86_64/ -drive
file=/var/lib/libvirt/images/vmtest-disk0,if=virtio,index=0,boot=on -net
nic,macaddr=ff:00:00:01:00:00,vlan=0,model=virtio -net
tap,fd=14,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc
127.0.0.1:0 -k en-us
But, when I open the VM display with virt-manager, I see that installation
can't start as DHCP is not answering... There's no trace of the DHCP
requests on DHCP server and vnet0 seems to have no trafic :
[root@lilith ~]# netstat -i
Table d'interfaces noyau
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP
TX-OVR Flg
br0 1500 0 173524 0 0 0 261005 0
0 0 BMRU
eth0 1500 0 173589 0 0 0 260909 0
0 0 BMPRU
lo 16436 0 29105 0 0 0 29105 0
0 0 LRU
vnet0 1500 0 0 0 0 0 1 0
0 0 BMRU
As far as I can see, it seems vnet0 doesn't forward its trafic to br0 like
there's no link.
I have also seen that the vnet0 interface seen from host (opposed to guest)
doesn't have the MAC address asked for vnet0, but this may be normal.
I may post the same question on libvirt mailing list...
--
Fabien
14 years, 11 months
Fedora 11 preview cobbler-1.6.4-1 sync wont rebuild tftpboot
by Lester M.
Has anyone tried cobbler 1.6.4 on Fedora 11 preview? I have imported RHEL
5.1, RHEL5.3 and Centos4.7. Normally when you do a "cobbler sync" in
addition to syncing records / repos, etc etc, it will sync and modify /
update the information under /tftpboot/* .
The problem that I am having is that tftp-server-0.49-3.fc11.i586,
tftp-0.49-3.fc11.i586, and cobbler-1.6.4-1.fc11.i586 are installed. Even tho
these rpms (and their dependencies) are installed, the VM will pxeboot, but
then nothing else happens. This behaviour prompted me check the /tftpboot/*
directory and files. I discovered that nothing changed, and the defaults
were still there.
I would like to get this troubleshooted. This could be a 'fedora' thing,
however I would like to hear anyone's ideas / experiences.
14 years, 11 months
right tool for PXEless boots
by Dick Davies
We use a webapp to register servers, so we can edit our hostnames, MACs and IPs,
but not the DHCP configuration directly. So I'm essentially PXEless.
Needless to say, 'cobbler buildiso' is helping a lot, but I only seem
to be able to
point a machine to a system definition by creating a custom ISO.
Is there a way to present the booting hosts with the menu they'd get
over TFTP? The machines under fairly heavy development and so we're building
an ISO each time we add a profile at the moment.
Ideally I'd like some way to get the booting servers to the TFTP
server, then let
the usual cobbler mechanisms take place (per-system settings etc.
pulled by MAC address).
Thanks!
14 years, 11 months
Integrating Repos with PXE Installation
by Corey Garst
I've successfully set up cobbler so that I can get to various profiles
over PXE. I've selected the corresponding repos (Ex: Fedora-10-i386-base
& Fedora-10-i386-updates for my Fedora-10-i386 profile). I'm finding
that my cobbler installations don't end up with these updates and the
local cobbler repo isn't pre-populated. What must I do to enable this
feature?
Thanks!
Corey Garst
14 years, 11 months
