As Sean said SystemImager has the concept of 1 ip per machine. In some cases the network configuration to reach the image server could be different from the configuration when the machine will work in production... i.e. some clients that use eth0 as private network (to reach the image server and for administrative purposes) and eth1 as public network (for services). In this case at the end of the installation I'd like to have both eth0 and eth1 setted up.
So to cover as many cases as possibile, probably, we should consider different network configurations (up to one for each interface).
The solution proposed by Brian is good, but it introduces a new config file.
The Erich's solution sounds good, but forces to use always SystemInstaller package (due to SIS DB dependency).
However if we will use the SIS DB we could generate the systemconfigurator config file when the autoinstallscript is generated; I mean the Server.pm should include the code to parse the SIS DB and produce the list of interfaces to pass to systemconfigurator, instead of using the infrastructure with sisqd and sisqc proposed by Erich. I think this infrastructure could be useful as an "extension" (look to autoconf stuff...), but IMHO it shouldn't be mandatory...
Other reflections in progress...
Regards, -- Andrea Righi System Management Group - CINECA - http://www.cineca.it Via Magnanelli 6/3 40033 Casalecchio di Reno (BO) - Italy
------------------------------------------------------- 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
