This site has been archived. For information on the GN Project’s eduPERT initiative please visit https://archive.geant.org/projects/gn3/geant/services/edupert/Pages/Home.html

Workshop Agenda

09:0009:30WelcomeSlidesHands-On CommandsHandouts (print) 
09:3009:50perfSONAR Architecture, workshop objectives, lab setuppS - Architecture—pS - ArchitectureAD
09:5010:10Central Measurement ArchiveSee pS - Architecture install + confSee pS - Architecture AD
10:1011:00Measurement MeshMesh ConfigconfigurationMesh ConfigIG
11:0011:20Break    
11:2011:50Measurement Point configurationMP ConfigconfigurationMP ConfigIG
11:5012:30Dashboard setupsee pS - Architecture configurationSee pS - Architecture AD
12:3013:30Lunch    
13:3013:50Measurements Analysis   IG
13:5015:00Tuning and AutomationPuppet Config Puppet ConfigIG - AD
15:0015:20Break    
15:2015:40

perfSONAR Roadmap Update

pS Roadmap——AD
15:4016:30perfSONAR Advanced FeaturesMaDDash, pScheduler——AD - IG

Hands-On Commands

Central Measurement Archive

Installation

With these commands, you'll install all you need to run a central server (measurement archive software: esmond and dashboard software: maddash) on your central server.

Run as root 
rpm -hUv http://software.internet2.edu/rpms/el6/x86_64/main/RPMS/Internet2-repo-0.6-1.noarch.rpm
yum install Internet2-repo-staging
rpm -hUv https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
yum install perfsonar-centralmanagement

Configuration

Configuration files

Configuration files involved (but no change should be required):

  • /etc/cassandra/
  • /etc/esmond/
  • /etc/httpd/conf.d/apache-esmond-proxy.conf
  • /opt/rh/httpd24/root/etc/httpd/conf.d/apache-esmond.conf

Log files

Log files to check:

  • /var/log/esmond/

  • /var/log/cassandra/
  • /var/log/httpd/
  • /var/log/httpd24/
Run as root 
# Examples:
tail /var/log/httpd/error_log
less /var/log/esmond/esmond.log

IP Authentication

With these commands, you'll configure esmond to accept data coming from a set of IP.

Run as root 
# if esmond API key not set by the install process
/usr/lib/perfsonar/scripts/system_environment/configure_esmond
# IP based authorization
cd /usr/lib/esmond
source /opt/rh/python27/enable
/opt/rh/python27/root/usr/bin/virtualenv --prompt="(esmond)" .
. bin/activate
python esmond/manage.py add_user_ip_address edupert_users 10.0.160.0/19

Verifying

Then check the cassandra, httpd, httpd24 and postgres processes are running. esmond, through httpd and httpd24, is listening on port 80 and 11413.  cassandra is listening on port 9160, postgres on port 5432  You should also be able to visit the esmond webinterface at an URL like http://pertcsxy.switch.ch/esmond/perfsonar/archive/

Run as root 
ps aux | grep httpd
ps aux | grep cassandra
ps aux | grep postgresql
netstat -tunlep
chkconfig
# If needed (but shouldn't be)
chkconfig cassandra on
chkconfig https on

Measurement Mesh

Run as root 
## Get an example of meshconfig template file (XML)
curl http://pertcs01.switch.ch/trainmesh.xml > mesh-config.xml


## Convert meshconfig in JSON
/usr/lib/perfsonar/bin/build_json -o mesh-config.json mesh-config.xml


## simply publish in /var/www/html

 

Measurement Point configuration

Run as root 
## General mesh configuration + admin + reloads + pscheduler + tasks
/etc/perfsonar/meshconfig-agent.conf


## Specific tests from mesh and Esmond archives
/etc/perfsonar/meshconfig-agent-tasks.conf


## services:
service perfsonar-meshconfig-agent restart
service pscheduler-scheduler restart


## logs:
/var/log/perfsonar/meshconfig-agent.log
/var/log/messages
/var/lib/perfsonar/meshconfig/psc_tracker


## pScheduler commands:
psc debug off
psc task simplestream --timeout PT5S --source pertmp01 --dest pertmp02
psc task rtt --debug --count 100 --source pertmp01 --ip-version 4 --dest pertmp02
psc task latency --count 100 --source pertmp01 --ip-version 4 --dest pertmp02

Dashboard setup

Installation

Installation of MaDDash has already been done when installing the perfsonar-centralmanagement bundle package.

Configuration

Configuration files

Configuration files involved:

  • /etc/maddash/maddash-server/maddash.yaml
  • /etc/maddash/maddash-webui/config.json
  • /etc/perfsonar/meshconfig-guiagent.conf

Log files

Log files to check:

  • /var/log/maddash/
  • /var/log/httpd/

Verifying

Checking the public dashboard at http://pertcsxy.switch.ch/maddash-webui/  If a change is done to the maddash-webui/config.json file, reload it from http://pertcsxy.switch.ch/maddash-webui/etc/config.json

Run as root 
cd /etc/maddash/maddash-webui
# Compare config.json and config.example.json
vi config.json

# Reload http://pertcsXY.switch.ch/maddash-webui/etc/config.json in your browser after change!

# Add an HTML redirect in /var/www/html/index.html or in your apache config

# Check running processes
ps aux | grep maddash
ps aux | grep https
 
# Check log files
tail /var/log/httpd/access_log
 
# Start, stop or restart service
/etc/init.d/maddash-server start|stop|restart

Tuning and Automation

 

  • No labels