resolv.conf.save ??

[Tom Brown]

what creates this file as i am trying to manipulate my resolv.conf with 
a snippet but after a while looking into why it seemed to not be working 
it seems that changes get wiped out by whatever creates resolv.conf.save -

I am doing manipulation at the very end of the ks post so i would have 
thought all cobbler internal stuff would have finished by then ?

thanks

[Michael DeHaan]

Tom Brown wrote:
>  what creates this file as i am trying to manipulate my resolv.conf
> with 
>  a snippet but after a while looking into why it seemed to not be working 
>  it seems that changes get wiped out by whatever creates resolv.conf.save -
>
>  I am doing manipulation at the very end of the ks post so i would have 
>  thought all cobbler internal stuff would have finished by then ?
>
>  thanks
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Most likely the network config snippets are doing this. Try manipulating 
it after that, further down in %post.

[Tom Brown]

>  Most likely the network config snippets are doing this. Try manipulating 
>  it after that, further down in %post.
>
>     
thats the thing - i cant find it within the .ks at all so i am not sure 
where it comes from. My stuff does its thing at the very end of the 
%post i.e

SNIPPET::set_nameserver
# Start final steps
$kickstart_done
# End final steps

so cant really go much further down the list

thanks

[James Cammarata]

On Wed, 25 Mar 2009 15:33:16 +0000, Tom Brown <tom(a)ng23.net&gt; wrote:
> >
> > Most likely the network config snippets are doing this. Try manipulating 
> > it after that, further down in %post.
> >
> >   
>  
>  thats the thing - i cant find it within the .ks at all so i am not sure 
>  where it comes from. My stuff does its thing at the very end of the 
>  %post i.e
>  
>  SNIPPET::set_nameserver
>  # Start final steps
>  $kickstart_done
>  # End final steps
>  
>  so cant really go much further down the list
>  
>  thanks 
Are you running a distribution that uses Network Manager?  That could be
the culprit.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Tom Brown]

>  Are you running a distribution that uses Network Manager?  That could
> be
>  the culprit.
>
>     
well its CentOS-5.2

# rpm -qf /etc/resolv.conf.save
file /etc/resolv.conf.save is not owned by any package

its not 'owned' by a package and neither is resolv.conf but i would not 
really expect it to be

i will try to remove network manager at install time to see if that has 
any impact

[Joseph Boyer Jr.]

They are a few things that change the /etc/resolv.conf

        1. network manager. -- you should not be installing this on severs or least turn
the service off
        2. if you are using dhcp, your dhcp server can configure you /etc/resolv.conf i.e.
does your /etc/dhcp.conf have the following:
                Option domain-name "xxx"
                Option domin-name servers xxxx, xxxxx
        3. avahi-dnsd - will rewrite your /etc/resolv.conf. you can turn avahi off unless
you need to talk to mac bonjour servers

Any hoo... I add a line to /etc/rc.local to rewrite my /etc/resolv.conf each time the
machine boots, thus ensuring that my boxes always have the proper resolver configuration.

Joseph Boyer Jr.
Liquidnet Holdings, Inc.
E joseph.boyer(a)liquidnet.com
T +1 646.660.8352
C +1 646.284.8394

-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:[e-mail]] On Behalf Of Tom Brown
Sent: Wednesday, March 25, 2009 11:19 AM
To: cobbler mailing list
Subject: resolv.conf.save ??

what creates this file as i am trying to manipulate my resolv.conf with
a snippet but after a while looking into why it seemed to not be working
it seems that changes get wiped out by whatever creates resolv.conf.save -

I am doing manipulation at the very end of the ks post so i would have
thought all cobbler internal stuff would have finished by then ?

thanks
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

[Tom Brown]

>  They are a few things that change the /etc/resolv.conf
>
>          1. network manager. -- you should not be installing this on severs or least turn
> the service off
>          2. if you are using dhcp, your dhcp server can configure you /etc/resolv.conf
> i.e. does your /etc/dhcp.conf have the following:
>                  Option domain-name "xxx"
>                  Option domin-name servers xxxx, xxxxx
>          3. avahi-dnsd - will rewrite your /etc/resolv.conf. you can turn avahi off unless
> you need to talk to mac bonjour servers
>
>  Any hoo... I add a line to /etc/rc.local to rewrite my /etc/resolv.conf each time the
> machine boots, thus ensuring that my boxes always have the proper resolver configuration.
>
>     
network manager is not used - it is not even installed, at least now

