| | 1 | == Project Number == |
| | 2 | |
| | 3 | 1892 |
| | 4 | |
| | 5 | == Project Title == |
| | 6 | InstaGENI: An instant worldwide GENI Network [[BR]] |
| | 7 | a.k.a. INSTAGENI |
| | 8 | |
| | 9 | === Technical Contacts === |
| | 10 | |
| | 11 | '''PI''': Rick McGeer, HP Labs, rick.mcgeer@hp.com [[BR]] |
| | 12 | |
| | 13 | |
| | 14 | |
| | 15 | === Participating Organizations === |
| | 16 | |
| | 17 | HP Labs [[BR]] |
| | 18 | |
| | 19 | |
| | 20 | |
| | 21 | |
| | 22 | === GPO Liaison System Engineer === |
| | 23 | |
| | 24 | '''GPO System Engineer:''' [mailto:hdempsey@bbn.com Heidi Dempsey] |
| | 25 | |
| | 26 | == Scope == |
| | 27 | |
| | 28 | This project will design, document, build, deploy and support GENI racks at sites that are interested in experimentation and integration with GENI. The main hardware components of each rack include an HP OpenFlow switch, an HP Blade chassis, and at least three dual-socket quad-core blade servers. Each server will include 4TB storage and HP Integrated Lights-Out Management software (iLO) providing in-situ remote monitoring and remote management, including reboot and diagnosis functions. [[BR]] |
| | 29 | This project will fully integrate, test, and maintain a complete software system for managing and monitoring rack resources. Each GENI rack will be fully compliant with GENI software standards for GENI aggregates, as published at GENI Engineering Conferences. Each rack will provide a single GENI Aggregate Manager controlling access to the rack’s on-board resources. The racks will support GENI experimenter access via the GENI control framework, and credentials from all GENI-federated trust authorities, as published at GENI Engineering Conferences. Each rack will support shared GENI monitoring and operations procedures and interfaces for the meso-scale infrastructure as published at GENI Engineering Conferences. [[BR]] |
| | 30 | The project will provide software support for the racks, which includes hardware and software monitoring, bug reporting and fixing, integration and testing, scalability and security enhancements as needed, and updates to comply with published GENI software standards. The project will play an active role in discussions about new standards for GENI software. The project will support GENI architecture and prototyping activities for rack forensics, stitching, and integration with GENI Instrumentation and Measurement systems. |
| | 31 | |
| | 32 | |
| | 33 | === Current Capabilities === |
| | 34 | |
| | 35 | BRIEF descriptions of resources/functions/tools that are available to anyone in the GENI community |
| | 36 | |
| | 37 | == Milestones == |
| | 38 | |
| | 39 | == Spiral 4 == |
| | 40 | |
| | 41 | |
| | 42 | |
| | 43 | == Project Technical Documents == |
| | 44 | |
| | 45 | 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. |
| | 46 | |
| | 47 | === Quarterly Status Reports === |
| | 48 | |
| | 49 | QuarterlyStatusReportTemplate |
| | 50 | |
| | 51 | due 31Dec09: [wiki:ProjTemp-4Q09-status 4Q09 Status Report] |
| | 52 | |
| | 53 | === Spiral 2 Connectivity === |
| | 54 | |
| | 55 | 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. |
| | 56 | |
| | 57 | |
| | 58 | === Related Projects === |
| | 59 | |
| | 60 | [http://URL Project-Name] |
| | 61 | Includes non-GENI projects. |
