MEDOC - Multi Experiment Data & Operation Center » NetDRMS_8.12

h1. config.local

See here change from the original config.local file :

DRMS_DATABASE ias_sdo

DBSERVER_HOST sdo3

DRMS_SITE_CODE 0x0018

SUMS_GROUP ias

SUMS_SERVER_HOST sdo3

SUMS_DB_HOST sdo3

SUMS_LOG_BASEDIR /usr/local/netdrms_current/logs/SUM

SUMRM_NOOP 1

POSTGRES_INCS:X86_64 /usr/local/pgsql/include

POSTGRES_INCS:AVX /usr/local/pgsql/include

POSTGRES_LIBS:X86_64 /usr/local/pgsql/lib

POSTGRES_LIBS:AVX /usr/local/pgsql/lib

CFITSIO_LIBS:X86_64 /usr/local/lib

CFITSIO_LIBS:AVX /usr/local/lib

TAR_LIBS:X86_64 /usr/lib

TAR_LIBS:AVX /usr/lib

Complete file :

<pre>

__DEFS__

# NetDRMS local site configuration info.

#

# This file contains configurable parameters that allow NetDRMS sites to customize their DRMS installation. By editing this file, you can specify which resources to use, such as the PostgreSQL database host, you can specify arguments to certain programs, like arguments that control how often SUMS purges expired Storage Units, and you can enable/disable certain features, like remoteSUMS. Each line that is not a comment contains two columns of information. The first column contains the name of a parameter and the second contains its value. To customize your installation, you would edit the value in the second column.

#

# Once you have edited this file, you must run the configure script, which parses this file to create macros and constants and such that are used by the various DRMS components. These data are stored in files which are then either compiled into binaries or loaded by scripts. The configure script accomplishes much of this work by calling localize.py. The resulting files are stored in the localization directory.

# The name of the NetDRMS database (e.g., sdac_drms, nso_drms); this is also the prefix of the SUMS database,

#   which is constructed by appending "_sums" to the prefix.

DRMS_DATABASE   ias_sdo

# The database user account that cgi programs access when they need to read from or write to database relations.

WEB_DBUSER      apache

# The host machine of the database server you will be accessing; if

#   the DRMS server and client reside on different subnets, then the host

#   name should be a fully qualified domain name (FQDN).

# A value of 'localhost' can be used, but it is only appropriate if you

#   are running in a single-user environment, such as on a laptop. In

#   this case, the client and the server are the same machine, so

#   it is not necessary to specify a host name for the server.

DBSERVER_HOST   sdo3

# The port number for the DRMS database server - the default of 5432 is a

#   good choice, unless it is already in use.

DRMS_DBPORT     5432

# A 15-bit numerical site identifier. Values < 16384 (0x4000) are for

#   NetDRMS sites that create Storage Units for public export / distribution.

#   They must be unique across all DRMS sites. Values >= 16384 are for private

#   use and need not be unique across sites.

DRMS_SITE_CODE  0x0018

# The database user name of the postgres administrative account; this is normally "postgres"

#   if you have followed the PostgreSQL installation suggestions.

POSTGRES_ADMIN  postgres

# The following entries are specific to the SUMS configuration

# The user name of the SUMS administrator database account.

SUMS_MANAGER    production

# The linux group name for users permitted to add data to SUMS Storage Units; not

#   currently used in code, but should match the group ownership of

#   the SUMS root directories /SUM*

SUMS_GROUP      ias

# The host of the default SUMS server you will be using; this is the

#   the machine that the SUMS storage units are mounted on, not necessarily

#   the machine serving the PostgreSQL SUMS database.

SUMS_SERVER_HOST        sdo3

# The machine hosting the SUMS database.

SUMS_DB_HOST            sdo3

# The port number for the DRMS database server - the default of 5434 should be okay

#   unless it is in use already.

SUMS_DBPORT     5434

# The number of sum_svc processes, per sum service (e.g., SUM_get, SUM_alloc) to start,

# by default, when multi-SUMS starts up.

SUM_NUMSUM    1

# The maximum number of sum_svc processes, per sums service.

SUM_MAXNUMSUM 8

# The base directory for SUMS logs and configuration files; used by

# sum_svc and sum_rm.

SUMS_LOG_BASEDIR        /usr/local/netdrms_current/logs/SUM

# The directory in which sum_chmown, a root setuid program,

#   is installed; must be mounted locally on the machine on which the

#   SUMS partition are mounted; used by base/sums/apps/sum_svc_proc.c

SUMS_BIN_BASEDIR        /usr/local/bin

# If set to 1, then SUMS includes a tape-archive system.

SUMS_TAPE_AVAILABLE     0

