|
|
| static network configuration ask |
|
2007-08-30 16:02:50 |
|
Is there an option that will allow me to automate everything in kickstart except just the network portion so that I can have the same kickstart config for a bunch of clustered hosts but input the network information myself?
The reason I ask is because I would like to automate a lot of other stuff in %post ; or on first boot but need networking to be set up properly by the time that stuff runs or it will screw all of that up.
Thanks in advance
Kit Stube
|
| Re: static network configuration ask |
 
United States |
2007-08-30 16:05:00 |
Check out http://cobbler.et.redhat
.com It's made our life here tons easier.
Ben
Kit Stube wrote:
> Is there an option that will allow me to automate
everything in
> kickstart except just the network portion so that I can
have the same
> kickstart config for a bunch of clustered hosts but
input the network
> information myself?
>
> The reason I ask is because I would like to automate a
lot of other
> stuff in %post or on first boot but need networking to
be set up
> properly by the time that stuff runs or it will screw
all of that up.
>
> Thanks in advance
> Kit Stube
>
>
>
------------------------------------------------------------
------------
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
|
| RE: static network configuration ask |
United States |
2007-08-30 16:23:26 |
|
| If you can use DHCP to assign the network address, even for
just the first boot, that makes life the easiest. Otherwise, you can
create a kickstart file that simply takes the values entered on the boot: line
and creates a static network entry for them in %pre that is then included in the
command section.
Search
the archives and you will find lots of references to both of the
above.
Chip
Is there an option that will allow me to automate everything in
kickstart except just the network portion so that I can have the same kickstart
config for a bunch of clustered hosts but input the network information
myself?
The reason I ask is because I would like to automate
a lot of other stuff in %post ; or on first boot but need networking to be
set up properly by the time that stuff runs or it will screw all of that
up.
Thanks in advance
Kit Stube
|
| Re: static network configuration ask |
 
