| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | == Project Number == |
| | 4 | |
| | 5 | 1788 |
| | 6 | |
| | 7 | == Project Title == |
| | 8 | |
| | 9 | Leveraging and Abstracting Measurements with perfSONAR (LAMP) [[BR]] |
| | 10 | a.k.a. LAMP |
| | 11 | |
| | 12 | === Technical Contacts === |
| | 13 | |
| | 14 | Principal Investigator Martin Swany swany@cis.udel.edu [[BR]] |
| | 15 | Co-PI Eric Boyd eboyd@internet2.edu |
| | 16 | |
| | 17 | === Participating Organizations === |
| | 18 | |
| | 19 | Department of Computer and Information Sciences, University of Delaware [[BR]] |
| | 20 | Internet2 |
| | 21 | |
| | 22 | === GPO Liason System Engineer === |
| | 23 | |
| | 24 | Vic Thomas vthomas@geni.net |
| | 25 | |
| | 26 | == Scope == |
| | 27 | |
| | 28 | The project will create an instrumentation and measurement system, based on perfSONAR, for use by experimenters on ProtoGENI. The project will collaborate on a plan to develop a common GENI instrumentation and measurement architecture with an emphasis on providing a common but extensible format for data storage and exchange. The project will work to develop a representation of GENI topology to be used to describe measurements and experiment configuration, also based on perfSONAR. The project will collaborate with related GENI measurement and security projects (e.g. University of Wisconsin's Instrumentation and Measurement for GENI) on a common GENI instrumentation and measurement architecture. |
| | 29 | |
| | 30 | === Current Capabilities === |
| | 31 | |
| | 32 | BRIEF descriptions of resources/functions/tools that are available to anyone in the GENI community |
| | 33 | |
| | 34 | === Milestones === |
| | 35 | [[MilestoneDate(LAMP: S2.a Requirements and design doc)]] Requirements and design document [[BR]] |
| | 36 | [[MilestoneDate(LAMP: S2.b Prospectus on integration of perfSONAR with other monitoring efforts)]] Prospectus on integration of perfSONAR with other monitoring efforts in GENI [[BR]] |
| | 37 | [[MilestoneDate(LAMP: S2.c Updated prospectus)]] Updated prospectus on integration of perfSONAR with other monitoring efforts in GENI [[BR]] |
| | 38 | [[MilestoneDate(LAMP: S2.d Demonstration of perfSONAR on ProtoGENI)]] Demonstration of perfSONAR on ProtoGENI at GEC [[BR]] |
| | 39 | [[MilestoneDate(LAMP: S2.e V1.0 of perfSONAR on ProtoGENI)]] V1.0 of perfSONAR on ProtoGENI [[BR]] |
| | 40 | [[MilestoneDate(LAMP: S2.f V1.1 of perfSONAR on ProtoGENI)]] Version available to experimenters on GENI [[BR]] |
| | 41 | [[MilestoneDate(LAMP: S2.g Demonstration of perfSONAR on ProtoGENI)]] Demonstration of perfSONAR on ProtoGENI at GEC [[BR]] |
| | 42 | [[MilestoneDate(LAMP: S2.h Evaluation report)]] Report on evaluation of perfSONAR on ProtoGENI [[BR]] |
| | 43 | [[MilestoneDate(LAMP: S2.e V2.0 of perfSONAR on ProtoGENI)]] V2.0 of perfSONAR on ProtoGENI |
| | 44 | |
| | 45 | == Project Technical Documents == |
| | 46 | |
| | 47 | Links to wiki pages for the project's technical documents go here. List should include any document in the working groups, as well as other useful documents. Projects may have a full tree of wiki pages here. |
| | 48 | |
| | 49 | === Quarterly Status Reports === |
| | 50 | |
| | 51 | QuarterlyStatusReportTemplate |
| | 52 | |
| | 53 | |
| | 54 | === Spiral 2 Connectivity === |
| | 55 | |
| | 56 | Links to wiki pages about details of infrastrcture that the project is using (if any). Examples include IP addresses, hostnames, URLs, DNS servers, local site network maps, VLANIDs (if permanent VLANs are used), pointers to public keys. GPO may do first drafts of any of these and have the PI correct them to bootstrap. May also include ticket links for pending or known connectivity issues. Many projects will have a full tree of wiki pages here. |
| | 57 | |
| | 58 | |
| | 59 | === Related Projects === |
| | 60 | |
| | 61 | Includes non-GENI projects. |
