Changes between Version 8 and Version 9 of PlasticSlices/MonitoringRecommendations/FoamConfiguration
- Timestamp:
- 06/14/12 16:16:02 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PlasticSlices/MonitoringRecommendations/FoamConfiguration
v8 v9 7 7 This page explains how to configure an !OpenFlow FOAM server for [wiki:PlasticSlices/MonitoringRecommendations central GENI operational monitoring]. This page was written for 8 8 {{{ 9 tango-monitor-foam_0. 2-39 tango-monitor-foam_0.3-1 10 10 }}} 11 11 and may not work well with earlier versions. We have tested the FOAM utilities on Ubuntu 10.04 only, but expect they will also work on CentOS. If you are running a different OS and it is not obvious how to translate the instructions, please contact GPO infra. … … 13 13 == Upgrading from previous versions == 14 14 15 If you are currently running a previous version of `tango-monitor-foam`, you need only do the following steps of this update: 16 * [#II.Installthemonitoringsoftware II. Upgrade the monitoring software itself] 17 * [#IV.Testthescript IV. Test the new script and make sure it still works] 15 Version 0.3 of tango-monitor-foam introduces a new dependency and a config file. If you are currently running a previous version of `tango-monitor-foam`, you need to do the following steps of this update: 16 * [#II.Installsoftwaredependencies II. Install software dependencies] 17 * [#III.Installthemonitoringsoftware III. Upgrade the monitoring software itself] 18 * [#IV.Createrequireddirectoriesandfiles IV. Create required directories and files: Step 1 (add a config file for monitoring)] 19 * [#V.Testthescript V. Test the new script and make sure it still works] 18 20 19 21 If you are installing `tango-monitor-foam` for the first time or upgrading from an earlier version, read all sections to see which steps you need to take. … … 23 25 * `<cronuser>`: The user as which to run the FOAM monitoring. The scripts can run as root, or as a non-root user of your choice. (At GPO, we use the `ganglia` user.) 24 26 * `<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. 25 * `<fqdn>`: The fully-qualified domain name as which your FV should report data. ''IF this is not the same as the output of `uname -n` on your node, pay attention to section III step 2 below.''26 27 27 28 == Steps to configure FOAM monitoring == … … 44 45 3. Register site credentials: IF you have not yet registered your site to submit data to GMOC, follow the instructions at [wiki:GENIMetaOps/SiteCredentials]. 45 46 46 === II. Install the monitoring software === 47 === II. Install software dependencies === 48 49 === III. Install the monitoring software === 47 50 48 51 Do these steps every time you install or upgrade the monitoring software. … … 50 53 ==== If you are installing on Ubuntu ==== 51 54 52 1. Download the `tango-monitor-foam_0. 2-3.deb` package file from [http://software.geni.net/local-sw/], and copy it onto your FOAM host, e.g. into `~/tango-monitor-foam_0.2-3.deb`.55 1. Download the `tango-monitor-foam_0.3-1.deb` package file from [http://software.geni.net/local-sw/], and copy it onto your FOAM host, e.g. into `~/tango-monitor-foam_0.3-1.deb`. 53 56 54 57 2. Use dpkg to install the local package. This may fail due to dependencies and say it is leaving the package "unconfigured". Therefore, invoke apt-get to fix any missing dependencies: 55 58 {{{ 56 sudo dpkg -i ~/tango-monitor-foam_0. 2-3.deb59 sudo dpkg -i ~/tango-monitor-foam_0.3-1.deb 57 60 sudo apt-get -f install 58 61 }}} … … 60 63 ==== If you are installing on CentOS ==== 61 64 62 1. Download the `tango-monitor-foam-0. 2-3.noarch.rpm` package file from [http://software.geni.net/local-sw/], and copy it onto your FOAM host, e.g. into `~/tango-monitor-foam-0.2-3.noarch.rpm`.65 1. Download the `tango-monitor-foam-0.3-1.noarch.rpm` package file from [http://software.geni.net/local-sw/], and copy it onto your FOAM host, e.g. into `~/tango-monitor-foam-0.3-1.noarch.rpm`. 63 66 64 67 2. Use yum localinstall to install the local package. This will install the provided file, using your standard yum repositories to find any dependencies: 65 68 {{{ 66 sudo yum localinstall ~/tango-monitor-foam-0. 2-3.noarch.rpm69 sudo yum localinstall ~/tango-monitor-foam-0.3-1.noarch.rpm 67 70 }}} 68 71 69 === I II. Create required directories and files ===72 === IV. Create required directories and files === 70 73 71 These steps only need to be done the first time you install the monitoring software. 74 Step 1 needs to be done when you upgrade to `tango-monitor-foam-0.3`. The other steps only need to be done the first time you install the monitoring software. 75 76 1. Populate the gmoc_monitoring configuration file: 77 * Create the config file (the file does not contain sensitive information, and may safely be left world-readable): 78 {{{ 79 /usr/local/etc/gmoc_monitoring.conf 80 }}} 81 * Edit the file and make sure it contains the variables `SITENAME`, `ORGNAME`, and `POPNAME`: 82 {{{ 83 $ cat /usr/local/etc/gmoc_monitoring.conf 84 85 # GMOC short name which is your username for authenticated monitoring data submission 86 SITENAME=<site> 87 88 # GMOC short name of organization which manages your aggregate (may be the same as SITENAME) 89 ORGNAME=<site> 90 91 # GMOC short name of "POP"/lab where your aggregate is located (may be the same as SITENAME) 92 POPNAME=<site> 93 }}} 72 94 73 1. Create required directories:95 2. Create required directories: 74 96 {{{ 75 97 sudo mkdir -p /var/cache/fvmetrics/monitoring 76 98 sudo chown <cronuser> /var/cache/fvmetrics/monitoring 77 99 78 sudo mkdir -p /var/spool/rrds/$(uname -n)79 100 sudo mkdir -p /var/spool/rrds/REPORT 80 101 sudo chown -R <cronuser> /var/spool/rrds 81 }}}82 83 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:84 {{{85 cd /var/spool/rrds86 sudo ln -s $(uname -n) <fqdn>87 102 }}} 88 103 … … 93 108 This file should contain the admin password for FOAM. (This is the password you use with `foamctl` to run FOAM commands.) 94 109 95 === IV. Test the script ===110 === V. Test the script === 96 111 97 112 Run the monitoring and submission scripts by hand to make sure they work. … … 104 119 }}} 105 120 * This should produce no output 106 * After this runs, a number of RRD files should be created in `/var/spool/rrds/ $(uname -n)`121 * After this runs, a number of RRD files should be created in `/var/spool/rrds/metrics` 107 122 108 123 3. Run the data reporting script by hand to make sure it works: 109 124 {{{ 110 sudo -u <cronuser> /usr/bin/report_data_to_gmoc <site> <fqdn>125 sudo -u <cronuser> /usr/bin/report_data_to_gmoc 111 126 }}} 112 127 * This should produce no output 113 * You should be able to browse to [http://gmoc-db.grnoc.iu.edu/api-demo/], view data by Location, select your site, and find an entry for `<fqdn>`.128 * You should be able to browse to [http://gmoc-db.grnoc.iu.edu/api-demo/], view data by Location, select your site, and find an entry for your node. 114 129 115 === V . Install the scripts to run from cron ===130 === VI. Install the scripts to run from cron === 116 131 117 132 This only needs to be done the first time you install the monitoring software. … … 124 139 {{{ 125 140 */1 * * * * /usr/bin/metric_foam 126 */5 * * * * /usr/bin/report_data_to_gmoc <site> <fqdn>141 */5 * * * * /usr/bin/report_data_to_gmoc 127 142 }}}