On Monday 28 March 2005 20:21, Brian Elliott Finley wrote:
> One idea I heard, went something like this:
>
> * have a lookup table, maybe it lives in the scripts directory
Yet another configuration information outside the SIS database? The
beauty of having a central cluster configuration database is (IMO) the
big plus of SIS.
Why not simply introduce an additional TYPE field in the SIS/Adapter
database, which can take the values:
- STATIC (default value, if empty)
- DHCP
- NOPXE (or something else...: generate entry in dhcpd.conf but
don't load pxelinux.0: this way we could add appliances
in the cluster which need an IP through DHCP)
>
> Comments? Other ideas?
>
On March 9th I posted two messages to sisuite-devel, one on
mksiadapter and one on sis_reload. Using sis_reload is my preferred
method for configuring multiple adapters. When using it the clumsy
config line in the autoinstall script can be replaced by
chroot /a sis_reload network
This would get the network-specific systemconfigurator input file from
the sis database over the network and configure all the adapters
accordingly. And, by the way, generating the fstab is as simple as
chroot /a sis_reload fstab
This is not perfect and not complete, but helps you keep a consistent
and _unique_ cluster config database.
Best regards,
Erich
> Sean Dague wrote:
>
> >On Sun, Mar 27, 2005 at 10:33:43PM -0600, Brian Elliott Finley wrote:
> >
> >
> >>So,
> >>
> >>Let's go ahead and tackle this. There have been a handful of methods
> >>suggested for handling multiple interfaces in SystemImager in the past.
> >>Has anybody stumbled upon what they think is a "ringer"?
> >>
> >>
> >
> >SystemInstaller did some of this a long time ago. The real issue is that
> >SystemImager has the concept of 1 ip per machine name pretty firmly
> >hardcoded in it (using hosts files and such). You'd have to gut that out to
> >make a reasonable solution here. Also, getting more than 1 dhcp response
> >starts getting pretty tricky, so you'd really need to truly generate a new
> >autoinstallscript per client if you wanted to support static ip on multiple
> >interfaces.
> >
> >If you just want dhcp add lines to /etc/systemconfig/systemconfig.conf in
> >the image like:
> >
> >[INTERFACE1]
> >DEVICE = eth1
> >TYPE = dhcp
> >
> >[INTEFACE2]
> >DEVICE= eth2
> >TYPE = dhcp
> >
> >etc.
> >
> >Anyway, I'm going to revert that one last change, as I know many people that
> >it will break.
> >
> > -Sean
> >
> >
> >
> >
> >>-Brian
> >>
> >>
> >>Sean Dague wrote:
> >>
> >>
> >>
> >>>On Sun, Mar 27, 2005 at 10:07:14AM -0800, [EMAIL PROTECTED] wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>sub write_sc_command {
> >>>> my ( $out, $ip_assignment_method ) = @_;
> >>>>+
> >>>>+ # Configure the network device used to contact the image-server -AR-
> >>>>+ print $out "[ -z \$DEVICE ] && DEVICE=eth0\n";
> >>>>+
> >>>> my $sc_excludes_to = "/etc/systemimager/systemconfig.local.exclude";
> >>>> my $sc_cmd = "chroot /a/ systemconfigurator
> >>>> --excludesto=$sc_excludes_to";
> >>>> if ($ip_assignment_method eq "replicant") {
> >>>>@@ -1595,7 +1599,7 @@
> >>>> print $out "\n";
> >>>>
> >>>> print $out "[INTERFACE0]\n";
> >>>>- print $out "DEVICE = eth0\n";
> >>>>+ print $out "DEVICE = \$DEVICE\n";
> >>>>
> >>>>
> >>>>
> >>>>
> >>>I don't think you should change this last portion. There are a lot of
> >>>users
> >>>that make assumptions on [INTERFACE0] ending up to be eth0 (including the
> >>>OSCAR folks) and changing that to be the install interface will break
> >>>some other things.
> >>>
> >>>The right thing is doing multiple interfaces through SystemImager. So
> >>>while
> >>>shutting down $DEVICE is definitely a good thing, setting up $DEVICE by
> >>>default with SystemConfigurator is a change in behavior that is going to
> >>>break some people.
> >>>
> >>> -Sean
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
