Building LDMS For Generic Linux Distributions

Table of Contents Modify your build environment to use the gnu compiler Building LDMS and support libraries and headers Building libevent-2.0 Building LDMS Running LDMS

Modify your build environment to use the gnu compiler

If your platform environment does not use "modules", then set PATH and LD_LIBRARY_PATH environment variables appropriately and skip the rest of this section.

• Using the "module" command
  • module avail -- prints available modules
  • module list -- lists currently loaded modules
  • module unload <module name> -- unloads named module
  • module load <module name> -- loads named module
• Examples (actual file names and responses will be system dependent):

 $ module list
 Currently Loaded Modulefiles:
   1) intel/vtune/2017.0.2

 $ module unload intel

 $ module list
 No Modulefiles Currently Loaded.

 $ module load gcc
 $ module list
 Currently Loaded Modulefiles:
  1) binutils/2.26.0  2) gcc/6.2.0

Building LDMS and support libraries and headers

• Download ovis and gpcd from github.com/ovis-hpc. For example, click the download button to obtain the directory "ovis-master".
• Download libevent-2.0.x-stable from libevent.org, if it is not already installed on your system.
• In this example source files are assumed to be in ~/Source and builds in ~/Build

Building libevent-2.0

If libevent-2.0 is already installed on your system, you may skip this step.

• Unpack the libevent source:

  cp <path>/libevent-2.0.x-stable.tar.gz ~/Source 
  cd ~/Source
  untar libevent-2.0.x-stable.tar.gz
  cd libevent-2.0.x-stable

• Run autogen.sh

 ./autogen.sh

• Create config file (in this example, call it configure.sh) with the following:

 ../configure --prefix=<absolute path>/Build/libevent-2.0_build

• Make configure.sh executable

 chmod +x configure.sh

• Configure, build, and install libevent-2.0 libs and includes

 mkdir build
 cd build
 ../configure.sh
 make
 make install

Building LDMS

• Obtain the submodules for the source

 cd <absolute_path>/Source
 cd ovis-master
 git submodule init
 git submodule update sos

• Run autogen.sh

 ./autogen.sh

• Create a build directory

 mkdir build

• cd to build directory and configure

 cd build
 ../configure --prefix=<absolute_path>/Build/OVIS-3.4 --enable-sos --enable-baler --enable-swig --enable-python 

• Build and install ldms libs, executables, and includes

 make && make install

Running LDMS

• README files and sample scripts reside in the ovis-master/util/sample_init_scripts/XXX directory.
  • Note that the scripts must be modified, as described in the README file, to fit a particular deployment configuration.

QuickStart Example:

• Set up environment

 TOP=<absolute_path>/Build/OVIS-3.4
 export LD_LIBRARY_PATH=$TOP/lib/:$TOP/lib:$LD_LIBRARY_PATH
 export LDMSD_PLUGIN_LIBPATH=$TOP/lib/ovis-ldms/
 export ZAP_LIBPATH=$TOP/lib/ovis-lib/
 export PATH=$TOP/sbin:$TOP/bin:$PATH
 export PYTHONPATH=$TOP/lib/python2.7/site-packages/

• Use this if using shared secret authentication

 export LDMS_AUTH_FILE=<absolulte_path>/ldmsauth.conf

• Make a configuration file (called meminfo.conf) to load the meminfo sampler with the following contents:

 load name=meminfo
 config name=meminfo producer=${HOSTNAME} instance=${HOSTNAME}/meminfo component_id=${COMPONENT_ID} schema=meminfo job_set=${HOSTNAME}/jobinfo
 start name=meminfo interval=${SAMPLE_INTERVAL} offset=${SAMPLE_OFFSET}

• Set up environment variables for configuration file

 export COMPONENT_ID=2
 export SAMPLE_INTERVAL=1000000
 export SAMPLE_OFFSET=50000

• Run a daemon

 ldmsd -x sock:10444 -c meminfo.conf -l /tmp/demo_ldmsd_log -v DEBUG

• Run ldms_ls to see set, meta-data, and contents

 ldms_ls -h localhost -x sock -p 10444
 ldms_ls -h localhost -x sock -p 10444 -v
 ldms_ls -h localhost -x sock -p 10444​ -l