Changes between Version 4 and Version 5 of PlasticSlices/MonitoringRecommendations/FlowvisorConfiguration
- Timestamp:
- 05/05/11 10:16:26 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PlasticSlices/MonitoringRecommendations/FlowvisorConfiguration
v4 v5 70 70 Either create a file in this location containing only the flowvisor root password, or create a file in a different location containing the password, and modify `/usr/local/bin/metric_flowvisor` to look in the new location. 71 71 72 7. Start the metric-gathering service: 72 7. The `metric_flowvisor` service init script contains a variable indicating which username to use when running the metric daemon. 73 * Edit the file `/etc/init.d/metric_flowvisor` 74 * Near the top of that file, correct the METRIC_USER setting for your environment: 75 {{{ 76 METRIC_USER=<daemonuser> 77 }}} 78 8. Start the metric-gathering service: 73 79 {{{ 74 80 sudo service metric_flowvisor start … … 81 87 * Within two minutes or so, a number of RRD files should be created in `/var/spool/rrds/$(uname -n)` 82 88 83 8. Run the data reporting script by hand to make sure it works:89 9. Run the data reporting script by hand to make sure it works: 84 90 {{{ 85 91 sudo -u <daemonuser> /usr/local/bin/report_data_to_gmoc <site> <fqdn> … … 88 94 * 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>`. 89 95 90 9. Configure the metric-gathering service to start at boot:96 10. Configure the metric-gathering service to start at boot: 91 97 {{{ 92 98 sudo update-rc.d metric_flowvisor defaults 93 99 }}} 94 1 0. Add the reporting script to cron: modify the `<daemonuser>` crontab:100 11. Add the reporting script to cron: modify the `<daemonuser>` crontab: 95 101 {{{ 96 102 sudo -u <daemonuser> crontab -e