FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora/Linux Management Tools

 
 
LinkBack Thread Tools
 
Old 11-26-2007, 09:46 PM
Michael DeHaan
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

Tom Brown wrote:



Good deal.

I'd suggest writing a minimal script that calls the cobbler edit
command locally, and then runs koan on the remote system as:


koan --replace-self --server=bootserver.example.org (no arguments)

then reboots the box.


would there be any chance the functionality of using the contents of
kickstart_sys for rebuilding using koan rather than kickstart?


koan is designed to deploy what is specified in Cobbler. It's designed
around centralized management.


Alas things are not as simple as scripting a cobbler edit as once
deployed into the stack, these machines are basically application
stacks, then when and what they get rebuilt to is handled by another
process that is local to a box on the stack and so only has access to
koan. It seems to me that koan/cobbler has the info available to it,
ie kickstart_sys, however it seems to not make use of it?


That doesn't work because the kickstart_sys file without doing the
associated cobbler edit points to the /old/ cobbler profile, not the new
one. Once you issue the cobbler command to remap it, the kickstart
is then correct, and you can use koan with the --system flag (or leave
it off and let things be autodetected).


Really the easiest option here is to just use the profiles with DHCP.
Failing that, you should just issue the cobbler commands to remap
systems to new profiles.


We're not going to do client-side templating of kickstart files in koan
because we already do that Cobbler side, and also because to support
older distros (EL3), we can't use the same templating engine... which
adds way too much complexity, and it is also hard to explain why we'd
actually need that feature if we already have a cobbler command that
does the same thing


In conclusion ... (A) use profiles with DHCP, or (B) run cobbler edit
command before using koan. Those are the two suggestions.



thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 11-26-2007, 09:57 PM
Tom Brown
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

koan is designed to deploy what is specified in Cobbler. It's
designed around centralized management.


fair enough - can i ask then what is the intended purpose of
"--profile=PROFILE cobbler profile to install" as that would do exactly
as i want but as you state it does not handle the IP issues i have




Alas things are not as simple as scripting a cobbler edit as once
deployed into the stack, these machines are basically application
stacks, then when and what they get rebuilt to is handled by another
process that is local to a box on the stack and so only has access to
koan. It seems to me that koan/cobbler has the info available to it,
ie kickstart_sys, however it seems to not make use of it?


That doesn't work because the kickstart_sys file without doing the
associated cobbler edit points to the /old/ cobbler profile, not the
new one. Once you issue the cobbler command to remap it, the kickstart
is then correct, and you can use koan with the --system flag (or leave
it off and let things be autodetected).


Really the easiest option here is to just use the profiles with
DHCP. Failing that, you should just issue the cobbler commands to
remap systems to new profiles.




for me dhcp in production is not really an option. i can get away with
it for bare metal but alas not for rebuilds


We're not going to do client-side templating of kickstart files in
koan because we already do that Cobbler side, and also because to
support older distros (EL3), we can't use the same templating
engine... which
adds way too much complexity, and it is also hard to explain why we'd
actually need that feature if we already have a cobbler command that
does the same thing


In conclusion ... (A) use profiles with DHCP, or (B) run cobbler edit
command before using koan. Those are the two suggestions.


thanks for your advice regarding this issue - i'll see what i can come
up with.




_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 11-29-2007, 10:07 PM
Michael DeHaan
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

Tom Brown wrote:


for me dhcp in production is not really an option. i can get away with
it for bare metal but alas not for rebuilds


We're not going to do client-side templating of kickstart files in
koan because we already do that Cobbler side, and also because to
support older distros (EL3), we can't use the same templating
engine... which
adds way too much complexity, and it is also hard to explain why we'd
actually need that feature if we already have a cobbler command that
does the same thing


In conclusion ... (A) use profiles with DHCP, or (B) run cobbler
edit command before using koan. Those are the two suggestions.


thanks for your advice regarding this issue - i'll see what i can come
up with.




_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


Tom,

I've applied Al Tobey's --autonet patch to koan upstream.

This seems like it will fix your problem for profile based reinstalls,
because it will add in the IP info on the kernel command line based on
what you are currently using.


Might be worth checking out. You should be able to use koan 0.6.4 from
git with your existing Cobbler install.


