I was just playing with something similar (APP/DB and PROD/TEST)
Using profile Names APP-TEST DB-PROD I used pattern tests in the
snippets to determine what should and shouldn't be included.
This let me keep one kickstart file for our typical systems.
--Patrick
An Example:
#import re
#set profilepatt= $re.compile(".*PROD.*")
#if $profilepatt.match($profile)
key --skip
#end if
On Tue, Nov 10, 2009 at 4:11 PM, brett lentz <wakko666(a)gmail.com> wrote:
On Tue, Nov 10, 2009 at 1:03 PM, Aaron Lippold
<lippold(a)gmail.com> wrote:
> Hello,
>
> I was wondering if anyone had suggestion and or lessons on building
> and deploying a "profile set" that has multiple systems / profiles. I
> would assume this would be scripting the API or a set of inherited
> sub-profiles. The driver / use case for this is a deployment that has
> three to four machines ( app, db, svn, directory ) that combine to
> make the total deployment. This is easy on a single profile, has
> anyone looked at the "multi-machine" profile case?
>
> Thanks,
>
> Aaron
The way we do it at $DAYJOB is to have a "base" package set that is a
snippet used across multiple profiles, then have puppet do the
role-specific configuration post-install.
---Brett.
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel