Version 8 (modified by 13 years ago) (diff) | ,
---|
What Resources Are in GENI (and what are they good for)?
This table gives new GENI users a quick and easy way to see what testbed / framework might be useful for their experiment. Each of the groups listed under here has a page which describes the tools and facilities available for their users. The list is sorted by scale.
Note that some resources in GENI are supported as production resources, while others are available as prototype resources. More details are available at ProductionResources .
Testbed Name | Cluster | Physical connectivity | Layer 2 Control | Layer 3 Control | Scale | Programming environment | Restrictions |
Million Node GENI / Seattle | C | Real end user networks | None | None | ~3K nodes | Python based VM | TCP / UDP traffic only, see AUP |
PlanetLab | B | Edu networks | Some via OpenFlow | Limited RAW sockets, VINI | ~1K nodes | Linux VM | See AUP |
ProtoGENI | C | Machine room, real switches, etc. | OpenFlow, VLANs across the WAN, | None | ~500 nodes | Any OS VM | See AUP |
DETER / TIED | Machine room, real switches, etc. | ?? | ?? | ~500 nodes | Any OS VM | Allows disruptive experiments, see AUP | |
ORBIT | E | 802.22 | None | None | ??? nodes | Any OS VM | ?? |
GpENI | B | Edu networks | OpenFlow, ?? | Limited RAW sockets, VINI, ?? | ~200 nodes | Linux VM | See AUP |