| 6 | | * ''More resources than would ordinarily be found in your lab.'' Since GENI is a suite of infrastructures it can potentially provide you with more resources than is typically found in any one laboratory. This is especially true for compute resources: GENI provides access to large testbeds with hundreds of PCs and to cloud computing resources. |
| 7 | | * ''Non-IP connectivity across resources.'' Some GENI aggregates allow you to set up Layer 2 connections between resources within the aggregate. Experimenters may install and run their own Layer 3 and above protocols on these resources. It is also possible to setup Layer 2 connections between many GENI aggregates that connect to GENI backbone networks (Internet2 and NLR). You can even set up your network to route through experimenter programmable switches in the GENI backbone. |
| 8 | | * ''A deeply programmable network.'' GENI has switches in the backbone and at the edges that you can program to set up the network topologies you need and to control flows in your network. |
| 9 | | * ''Geographically distributed resources.'' Some GENI resources are distributed around the world. |
| 10 | | * ''Reproducibility.'' You can get exclusive access to certain GENI resources including CPU resources and network resources. This gives you control over your experiment's environment and hence the ability for you and others to repeat experiments under identical or very similar conditions. |
| | 6 | * '''More resources than would ordinarily be found in your lab.''' Since GENI is a suite of infrastructures it can potentially provide you with more resources than is typically found in any one laboratory. This is especially true for compute resources: GENI provides access to large testbeds with hundreds of PCs and to cloud computing resources. |
| | 7 | * '''Non-IP connectivity across resources.''' Some GENI aggregates allow you to set up Layer 2 connections between resources within the aggregate. Experimenters may install and run their own Layer 3 and above protocols on these resources. It is also possible to setup Layer 2 connections between many GENI aggregates that connect to GENI backbone networks (Internet2 and NLR). You can even set up your network to route through experimenter programmable switches in the GENI backbone. |
| | 8 | * '''A deeply programmable network.''' GENI has switches in the backbone and at the edges that you can program to set up the network topologies you need and to control flows in your network. |
| | 9 | * '''Geographically distributed resources.''' Some GENI resources are distributed around the world. |
| | 10 | * '''Reproducibility.''' You can get exclusive access to certain GENI resources including CPU resources and network resources. This gives you control over your experiment's environment and hence the ability for you and others to repeat experiments under identical or very similar conditions. |
| 13 | | * ''Unified access to a large number of resources''. Your GENI account (experimenter credentials) will give you access to a number of resources owned and operated by different organizations without your having to get separate accounts from each of them. |
| 14 | | * ''Unified tools and services''. Many GENI experiment control and measurement tools and services work across diverse resources owned and operated by different organizations. You do not have to switch between tools to use resources from different organizations. |
| 15 | | * ''Help desk support.'' The GENI help desk can help you get GENI experimenter credentials, identify resources that might be suitable for your experiment, and point you to relevant tutorials, examples and support mailing lists. Send your requests for help to [mailto:help@geni.net]. |
| 16 | | * ''Operations support''. A GENI-wide meta-operations team coordinates GENI operations, security, and network stitching (setting up Layer 2 VLANS over GENI backbone networks). For assistance with any of these issues contact [mailto:gpo-infra@geni.net]. |
| 17 | | [[BR]] |
| | 13 | * '''Unified access to a large number of resources'''. Your GENI account (experimenter credentials) will give you access to a number of resources owned and operated by different organizations without your having to get separate accounts from each of them. |
| | 14 | * '''Unified tools and services'''. Many GENI experiment control and measurement tools and services work across diverse resources owned and operated by different organizations. You do not have to switch between tools to use resources from different organizations. |
| | 15 | * '''Help desk support.''' The GENI help desk can help you get GENI experimenter credentials, identify resources that might be suitable for your experiment, and point you to relevant tutorials, examples and support mailing lists. Send your requests for help to [mailto:help@geni.net]. |
| | 16 | * '''Operations support'''. A GENI-wide meta-operations team coordinates GENI operations, security, and network stitching (setting up Layer 2 VLANS over GENI backbone networks). For assistance with any of these issues contact [mailto:gpo-infra@geni.net]. |
| 24 | | As an experimenter you will need to know about GENI ''clearinghouses'', GENI ''aggregates'' and GEN ''slices''. |
| 25 | | * A GENI ''clearinghouse'' authenticates experimenters and issues them credentials needed to obtain GENI resources for experimentation. If you need GENI experimenter credentials email [mailto:help@geni.net]. |
| 26 | | * GENI ''aggregates'' provide resources to experimenters with GENI credentials. GENI has a number of different aggregates that provide a variety of resources for experimentation. An important aspect of planning your experiment is deciding what resources you need (resource types and numbers) and which aggregates might be able to provide you these resources. |
| 27 | | * A GENI ''slice'' holds a collection of computing and communications resources capable of running an experiment or a wide area service. An experiment is a researcher-defined use of resources in a slice; an experiment runs in a slice. A researcher may run multiple experiments using resources in a slice, concurrently or over time. |
| | 23 | As an experimenter you will need to know about GENI ''clearinghouses'', GENI ''aggregates'' and GEN ''slices and slivers''. |
| 29 | | The following figure illustrates the role of GENI clearinghouses and aggregates: |
| 30 | | [[Image(GENIComponentsPicture-2.png, 25%)]] |
| 31 | | [[BR]] |
| 32 | | [[BR]] |
| | 25 | {{{ |
| | 26 | #!html |
| | 27 | |
| | 28 | <table border="0"> |
| | 29 | <tr> |
| | 30 | <td> <img border="0" src="http://groups.geni.net/geni/attachment/wiki/UnderstandingGENI/GENIComponentsPicture-2.png?format=raw" alt="GENI Glossary" height="300"/> </td> |
| | 31 | <td> <pre> </pre> </td> |
| | 32 | |
| | 33 | <td> |
| | 34 | <ul> |
| | 35 | <li> A GENI <b>clearinghouse</b> authenticates experimenters and issues them credentials needed to reserve GENI resources for experimentation. To get a GENI account(credentials) please follow <a href ="SignMeUp"> these instructions </a> or contact <a href="mailto:help@geni.net help@geni.net"> help@geni.net </a>. </li> |
| | 36 | <li> GENI <b>aggregates</b> provide resources to experimenters with GENI credentials. GENI has a number of different aggregates that provide a variety of resources for experimentation. An important aspect of planning your experiment is deciding what resources you need (resource types and numbers) and which aggregates might be able to provide you these resources.</li> |
| | 37 | <li>A GENI <b>slice</b> is a virtual container that can hold a collection of computing and communications resources for running an experiment or a wide area service. A slice might span multiple GENI aggregates. An experiment is a researcher-defined use of resources in a slice; an experiment runs in a slice. A researcher may run multiple experiments using resources in a slice, concurrently or over time. A GENI <b>sliver</b> is a set of resources that an experimenter has in a specific GENI aggregate, i.e. a GENI slice is comprised of a set of slivers. </li> |
| | 38 | |
| | 39 | </td> |
| | 40 | <td> <pre> </pre> </td> |
| | 41 | </tr> |
| | 42 | </table> |
| | 43 | }}} |
| 47 | | * ''The degree of control you need over your experiment.'' Do you need to tightly control the resources (CPU, bandwidth, etc.) allocated to your experiment or will best-effort suffice? If you need a tightly controlled environment you might want to consider one of the ProtoGENI aggregate that allocate entire PCs that can be connected in arbitrary topologies. |
| 48 | | * ''The desired network topology.'' Does your experiment have to be geographically distributed? What kinds of connectivity do you need between these geographically distributed locations. Almost all aggregates can connect using IP connectivity over the Internet. Many aggregates connect to one of the GENI backbones and allow you to set up IP connections with other resources on the backbone. This will give you a bit more control over the network. Some aggregates provide Layer 2 connectivity over a GENI backbone i.e. you can set up vlans between these aggregates and other resources on the backbone network. This allows you to run non-IP protocols across between the aggregate and other resources. |
| 49 | | * ''The desired control over network flows.'' If you need to manage network traffic to/from an aggregate you might want to use aggregates that connect to a GENI backbone using OpenFlow switches or set up vlans to these aggregates through the ProtoGENI Backbone Nodes or the SPP Nodes. |
| 50 | | * ''The number of resources you need from an aggregate.'' Aggregates vary from small installations such as the GPO Lab ProtoGENI aggregate that consists of eleven nodes to the PlanetLab and ProtoGENI aggregates that consist of hundreds of nodes. |
| 51 | | * ''If the aggregate accepts GENI credentials''. You will likely be able to use resources from these aggregates with a credential issued by a GENI clearinghouse; you do not have to contact the aggregate owner to get an account for the aggregate. Additionally, aggregates that accept GENI credentials typically implement the GENI Aggregate Manager API. A growing number of GENI experiment control tools support this API i.e. these tools can be used to create slices, add resources from aggregates that support the GENI API, etc. Examples of such tools include the [http://www.protogeni.net/trac/protogeni/wiki/Flack Flack], [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] and [http://gush.cs.williams.edu/trac/gush Gush]. |
| | 64 | * '''The degree of control you need over your experiment.''' Do you need to tightly control the resources (CPU, bandwidth, etc.) allocated to your experiment or will best-effort suffice? If you need a tightly controlled environment you might want to consider one of the ProtoGENI aggregate that allocate entire PCs that can be connected in arbitrary topologies. |
| | 65 | * '''The desired network topology.''' Does your experiment have to be geographically distributed? What kinds of connectivity do you need between these geographically distributed locations. Almost all aggregates can connect using IP connectivity over the Internet. Many aggregates connect to one of the GENI backbones and allow you to set up IP connections with other resources on the backbone. This will give you a bit more control over the network. Some aggregates provide Layer 2 connectivity over a GENI backbone i.e. you can set up vlans between these aggregates and other resources on the backbone network. This allows you to run non-IP protocols across between the aggregate and other resources. |
| | 66 | * '''The desired control over network flows.''' If you need to manage network traffic to/from an aggregate you might want to use aggregates that connect to a GENI backbone using OpenFlow switches or set up vlans to these aggregates through the ProtoGENI Backbone Nodes or the SPP Nodes. |
| | 67 | * '''The number of resources you need from an aggregate.''' Aggregates vary from small installations such as the GPO Lab ProtoGENI aggregate that consists of eleven nodes to the PlanetLab and ProtoGENI aggregates that consist of hundreds of nodes. |
| | 68 | * '''If the aggregate accepts GENI credentials'''. You will likely be able to use resources from these aggregates with a credential issued by a GENI clearinghouse; you do not have to contact the aggregate owner to get an account for the aggregate. Additionally, aggregates that accept GENI credentials typically implement the GENI Aggregate Manager API. A growing number of GENI experiment control tools support this API i.e. these tools can be used to create slices, add resources from aggregates that support the GENI API, etc. Examples of such tools include the [http://www.protogeni.net/trac/protogeni/wiki/Flack Flack], [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] and [http://gush.cs.williams.edu/trac/gush Gush]. |
| 57 | | == 5 Experimenter Tools == |
| 58 | | |
| 59 | | === 5.1 Experiment Control Tools === |
| 60 | | GENI experiment control tools are used to create slices, add or remove resources to slices, and delete slices. Some tools may also help with the installation of experimenter specified software into resources in slices; starting, pausing, resuming and stopping the execution of an experiment; and monitoring of the resources in slices for failures. Examples of GENI experiment control tools include [http://gush.cs.williams.edu/trac/gush Gush], [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni], [http://www.cs.princeton.edu/~jrex/gew/gew-sfi.ppt PlanetLab SFI] and [http://www.protogeni.net/trac/protogeni/wiki/Flack Flack]. |
| 61 | | |
| 62 | | In addition to these experiment control tools, individual aggregates provide experimenters with additional tools to install and manage software on their resources. For example, the Million Node GENI aggregate provides a set of tools to manage the virtual machines it proves as computing resources. |
| 63 | | |
| 64 | | === 5.2 Instrumentation and Measurement Tools === |
| 65 | | GENI instrumentation tools are currently aggregate specific. Examples of such tools include [http://www.netlab.uky.edu/p/instools Instrumentation Tools] for the Kentucky ProtoGENI aggregate, [http://raven.cs.arizona.edu/projects/project Owl] for the !PlanetLab aggregate and [http://mytestbed.net/wiki/omf/Introduction OMF/OML] for the ORBIT aggregate. |
| 66 | | [[BR]] |
| 67 | | [[BR]] |
| 68 | | |
| 69 | | == 6 Getting Access to GENI == |
| 70 | | To use GENI for experimentation please contact [mailto:help@geni.net help@geni.net] or follow the instructions at SignMeUp. |
| 71 | | [[BR]] |
| 72 | | [[BR]] |
| 73 | | |
| 74 | | == 7 Tutorials == |
| 75 | | For a tutorial on using [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni tools] to run experiments on GENI, see [wiki:HowToUseOmni]. |
| 76 | | |
| 77 | | For a tutorial on using ProtoGENI Tools to run experiments on GENI, see [http://www.protogeni.net/trac/protogeni/wiki/Tutorial]. |
| 78 | | [[BR]] |
| 79 | | [[BR]] |
| 80 | | |
| 81 | | == 8 GENI Aggregates Currently Available to Experimenters == |
| 82 | | See [wiki:AvailableAggregates]. |
| | 73 | == 6 Tutorials and Experimenter Tools == |
| | 74 | The best way to learn what GENI is and what it provides, is by using it. After you get your GENI Account, familiarize yourself with the [wiki:NikySandbox/GENIExperimenter/Tools tools] that are available to experimenters for accessing and using GENI and go over some [wiki:NikySandbox/GENIExperimenter/Tutorials tutorials] to get some hands on experience. |