# If set to 1, then SUMS has more than one partition set.

SUMS_MULTIPLE_PARTNSETS      0

# If AUTOSELCOMP is 1, then the configure script will automatically select

# the 'best' compiler for use with the make system (choosing icc over gcc).

# Set this to 0 to permit manual selection via the JSOC_COMPILER and JSOC_FCOMPILER

# environment variables, or via editing of make_basic.mk

AUTOSELCOMP (1)

###############################

# TABLE OF PRODUCTION USERS

#   These parameters are used by lib DRMS to identify a database table (not a data series)

#   that lists the database users that are 'production users'. These users have privileges

#   that ordinary users do not. For example, production users can reduce the retention of

#   data series that the production user does not own.

# The host:port of the machine serving as the db server that contains the production-user table.

#PRODUSER_DBHOST    hmidb:5432

# The name of database on the database host that contains the production-user table.

#PRODUSER_DBNAME    jsoc

# The name of the production-user table

#PRODUSER_PRODTAB   su_production.produsers

# The name of the column that contains the list of production users in the production-user table.

#PRODUSER_COLUSER   username

#

# END TABLE OF PRODUCTION USERS

###############################

###############################

# Parameters for sum_rm

# This is the percentage at which all disk partitions are to be kept free.

# If not specified, this defaults to 3. For example, setting PART_PERCENT_FREE = 5 will allow all partitions to

# fill to 95% full. Dividing the number of unused blocks by the total number of blocks, and rounding up,

# will result in the number specified by PART_PERCENT_FREE.

SUMRM_PART_PERCENT_FREE                3

# The value is the number of seconds to sleep between iterations of the main loop in sum_rm.

SUMRM_SLEEP                          300

# The value is the log file (opened only at sum_rm startup; the sum_rm pid is appended to this file name).

SUMRM_LOG                /tmp/sum_rm.log

# The value is the email address of the recipient to be notified in case of a problem.

# SUMRM_MAIL    president@whitehouse.gov

# If the value is set to anything other than 0, then sum_rm is rendered inactive. Otherwise, sum_rm is active.

SUMRM_NOOP                             0

# The value designates the linux user who is allowed to run sum_rm.

SUMRM_USER                    production

# This pair of parameters defines a window of time, during which sum_rm will become torpid - in this

# window, sum_rm will not scan for SUs to delete, not will it delete any SUs. Each value is an integer, 0-23, that

# represents an hour of the day. For example, if NORUN_START=8 and NORUN_STOP=10, then between 8am and 10am

# local time, sum_rm will be dormant. To disable this behavior, set both parameters to the same value.

SUMRM_NORUN_START                      0

SUMRM_NORUN_STOP                       0

JMD_IS_INSTALLED                       0

# If the JMD is installed, then this parameter is the root URL to the JMD cgi interface.

JMD_URL                       http://localhost:8080/JMD/JMD

###############################

###############################

# Parameters for remote sums - these parameters allow configuration of the remote-sums components

# The database table that lists the remote sites, their site codes, and their base urls that provide access to the rs.py CGI.

# Each site that provides SUs to other sites must have a rs.py CGI that provides the scp path to the site requesting the SUs.

RS_SITE_TABLE                         drms.rs_sites

# The database table used by rsumsd.py daemon running at the receiving site to track remote-site SU requests.

RS_REQUEST_TABLE                      drms.rs_requests

# The database table used by rsumsd.py daemon running at the receiving site to track SU downloads.

RS_SU_TABLE                           drms.rs_sus

# The name of the database that contains the three previous tables.

RS_DBNAME                             mydb

# The database host that contains the database identified by RS_DBNAME.

RS_DBHOST                             localhost

# The database user that manages remote sums programs.

RS_DBUSER                             user

# The port on the database host used by rsumsd.py to access the database identified by RS_DBNAME.

RS_DBPORT                             5432

# The (advisory) lockfile used by rsumsd.py to prevent multiple instances of rsumsd.py from running.

RS_LOCKFILE                           /usr/share/drms/locks/remotesums.lck

# The directory in which remote-sums log files are written.

RS_LOGDIR                             /usr/share/drms/logs/rsums

# The number of minutes after which a storage-unit download will time-out.

RS_DLTIMEOUT                          30

# The number of minutes after which a new remote-sums fetch will time-out if no download has yet started.

RS_REQTIMEOUT                          5

# The maximum number of simultaneously storage unit downloads to process at once.

RS_MAXTHREADS                         32

# The path to executables run by the remote-sums system.

RS_BINPATH                            /opt/drms/bin/linux_x86_64

# If set to 1, then this DRMS allows access by the public to series defined in the internal database (SERVER).

