1 / 7

LAMP Spiral 2 Year-end Project Review

LAMP Spiral 2 Year-end Project Review. LAMP. University of Delaware PI: Martin Swany Staff: Eric Boyd, Jason Zurawski , Internet2 Students: Guilherme Fernandes , Ezra Kissel 29-August-2010. Project Summary.

berit
Download Presentation

LAMP Spiral 2 Year-end Project Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. LAMPSpiral 2 Year-end Project Review LAMP University of Delaware PI: Martin Swany Staff: Eric Boyd, Jason Zurawski, Internet2Students: GuilhermeFernandes, Ezra Kissel 29-August-2010

  2. Project Summary • LAMP (Leveraging and Abstracting Measurements with perfSONAR) is an effort to use and extend the perfSONAR system for Instrumentation and Measurement (I&M) in ProtoGENI • perfSONAR (www.perfsonar.net) has wide adoption in research and education networks • One key to the success of perfSONAR system is its extensibility • Ability to wrap many data sources, while fully capturing relevant metadata • Key Goals of LAMP • Inclusion of various modes of operation • Slice creation with embedded I&M • Dynamic dedicated monitoring slice • Access to persistent I&M services • Generic metadata, including slice topology and data description to provide “lingua franca” for various I&M projects • Easy access to commonly-desired data • Easy support for experiment-specific metrics • Exploratory work toward GENI I&M Architecture 29-August-2010

  3. Milestone & QSR Status 29-August-2010

  4. Accomplishments 1: Advancing GENI Spiral 2 Goals • One of the main Spiral 2 goals was to establish various Instrumentation and Measurement (I&M) Systems and to work toward a strawman proposal for a GENI-wide framework • LAMP has the twin goals of a working system and exploratory investigation toward the larger framework • The LAMP team has actively participated in the I&M WG to advance the I&M Architecture • This effort has been substantial and wasn’t reflected in our original milestones! • Development of an I&M System Prototype that integrates perfSONAR in ProtoGENI, while serving as a continuous experimenter • This helped improve the Control Framework by identifying needs of I&M systems, providing feedback on general CF use/design, and generating bug reports • We have paid substantial attention to Interoperability by understanding the various RSpecs used by CFs and looking toward a common representation • Similarly, we have faced Identity Management questions from the outset, and have worked toward support for this in LAMP 29-August-2010

  5. Accomplishments 2:Other Project Accomplishments • Deployed perfSONAR measurement infrastructure for ProtoGENI backbone nodes • Substantial integration with ProtoGENI • I&M infrastructure deployment and bootstrapping integrated with the CF • ProtoGENI AA support added to perfSONAR services and global infrastructure • ProtoGENIRSpec translated into UNIS topology schema • Developed a different approach for bootstrapping and configuring the perfSONAR I&M infrastructure that • Nodes configure themselves by retrieving annotations on the topology description of the slice • Continuous configuration changes possible • Nodes can push changes back into the topology description so that information is up-to-date (e.g. IP addresses) • The measurement and (UNIS) topology schema integration in the LAMP I&M system demonstrates a possible solution for storing and sharing measurement data from virtual topologies (i.e. non-public IP addresses, etc) 29-August-2010

  6. Issues • We (LAMP) need to improve in our completion (and revision if necessary) of project milestones • When we became substantially involved in the I&M WG, we let our own milestone languish as the analysis and description was largely the same • Lack of instrumentation/measurement resources (e.g. measurement boxes) at various aggregates • Creates difficulties in integrating substrate and slice measurement planes • Topology of the substrates should be described in more detail • Lack of dedicated measurement plane network • CFs and RSpecs are very different underneath • This will be a major barrier to fully integrating I&M systems to all CFs (i.e. bootstrapping, determining virtual topology vs physical topology mappings (including hostnames/IPs), etc). 29-August-2010

  7. Plans • Integrating the rest of the perfSONAR-PS services • Adapting the pS-PS-Toolkit web configuration tool for managing distributed services through changes to UNIS • Making the topology based (node) configuration service a full blown pS service • Improve GUIs available to GENI experimenters for visualizing perfSONAR data of slices (Periscope, perfAdmin, others) • Public release of software available to all experiments with documentation and user manual • Continued emphasis on GENI I&M Architecture document and discussion • The GPO is starting to formulate goals for Spiral 3. What are your thoughts regarding potential Spiral 3 work? • An increased emphasis on common language and more correspondence in RPecs. Diversity is good, but not for its own sake. 29-August-2010

More Related