we are using static interfaces

avahi is not installed

its still being clouted by something and this one has me stuck - i dont 
want to start working around an issue without first figuring out what 
the issue is.

thanks

[Tom Brown]

>  network manager is not used - it is not even installed, at least now
>
>  we are using static interfaces
>
>  avahi is not installed
>
>  its still being clouted by something and this one has me stuck - i dont 
>  want to start working around an issue without first figuring out what 
>  the issue is.
>
>     
seems to be something dhclient related - i guess that even though the 
interfaces are static during PXE they are dhcp'd so it seem that this is 
somehow interfering with changing the resolv.conf but i would have 
thought that once the machine was up and installing dhcp would not be 
involved but it seems somehow to be.

[Joseph Boyer Jr.]

PXE requires dhcp. Thus the initial /etc/resolv.conf may be configured via dhcp, even with
static IPs. If you continue to you use dhcp, after the build is completed, than that is
source of the issue. FYI: You can configure the dhcp-client not to setup the
/etc/resolv.conf

Joseph Boyer Jr.
Liquidnet Holdings, Inc.
E joseph.boyer(a)liquidnet.com
T +1 646.660.8352
C +1 646.284.8394


-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:[e-mail]] On Behalf Of Tom Brown
Sent: Wednesday, March 25, 2009 1:33 PM
To: cobbler mailing list
Subject: Re: resolv.conf.save ??


>  network manager is not used - it is not even installed, at least now
>
>  we are using static interfaces
>
>  avahi is not installed
>
>  its still being clouted by something and this one has me stuck - i dont
>  want to start working around an issue without first figuring out what
>  the issue is.
>
>  
seems to be something dhclient related - i guess that even though the
interfaces are static during PXE they are dhcp'd so it seem that this is
somehow interfering with changing the resolv.conf but i would have
thought that once the machine was up and installing dhcp would not be
involved but it seems somehow to be.
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

[Tom Brown]

>  PXE requires dhcp. Thus the initial /etc/resolv.conf may be
> configured via dhcp, even with static IPs. If you continue to you use dhcp, after the
> build is completed, than that is source of the issue. FYI: You can configure the
> dhcp-client not to setup the /etc/resolv.conf
>     
i dont - once the build happens dhcp is not used

[Tom Brown]

> > PXE requires dhcp. Thus the initial /etc/resolv.conf may be 
> > configured via dhcp, even with static IPs. If you continue to you use 
> > dhcp, after the build is completed, than that is source of the issue. 
> > FYI: You can configure the dhcp-client not to setup the /etc/resolv.conf
> >   
>
>  i dont - once the build happens dhcp is not used 
in fact the nameservers in resolv.conf are the ones set by cobbler not 
the ones provided by dhcp

to try to explain my 'issue' - i am trying to set certain OS specific 
things based on which dc the machine is sitting in and i can work this 
out by its hostname. This stuff happens in the post of the ks so thats 
why i am trying to manipulate the nameservers like this rather than 
using the ones offered by cobbler.

which brings me onto another point which i am sure cobbler can solve but 
i am not sure of what 'flag' to use or similar but the issue is........

lets say i have 100 different types of machine that are fundamentally 
the _same_ bar the application they run. They would all have as near as 
damn it the same profile but rather than having 100 profiles with 100 
different kickstarts where the only difference is a single like in the 
packages section is there a more clever way to solve that issue?

if there is then i could also expand this to solve this issue of DNS as 
i am also needing to use a similar trick to solve mail relays, ntp 
servers etc etc

thanks

[James Cammarata]

On Wed, 25 Mar 2009 17:46:57 +0000, Tom Brown <tom(a)ng23.net&gt; wrote:
> > PXE requires dhcp. Thus the initial /etc/resolv.conf may be
> configured
> > via dhcp, even with static IPs. If you continue to you use dhcp, after
> > the build is completed, than that is source of the issue. FYI: You can
> > configure the dhcp-client not to setup the /etc/resolv.conf
> >   
>  
>  i dont - once the build happens dhcp is not used
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler 
Add "chattr +i /etc/resolv.conf" to your snippet, that will prevent the
file from getting changed after you write it :)

