cobbler November 2008

cobbler@lists.fedorahosted.org

41 participants
119 discussions

LOGVOL --grow Seems to Be Broken
by William J. Dennison 04 Nov '08

04 Nov '08

The Kickstart documentation located here (http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Gu…) specifically notes that you can use "--grow" with a "logvol" parameter. When I do this the RHEL5 installation blows up. Is this an issue with Cobbler, Kickstart, RHEL 5 limitations, etc.? Below is my partitioning area in my kickstart file. -------------------------------------------------------------------------------------------------------------------- clearpart --all --initlabel partition /boot --size=1000 --ondisk=sda --asprimary --fstype=ext3 partition pv.01 --size=22000 --ondisk=sda --asprimary partition pv.02 --size=1024 --grow --ondisk=sda --asprimary volgroup vg_system pv.01 volgroup vg_data pv.02 logvol / --vgname=vg_system --size=2000 --name=lv_root --fstype=ext3 logvol /swap --vgname=vg_system --size=4000 --name=lv_swap --fstype=swap logvol /usr --vgname=vg_system --size=4000 --name=lv_usr --fstype=ext3 logvol /var --vgname=vg_system --size=2000 --name=lv_var --fstype=ext3 logvol /var_log --vgname=vg_system --size=2000 --name=lv_var_log --fstype=ext3 logvol /var_log_audit --vgname=vg_system --size=2000 --name=lv_var_log_audit -- fstype=ext3 logvol /var/tmp --vgname=vg_system --size=2000 --name=lv_var_tmp --fstype=ext3 logvol /tmp --vgname=vg_system --size=2000 --name=lv_tmp --fstype=ext3 logvol /opt --vgname=vg_system --size=1000 --name=lv_opt --fstype=ext3 logvol /home --vgname=vg_data --size=10000 --name=lv_home --fstype=ext3 logvol /opt/store/incomming_data --vgname=vg_data --size=1000 --name=lv_incom ming_data --fstype=ext3 logvol /opt/store/saved_data --vgname=vg_data --size=1000 --name=lv_saved_data --fstype=ext3 logvol /opt/store/upload_data --vgname=vg_data --size=1000 --name=lv_upload_data --fstype=ext3 logvol /opt/store/export_data --vgname=vg_data --size=1000 --name=lv_export_data --fstype=ext3 logvol /opt/store/webserver --vgname=vg_data --size=1000 --name=lv_appserver --fstype=ext3 logvol /opt/store/dbserver --vgname=vg_data --size=1000 --name=lv_dbserver --fstype=ext3 logvol /opt/store/virtual_machines --vgname=vg_data --size=1 --grow --name=lv_virtual_machines --fstype=ext3 ---------------------------------------------------------------------------------------------------------------------------------------------------------------- If I remove the --grow from "virtual_machines", all works fine, if I leave it in the Anaconda load blows up. When I run an interactive install, I notice that the --grow feature is not allowed on logvols. Does the logvol RED HAT documentation have to be edited? -- William J. Dennison Principal Consultant SRA International Inc. - RABA Center 8830 Stanford Blvd, Suite 205 Columbia, Maryland 21045 Phone: (410) 715-9399 x2351 Mobile: (410) 218-5866 Email: william_dennison(a)sra.com Email2: wjdennison(a)gmail.com Email3: wjdennison(a)cablespeed.com Jabber: wjdennison(a)jabber.org AIM: dennisonwjonly GTalk: wjdennison(a)gmail.com

3 10

FYI: reposync_flags
by Michael DeHaan 04 Nov '08

04 Nov '08

By default there is reposync_flags value of "-l" in /var/lib/cobbler/settings. If you encounter problems using reposync you should remove this parameter from settings. In the future, we may include some sort of basic check for this -- as it /is/ needed by newer versions of yum in order to enable plugins. We could do this in a couple of ways, but most likely it would just be done in cobbler check, comparing the values in reposync_flags against what is provided by yum's --help. It's a minor problem, but I wanted to mention it. --Michael

1 0

VMWare / Cobbler Work flow
by Aaron Lippold 03 Nov '08

03 Nov '08

Hello, I was hoping some of the folks working the VMWare Cobbler integration could chat a little on the general work flow for creating VMWare target profiles and how a development team would collaborate on developing them. I have a team now working to develop a set of profiles targeted at VMWare as the host and was hoping the list could help just start the team. The wiki seems a little sparse on what is supported, how to utilize what is supported and what the development road map is. Thanks, Aaron

4 5

(devel) Higher level Cobbler XMLRPC bindings
by Michael DeHaan 03 Nov '08

03 Nov '08

