Changes between Version 1 and Version 2 of PlasticSlices/MonitoringRecommendations/MyplcConfiguration
- Timestamp:
- 05/05/11 12:31:10 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PlasticSlices/MonitoringRecommendations/MyplcConfiguration
v1 v2 15 15 * `<cronuser>`: The user as which to run the monitoring on MyPLC. The scripts can run as root, or as a non-root user of your choice. (At GPO, we use the `ganglia` user.) 16 16 * `<site>`: a one-word phrase describing your site, probably the name of your university or lab (e.g. `stanford`, `gpolab`). Use the same value for all hosts your site is monitoring. 17 * `<fqdn>`: The fully-qualified domain name as which your MyPLC should report data. ''IF this is not the same as the output of `uname -n` on your node, pay attention to step 6below.''17 * `<fqdn>`: The fully-qualified domain name as which your MyPLC should report data. ''IF this is not the same as the output of `uname -n` on your node, pay attention to step 5 below.'' 18 18 19 19 == Steps == … … 35 35 }}} 36 36 37 3. Optionally cache packages for later use on !PlanetLab nodes: later, when you follow [wiki:PlasticSlices/MonitoringRecommendations/PlnodeConfiguration], you will install the same packages on your MyPLC !PlanetLab nodes, which you are now installing on the myplc server. IF your nodes cannot run yum, you'll have to install these packages by hand using RPM. In that case, try downloading these packages on your myplc server now, using a program called `yumdownloader`. It may save you from having to resolve dependencies by hand on your nodes later. The steps to download the packages are: 38 {{{ 39 sudo yum install yum-utils 40 mkdir ~/rpms 41 sudo yumdownloader --destdir ~/rpms --resolve rrdtool-python rrdtool-perl perl-File-Find-Rule perl-XML-Writer perl-libwww-perl 42 }}} 43 (You need to do this before you actually install the packages on your myplc, because `yumdownloader` will only download dependencies if they aren't already installed.) 37 3. Install required packages: 38 '''Note:''' Later, when you follow [wiki:PlasticSlices/MonitoringRecommendations/PlnodeConfiguration], you will install these same packages on each of your MyPLC !PlanetLab nodes. IF your plnodes cannot run yum, you'll have to install the RPMs by hand during that step. You may be able to save yourself time by caching the RPMs and their dependencies on your MyPLC ''before'' you actually install them on the MyPLC. Using [wiki:GpoLab/MyplcPackageInstallationTips#UseyumdownloadertodownloadpackagesanddependenciesontheMyPLC yumdownloader to download packages and dependencies] has worked for us. If you want to try that, do it now, before installing the packages on the MyPLC for the first time, or it will be of limited help. 44 39 45 4. Install required packages (whether or not you just downloaded the RPMs for use on your nodes, install them on the myplc itself now):40 Regardless, you should be able to install the packages on the MyPLC itself using yum directly: 46 41 {{{ 47 42 sudo yum install rrdtool-python rrdtool-perl perl-File-Find-Rule perl-XML-Writer perl-libwww-perl … … 52 47 * Send the formatted data to GMOC via HTTP 53 48 54 5. Create required directories:49 4. Create required directories: 55 50 {{{ 56 51 sudo mkdir -p /var/spool/rrds/$(uname -n) … … 59 54 }}} 60 55 61 6. 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:56 5. 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: 62 57 {{{ 63 58 cd /var/spool/rrds … … 65 60 }}} 66 61 67 7. Run the metric-gathering script by hand to make sure it works:62 6. Run the metric-gathering script by hand to make sure it works: 68 63 {{{ 69 64 sudo -u <cronuser> /usr/share/plc_api/plcsh /usr/local/bin/metric_plc … … 72 67 * After this runs, a number of RRD files should be created in `/var/spool/rrds/$(uname -n)` 73 68 74 8. Run the data reporting script by hand to make sure it works:69 7. Run the data reporting script by hand to make sure it works: 75 70 {{{ 76 71 sudo -u <cronuser> /usr/local/bin/report_data_to_gmoc <site> <fqdn> … … 79 74 * You should be able to browse to [http://gmoc-dev.grnoc.iu.edu/api-demo/data/], view data by Location, select your site, and find a new entry for `<fqdn>`. 80 75 81 9. Add the two scripts to cron: modify the `<cronuser>` crontab:76 8. Add the two scripts to cron: modify the `<cronuser>` crontab: 82 77 {{{ 83 78 sudo -u <cronuser> crontab -e