| Revision: | 1.1.1.1 (vendor branch) |
| Committed: | Tue Oct 2 00:12:21 2007 UTC (15 years, 11 months ago) by arta |
| Branch: | MAIN, Vtag |
| CVS Tags: | Ver_6-0, Ver_6-1, Ver_6-2, Ver_6-3, Ver_6-4, Ver_4-3, Ver_4-0, Ver_4-1, NetDRMS_Ver_8-8, NewTree01_cp03_JSOC, Ver_4-4, Ver_8-5, Ver_4-7, NewTree01_cp05_JSOC, Ver_5-14, Ver_5-13, Ver_5-12, Ver_5-11, Ver_5-10, Ver_LATEST, NetDRMS_Ver_LATEST, Ver_4-6, NewTree01_cp04_JSOC, NetDRMS_Ver_8-12, NetDRMS_Ver_8-10, NetDRMS_Ver_8-11, NetDRMS_Ver_9-1, NetDRMS_Ver_9-0, NetDRMS_Ver_9-3, NetDRMS_Ver_9-2, NetDRMS_Ver_9-5, NetDRMS_Ver_9-4, Ver_7-0, Ver_5-6, Ver_4-5, NewTree01_cp07_JSOC, NewTree01_cp08_JSOC, NewTree01_cp01_JSOC, Ver_4-2, NetDRMS_Ver_9-41, Ver_9-41, NewTree01_cp02_JSOC, NetDRMS_Ver_8-4, NetDRMS_Ver_8-5, Ver_5-8, NetDRMS_Ver_8-6, Ver_5-7, Ver_8-8, NetDRMS_Ver_8-7, NewTree01_cp06_JSOC, Ver_5-9, Ver_8-2, Ver_9-3, Ver_8-0, Ver_8-1, Ver_8-6, Ver_8-7, Ver_8-4, Ver_8-11, Ver_5-3, Ver_5-2, Ver_5-1, Ver_5-0, Ver_7-1, Ver_9-1, Ver_5-5, Ver_8-3, NewTree01_cp09_JSOC, Ver_9-5, Ver_9-4, Ver_8-10, Ver_9-2, Ver_8-12, Ver_9-0, HEAD |
| Changes since 1.1: | +0 -0 lines |
| Log Message: | First new, reorganized JSOC tree |
| # | Content |
|---|---|
| 1 | Release Notes JSOC V2.0 03Feb2006 |
| 2 | ----------------------- --------- |
| 3 | |
| 4 | |
| 5 | The official release version is in /home/production/cvs/jsoc. |
| 6 | This will remain unchanged until the next release. |
| 7 | You may make any changes you want in your sandbox, but anything that you |
| 8 | commit will appear in the next offical release. |
| 9 | |
| 10 | ****************************** Sandbox *************************************** |
| 11 | |
| 12 | You need a cvs "sandbox" to contain your view of the V2.0 release: |
| 13 | (There is no need to do this unless you're going to be a jsoc developer.) |
| 14 | |
| 15 | Set the env variables: |
| 16 | CVSROOT=:ext:sunroom.stanford.edu:/home/cvsuser/cvsroot |
| 17 | CVS_RSH=ssh |
| 18 | |
| 19 | ################# If you don't already have a sandbox do this: ############# |
| 20 | Make a cvs dir and do: |
| 21 | > cd /home/you/cvs |
| 22 | > cvs checkout jsoc |
| 23 | ############################################################################ |
| 24 | |
| 25 | Resync your sandbox with the V2.0 release: |
| 26 | |
| 27 | > cd /home/you/cvs/jsoc |
| 28 | > cvs update -APd |
| 29 | |
| 30 | Check for any files that have not been commited (not Status: Up-to-date): |
| 31 | |
| 32 | > cvs status | egrep ^File: | egrep -v Up-to-date |
| 33 | |
| 34 | These should only be files that have local changes that you are aware of. |
| 35 | If you have a file here that you wanted in the release, please contact CM. |
| 36 | |
| 37 | |
| 38 | You now need to make on linux_ia64 (lws) or linux_x86_64 (d00) machines: |
| 39 | |
| 40 | > ssh lws (and then again for d00) |
| 41 | > cd /home/you/cvs/jsoc |
| 42 | > ./configure -force -client -static (this static is new 3/2/06) |
| 43 | > make clean |
| 44 | > make -j 4 (run 4 jobs in parallel for speed) |
| 45 | |
| 46 | Set your path for /home/you/cvs/jsoc/bin/linux_ia64 (or linux_x86_64) |
| 47 | |
| 48 | The command |
| 49 | |
| 50 | > configure -help |
| 51 | |
| 52 | will print information about how to create a customized build, |
| 53 | to e.g. use a different compiler or turn on debugging flags. |
| 54 | |
| 55 | If you are unfamiliar with the use of cvs see the file: |
| 56 | jsoc/CM/<version>/working_with_sandbox.txt. |
| 57 | |
| 58 | |
| 59 | There's a linux4 cvs gui at xim:/usr/bin/lincvs |
| 60 | |
| 61 | ****************************** SUMS ****************************************** |
| 62 | |
| 63 | The Storage Unit Management (SUM) subsystem is discussed and its API |
| 64 | presented in: |
| 65 | |
| 66 | http://sun.stanford.edu/web.hmi/development/SU_Development_Plan/SUM_API.html |
| 67 | |
| 68 | The V2.0 release notes are in: |
| 69 | |
| 70 | jsoc/CM/V2.0/sum_release.txt |
| 71 | |
| 72 | NOTE: Only DRMS needs to be concerned with SUMS. |
| 73 | |
| 74 | |
| 75 | ************************** DRMS *********************** |
| 76 | |
| 77 | The Data Record Management System (DRMS) is discussed in |
| 78 | |
| 79 | http://sun.stanford.edu/web.hmi/development/JSOC_Documents/DRMS_V10.pdf |
| 80 | |
| 81 | which explains the motiviation and conceptual design. |
| 82 | |
| 83 | Creating and running DRMS modules is discussed in |
| 84 | |
| 85 | jsoc/CM/<version>/drms_module.txt |
| 86 | |
| 87 | The current user-level DRMS API is discussed in |
| 88 | |
| 89 | jsoc/CM/<version>/drms_api.txt |
| 90 | |
| 91 | The DRMS recordset query syntax is defined in |
| 92 | |
| 93 | jsoc/CM/<version>/drms_names.txt |
| 94 | |
| 95 | A few DRMS command line utilities used to create and manage data |
| 96 | series are listed in |
| 97 | |
| 98 | jsoc/CM/<version>/drms_series.txt |
| 99 | |
| 100 | DRMS uses the PostgreSQL database called "jsoc" on the host |
| 101 | "hmidb.stanford.edu". |
| 102 | |
| 103 | * To use DRMS you must have a user account in the database. |
| 104 | Contact Rasmus Munk Larsen (rmunk@quake.stanford.edu) to obtain |
| 105 | such an account. |
| 106 | * The database is continuously backed up to disk using the Point In Time |
| 107 | Recovery mechanism. We do not yet have tape backups running. |
| 108 | * A full table dump (to disk) and table maintenance (VACUUM ANALYZE) is |
| 109 | performed every Monday morning at 2am (dump) and 4am (vacuum). Expect |
| 110 | some performance degradation for modules with heavy database usage at |
| 111 | such times. |
| 112 | * The database is stopped and started (as root) with |
| 113 | > service postgresql stop |
| 114 | > service postgresql start |
| 115 | |
| 116 | To compile and run the DRMS server, the following RPMs must be installed |
| 117 | installed on the machine: |
| 118 | |
| 119 | postgresql |
| 120 | postgresql-devel |
| 121 | postgresql-libs |
| 122 | openssl-devel |