cobbler November 2008

cobbler@lists.fedorahosted.org

41 participants
119 discussions

Add PowerPC network boot support using yaboot
by James Laska 14 Nov '08

14 Nov '08

The following patches add support for network booting PowerPC systems using yaboot. The version of yaboot included is yaboot-1.3.14. This version does not yet full support booting Fedora10 ppc images yet. Work is underway with the yaboot-devel (http://yaboot.ozlabs.org/) crew to address this. In addition to network boot support, `cobbler import` will now recognize and process ppc distros. As suggested by Michael, my next step will be to flesh out a wiki page detailing the process. Comments/questions welcome. Thanks, James

2 13

change netboot-enabled=1 to profile=localboot?
by Vreman, Peter 14 Nov '08

14 Nov '08

The netboot-enable option is related to the profile. When the netboot-enable=0 then the localboot pxelinux.cfg is made. Is there a reason to keep this a separate option instead of adding a -profile=localboot? This allows to have a single item to toggle what the system is going to do at the next reboot. In the system editing a list of allowed profiles can be created and a button can be added to view the KS for the selected profile. cobbler edit system -name=virt1 -allowed-profiles="RHEL4.6-Xen RHEL5.2-Xen" cobbler edit system -name=physical1 -allowed-profiles="RHEL4.6 RHEL5.2" cobbler edit system -name=physical1 -active-profile=RHEL4.6 cobbler edit system -name=virt1 -active-profile=Localboot cobbler edit profile -name=Localboot -all-systems=1 cobbler edit profile -name=ImageSave -all-systems=1 Regards, Peter This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

[PATCH] Detection of ubuntu 8.10
by Javier Palacios 13 Nov '08

13 Nov '08

The recently released ubuntu version is not properly detected due to a change in the versioning of base-files package http://github.com/javiplx/cobbler/commit/4ceb886ce836e76de53d79cc5ebc306261…

2 1

Power commands
by Bill Peck 13 Nov '08

13 Nov '08

Here is a sample of the different power commands we use internally. You can see most options are the same but some require plug number or domain or blade. Some don't support reboot so its probably best if we do the "reboot" ourselves and just call off and then on. /sbin/fence_bullpap -a mgmt.example.com -l Administrator -p PASSWORD -d Domaine2-8CPU -o reboot || exit 1 /sbin/fence_wti -a mgmt.example.com -n PLUGNUMBER -p PASSWORD -o reboot || exit 1 /usr/local/sbin/fence_apc_snmp -a mgmt.example.com -n PLUGNUMBER -o reboot /usr/bin/sudo /sbin/ether-wake -i eth0 HOSTNAME.com /sbin/fence_ipmilan -i mgmt.example.com -l root -p PASSWORD -o reboot || exit 1 /sbin/fence_drac -a mgmt.example.com -l root -p PASSWORD -m Server-10 -o reboot || exit 1 /usr/bin/ipmitool -H mgmt.example.com -U root -P PASSWORD power off; sleep 10 \ /usr/bin/ipmitool -H mgmt.example.com -U root -P PASSWORD power on || exit 1 /sbin/fence_ilo -a mgmt.example.com -l Administrator -p password -o reboot || exit 1 /sbin/fence_rsa -a mgmt.example.com -l USERID -p PASSW0RD -o Reboot || exit 1

1 0

The plan for 1.3/1.4 release schedule
by Michael DeHaan 13 Nov '08

13 Nov '08

I said I'm going to release a test release for Cobbler 1.3 tomorrow, we'll call this 1.3.1. -- I very much encourage folks with cycles to help test and offer their feedback. Generally we've tried to release a "stable" release a few weeks after the test release. In this case I'm planning to /not/ do that. I'll explain. There are several key features that we want to continue on and get in/tested before we do release 1.4, so despite my earlier comments about timeframes, I think we need to wait for these. I think it's the right thing to do in terms of delivering a solid release with a lot of very nice features. See my earlier email about what else is already included. After we get these done we can do another test release, and hopefully the previous testing will mean we won't have to leave that in "test" stage so long. Those features are: -- Jasper's Advanced network management for ordering, bonding, and VLANs -- James Laska's ppc PXE support in addition to his already added support to making koan work with s390 and ppc -- Javier's Debian support patches (I want to test these myself... just so I can see them in action) (thumbs up to people starting with "J" this month, and everyone else who have added features -- couldn't do it without you!) In addition, the power management idea seems easy enough and very powerful, so we might as well do it. It gives us a big feature to talk about for 1.4 in addition to all of the above. We also want to close all the open defects, though I don't expect to be addressing many more of the open RFEs. Comments/questions? Sound ok? --Michael

1 0

(devel) bonding test results
by Vreman, Peter 13 Nov '08

13 Nov '08

Hi, I'm testing the bonding patches of the current devel tree and found some issues. The executed provisioning commands are: cobbler system edit --name=bcsia74 --interface=bond0 --bonding=master \ --bonding-opts="mode=active-backup miimon=100" --ip=10.227.128.204 \ --subnet=255.255.255.0 --gateway=10.227.128.254 --static=1 cobbler system edit --name=bcsia74 --interface=eth0 \ --mac=00:21:5A:AB:29:22 --bonding=slave --bonding-master=bond0 cobbler system edit --name=bcsia74 --interface=eth1 \ --mac=00:21:5a:ab:29:12 --bonding=slave --bonding-master=bond0 I found the following issues: - The WebUI can't be used. Bonding configurations are not saved. - In the WebUI can some parts be made dynamic? E.g. when Static is disabled that the IP address/netmask/gateway are hidden/disabled. And for bonding=slave that only enables bonding master field maybe even with a drop down box. - The new network code expects a MAC address for all NICs. I have about 100 nodes with each 6 NICs, that means 600 MAC addresses need to be added. Is there a way for auto-discovery? E.g. booting a live cd image and provising all detected NICs with a MAC address. Can the cloner live-cd be extended for such 'bare-metal' discovery? - The physical slave nics don't get an IP address assigned in dhcpd.conf host generic2 { hardware ethernet 00:21:5A:AB:29:22; } host generic1 { hardware ethernet 00:21:5a:ab:29:12; } - I found that eth1 is configured and not the expected eth0 that was used for the PXE boot. See below for the generated pre_install code. This might give problems with DHCP where the dhpcd is configured to send the PXE boot only for the first NIC. Maybe this can be solved with configuring a primary NIC? # Start bond0 # Found a slave for this interface: eth1 (00:21:5a:ab:29:12) # Configuring bond0 (00:21:5a:ab:29:12) if ifconfig | grep -i 00:21:5a:ab:29:12 then IFNAME=$(ifconfig | grep -i '00:21:5a:ab:29:12' | cut -d " " -f 1) echo "network --device=$IFNAME --bootproto=static --ip=10.227.128.204 --netmask=255.255.255.0 --gateway=10.227.128.254 --hostname=bcsia74.intinfra.com" >> /tmp/pre_install_network_config fi # Start eth1 # Skipping (slave-interface) # Start eth0 # Skipping (slave-interface) # Start pre_install_network_config generated code - In the postinstall there is a replacement done in modprobe.conf. This replacement might go wrong in case the eth0 and eth1 are swapped. The first sed will e.g. replace eth0->eth1. And the second sed will replace eth1->eth0. The end result is that both are eth0. The solution is to process the modprobe.conf in a single run. # Start eth1 IFNAME=$(ifconfig | grep -i '00:21:5a:ab:29:12' | cut -d ' ' -f 1) sed -i "s/$IFNAME/eth1/" /etc/modprobe.conf rm -f /etc/sysconfig/network-scripts/ifcfg-$IFNAME ... # End eth1 # Start eth0 IFNAME=$(ifconfig | grep -i '00:21:5A:AB:29:22' | cut -d ' ' -f 1) sed -i "s/$IFNAME/eth0/" /etc/modprobe.conf rm -f /etc/sysconfig/network-scripts/ifcfg-$IFNAME ... # End eth0 # End post_install_network_config generated code Regards, Peter This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

4 8

WebUI operations page
by Vreman, Peter 13 Nov '08

13 Nov '08

I think the Netboot Enable option is hidden too much between other settings in the edit systems page. The option has major impact on system behaviour if the nodes are always using PXE boot. An example of a situation that can happen. A user selects a profile and marks the checkbox for a node. Nothing happens at first. But a week later the node crashes with a kernel panic and reboots. Now the system will be redeployed. A solution might be to not only disable the PXE after deployment, but also change the profile assigned to the system. Enabling the netboot and assigning a profile is an operation and not a node configuration. Is it possible to create a operations page. In the operations page you can then do the actions like: - set active profile - enable netboot, with also a trigger that allows a script to be called that modifies bootorder at the node through ILO. - (optional) additional features like reboot automatic through ILO - Actions button like reboot Example layout: System Netboot Active Profile Profile Option Actions Node1 X Localboot Reboot Poweron Poweroff Node2 X Saveimage node2-20081113.img Reboot Poweron Poweroff Node3 RHEL4.6 webserver Reboot Poweron Poweroff Node4 X RHEL4.6 Reboot Poweron Poweroff Node5 X Loadimage node5-20081031.img Reboot Poweron Poweroff In the system edit page you can then select multiple profiles that are allowed for the node. Do you think this is a good idea? How hard is it to implement the parts: - WebUI with dropdown boxes - Add ILO support - Add (customizable) Actions to call a shell scripts Regards, Peter This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 3

(new thread) update-cobbler-from-func script
by Michael DeHaan 13 Nov '08

13 Nov '08

I opened a ticket to track this idea here: https://fedorahosted.org/cobbler/ticket/301 This would work really well with the Func integration already in Cobbler 1.3 https://fedorahosted.org/cobbler/wiki/FuncIntegration Setup would not be super-automagical, but would be pretty close. --Michael

1 0

Re: WebUI operations page
by Joseph Boyer Jr. 13 Nov '08

13 Nov '08

In reference to the ilo pieces we should have a look at the code for fence ilo for the cluster project. This will give the necessary bits to write ilo code for cobbler ------------------- Joseph Boyer Jr. Liquidnet Holdings Inc. Enterprise Technology Services Joseph.Boyer(a)liquidnet.com T: +1 646.660.8352 C: +1 646.284.8394 -----Original Message----- From: Michael DeHaan [mailto:mdehaan@redhat.com] Sent: Thursday, November 13, 2008 01:35 PM Eastern Standard Time To: cobbler mailing list Subject: Re: WebUI operations page Vreman, Peter - Acision wrote: > > I think the Netboot Enable option is hidden too much between other > settings in the edit systems page. The option has major impact on > system behaviour if the nodes are always using PXE boot. An example > of a situation that can happen. A user selects a profile and marks the > checkbox for a node. Nothing happens at first. But a week later the > node crashes with a kernel panic and reboots. Now the system will be > redeployed. > > > > A solution might be to not only disable the PXE after deployment, but > also change the profile assigned to the system. > I'm not sure if you're aware, but the pxe_just_once setting in /etc/cobbler/settings is designed to prevent this from happening. It toggles the netboot flag automatically after finishing installing the system. If you were, I thought it beared repeating for everyone else's context and in case they weren't aware of this. > > > > Enabling the netboot and assigning a profile is an operation and not a > node configuration. Is it possible to create a operations page. > > In the operations page you can then do the actions like: > > - set active profile > > - enable netboot, with also a trigger that allows a script to > be called that modifies bootorder at the node through ILO. > > - (optional) additional features like reboot automatic > through ILO > > - Actions button like reboot > > > > Example layout: > > > > System Netboot Active Profile Profile > Option Actions > > Node1 X > Localboot > Reboot Poweron Poweroff > > Node2 X Saveimage > node2-20081113.img Reboot Poweron Poweroff > > Node3 RHEL4.6 > webserver Reboot Poweron > Poweroff > > Node4 X > RHEL4.6 > Reboot Poweron Poweroff > > Node5 X Loadimage > node5-20081031.img Reboot Poweron Poweroff > > > > In the system edit page you can then select multiple profiles that are > allowed for the node. > > > > Do you think this is a good idea? How hard is it to implement the parts: > I think it's an excellent idea, and can be done by making modifications to the existing "list systems" page. > - WebUI with dropdown boxes > > - Add ILO support > There have been talks about doing this, though the one project to simplify the setup of the ILO bits wasn't ever created. Do you have ideas on what tools you would use to implement this and how configuration of the cobbler-system to power management tools would be handled? I believe the suggestions revolved around using the fence scripts from our cluster tools though those aren't available seperately IIRC. It could be done as simply as having a field for "poweron command" and "poweroff" command, couldn't it? Then we could enable those buttons if those fields were set. cobbler system list | grep lab3 | xargs -n1 --replace cobbler system edit --name={} --poweron-command="..." ??? Want to take a crack at adding this? I think if we do this we also want the following commands to work: cobbler system edit --name=foo --power=on --netboot-enabled=1 cobbler system edit --name=foo --power=off > - Add (customizable) Actions to call a shell scripts > Not sure what you mean by this last one, though something like the above may work well. > > > > Regards, > > Peter > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be > copied, disclosed to, retained or used by, any other party. If you are > not an intended recipient then please promptly delete this e-mail and > any attachment and all copies and inform the sender. Thank you. > ------------------------------------------------------------------------ > > _______________________________________________ > cobbler mailing list > cobbler(a)lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler

1 0

[PATCH] Makefile savestate path and prefix
by Vreman, Peter 13 Nov '08

13 Nov '08

A make devinstall saves the files in / instead of the /tmp/cobbler_settings. The reason is that the path and prefix environments are set within shell commands, but the save/restore commands use Makefile variables that unset and therefor empty. Attached patch makes the prefix and path (renamed to statepath) setting a Makefile variable. Regards, Peter This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

← Newer
1
...
4
5
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

cobbler November 2008