[Swift-devel] Swiftconfig merge / changes

[wilde at mcs.anl.gov]

I agree that anything swiftrun does which we want to retain should be integrated into swift. Two things I think are important are: 
- allow selection of a set of sites 
- copy all relevant config information into the swift log (by default) 


Regarding swiftconfig: 
- I think we can code its functions in the lowest common denominator of /bin/sh capabilities 
- the difficult part is organizing the many sites file variations into a manageable set of parameterized templates, possible both provided by swift and also managed as a sites template library by users or groups. 


Mike 



----- Original Message -----




On Wed, Feb 2, 2011 at 1:04 AM, jon.monette at gmail.com < jon.monette at gmail.com > wrote: 


Having a java process call a shell script which in turns starts java processes may not be the best plan of action. 


That is a good point. Perhaps we should think about integrating what swiftrun does/should do directly into swift. It may be better than building up layers of scripts around it. I think it could done in a way that is backwards compatible. We would have to discuss the details, but for example, if you specify -sites.file it will use that exclusively. Otherwise you could pass it a -site <sitename> and it will know to look in $HOME/.swift for templates, to replace values in templates with environment variables where requested, and so on. There's more to it, but that's the basic idea. 

Then swiftconfig just has to worry about managing the config files. It would simplify the test suite. Swift would be more flexible.. and maybe it would reduce the number of people having to write custom shell scripts to do things like this. 

David 







-- 
Michael Wilde 
Computation Institute, University of Chicago 
Mathematics and Computer Science Division 
Argonne National Laboratory 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20110202/22ce1d6c/attachment.html>