Just don't forget to "chattr -i" later.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Jeff Schroeder]

On Wed, Mar 25, 2009 at 11:13 AM, James Cammarata <jimi(a)sngx.net&gt; wrote:
>  On Wed, 25 Mar 2009 17:46:57 +0000, Tom Brown <tom(a)ng23.net&gt; wrote:
> >> PXE requires dhcp. Thus the initial /etc/resolv.conf may be configured
> >> via dhcp, even with static IPs. If you continue to you use dhcp, after
> >> the build is completed, than that is source of the issue. FYI: You can
> >> configure the dhcp-client not to setup the /etc/resolv.conf
> >>
> >
> > i dont - once the build happens dhcp is not used
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
>
>  Add "chattr +i /etc/resolv.conf" to your snippet, that will prevent the
>  file from getting changed after you write it :)
>
>  Just don't forget to "chattr -i" later. 
Don't do that. I've got a snippet that sets the right timezone based
on the "hostname" and put a trimmed down version on the wiki. You can
use the same logic and put in your code:
https://fedorahosted.org/cobbler/wiki/KickstartSnippets#ConfigureTimezone...

Basicly use cheetah templating to split on the hostname and recognize
the location you are in and then run some code.

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Tom Brown]

>  Don't do that. I've got a snippet that sets the right timezone based
>  on the "hostname" and put a trimmed down version on the wiki. You can
>  use the same logic and put in your code:
>  https://fedorahosted.org/cobbler/wiki/KickstartSnippets#ConfigureTimezone...
>
>  Basicly use cheetah templating to split on the hostname and recognize
>  the location you are in and then run some code.
>
>     
thanks for this - i achieve something similar at the moment using case 
but your way seems neater.

can i ask you to explain how in your example the system_name is set as i 
see it starts with

#if $getVar("system_name","") != ""

but where does 'system_name' come from ?

thanks

[Jeff Schroeder]

On Thu, Mar 26, 2009 at 4:26 AM, Tom Brown <tom(a)ng23.net&gt; wrote:
> >
> > Don't do that. I've got a snippet that sets the right timezone based
> > on the "hostname" and put a trimmed down version on the wiki. You can
> > use the same logic and put in your code:
> >
> >
> https://fedorahosted.org/cobbler/wiki/KickstartSnippets#ConfigureTimezone...
> >
> > Basicly use cheetah templating to split on the hostname and recognize
> > the location you are in and then run some code.
> >
> >
>
>  thanks for this - i achieve something similar at the moment using case but
>  your way seems neater.
>
>  can i ask you to explain how in your example the system_name is set as i see
>  it starts with
>
>  #if $getVar("system_name","") != ""
>
>  but where does 'system_name' come from ? 
'system_name' is a cobbler internal variable whenever you specify
something with a system_name.

For examples compare differences between "cobbler system dumpvars
--name foo" and "cobbler profile dumpvars --name foo-profile". Michael
wrapped one of his snippets in that if block and I didn't see why at
first. When you run "cobbler validateks" it will try to render the
kickstart without a system name. Obviously this usecase will break if
you don't wrap code depending on 'system_name'. This is purely my
understanding from writing that aforementioned snippet to magically
give our systems around the globe the right timezone depending on
their hostname.

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Michael DeHaan]

>  can i ask you to explain how in your example the system_name is set as i 
>  see it starts with
>
>  #if $getVar("system_name","") != ""
>
>  but where does 'system_name' come from ?
>
>  thanks
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Internals magic, basically.

The variable "$name" was confusing because if you were on a per-profile 
kickstart, it's different than a per-system kickstart.   So I added some 
extra code to create some extra variables, so whether I was doing a 
profile install or a system install, I always knew that $profile_name 
referenced the name of the profile.

"cobbler system dumpvars --name=foo" will show you all of them.

[Jeff Schroeder]

