Changes between Version 43 and Version 44 of ExperimenterPortal
- Timestamp:
- 03/11/11 17:20:04 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ExperimenterPortal
v43 v44 7 7 * Your experiment requires 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 8 * Your experiment requires requires geographically distributed resources. Some GENI aggregates include resources distributed around the world. 9 [[BR]] 9 10 10 11 == 2.0 An Experimenter's View of GENI == … … 20 21 21 22 You will also need to know about GENI ''slices''. A 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 [[BR]] 22 24 23 25 == 3.0 GENI Aggregates == … … 225 227 * 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. 226 228 * 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. 229 * 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. 227 230 * 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. 228 229 To help you pick resources for your experiment, the following table shows examples of GENI aggregates that provide computing resources and the type of connectivity to these resources: 230 [[Image(ResourceTable.png, 40%)]] 231 231 [[BR]] 232 232 233 233 == 4.0 Experimenter Tools == … … 239 239 240 240 === 4.2 Instrumentation and Measurement Tools === 241 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. 242 [[BR]] 241 243 242 244 == 5.0 Getting Access to GENI == 243 245 To use GENI for experimentation please contact [mailto:mberman@bbn.com Mark Berman]. 246 [[BR]] 244 247 245 248 == 6.0 Tutorials ==