Current Status of NGAS Implementations at the AOC. 

 2008-04-04  JMB
 2008-04-08  JMB
------------------------------------------------------------------------------

- NGAS version v3.2 (ALMA_NGAS_V3_2_2008-02-07.tar)
  received from ESO and deployed on newtech-4. The 
  1 TB of VLBA files on the 3rd newtech-4 partition were kept and
  registered in the new system.

- NGAS v3.2 has a GenericLinuxOnLine plugin that allows 'connection' to
  any mount points. HD RAID partitions are mounted by me outside of NGAS.
  This works fine.

- I scratched the previous NGAS Oracle DB. Created a new NGAS DB,
  on quigon.aoc.nrao.edu, db name : NRAONGAS, reset date datatype to
  varchar2(23) per Jens' approval. Used Jens' new tool to initialize
  the ngas_disks table.. Works fine.

- The new NGAS supports file pull (ingest) and file retrieve. Also the
  archive query tool will deliver files from newtech-4 NGAS.

- Sent a collection db table files, ngas log file and configuration file
  to Jens to check over. Hopefully we're in good shape.

To Do :

- Write NGAS plugin to support archiving VLAraw data files.
* Completed, works.

- Test archiving application/x-image ..

- Ingest data files into NGAS newtech-4 that are currently being
  archived in the disk arrays (in parallel). Some sort of operational
  stability test..
* In progress, parallel archiving of the daily VLA data files.

- Test archive VLBA calibrated AIPS-FITS files. Works okay. I'm
  surprised because these files have an '=' imbedded in their file
  names. But the ngamsCClient ARCHIVE and RETRIEVE commands work
  properly. 
* Works okay.

- Need to check the above using the ngamsPClient.py app, it may
  use an Http parser (I think it does). If so it will fail because
  of the imbedded '=".

- ngamsCClient max file size measures 1000000000. Need recomplied
  version gcc with 64 bit ints. Next ngams release. Also I need to
  update the ngams--Client apps on /home/pecos3/jbenson wrst the
  latest ngams release..

-