On Tuesday 29 March 2005 17:28, Sean Dague wrote:
On Tue, Mar 29, 2005 at 04:01:19PM +0200, Andrea Righi wrote:
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).
My own personal opinion is that SystemInstaller solved the problem already, and using that as the front end if you want this functionality is the right approach. What is wrong with using SystemInstaller?
Anything that reinvents this all over again is largely a waste of time.
I'm not sure whether you argue against sis_reload or not. The SI release I can access and download is version 1.04 and that one has huge deficits when it comes to multiple interfaces. I was trying to solve that problem by using the SIS infrastructure and database, as well as systemconfigurator for loading the changes into the clients. The SIS infrastructure is prepared for multiple interfaces, but I needed something like sisqd/sisqc to access it from the client nodes. If there is another way, please explain it.
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...
You don't just need parsing, you need a way to put that info in there... and that way is SystemInstaller. Just use it.
Yes, the parsing is what I wanted to avoid. Otherwise one ends up with a huge bunch of additional perl packages which need to be installed on the cluster nodes, too.
Regards, Erich
Sorry... maybe I haven't been very clear... with parsing I meant reading data from the DB, and this can be done at the image server side when the autoinstallscript is produced (using si_mkautoinstallscript). No additional perl packages have to be added to the client nodes...
Anyway, I really like the SIS DB solution... but for now I don't know the SystemInstaller so closely... First of all I will deep my knowledge on the SIS DB structure...
Regards, -Andrea
------------------------------------------------------- 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