On Thu, Mar 26, 2009 at 6:22 AM, Michael DeHaan <mdehaan(a)redhat.com&gt; wrote:
> >
> > can i ask you to explain how in your example the system_name is set as i
> > see it starts with
> >
> > #if $getVar("system_name","") != ""
> >
> > but where does 'system_name' come from ?
> >
> > thanks
> > _______________________________________________
>
>  Internals magic, basically.
>
>  The variable "$name" was confusing because if you were on a per-profile
>  kickstart, it's different than a per-system kickstart.   So I added some
>  extra code to create some extra variables, so whether I was doing a profile
>  install or a system install, I always knew that $profile_name referenced the
>  name of the profile.
>
>  "cobbler system dumpvars --name=foo" will show you all of them. 
You hit send first :)

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Tom Brown]

>  On Thu, Mar 26, 2009 at 6:22 AM, Michael DeHaan
> <mdehaan(a)redhat.com&gt; wrote:
>    
> >> can i ask you to explain how in your example the system_name is set as i
> >> see it starts with
> >>
> >> #if $getVar("system_name","") != ""
> >>
> >> but where does 'system_name' come from ?
> >>
> >> thanks
> >> _______________________________________________
> >>       
> > Internals magic, basically.
> >
> > The variable "$name" was confusing because if you were on a per-profile
> > kickstart, it's different than a per-system kickstart.   So I added some
> > extra code to create some extra variables, so whether I was doing a profile
> > install or a system install, I always knew that $profile_name referenced the
> > name of the profile.
> >
> > "cobbler system dumpvars --name=foo" will show you all of them.
> >     
>
>     
this is very neat and it seems that i can use the variable 'hostname' as 
set in cobbler to do what i want.

could anyone offer me a slight hint on something that would basically do

if $getVar("hostname") = foo do something

if $getVar("hostname") = bar do something_else

and if $getVar("hostname") = baz do this final thing

i know this is basic stuff and i can do it with case but i think i need 
to adapt!

thanks

[Jeff Schroeder]

On Thu, Mar 26, 2009 at 9:30 AM, Tom Brown <tom(a)ng23.net&gt; wrote:
...
>  this is very neat and it seems that i can use the variable
> 'hostname' as set
>  in cobbler to do what i want.
>
>  could anyone offer me a slight hint on something that would basically do
>
>  if $getVar("hostname") = foo do something
>
>  if $getVar("hostname") = bar do something_else
>
>  and if $getVar("hostname") = baz do this final thing
>
>  i know this is basic stuff and i can do it with case but i think i need to
>  adapt!
>
>  thanks 
This looks like a pretty good example of an if --> elsif --> else
conditional in cheetah:
http://www.cheetahtemplate.org/docs/users_guide_html_multipage/flowContro...

Here is a cheesy way to test it in cobbler. Create a blank profile for
testing and assign an empty file as the ks.cfg. Then put your snippet
in that blank config and assign it to a system. Then you can do
"cobbler system getks --name snippettest" to render your snippet. That
should get you started in the right direction. If you make something
worth sharing please put it on the wiki in the snippets section.

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Michael DeHaan]

Tom Brown wrote:
> > On Thu, Mar 26, 2009 at 6:22 AM, Michael DeHaan <mdehaan(a)redhat.com&gt; 
> > wrote:
> >  
> >>> can i ask you to explain how in your example the system_name is set 
> >>> as i
> >>> see it starts with
> >>>
> >>> #if $getVar("system_name","") != ""
> >>>
> >>> but where does 'system_name' come from ?
> >>>
> >>> thanks
> >>> _______________________________________________
> >>>       
> >> Internals magic, basically.
> >>
> >> The variable "$name" was confusing because if you were on a
> per-profile
> >> kickstart, it's different than a per-system kickstart.   So I added 
> >> some
> >> extra code to create some extra variables, so whether I was doing a 
> >> profile
> >> install or a system install, I always knew that $profile_name 
> >> referenced the
> >> name of the profile.
> >>
> >> "cobbler system dumpvars --name=foo" will show you all of them.
> >>     
> >
> >   
>
>  this is very neat and it seems that i can use the variable 'hostname' 
>  as set in cobbler to do what i want.
>
>  could anyone offer me a slight hint on something that would basically do
>
>  if $getVar("hostname") = foo do something 
#set myhost = $getVar("hostname","")
#if $myhost == "foo"
   something
