Changes between Version 3 and Version 4 of LAMP-FirstQuarter2011
- Timestamp:
- 03/31/11 12:51:13 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LAMP-FirstQuarter2011
v3 v4 9 9 === A. Milestones achieved === 10 10 11 * Completed S3.d and S3.e milestones. 12 11 13 === B. Deliverables made === 12 14 15 * Demonstrated LAMP system for experimenters at GEC10. 16 * Updated documentation for LAMP perfSONAR Skeleton 13 17 14 18 == II. Description of work performed during last quarter == … … 17 21 18 22 '''Activity:''' Discussions with I&M WG and Utah’s ProtoGENI team regarding measurement and topology representation (RSpec). [[BR]] 19 '''Description:''' LAMP project members believe that leveraging the existing topology (referred to as UNIS schema in this document) used by projects like perfSONAR, Inter-Domain Controller Protocol (and thus Internet2’s ION, OSCARS and GÉANT2 AutoBAHN), Phoebus, among others, to represent the topology elements in GENI’s RSpec and related schemas would provide several benefits (e.g. a more general and tested topology model, easier integration with Measurement and O&M planes). One of the overarching goals of the LAMP project is to leverage perfSONAR to create interoperability between the different I&M systems, and work towards a unified measurement architecture for GENI. [[BR]]20 23 '''Findings:''' 21 24 * Martin Swany gave a presentation on UNIS at RSpec Meeting at GEC10. A general consensus has been reached that the ProtoGENI RSpec will be adopted as the general RSpec within GENI. There was recognition of the fact that the core RSpec cannot currently represent all current and future use-cases and that the core specification should remain easily extensible using a namespacing extension mechanism. 22 25 * Martin Swany served on the I&M WG panel. No general consensus was reached. The perfSONAR measurement schema was discussed as a likely contender to provide a common measurement representation across CFs. 23 26 [[BR]][[BR]] 24 '''Activity:''' Network monitoring of the ProtoGENI backbone using perfSONAR. [[BR]] 25 '''Description:'''We have started a measurement infrastructure of the ProtoGENI backbone using perfSONAR. The infrastructure is currently retrieving SNMP data from the HP switches in Internet2’s Washington, Salt Lake and Kansas POPs. The data is made available to Utah’s ProtoGENI team through perfSONAR’s SNMP MA and related GUIs. 27 '''Activity:''' Network monitoring of the ProtoGENI backbone using perfSONAR. [[BR]] 26 28 '''Findings:''' 27 29 * This service has been working continuously since the last quarter. … … 31 33 [[BR]][[BR]] 32 34 '''Activity:''' Development of a perfSONAR-based I&M system for GENI experimenters. [[BR]] 33 '''Description:''' A proof-of-concept I&M system will be developed using the current perfSONAR framework (architecture and services) to show how perfSONAR adapts to the GENI environment. This system will provide great flexibility to experimenters in choosing performance metrics ranging from SNMP data to active measurements to mix-and-match based on the experimenters’ needs. [[BR]]34 35 '''Findings: ''' 35 36 * The latest LAMP developments were presented at the GEC10 Demo Session 37 * LAMP I&M "Portal" to control active and passive measurements 38 * Complete host monitoring 39 * Experiment topology visualization 40 * Mapping measurements to interactive topology 41 * Cross-CM measurements with stitching between Utah and Kentucky nodes 36 42 37 43 === B. Project participants === … … 47 53 48 54 === D. Outreach activities === 49 No outreach activities. 55 * Engaged w/ RENCI researchers on integrating measurement 56 infrastructure into the LAMP perfSONAR Skeleton 57 * Engaged with experimenters attending the 1st Doctoral Consortium 58 * Demonstrated and discussed the use of LAMP I&M within experiments 50 59 51 60 === E. Collaborations ===