LAMP: Bringing perfSONAR to ProtoGENI

Martin Swany

perfSONAR Overview

• The perfSONAR framework provides key components necessary in a large-scale, federated, interoperable measurement infrastructure– Information service (topology and service discovery)– Measurement points and archives

• Developed and deployed by research and education networks– Internet2, ESnet, GEANT, and RNP– Other international networks

perfSONAR

• Open and extensible formats• Separation of data and metadata• Extensible topology and service schema

called UNIS– Also used by Internet2 ION, ESnet OSCARs

LAMP

• LAMP integrates perfSONAR to provide extensible, unified network and host metrics in a common interface for GENI experiments– A measurement metadata format and storage

infrastructure that can be extended to uniformly store all instrumentation within the GENI system

• Provides a measurement portal with control and visualization interfaces to the user

• Interoperates with existing security model within ProtoGENI

LAMP Workflow1. User provides a resource specification annotated with an initial LAMP configuration

– Specifies a dedicated “portal” node, the custom LAMP disk image, and bootstrap behavior

2. User creates a slice and allocates requested sliver resources

3. Resulting manifest and slice credential are sent to UNIS with provided scripts– UNIS now contains a representation of the experimental topology with I&M

properties

4. Once the user’s slivers become active, the portal is reachable only with proper slice credentials from the SA

5. The user may then activate a number of measurement services from the portal, including:

– Host monitoring (CPU, memory, disk, network)– Scheduled throughput and delay testing– Experiment-wide NTP services– The Periscope topology and measurement visualization tool

6. Current LAMP I&M configuration is saved and pushed to a UNIS store

7. Configured systems within the experiment pull and apply the configuration, collecting and reporting measurements within instantiated MAs

Periscope