Currently Daryl Pierce has rubygem-cobbler (written originally for oVirt), whose code lives in contrib/ruby. For Spacewalk, they have a higher level remote Java binding that is going to live in contrib/java (written for Spacewalk). Both of the above projects wanted a higher level API that abstracted away some of the underlying XMLRPC calls so remote cobbler access felt more like a local object. Obviously we already have a remote Python API as Cobbler Web and Koan have been using it for a long time, but is a higher level Python binding something anyone would be interested in? I think I'm ok with the current API if everyone else is, though if this is something someone is interested in, perhaps this would be an interesting feature for someone to take on. I also know of at least one or two PHP projects using the Cobbler XMLRPC interface, so if you folks would like to share those bindings with everyone else (if you've written any), we have room for them in git. --Michael

1 0

Thoughts on Windows Deployment continued
by Jeroen van Meeuwen 03 Nov '08

03 Nov '08

Knowingly cloning the topic from another thread from some time ago, I wanted you to know I've put up ris-linux for review: https://bugzilla.redhat.com/show_bug.cgi?id=469052 This has been working great for me, and I might have a chance at writing up how to (manually) proceed in a consistent, reproducible manner, possibly considering the routines in python as I go along. Anyone interested in collaborating (on the cobbler wiki)? Kind regards, Jeroen van Meeuwen -kanarip

2 1

1.2.7 is in Fedora, not 1.2.8, you'll want 1.2.8
by Michael DeHaan 02 Nov '08

02 Nov '08

Apparently the Fedora updates system has pushed Cobbler packages out of order. https://fedorahosted.org/bodhi/ticket/260#preview So, as I submitted 1.2.8 as an important fix on top of 1.2.7, 1.2.7 is still in there. If you are using Fedora, be sure to install 1.2.8 from http://people.fedoraproject.org/~mdehaan/files/cobbler/ rpmbuild --rebuild *.src.rpm rpm -Uvh /usr/src/redhat/... 1.2.7 is the version that didn't read the settings file, which is something we obviously don't want happening. I'll see if I can get the Fedora updates sorted out in the meantime. --Michael

1 0

Quick question on dynamic loading of authn_spacewalk
by Partha Aji 02 Nov '08

02 Nov '08

I am a bit puzzled on why authn_spacewalk is part of the cobbler upstream. Shouldn't it be part of spacewalk project upstream ? Is the problem just that there is no way to tell cobbler to dynamically load modules outside its realm ?? I am just concerned that every time we find a bug in authn_spacewalk.py its just going to take a lot of time to submit to cobbler and have them review it. This also requires cobbler reviewer to be aware of how authentication is done on spacewalk and looks unnecessary to me.. Ideally I 'd like to be as follows. In modules.conf [authentication] module = authn_spacewalk or [authentication] module = foo.authn_spacewalk The cobbler project should just assume authn_spacewalk.py exists somewhere in the python path and move on.. If this functionality is there already in cobbler I think spacewalk should be taking advantage of that. Partha

2 1

Manipulate yum repo files in %post
by Robin Bowes 01 Nov '08

01 Nov '08

Hi, I'd like to manipulate yum repo files in the %post section of my kickstarts, specifically to disable repos that are being provided through local mirrors. I've knocked together some python code that does this: http://robinbowes.com/article.php/20081026162228424 Sample usage: initool --file /etc/yum.repos.d/epel.repo --section epel --option enabled=0 initool --file /etc/yum.repos.d/epel.repo --section epel --del priority My question: what's the best way to make this available to a kickstart? Is there anything cobbler can do, or do I need to do something like: echo > /tmp/initool << \EOF # script goes here ... EOF chmod +x /tmp/initool R.

8 20

suse10 patch
by Shuichi Ihara 01 Nov '08

01 Nov '08