#elif $myhost == "bar"
   something something
#else
   yet another something
#end if

Generally if checks on the hostname are a sign you're doing something a 
little complicated.

The "Advanced Snippets" on the Wiki, for instance, allow you to override 
a snippet on a per-profile or per-system basis which can be pretty cool.


Plenty of good docs are also at:  http://cheetahtemplate.org/learn.html
>  if $getVar("hostname") = bar do something_else
>
>  and if $getVar("hostname") = baz do this final thing
>
>  i know this is basic stuff and i can do it with case but i think i 
>  need to adapt!
>
>  thanks

[Terry McIntyre]

A poster asked how to customize a hundred nearly-identical systems;
this is a lot like my environment.

We have a single kickstart template, and only the mountpoints differ
on a per-system basis.

The post section includes:

SNIPPET::config_mounts

Instead of a single snippets/config_mounts script, there is a
directory at /var/lib/cobbler/snippets/per_system/config_mounts ;
inside this directory is a script snippet for each system, with the same name.

More info on the cobbler wiki.

[Michael DeHaan]

Terry McIntyre wrote:
>  A poster asked how to customize a hundred nearly-identical systems;
>  this is a lot like my environment.
>
>  We have a single kickstart template, and only the mountpoints differ
>  on a per-system basis.
>
>  The post section includes:
>
>  SNIPPET::config_mounts
>
>  Instead of a single snippets/config_mounts script, there is a
>  directory at /var/lib/cobbler/snippets/per_system/config_mounts ;
>  inside this directory is a script snippet for each system, with the same name.
>
>  More info on the cobbler wiki.
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Using subprofiles and per_profile snippets may also work for you if you 
have a set of them that are quasi-indentical ...

(i..e webservers and webservers-pittsburgh and webservers-winston-salem 
and dbservers and dbservers-san-diego...)

[Jeff Schroeder]

On Thu, Mar 26, 2009 at 11:55 AM, Michael DeHaan <mdehaan(a)redhat.com&gt; wrote:
>  Terry McIntyre wrote:
> > A poster asked how to customize a hundred nearly-identical systems;
> > this is a lot like my environment.
> >
> > We have a single kickstart template, and only the mountpoints differ
> > on a per-system basis.
> >
> > The post section includes:
> >
> > SNIPPET::config_mounts
> >
> > Instead of a single snippets/config_mounts script, there is a
> > directory at /var/lib/cobbler/snippets/per_system/config_mounts ;
> > inside this directory is a script snippet for each system, with the same name.
> >
> > More info on the cobbler wiki.
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >
>
>  Using subprofiles and per_profile snippets may also work for you if you
>  have a set of them that are quasi-indentical ...
>
>  (i..e webservers and webservers-pittsburgh and webservers-winston-salem
>  and dbservers and dbservers-san-diego...) 
I'm failing to see how you couldn't replace 50 snippets (one per host)
with 1 cheetah template and some builtin hostname logic like the
timezone example I posted showed.

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Michael DeHaan]

Jeff Schroeder wrote:
>  On Thu, Mar 26, 2009 at 11:55 AM, Michael DeHaan
> <mdehaan(a)redhat.com&gt; wrote:
>    
> > Terry McIntyre wrote:
> >     
> >> A poster asked how to customize a hundred nearly-identical systems;
> >> this is a lot like my environment.
> >>
> >> We have a single kickstart template, and only the mountpoints differ
> >> on a per-system basis.
> >>
> >> The post section includes:
> >>
> >> SNIPPET::config_mounts
> >>
> >> Instead of a single snippets/config_mounts script, there is a
> >> directory at /var/lib/cobbler/snippets/per_system/config_mounts ;
> >> inside this directory is a script snippet for each system, with the same name.
> >>
> >> More info on the cobbler wiki.
> >> _______________________________________________
> >> cobbler mailing list
> >> cobbler(a)lists.fedorahosted.org
> >> https://fedorahosted.org/mailman/listinfo/cobbler
> >>
> >>       
> > Using subprofiles and per_profile snippets may also work for you if you
> > have a set of them that are quasi-indentical ...
> >
> > (i..e webservers and webservers-pittsburgh and webservers-winston-salem
> > and dbservers and dbservers-san-diego...)
> >     
>
>  I'm failing to see how you couldn't replace 50 snippets (one per host)
>  with 1 cheetah template and some builtin hostname logic like the
>  timezone example I posted showed.
>
>     
Indeed.

