[evla-sw-discuss] (no subject)

[Kevin Ryan]

Hi gang,

This is more of a James question but I think that many on this list  
might be interested in the outcome.

Work on the WIDAR correlator TestExecutor software suite has gotten  
me thinking about how (or if) we will implement a 'Central Server'.   
We want configuration files (the ones that set up the various  
correlator modes), data output files such as those generated by the  
Station Boards during OTS testing, property files and the Java Web  
Start GUI application files all to reside on one central file system  
that is mounted by all processors in the correlator including each of  
the 256 CMIBs.  ... I think.

Presently, the Java Web Start application files and the system  
property files reside on 'filehost'(?) at '/home/asg/www/widar'.   
This translates to the URL 'http://www.aoc.nrao.edu/asg/widar/' used  
by Java for access to these files.

Also, presently, the CMIBs access a directory on 'cmibhost' (the CMIB  
bootserver in Bruce & Kevin's office) called '/opt/widar' where  
configuration files are kept for now.  When the system goes online  
there will be more than one CMIB bootserver which will cause  
confusion since there will no longer be a single central '/opt/widar'  
directory.

It would be nice if we could combine the '/home/asg' and 'opt/widar'  
areas on 'filehost' and 'cmibhost' into one area common to (and  
mounted on) all processors in the correlator.  This machine must also  
be a web server.

I don't think this machine should be one of the online units like  
MCCC.  I don't even know if it has to reside in the correlator room,  
but keep in mind that there will be occasions where CMIBs will be  
writing output data products to it via NFS.

Suggestions James or anyone?  Is this something that the mirrored (or  
whatever it's called) 'filehost' at the VLA could do?  Does the EVLA  
already have something like this running out there that we could share?

Kevin