One idea I heard, went something like this:
* have a lookup table, maybe it lives in the scripts directory
* entries could be something like:
node99: DEVICE=eth0 IPADDR=10.0.0.99 NETMASK=255.255.255.0 \
NETWORK=10.0.0.0 BROADCAST=10.0.0.255 \
GATEWAY=10.0.0.1 GATEWAYDEV=eth0
node99: DEVICE=eth1 IPADDR=10.1.1.99 NETMASK=255.255.255.0 \
NETWORK=10.1.1.0 BROADCAST=10.1.1.255 \
GATEWAY=10.1.1.1
* If a device is to use dhcp, then it would simply not have an entry.
* The entire scripts directory is distributed to each client
already, so this interface.map file would just "be there" locally,
on each client, after the transfer of the scripts directory.
These network settings could even be used to re-configure the
interface prior to continuing the install.
* One nice thing about this is that the vars are the same as what is
currently used. We'd still have to modify some of the hard-coded
stuff, and deal with multiple interfaces using vars with the same
names (i have some ideas in the cranium) but I think it could be
done fairly readily, and probably without breaking backwards
compatibility (for config options).
Comments? Other ideas?
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
>>>
>>>
>>>
>>>
>>>
>>--
>>------------------------------------------------------
>> Brian Elliott Finley Mobile: 630.631.6621
>> gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
>>------------------------------------------------------
>>
>>
>>
>>-------------------------------------------------------
>>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
>>
>>
>>
>
>
>
--
------------------------------------------------------
Brian Elliott Finley Mobile: 630.631.6621
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
------------------------------------------------------
-------------------------------------------------------
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