Hi, I've created a patch to use cobbler on suse10 server. I would like to share this patch. I haven't tested all functions of cobbler yet, but the basic functions that are start/stop, distro/profile/system, dhcpd management, provisioning to clients and GUI interface worked well. Some lines in this patch might not be smart and need more investigations, but it would be good start as initial patch :) Thanks -Ihara diff --git a/cobbler.spec b/cobbler.spec index fe79c93..d1e9e94 100644 --- a/cobbler.spec +++ b/cobbler.spec @@ -8,17 +8,25 @@ Source0: %{name}-%{version}.tar.gz License: GPLv2+ Group: Applications/System Requires: python >= 2.3 +%if 0%{?suse_version} >= 1000 +Requires: apache2 +Requires: apache2-mod_python +Requires: tftp +%else Requires: httpd Requires: tftp-server +Requires: mod_python +%endif Requires: python-devel Requires: createrepo -Requires: mod_python Requires: python-cheetah Requires: rsync Requires(post): /sbin/chkconfig Requires(preun): /sbin/chkconfig Requires(preun): /sbin/service +%if 0%{?suse_version} < 0 BuildRequires: redhat-rpm-config +%endif BuildRequires: python-devel BuildRequires: python-cheetah %if 0%{?fedora} >= 8 @@ -53,7 +61,10 @@ applications. %install test "x$RPM_BUILD_ROOT" != "x" && rm -rf $RPM_BUILD_ROOT -%{__python} setup.py install --optimize=1 --root=$RPM_BUILD_ROOT +%if 0%{?suse_version} >= 1000 +PREFIX="--prefix=/usr" +%endif +%{__python} setup.py install --optimize=1 --root=$RPM_BUILD_ROOT $PREFIX %post if [ -e /var/lib/cobbler/distros ]; then @@ -150,8 +161,13 @@ test "x$RPM_BUILD_ROOT" != "x" && rm -rf $RPM_BUILD_ROOT %{python_sitelib}/cobbler/webui/*.py* %{_mandir}/man1/cobbler.1.gz /etc/init.d/cobblerd +%if 0%{?suse_version} >= 1000 +%config(noreplace) /etc/apache2/conf.d/cobbler.conf +%config(noreplace) /etc/apache2/conf.d/cobbler_svc.conf +%else %config(noreplace) /etc/httpd/conf.d/cobbler.conf %config(noreplace) /etc/httpd/conf.d/cobbler_svc.conf +%endif %dir /var/log/cobbler/syslog %defattr(755,root,root) diff --git a/cobbler/utils.py b/cobbler/utils.py index c6e5889..61137ef 100644 --- a/cobbler/utils.py +++ b/cobbler/utils.py @@ -726,6 +726,8 @@ def check_dist(): """ if os.path.exists("/etc/debian_version"): return "debian" + elif os.path.exists("/etc/SuSE-release"): + return "suse" else: # valid for Fedora and all Red Hat / Fedora derivatives return "redhat" @@ -761,6 +763,15 @@ def os_release(): rest = parts[1] make = "debian" return (make, float(version), rest) + elif check_dist() == "suse": + fd = open("/etc/SuSE-release") + for line in fd.read().split("\n"): + if line.find("VERSION") != -1: + version = line.replace("VERSION = ","") + if line.find("PATCHLEVEL") != -1: + rest = line.replace("PATCHLEVEL = ","") + make = "suse" + return (make, float(version), rest) else: return ("unknown",0) diff --git a/config/cobblerd b/config/cobblerd index 7d6d571..cf97f4d 100755 --- a/config/cobblerd +++ b/config/cobblerd @@ -26,10 +26,13 @@ [ -x /usr/bin/cobblerd ] || exit 0 DEBIAN_VERSION=/etc/debian_version +SUSE_RELEASE=/etc/SuSE-release # Source function library. if [ -e $DEBIAN_VERSION ]; then . /etc/init.d/functions +elif [ -f $SUSE_RELEASE -a -r /etc/rc.status ]; then + . /etc/rc.status else . /etc/rc.d/init.d/functions fi @@ -47,7 +50,12 @@ RETVAL=0 start() { echo -n $"Starting cobbler daemon: " - daemon --check $SERVICE $PROCESS --daemon $CONFIG_ARGS + if [ -e $SUSE_RELEASE ]; then + startproc -f -p /var/run/$SERVICE.pid /usr/bin/cobblerd $CONFIG_ARGS + rc_status -v + else + daemon --check $SERVICE $PROCESS --daemon $CONFIG_ARGS + fi RETVAL=$? echo [ $RETVAL -eq 0 ] && touch $LOCKFILE @@ -56,7 +64,12 @@ start() { stop() { echo -n $"Stopping cobbler daemon: " - killproc $PROCESS + if [ -e $SUSE_RELEASE ]; then + killproc -TERM /usr/bin/cobblerd + rc_status -v + else + killproc $PROCESS + fi RETVAL=$? echo if [ $RETVAL -eq 0 ]; then @@ -76,8 +89,14 @@ case "$1" in $1 ;; status) - status $PROCESS - RETVAL=$? + if [ -e $SUSE_RELEASE ]; then + echo -n "Checking for service cobblerd " + checkproc /usr/bin/cobblerd + rc_status -v + else + status $PROCESS + RETVAL=$? + fi ;; condrestart) [ -f $LOCKFILE ] && restart || : diff --git a/setup.py b/setup.py index a08c554..d6ad253 100644 --- a/setup.py +++ b/setup.py @@ -39,7 +39,10 @@ if __name__ == "__main__": backpath = "/var/lib/cobbler/backup/" trigpath = "/var/lib/cobbler/triggers/" etcpath = "/etc/cobbler/" - wwwconf = "/etc/httpd/conf.d/" + if os.path.exists("/etc/SuSE-release"): + wwwconf = "/etc/apache2/conf.d/" + else: + wwwconf = "/etc/httpd/conf.d/" wwwpath = "/var/www/cobbler/" wwwcon = "/var/www/cobbler/webui/" initpath = "/etc/init.d/"

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

cobbler November 2008