Spain |
2007-08-30 16:30:26 |
Hi
- Just don't fill it and you'll get prompted for it
- Send parameters on command line, process
/proc/commandline, and
write "semi-automatically" the network
configuration files
Regards
Pablo
--
Pablo Iranzo Gómez
(http://Alufis35.uv.es/
~iranzo/)
(PGPKey Available on http://www.uv.es
/~iranzop/PGPKey.pgp)
--
Postulado de Boling sobre la Ley de Murphy:
Si se encuentra bien, no se preocupe. Se le pasará
On Thu, 30 Aug 2007, Kit Stube wrote:
> Is there an option that will allow me to automate
everything in kickstart
> except just the network portion so that I can have the
same kickstart config
> for a bunch of clustered hosts but input the network
information myself?
>
> The reason I ask is because I would like to automate a
lot of other stuff in
> %post or on first boot but need networking to be set
up properly by the
> time that stuff runs or it will screw all of that up.
>
> Thanks in advance
> Kit Stube
>
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
|
| Re: static network configuration ask |
|
2007-08-30 16:38:21 |
|
Cobbler looks cool. Kinda like a front end for pxelinux and isc dhcpd? The problem we have is we don't want to have to look up the mac address for a host in order to configure it. Cobbler seems to rely on that.
Currently we have our dhcp server on an install network dump anyone that netboots on that network to a default pxelinux menu. ; That default menu allows a person to chose an os to install. Chosing one kicks them into one of several different default kickstart files. If I could get kickstart to ask for static network information like it would if I was installing from CD, I would be done.
On 8/30/07, Riggs, Ben < rigg0022umn.edu">rigg0022umn.edu> wrote:
Check out http://cobbler.et.redhat.com It's made our life here tons easier.
Ben
Kit Stube wrote:
>; Is there an option that will allow me to automate everything in
> kickstart except just the network portion so that I can have the same
> kickstart config for a bunch of clustered hosts but input the network
> information myself?
>
> The reason I ask is because I would like to automate a lot of other
> stuff in %post ; or on first boot but need networking to be set up
> properly by the time that stuff runs or it will screw all of that up.
>
> Thanks in advance
> Kit Stube
>
>
>; ------------------------------------------------------------------------
>;
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com">
Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com">Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
| Re: static network configuration ask |
United States |
2007-08-30 16:45:37 |
I'm here reviewing my kickstart file because I think the
answer is
much simpler than suggestions so far, and I'm wondering if
I'm
forgetting something. I don't think so. This is the
network line in
the kickstart file:
network --bootproto=static
Then don't wait for anaconda to prompt for parameters, just
enter them
at the 'boot:' prompt:
boot: ip=blah gateway=blah netmask=blah dns=blah
I don't think it's necessary to do any processing of
/proc/cmdline or
includes etc, this is it.
-Ed
Kit Stube wrote:
> Is there an option that will allow me to automate
everything in kickstart
> except just the network portion so that I can have the
same kickstart config
> for a bunch of clustered hosts but input the network
information myself?
>
> The reason I ask is because I would like to automate a
lot of other stuff in
> %post or on first boot but need networking to be set
up properly by the
> time that stuff runs or it will screw all of that up.
>
> Thanks in advance
> Kit Stube
>
>
>
>
------------------------------------------------------------
------------
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
|
| Re: static network configuration ask |
United States |
2007-08-30 16:55:48 |
> boot: ip=blah gateway=blah netmask=blah dns=blah
This is not quite complete. And actually, we make a custom
boot cd,
with multiple targets that contain the common parameters, so
all
that's needed at the boot prompt is target, ip and gateway.
You'll
probably need at least this:
boot: linux ks=http://url_of_kickstart_
file ip=... gateway=...
netmask=... dns=...
-Ed
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
|
| Re: static network configuration ask |
|
2007-08-30 17:14:36 |
|
Thanks Ed. I'll try that and report back. ; It's still a little more complicated than I would have liked as this will be used by people other than myself. It really simplifies all the scripting I was doing in %post to force it to work despite the difficulties. 
It would be much slicker if there were an "ask" option to the network or if it didn't default to dhcp :-(
On 8/30/07, Ed Brown
< ebrownlanl.gov">ebrownlanl.gov> wrote:> boot: ip=blah gateway=blah netmask=blah dns=blah
This is not quite complete. And actually, we make a custom boot cd,
with multiple targets that contain the common parameters, so all
that's needed at the boot prompt is target, ip and gateway. You'll
probably need at least this:
boot: linux ks=http://url_of_kickstart_file ip=... gateway=...
netmask=... dns=...
-Ed
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com">Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
| Re: static network configuration ask |
|
2007-08-30 17:33:32 |
|
As long as we don't have to enter a mac address it sounds good to me. The problem with mac addresses is that our servers boot so fast it's hard to catch the config menu as it flies by. We're normally looking at them through an ASM or IpKVM of some type which just makes it harder..... Our build process is already obnoxious enough already. I'll look into that further after I get this first batch of servers delivered to the poor folks who are waiting on me right now. :-( Thanks.
Kit
On 8/30/07, Michael DeHaan < mdehaanredhat.com">mdehaanredhat.com> wrote:
Kit Stube wrote:
>; Cobbler looks cool. Kinda like a front end for pxelinux and isc
> dhcpd? The problem we have is we don't want to have to look up the
> mac address for a host in order to configure it. Cobbler seems to
> rely on that.
Nah, you don't At least not in newer versions ...
Starting with 0.6.x (0.6.1 is out today -- I recommend installing that),
you can name a system anything arbitrarily. If you know the MAC
address, it helps to use that so we can assign a specific kickstart --
you can also use the ip if you know that instead. Otherwise you can
pick a specific profile and just assign that to be the "default" for all
PXE booting systems. You can also use it to create a PXE menu, so you
can walk up to a machine while it's booting, type "menu", and pick what
you want.
>;
> Currently we have our dhcp server on an install network dump anyone
> that netboots on that network to a default pxelinux menu. ; That
> default menu allows a person to chose an os to install. Chosing one
> kicks them into one of several different default kickstart files. If
> I could get kickstart to ask for static network information like it
> would if I was installing from CD, I would be done.
I should have read further before typing. Yeah, we can do that
The MAC address way of assigning the static info works really really
well though, if you can start doing it. I like kickstarts to be fully
interactive because I can start them and not have to baby-sit. Plus
mapping a system to a new profile is as easy as:
cobbler edit --name=<;MAC> --profile=<newprofile>
--Michael
>
>
> On 8/30/07, *Riggs, Ben* < rigg0022umn.edu">rigg0022umn.edu <mailto: rigg0022umn.edu">rigg0022umn.edu>>
> wrote:
>
> Check out http://cobbler.et.redhat.com It's made our life here
> ; tons easier.
>
> Ben
>
> Kit Stube wrote:
> > Is there an option that will allow me to automate everything in
> > kickstart except just the network portion so that I can have the
> same
> ; > kickstart config for a bunch of clustered hosts but input the
> ; network
> > information myself?
> >
> ; > The reason I ask is because I would like to automate a lot of other
> ; > stuff in %post ; or on first boot but need networking to be set up
> ; > properly by the time that stuff runs or it will screw all of
> that up.
> >
> ; > Thanks in advance
> > Kit Stube
> ; >
> ; >
> ; >
>; ------------------------------------------------------------------------
>; >
> ; > _______________________________________________
> > Kickstart-list mailing list
> ; >
Kickstart-listredhat.com">Kickstart-listredhat.com <mailto: Kickstart-listredhat.com">Kickstart-listredhat.com>
> ; >
https://www.redhat.com/mailman/listinfo/kickstart-list
>
> _______________________________________________
> Kickstart-list mailing list
> ; Kickstart-listredhat.com">
Kickstart-listredhat.com <mailto: Kickstart-listredhat.com">Kickstart-listredhat.com>
> ; https://www.redhat.com/mailman/listinfo/kickstart-list
>
>
> ------------------------------------------------------------------------
>;
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com">
Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com">Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|
| Re: static network configuration ask |
|
2007-08-30 17:39:20 |
|
That worked for the most part. Ed, your a genious!
The only problem now is that it didn't set the hostname. Is there some way to use something like $hostname in post so I can set all that up?
Perhaps that was what Pablo was trying to tell me? I don't understand how to process /proc/commandline. Does anyone have an example?
I would be greatly appreciative.
Kit
On 8/30/07, Ed Brown < ebrownlanl.gov">ebrownlanl.gov> wrote:
> boot: ip=blah gateway=blah netmask=blah dns=blah
This is not quite complete. And actually, we make a custom boot cd,
with multiple targets that contain the common parameters, so all
that's needed at the boot prompt is target, ip and gateway. You'll
probably need at least this:
boot: linux ks=
http://url_of_kickstart_file ip=... gateway=...
netmask=... dns=...
-Ed
_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com">Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
|