31 | | === 3.1 GENI aggregates currently available to experimenters === |
32 | | ==== 3.1.1 Programmable Hosts ==== |
| 31 | |
| 32 | === 3.1 Picking Resources for Your Experiment === |
| 33 | As you plan your experiment you will want to consider: |
| 34 | * ''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 the U. of Utah ProtoGENI aggregate that allocate entire PCs that can be connected in arbitrary topologies. |
| 35 | * ''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. |
| 36 | * ''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. |
| 37 | * ''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. |
| 38 | * ''Support for the GENI Aggregate Manager API.'' Aggregates that support the GENI Aggregate Manager API generally recognize credentials issued by one of the GENI Clearinghouses. Aggregates that do not will likely require you to get an account from them. Additionally, a growing number of GENI experiment control tools support the GENI 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/MapInterface ProtoGENI Tools], [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] and [http://gush.cs.williams.edu/trac/gush Gush]. |
| 39 | |
| 40 | The GENI Project Office is happy to help find the best match of resources for your experiments. Please contact [mailto:help@geni.net] for assistance. |
| 41 | [[BR]] |
| 42 | [[BR]] |
| 43 | |
| 44 | == 4 Experimenter Tools == |
| 45 | |
| 46 | === 4.1 Experiment Control Tools === |
| 47 | 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/MapInterface ProtoGENI Tools]. |
| 48 | |
| 49 | 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. |
| 50 | |
| 51 | === 4.2 Instrumentation and Measurement Tools === |
| 52 | 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. |
| 53 | [[BR]] |
| 54 | [[BR]] |
| 55 | |
| 56 | == 5 Getting Access to GENI == |
| 57 | To use GENI for experimentation please contact [mailto:help@geni.net help@geni.net]. |
| 58 | [[BR]] |
| 59 | [[BR]] |
| 60 | |
| 61 | == 6 Tutorials == |
| 62 | For a tutorial on using [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni tools] to run experiments on GENI, see [http://groups.geni.net/geni/wiki/GENIExperimenter]. |
| 63 | |
| 64 | For a tutorial on using ProtoGENI Tools to run experiments on GENI, see [http://www.protogeni.net/trac/protogeni/wiki/Tutorial]. |
| 65 | [[BR]] |
| 66 | [[BR]] |
| 67 | |
| 68 | == 7 GENI aggregates currently available to experimenters == |
| 69 | === 7.1 Programmable Hosts === |
283 | | === 3.3 Picking Resources for Your Experiment === |
284 | | As you plan your experiment you will want to consider: |
285 | | * ''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 the U. of Utah ProtoGENI aggregate that allocate entire PCs that can be connected in arbitrary topologies. |
286 | | * ''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. |
287 | | * ''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. |
288 | | * ''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. |
289 | | * ''Support for the GENI Aggregate Manager API.'' Aggregates that support the GENI Aggregate Manager API generally recognize credentials issued by one of the GENI Clearinghouses. Aggregates that do not will likely require you to get an account from them. Additionally, a growing number of GENI experiment control tools support the GENI 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/MapInterface ProtoGENI Tools], [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] and [http://gush.cs.williams.edu/trac/gush Gush]. |
290 | | |
291 | | The GENI Project Office is happy to help find the best match of resources for your experiments. Please contact [mailto:help@geni.net] for assistance. |
292 | | [[BR]] |
293 | | [[BR]] |
294 | | |
295 | | == 4.0 Experimenter Tools == |
296 | | |
297 | | === 4.1 Experiment Control Tools === |
298 | | 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/MapInterface ProtoGENI Tools]. |
299 | | |
300 | | 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. |
301 | | |
302 | | === 4.2 Instrumentation and Measurement Tools === |
303 | | 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. |
304 | | [[BR]] |
305 | | [[BR]] |
306 | | |
307 | | == 5.0 Getting Access to GENI == |
308 | | To use GENI for experimentation please contact [mailto:help@geni.net help@geni.net]. |
309 | | [[BR]] |
310 | | [[BR]] |
311 | | |
312 | | == 6.0 Tutorials == |
313 | | For a tutorial on using [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni tools] to run experiments on GENI, see [http://groups.geni.net/geni/wiki/GENIExperimenter]. |
314 | | |
315 | | For a tutorial on using ProtoGENI Tools to run experiments on GENI, see [http://www.protogeni.net/trac/protogeni/wiki/Tutorial]. |
316 | | |
317 | | |