Changes between Version 22 and Version 23 of LAMP/Tutorial


Ignore:
Timestamp:
09/21/10 22:00:24 (14 years ago)
Author:
fernande@cis.udel.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LAMP/Tutorial

    v22 v23  
    324324In this page we see all the services that are available to us. You can read their description for an overview of the functionality they provide, and you can find more information about them on the links on the bottom of the ''Configuration Status'' page. We will have the following setup for I&M on our slice:
    325325
    326 * '''node1:''' Runs the Host Monitoring Daemon, all latency services and the NTP server (note that NTP is a prerequisite for using OWAMP and BWCTL).
    327 
    328 * '''node2:''' Runs the Host Monitoring Daemon, the bandwidth services and the NTP server.
     326* '''node1:''' Runs the Host Monitoring Daemon, all latency services, BWCTL and the NTP server (note that NTP is a prerequisite for using OWAMP and BWCTL).
     327
     328* '''node2:''' Runs the Host Monitoring Daemon, the bandwidth services, OWAMP and the NTP server.
    329329
    330330* '''lamp:''' Runs the LAMP Portal, the Host Monitoring Collector, the Ganglia MA, and NTP server.
    … …  
    332332We will likely make the NTP server always enabled in the future, since it's usually (always?) desirable. Our flagship visualization service, Periscope, is not included in the RC1 version of the software, but it will hopefully be included soon.
    333333
    334 A couple of things to note. Enabling the host monitoring collector will automatically run the host monitoring daemon on the node. The data measured by the host monitoring daemons is only stored by the host monitoring collector. The Ganglia MA is actually a SNMP MA that wraps the data store of the host monitoring collector and exports it using the perfSONAR API and schemas.
     334A couple of things to note. Even if ''node1'' will not be initiating bandwidth tests itself, BWCTL must still be enabled (both endpoints must have BWCTL running for bandwidth tests to work). The same goes for ''node2'' and OWAMP. Enabling the host monitoring collector will automatically run the host monitoring daemon on the node. The data measured by the host monitoring daemons is only stored by the host monitoring collector. The Ganglia MA is actually a SNMP MA that wraps the data store of the host monitoring collector and exports it using the perfSONAR API and schemas.
    335335
    336336For each node, after selecting the appropriate services we must click the Save button to save the configuration locally.
    … …  
    368368* '''node2:''' Throughput test to node1 at 15 minutes interval (all other parameters default). Note that only ''iperf'' is currently installed on the LAMP image.
    369369
    370 Another change from the pS-Performance Toolkit is that we restrict the hosts that can be selected as targets for the tests to the nodes in the slice topology. We use the localname of each node so that the addresses on the virtual topology will be used for the tests (i.e. tests will not go through the control plane). The configuration for each node should look like this:
     370Another change from the pS-Performance Toolkit is that we restrict the hosts that can be selected as targets for the tests to the nodes in the slice topology. We use the localname of each node so that the addresses on the virtual topology will be used for the tests (i.e. tests will not go through the control plane). Because of this we have to emphasize that '''both''' endpoints must be running the corresponding daemon (BWCTL for throughput tests and OWAMP for one-way delay tests). In the near future, we intend to filter the possible targets by checking the daemons registered on UNIS (as it is done on the pS-Performance Toolkit, but here restricted to the slice topology). The configuration for each node should look like this:
    371371
    372372[[Image(node1-pinger.png)]]