Snippets are a very large hammer.

--ksmeta can work magic.

[Tom Brown]

Michael DeHaan wrote:
>  Tom Brown wrote:
> >
> >> On Thu, Mar 26, 2009 at 6:22 AM, Michael DeHaan <mdehaan(a)redhat.com&gt; 
> >> wrote:
> >>  
> >>>> can i ask you to explain how in your example the system_name is 
> >>>> set as i
> >>>> see it starts with
> >>>>
> >>>> #if $getVar("system_name","") != ""
> >>>>
> >>>> but where does 'system_name' come from ?
> >>>>
> >>>> thanks
> >>>> _______________________________________________
> >>>>       
> >>> Internals magic, basically.
> >>>
> >>> The variable "$name" was confusing because if you were on a 
> >>> per-profile
> >>> kickstart, it's different than a per-system kickstart.   So I added 
> >>> some
> >>> extra code to create some extra variables, so whether I was doing a 
> >>> profile
> >>> install or a system install, I always knew that $profile_name 
> >>> referenced the
> >>> name of the profile.
> >>>
> >>> "cobbler system dumpvars --name=foo" will show you all of them.
> >>>     
> >>
> >>   
> >
> > this is very neat and it seems that i can use the variable 'hostname' 
> > as set in cobbler to do what i want.
> >
> > could anyone offer me a slight hint on something that would basically do
> >
> > if $getVar("hostname") = foo do something
>
>  #set myhost = $getVar("hostname","")
>  #if $myhost == "foo"
>    something
>  #elif $myhost == "bar"
>    something something
>  #else
>    yet another something
>  #end if
>
>  Generally if checks on the hostname are a sign you're doing something 
>  a little complicated.
>
>  The "Advanced Snippets" on the Wiki, for instance, allow you to 
>  override a snippet on a per-profile or per-system basis which can be 
>  pretty cool.
>
>
>  Plenty of good docs are also at:  http://cheetahtemplate.org/learn.html 

thanks both - i will try this out and post questions as i get them

[Tom Brown]

> > #set myhost = $getVar("hostname","")
> > #if $myhost == "foo"
> >   something
> > #elif $myhost == "bar"
> >   something something
> > #else
> >   yet another something
> > #end if
> >
> > Generally if checks on the hostname are a sign you're doing something 
> > a little complicated.
> >
> > The "Advanced Snippets" on the Wiki, for instance, allow you to 
> > override a snippet on a per-profile or per-system basis which can be 
> > pretty cool.
> >
> >
> > Plenty of good docs are also at:  http://cheetahtemplate.org/learn.html
> >     
>
>     
how can i cascade this more so that i have perhaps 5 or even 10 if 
statements ? ie if myhost does not match one of the 10 given then dont 
do anything ?

#set myloc = $getVar("hostname","")split('.')[2]
 #if $myloc == "foo"
echo 'relayhost         = mail.foo' >> /etc/postfix/main.cf;
 #elif $myloc == "bar"
echo 'relayhost         = mail.bar' >> /etc/postfix/main.cf;
 #elif $myloc == "baz"
echo 'relayhost         = mail.baz' >> /etc/postfix/main.cf;
 #else $myloc == "more"
echo 'relayhost         = mail.more' >> /etc/postfix/main.cf;
 #end if

etc etc ??

thanks

[Jeff Schroeder]

On Fri, Mar 27, 2009 at 9:26 AM, Tom Brown <tom(a)ng23.net&gt; wrote:
>  how can i cascade this more so that i have perhaps 5 or even 10 if
>  statements ? ie if myhost does not match one of the 10 given then dont do
>  anything ?
>
>  #set myloc = $getVar("hostname","")split('.')[2]
>  #if $myloc == "foo"
>  echo 'relayhost         = mail.foo' >> /etc/postfix/main.cf;
>  #elif $myloc == "bar"
>  echo 'relayhost         = mail.bar' >> /etc/postfix/main.cf;
>  #elif $myloc == "baz"
>  echo 'relayhost         = mail.baz' >> /etc/postfix/main.cf;
>  #else $myloc == "more"
>  echo 'relayhost         = mail.more' >> /etc/postfix/main.cf;
>  #end if
>
>  etc etc ?? 
Thats overkill for what it looks like you're trying to do. Here is a
snippet that
does what it looks like you're trying to do:

