Return to release.notes CVS log

Up to [Development] / JSOC / CM / V2.0

First new, reorganized JSOC tree

			Release Notes JSOC V2.0		03Feb2006
			-----------------------		---------


The official release version is in /home/production/cvs/jsoc.
This will remain unchanged until the next release.
You may make any changes you want in your sandbox, but anything that you 
commit will appear in the next offical release.

****************************** Sandbox ***************************************

You need a cvs "sandbox" to contain your view of the V2.0 release:
(There is no need to do this unless you're going to be a jsoc developer.)

Set the env variables:
CVSROOT=:ext:sunroom.stanford.edu:/home/cvsuser/cvsroot
CVS_RSH=ssh

################# If you don't already have a sandbox do this: #############
Make a cvs dir and do:
> cd /home/you/cvs
> cvs checkout jsoc
############################################################################

Resync your sandbox with the V2.0 release:

> cd /home/you/cvs/jsoc
> cvs update -APd

Check for any files that have not been commited (not Status: Up-to-date):

> cvs status | egrep ^File: | egrep -v Up-to-date

These should only be files that have local changes that you are aware of.
If you have a file here that you wanted in the release, please contact CM.


You now need to make on linux_ia64 (lws) or linux_x86_64 (d00) machines:

> ssh lws		(and then again for d00)
> cd /home/you/cvs/jsoc
> ./configure -force -client -static (this static is new 3/2/06)
> make clean
> make -j 4  		(run 4 jobs in parallel for speed)

Set your path for /home/you/cvs/jsoc/bin/linux_ia64 (or linux_x86_64)

The command 

> configure -help

will print information about how to create a customized build,
to e.g. use a different compiler or turn on debugging flags.

If you are unfamiliar with the use of cvs see the file:
jsoc/CM/<version>/working_with_sandbox.txt. 


There's a linux4 cvs gui at xim:/usr/bin/lincvs

****************************** SUMS ******************************************

The Storage Unit Management (SUM) subsystem is discussed and its API
presented in:

http://sun.stanford.edu/web.hmi/development/SU_Development_Plan/SUM_API.html

The V2.0 release notes are in:

jsoc/CM/V2.0/sum_release.txt

NOTE: Only DRMS needs to be concerned with SUMS.


************************** DRMS ***********************

The Data Record Management System (DRMS) is discussed in 

  http://sun.stanford.edu/web.hmi/development/JSOC_Documents/DRMS_V10.pdf

which explains the motiviation and conceptual design.

Creating and running DRMS modules is discussed in 

  jsoc/CM/<version>/drms_module.txt

The current user-level DRMS API is discussed in 
 
  jsoc/CM/<version>/drms_api.txt

The DRMS recordset query syntax is defined in 

  jsoc/CM/<version>/drms_names.txt

A few DRMS command line utilities used to create and manage data 
series are listed in

  jsoc/CM/<version>/drms_series.txt

DRMS uses the PostgreSQL database called "jsoc" on the host
"hmidb.stanford.edu". 

 * To use DRMS you must have a user account in the database. 
   Contact Rasmus Munk Larsen (rmunk@quake.stanford.edu) to obtain 
   such an account. 
 * The database is continuously backed up to disk using the Point In Time 
   Recovery mechanism. We do not yet have tape backups running.
 * A full table dump (to disk) and table maintenance (VACUUM ANALYZE) is 
   performed every Monday morning at 2am (dump) and 4am (vacuum). Expect 
   some performance degradation for modules with heavy database usage at 
   such times.
 * The database is stopped and started (as root) with 
   > service postgresql stop
   > service postgresql start

To compile and run the DRMS server, the following RPMs must be installed
installed on the machine:

postgresql
postgresql-devel
postgresql-libs
openssl-devel