WL_HASWL                              0

# The file that contains a list of internal series that are accessible to external users.

WL_FILE                               /usr/share/drms/whitelist.txt

# The paths to various binaries.

BIN_EXPORT                            /opt/drms/bin

SCRIPTS_EXPORT                        /opt/drms/scripts

# The Python binary must be at least version 2.7. 3.x binaries will work.

BIN_PY                                /usr/bin/python

# The number of minutes after which a new email registration attempt will time-out if the registering user does

# not respond to the verification email sent to them.

REGEMAIL_TIMEOUT                      5

############## MT SUMS ##############

# These are parameters needed when using the multi-threaded SUMS daemon.

# Use the MT SUMS daemon (which serves SUM_infoArray() requests).

SUMS_USEMTSUMS                        0

# The maximum number of SUs to process in parallel.

SUMSD_MAX_THREADS                    32

# The port to be used by the MT SUMS daemon for incoming requests.

SUMSD_LISTENPORT                   6002

############ END MT SUMS ############

# The Slony server configure file. This is used only if you are generating Slony logs to distribute DRMS series data

# to subscribing mirror sites.

SLONY_CONFIG                       /home/jsoc/cvs/Development/JSOC/proj/replication/etc/repserver.cfg

###############################

__MAKE__

# Third-party libraries required in order to make NetDRMS binaries. Specify

# a default and also machine-specific locations (if desired). The default will

# be used if no machine-specific entry exists.

# *** PostgreSQL ***

#   defaults

#     PostgreSQL API headers (must contain libpq-fe.h)

POSTGRES_INCS:X86_64    /usr/include

POSTGRES_INCS:AVX       /usr/include

#     the location of the PostgreSQL libs; likely to be either

#     /usr/lib or /usr/lib64 or /usr/local/pgsql/lib

POSTGRES_LIBS:X86_64    /usr/lib64

POSTGRES_LIBS:AVX       /usr/lib64

#     actual library names

POSTGRES_LIB            pq

#   machine-specific

#     The following is an example:

#     POSTGRES_LIBS:N02     /usr/lib64

# *** end PostgreSQL ***

# *** CFITSIO ***

#   defaults

#     CFITSIO API headers (must contain fitsio.h)

CFITSIO_INCS:X86_64     /usr/local/include

CFITSIO_INCS:AVX        /usr/local/include

#     the location of the cfitsio libraries

CFITSIO_LIBS:X86_64     /usr/local/lib64

CFITSIO_LIBS:AVX        /usr/local/lib64

#     actual library names

CFITSIO_LIB             cfitsio

#   machine-specific

#     The following is an example:

#     CFITSIO_LIBS:N02  /usr/lib64

# *** end CFITSIO ***

#################### TAR ####################

# Tar library needed by JMD.

TAR_INCS:X86_64         /usr/include

TAR_INCS:AVX            /usr/include

TAR_LIBS:X86_64         /usr/lib64

TAR_LIBS:AVX            /usr/lib64

################## END TAR ##################

#################### PYTHON ####################

# Python library needed for multi-threaded SUMS (so far).

PY_LIB                  python3.4m

PY_INCS:X86_64          /home/jsoc/ActiveStatePy/linux_x86_64/ActivePython-3.4/include/python3.4m

PY_INCS:AVX             /home/jsoc/ActiveStatePy/linux_avx/ActivePython-3.4/include/python3.4m

PY_LIBS:X86_64          /home/jsoc/ActiveStatePy/linux_x86_64/ActivePython-3.4/lib

PY_LIBS:AVX             /home/jsoc/ActiveStatePy/linux_avx/ActivePython-3.4/lib

PY_HOME:X86_64          /home/jsoc/ActiveStatePy/linux_x86_64/ActivePython-3.4

PY_HOME:AVX             /home/jsoc/ActiveStatePy/linux_avx/ActivePython-3.4

################## END PYTHON ##################

# NetDRMS users can request subdirectories from the Stanford proj directories

# (e.g., JSOC/proj/util). These users will need to contact Stanford and obtain

# the source subdirectories desired. They will then place these subdirectories

# in the JSOC/proj directory of their NetDRMS release. To properly build

# targets in these subdirectories, using the JSOC make system, the user needs

# to add entries to this configuration file - one entry for each subdirectory

# that contains source code to be compiled. Each entry is a space-separated pair

# of strings: the string "PROJDIR" followed by a subdirectory (of the proj

# directory).  For example:

#

# PROJDIR     util/apps

# PROJDIR     util/libs

#

# NOTE: It is not sufficient to list only a parent directory, like util. Source code

# in child directories will not automatically be compiled.

</pre>