================ put this in /var/lib/cobbler/snippets/relay_host ===
#if $getVar("system_name","") != ""
    #set hostname = $getVar('system_name').split('.')
    #import re
    ## If system_name is server1.foo: hostname[0] == server1 and
hostname[1] = foo
    #set location = re.match('^([a-z]|[0-9])+', $hostname[1].lower()).group()
    #set relayhost = "mail." + $location
    #if $location == "foo"
        #set relayhost = "mail2.foo"
    #elif $location == "bar"
        #set relayhost = "evil.admin.workstation"
    #end if
echo 'relayhost = $relayhost" >> /etc/postfix/main.cf
#end if
=====================================================

I made a profile named test with a kickstart only including the line
below. Put that snippet line under your %post in the kickstart
template.
$SNIPPET('relay_host')

So this allows you to set explicit relay hosts for locations named foo
or bar and sets mail.$location for everything else.

root@cobbler1: snippets # cobbler system getks --name server1.foo
echo 'relayhost = mail2.foo" >> /etc/postfix/main.cf

root@cobbler1: snippets # cobbler system getks --name server1.bar
echo 'relayhost = evil.admin.workstation" >> /etc/postfix/main.cf

root@cobbler1: snippets # cobbler system getks --name server1.office
echo 'relayhost = mail.office" >> /etc/postfix/main.cf

Like I said earlier, by learning a bit of cheetah/python you can make
this much more concise. If you have a different hostname you'll need
to change the regex on the line that sets "location". Read the docs
and then ask more questions =)

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Tom Brown]

>  Thats overkill for what it looks like you're trying to do. Here
> is a
>  snippet that
>  does what it looks like you're trying to do:
>
>  ================ put this in /var/lib/cobbler/snippets/relay_host ===
>  #if $getVar("system_name","") != ""
>      #set hostname = $getVar('system_name').split('.')
>      #import re
>      ## If system_name is server1.foo: hostname[0] == server1 and
>  hostname[1] = foo
>      #set location = re.match('^([a-z]|[0-9])+', $hostname[1].lower()).group()
>      #set relayhost = "mail." + $location
>      #if $location == "foo"
>          #set relayhost = "mail2.foo"
>      #elif $location == "bar"
>          #set relayhost = "evil.admin.workstation"
>      #end if
>  echo 'relayhost = $relayhost" >> /etc/postfix/main.cf
>  #end if
>  =====================================================
>
>  I made a profile named test with a kickstart only including the line
>  below. Put that snippet line under your %post in the kickstart
>  template.
>  $SNIPPET('relay_host')
>
>  So this allows you to set explicit relay hosts for locations named foo
>  or bar and sets mail.$location for everything else.
>
>  root@cobbler1: snippets # cobbler system getks --name server1.foo
>  echo 'relayhost = mail2.foo" >> /etc/postfix/main.cf
>
>  root@cobbler1: snippets # cobbler system getks --name server1.bar
>  echo 'relayhost = evil.admin.workstation" >> /etc/postfix/main.cf
>
>  root@cobbler1: snippets # cobbler system getks --name server1.office
>  echo 'relayhost = mail.office" >> /etc/postfix/main.cf
>
>  Like I said earlier, by learning a bit of cheetah/python you can make
>  this much more concise. If you have a different hostname you'll need
>  to change the regex on the line that sets "location". Read the docs
>  and then ask more questions =)
>
>     
thanks for this - for me hostname is good to use as thats actually the 
FQDN and from that i can work out the DC the box is in. At the moment i 
have to worry about 6 DC's but this is likely to increase and i just 
want common ks's and snippets between them. I take the first parameter 
of the hostname to work out the box role and from that can work out what 
packages to install, again all by using a common kickstart and snippet set.

i am getting to grips with this slowly but alas its not coming super 
quick but getting there one bit at a time.

thanks