Hmm, I think there are a couple of different but sort-of related issues.

The first is the original thread: sharing pre/post scripts between kickstart 
profiles.  This is an area that lets spacewalk/satellite down.  I logged this 
as an RFE (SR #1783022) Nov 13, 2007.

The second is have a 'template' kickstart profile and being able to say, create 
a new kickstart profile based on the template but it tracks changes made in the 
template kickstart profile.  For example, any changes in the template are 
reflected in the kickstarts based on the template.  However, if you change 
something in the kickstart based on the template, then that thing that is 
changed stops tracking the template.

Does that make sense?

CC

________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Lars Jonsson [EMAIL 
PROTECTED]
Sent: Wednesday, 19 November 2008 5:56 PM
To: [email protected]
Subject: Re: [Spacewalk-devel] Kickstart script questions

I would like to see the same thing! a lot of customers are facing the same 
issue..
You don't want to have 15 different kickstart profiles to maintain.

I have a parametrized post script which will parse the /proc/cmdline. The 
custom options is added using syslinux menus.

see attachment.

Cheers,

Lars Jonsson
EMEA Global Professional Services
Red Hat AB
Kista Science Tower
SWEDEN

----- Original Message -----
From: "Colin C. Coe (Unix Engineer)" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, November 18, 2008 11:49:48 PM GMT +01:00 Amsterdam / Berlin / 
Bern / Rome / Stockholm / Vienna
Subject: [Spacewalk-devel] Kickstart script questions


Hi all

Are there any plans to enable sharing of kickstart pre/post scripts between 
different kickstart profiles?

ATM, virtually all my kickstarts have one pre, one non-chroot post and one 
post.  All pre scripts look a little like:
---
common_script() {
        wget -P /tmp http://sat.server/pub/build_scripts/pre/$1
        . /tmp/$@
        rm -f /tmp/$1
}

set -x

common_script monolithic.sh

disklayoutEL5Client
---

All non-chroot posts look like:
---
cp `awk '{ if ($1 ~ /%include/) { print $2}}' /tmp/ks.cfg` /tmp/ks-pre.log 
/tmp/ks.cfg /mnt/sysimage/root
---
(Hopefully I won't need this when Sat v5.3 comes out)

And all post scripts look a little like:
---
common_script() {
   wget -q -P /tmp http://sat.server/pub/build_scripts/post/$1
   . /tmp/$@
   rm -f /tmp/$1
}

set -x

common_script monolithic.sh \
    
--subscribe-software-channels=rhel-x86_64-client-5,wel-rhel5-client-x86_64,rhel-x86_64-client-supplementary-5,rhel-x86_64-client-workstation-5,rhn-tools-rhel-x86_64-client-5,rhel-x86_64-desktop-epel-5,dag-x86_64-desktop-5
 \
    
--join-config-channels=welgen_rhel5_x86_64_lws,welgen_rhel5_x86_64,welgen_rhel5,welgen_lws,welgen,welcommon
 \
    --additional-packages=samba,nbtscan,kchmviewer,kernel-devel
---

I'd really like to be able to share scripts between kickstarts as this would 
save me a lot of work.

Also, it used to be the case that if you had mulitple post scripts you couldn't 
control the order in which they ran.  Is this still the case?

Thanks

CC

NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.


_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel

NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.


_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to