Changes between Version 15 and Version 16 of PlasticSlices/MonitoringRecommendations/PlnodeConfiguration
- Timestamp:
- 06/14/12 16:36:15 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PlasticSlices/MonitoringRecommendations/PlnodeConfiguration
v15 v16 7 7 This page explains how to configure a MyPLC !PlanetLab node for the [wiki:PlasticSlices/MonitoringRecommendations Plastic Slices central monitoring configuration]. This page was written for 8 8 {{{ 9 tango-monitor-plnode-0. 6-19 tango-monitor-plnode-0.7-1 10 10 }}} 11 11 which is the latest version of the monitoring utilities for a MyPLC !PlanetLab node running Fedora 8 or Fedora 12. 12 12 13 == Upgrading from version 0. 4 or later==13 == Upgrading from version 0.6 == 14 14 15 If you are currently running `plastic-slices-monitor-plnode-0.4` or later, you need only do the following steps of this upgrade:15 Version 0.7 of tango-monitor-plnode introduces a config file. If you are currently running a previous version of `tango-monitor-plnode`, you need to do the following steps of this update: 16 16 * [#II.Installthemonitoringsoftware II. Install the monitoring software itself] 17 * [#III.Createrequireddirectoriesandfiles III. Create required directories and files: Step 1 (add a config file for monitoring)] 17 18 * [#IV.Testthescript IV. Test the new script and make sure it still works] 18 * [#V.Installthescriptstorunfromcron V. Install the scripts to run from cron]: the script paths have changed, so you will need to update your crontab.19 19 20 20 If you are installing `tango-monitor-plnode` for the first time or upgrading from an earlier version, read all sections to see which steps you need to take. … … 47 47 === II. Install the monitoring software === 48 48 49 1. Download `tango-monitor-plnode-0. 6-1.noarch.rpm` from [http://software.geni.net/local-sw/], and copy it onto your node, e.g. into `~/tango-monitor-plnode-0.6-1.noarch.rpm`.49 1. Download `tango-monitor-plnode-0.7-1.noarch.rpm` from [http://software.geni.net/local-sw/], and copy it onto your node, e.g. into `~/tango-monitor-plnode-0.7-1.noarch.rpm`. 50 50 51 51 2. Use yum localinstall to install the RPM and any necessary dependencies: 52 52 {{{ 53 sudo yum localinstall ~/tango-monitor-plnode-0. 6-1.noarch.rpm53 sudo yum localinstall ~/tango-monitor-plnode-0.7-1.noarch.rpm 54 54 }}} 55 55 * IF this doesn't work for you because you do not have a working yum on your plnode and can't resolve package dependencies, see [wiki:GpoLab/MyplcPackageInstallationTips#Debuggingmonitoringdependencies] for some other suggestions which might work. … … 57 57 === III. Create required directories and files === 58 58 59 Thesesteps only need to be done the first time you install the monitoring software.59 Step 1 needs to be done when you upgrade to `tango-monitor-plnode-0.7`. The other steps only need to be done the first time you install the monitoring software. 60 60 61 1. Create required directories: 61 1. Populate the gmoc_monitoring configuration file: 62 * Create the config file (the file does not contain sensitive information, and may safely be left world-readable): 62 63 {{{ 63 sudo mkdir -p /var/spool/rrds/$(uname -n) 64 sudo mkdir -p /var/spool/rrds/REPORT 64 /usr/local/etc/gmoc_monitoring.conf 65 }}} 66 * Edit the file and make sure it contains the variables `SITENAME`, `ORGNAME`, and `POPNAME`. ''(N.B. If you are upgrading from a previous version, all three of these variables should contain the `<site>` value you used in the past)'': 67 {{{ 68 $ cat /usr/local/etc/gmoc_monitoring.conf 69 70 # GMOC short name which is your username for authenticated monitoring data submission 71 SITENAME=<site> 72 73 # GMOC short name of organization which manages your aggregate (may be the same as SITENAME) 74 ORGNAME=<site> 75 76 # GMOC short name of "POP"/lab where your aggregate is located (may be the same as SITENAME) 77 POPNAME=<site> 78 79 # Fully qualified hostname of this plnode 80 HOSTNAME=<fqdn> 65 81 }}} 66 82 67 2. IF `uname -n` does not report your node's FQDN for whatever reason, create a symlink so that reporting and reading scripts can find your RRD files:83 2. Create required directories: 68 84 {{{ 69 cd /var/spool/rrds 70 sudo ln -s $(uname -n) <fqdn> 85 sudo mkdir -p /var/spool/rrds/REPORT 71 86 }}} 72 87 … … 87 102 3. Run the data reporting script by hand to make sure it works: 88 103 {{{ 89 sudo /usr/bin/report_data_to_gmoc <site> <fqdn>104 sudo /usr/bin/report_data_to_gmoc 90 105 }}} 91 106 * This should produce no output … … 103 118 {{{ 104 119 */1 * * * * /usr/bin/metric_plnode 105 */5 * * * * /usr/bin/report_data_to_gmoc <site> <fqdn>120 */5 * * * * /usr/bin/report_data_to_gmoc 106 121 }}} 107 122