315 | | |
316 | | |
| 315 | The first time the LAMP Portal is opened it will query UNIS and retrieve the set of configurable nodes and their current configuration. The home page that we're seeing on the above image is the ''Configuration Status'' page on the left sidebar. Here we can see all the LAMP nodes on our slice and their current services. We also see the date we last fetched the topology information from UNIS and that we haven't modified it. |
| 316 | |
| 317 | |
| 318 | === 6. Enabling/Disabling Services === |
| 319 | |
| 320 | At this moment we can see that no I&M services are running on our slice. To remedy this situation we click on the ''Enabled Services'' link under the ''Configuration'' menu on the left sidebar. |
| 321 | |
| 322 | [[Image(portal2.png)]] |
| 323 | |
| 324 | In 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: |
| 325 | |
| 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. |
| 329 | |
| 330 | * '''lamp:''' Runs the LAMP Portal, the Host Monitoring Collector, the Ganglia MA, and NTP server. |
| 331 | |
| 332 | We 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. |
| 333 | |
| 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 an SNMP MA that wraps the data store of the host monitoring collector and exports it using the perfSONAR API and schemas. |
| 335 | |
| 336 | For each node, after selecting the appropriate services we must click the Save button to save the configuration locally. |
| 337 | |
| 338 | [[Image(portal3.png)]] |
| 339 | |
| 340 | |
| 341 | |
| 342 | |
| 343 | |
| 344 | |