--Michael


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 11-30-2007, 09:56 AM
Tom Brown
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

I've applied Al Tobey's --autonet patch to koan upstream.

This seems like it will fix your problem for profile based reinstalls,
because it will add in the IP info on the kernel command line based on
what you are currently using.


Might be worth checking out. You should be able to use koan 0.6.4
from git with your existing Cobbler install.




thanks for the effort here - alas it does not work for me as it makes
grub look like this


kernel /vmlinuz ro root=LABEL=/1 ksdevice=eth0 lang= kssendmac syslog=19
2.168.10.4:25150 text ks=file:ks.cfg ip=$ip_address netmask=$subnet
hostname=$ho

stname nameserver=$nameserver gateway=$gateway

So its not getting the values, its getting the info from the ks template
- Is there no way to get these values from the currently running OS ?


thanks

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 11-30-2007, 03:23 PM
Michael DeHaan
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

Tom Brown wrote:





I've applied Al Tobey's --autonet patch to koan upstream.

This seems like it will fix your problem for profile based
reinstalls, because it will add in the IP info on the kernel command
line based on what you are currently using.


Might be worth checking out. You should be able to use koan 0.6.4
from git with your existing Cobbler install.




thanks for the effort here - alas it does not work for me as it makes
grub look like this


kernel /vmlinuz ro root=LABEL=/1 ksdevice=eth0 lang= kssendmac syslog=19
2.168.10.4:25150 text ks=file:ks.cfg ip=$ip_address netmask=$subnet
hostname=$ho

stname nameserver=$nameserver gateway=$gateway

So its not getting the values, its getting the info from the ks
template - Is there no way to get these values from the currently
running OS ?




From the manpage for the new feature:

--autonet

"First, koan will download the kickstart configuration and check for a
network --bootproto=static method. If that fails and --replace-self has
been specified, koan will use the current system's network
configuration, as found using iproute2. "



What it looks like is it's finding the first thing (your template line),
and not going to iproute2. So you'll need to modify your kickstart to
only include the network line when you are doing per-system (and not
per-profile) installations. The question then remains (and this is
perhaps more suited for kickstart-list@redhat.com), if you have all the
network setup arguments on the kernel command line, do you still need
the entry in the kickstart file?


Here's what your template might look like (untested, see
https://hosted.fedoraproject.org/projects/cobbler/wiki/KickstartTemplating
for pointers)


#if $getVar("ip_address","none") != "none"
## this is a per-system kickstart, not a per-profile kickstart
network ... etc ... etc ...
#else
## possibly might need something here to build the network line in the kickstart based on kernel parameters
## using a hack in %pre, though I am not entirely sure. Hopefully Anaconda can just figure it out from kernel
## args automatically
#end if


Make sense? Sort of? It is a bit of a messy corner case but you're
really close.


--Michael





thanks

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 12-01-2007, 12:13 AM
"Al Tobey"
 
Default koan-0.6.3-3.el4.mrh - kix templating - network rebuilt issue

On Nov 30, 2007 2:56 AM, Tom Brown <tom@ng23.net> wrote:
>
> >
> >
> > I've applied Al Tobey's --autonet patch to koan upstream.
> >
> > This seems like it will fix your problem for profile based reinstalls,
> > because it will add in the IP info on the kernel command line based on
> > what you are currently using.
> >
> > Might be worth checking out. You should be able to use koan 0.6.4
> > from git with your existing Cobbler install.
> >
>
> thanks for the effort here - alas it does not work for me as it makes
> grub look like this
>
> kernel /vmlinuz ro root=LABEL=/1 ksdevice=eth0 lang= kssendmac syslog=19
> 2.168.10.4:25150 text ks=file:ks.cfg ip=$ip_address netmask=$subnet
> hostname=$ho
> stname nameserver=$nameserver gateway=$gateway

I would think that would cause anaconda to fail anyways.

In your template, try putting a check around the net config something like:

#if $varExists('ip_address')
network --bootproto=static ...
#end if

-Al

> So its not getting the values, its getting the info from the ks template
> - Is there no way to get these values from the currently running OS ?
>
> thanks
>
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 

Thread Tools




All times are GMT. The time now is 01:01 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org