| | 36 | The scope of work of our proposal consists of four interdependent core activities involving development and prototyping, infrastructure development, early federation experiments and opt-in support capabilities, and education and outreach. The following sections detail these activities. |
| | 37 | |
| | 38 | '''Development and Prototyping Activities''': PrimoGENI includes the following major activities, with the objective of substantially broadening GENI’s prospect in supporting realistic, scalable, and flexible experimental networking studies: |
| | 39 | * A prototype implementation of PrimoGENI, which includes augmenting PRIME with the GENI aggregate interface, so that PrimoGENI will be able to support large-scale network experiments consisting of simulated, emulated and physical network entities. |
| | 40 | * An early adoption of the ProtoGENI control framework, through which researchers will be able to remotely launch, monitor, control, and thus realize large-scale network experiments consisting of both PrimoGENI and other GENI components. |
| | 41 | * An exploitation of the full potential of real-time simulation capabilities, with special emphasis on the design and implementation of PrimoGENI experiment workflow (including network model construction, resource specification, allocation and sharing), experiment monitoring, instrumentation and measurement capabilities. |
| | 42 | |
| | 43 | '''Infrastructure Development''': PrimoGENI proposes to augment the GENI suite of interoperable infrastructure to enable large-scale experiments involving both physical and simulated networked components. To achieve this large-scale goal, PrimoGENI has broad support from academic, research and industry partners, both domestic and international. Through their participation, we will integrate the following components and substrate technologies in support of large-scale federated experiments: |
| | 44 | * Geographically distributed computational nodes located in Miami at FIU, AMPATH, NAP of the Americas, and in Brazil. |
| | 45 | * Regional backbone nodes to Florida LambdaRail (FLR) and national backbone nodes to Internet2, National LambdaRail (NLR) and Cisco Research Wave (C-Wave) to establish non-dedicated configurable end-to-end connections to GENI resources. |
| | 46 | * International backbone nodes between the U.S. and Brazil, connecting the KyaTera research network in the State of Sao Paulo and the Project GIGA optical testbed, run by RNP, Brazil’s national research and education network. |
| | 47 | |
| | 48 | '''Early Federation Experiments and Opt-in Support Capabilities''': PrimoGENI will motivate the federation with GENI components and aggregates, including: |
| | 49 | * Federating with international collaborators, leveraging FIU's unique position and strategic partnership connecting end-users, researchers and interested stakeholders in South America. |
| | 50 | * Extending PRIME’s existing support for real applications (such as web services, peer-to-peer systems, and multimedia streaming) and developing case studies and demonstrations of new network services and applications (such as conducting performance evaluation of Grid applications with our Brazil research partners), with the goal of attracting early adoption as well as opt-in end-users for PrimoGENI. |
| | 51 | |
| | 52 | '''Outreach and Evaluation Activities''': |
| | 53 | |
| | 54 | * An integrated education, training and outreach plan, which includes organizing PrimoGENI tutorials, lectures and demonstrations to the GENI community, as well as students and researchers in academia and industry in the broad community. |
| | 55 | * An evaluation plan assessing the effectiveness PrimoGENI and the potential opt-ins through usage statistics, such as user activity levels of experiments, and dissection of applications involving experiments with simulated/emulated components. |
| | 56 | |
| 59 | | 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. |
| 60 | | |
| | 81 | TBA. 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. |
