38 | | [wiki:Integration ProtoGENI backbone] nodes are available in Internet 2 (Kansas City, MI, Salt Lake City, UT, Washington, DC). Layer 2 data-plane access to these services is available via dedicated campus connections to Internet 2 or via Internet 2's ION service using the [https://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI ProtoGENI Component Manager API] or the [http://www.emulab.net Emulab] interfaces. Layer 3 access is also available via any Internet connection. Additional ProtoGENI node deployments are planned for Spiral 3 at Houston, TX, Atlanta, GA, and Seattle WA, and one other site. |
| 42 | [wiki:Integration ProtoGENI backbone] nodes are available in Internet 2 (Kansas City, MI, Salt Lake City, UT, Washington, DC). Layer 2 data-plane access to these services is available via dedicated campus connections to Internet 2 or via Internet 2's ION service using the [https://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI ProtoGENI Component Manager API] or the [http://www.emulab.net Emulab] interfaces. Layer 3 access is also available via any Internet connection. Additional ProtoGENI node deployments are planned for Spiral 3 at Houston, TX, Atlanta, GA, and Seattle WA, and one other site. |
40 | | [wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are available at Kansas City, MI, Salt Lake City, UT, and Washington, DC. Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes. Additional nodes at Houston, TX and Atlanta, GA are planned for Spiral 3. |
| 44 | [wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are available at Kansas City, MI, Salt Lake City, UT, and Washington, DC. Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes. Additional nodes at Houston, TX and Atlanta, GA are planned for Spiral 3. |
46 | | OpenFlow switch deployments on [wiki:OFNLR National LambdaRail] and [wiki:OFI2 Internet 2] are underway in Spiral 2. Layer 2 data plane access to these services is available via a dedicated campus connection to either backbone, or via NLR Framenet (Sherpa) or Internet2 ION service. Layer 3 access is also available via any Internet connection. |
47 | | |
48 | | == GENI API == |
49 | | |
50 | | The [wiki:GeniApi GENI API] is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates. |
51 | | |
52 | | The [wiki:GeniApi GENI API] implements a key interface of the [wiki:SliceFedArch SFA 2.0 Draft], providing a common interface to Aggregate Managers. Experimenters can use the API to access resources belonging to any compliant Control Framework. The API lets you mix and match aggregates with control frameworks. |
53 | | |
54 | | [http://www.protogeni.net/trac/protogeni ProtoGENI], [http://www.planet-lab.org/ PlanetLab], and [http://www.openflow.org/ Openflow] all have implemented the API and are now interoperable, as demonstrated at GEC8 (mostly). |
55 | | |
56 | | Full details about the [wiki:GeniApi GENI API] and the reference implementation are available at the [wiki:GeniApi GENI API] page. From there you can also download code for the gcf reference aggregate manager and the Omni client. |
| 50 | OpenFlow switch deployments on [wiki:OFNLR National LambdaRail] and [wiki:OFI2 Internet 2] are underway in Spiral 2. Layer 2 data plane access to these services is available via a dedicated campus connection to either backbone, or via NLR Framenet (Sherpa) or Internet2 ION service. Layer 3 access is also available via any Internet connection. |