Changes between Version 28 and Version 29 of GeniApi


Ignore:
Timestamp:
08/08/13 14:46:28 (5 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniApi

    v28 v29  
    55
    66= The GENI Aggregate Manager API =
    7 The [wiki:GAPI_AM_API GENI AM API] defines a key interface of the [wiki:SliceFedArch SFA 2.0 Draft], providing a common interface to Aggregate Managers.The GENI AM API has been implemented by [http://www.planet-lab.org/ PlanetLab], [http://www.protogeni.net/trac/protogeni ProtoGENI], and [http://www.openflow.org/ OpenFlow]. Furthermore, through the sharing of root certificates, these implementations are now interoperable. Researchers with a ProtoGENI account can use !PlanetLab resources, and researchers with a !PlanetLab account can use ProtoGENI resources. Many !OpenFlow aggregates also trust the !PlanetLab and ProtoGENI root certificates. Initial implementations of the GENI AM API were demonstrated at GEC 8 and interoperability was demonstrated via the GEC 9 plenary session demos.
     7The [wiki:GAPI_AM_API GENI AM API] defines a key interface of the [wiki:SliceFedArch SFA 2.0 Draft], providing a common interface to Aggregate Managers.The GENI AM API has been implemented by [http://www.planet-lab.org/ PlanetLab], [http://www.protogeni.net/trac/protogeni ProtoGENI], [http://www.exogeni.net/ ExoGENI], [http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks InstaGENI] and [http://www.openflow.org/ OpenFlow]. Furthermore, through the sharing of root certificates, these implementations are now interoperable. For example, researchers with a ProtoGENI account can use !PlanetLab resources, and researchers with a !PlanetLab account can use ProtoGENI resources. Initial implementations of the GENI AM API were demonstrated at GEC 8 and interoperability was demonstrated via the GEC 9 plenary session demos.
    88
    9 Experimenters can begin designing and conducting experiments that take advantage of the broad variety of resources now available to them. Contact Mark Berman and the Experimentation Working Group with questions.
     9Experimenters can begin designing and conducting experiments that take advantage of the broad variety of resources now available to them. Contact [mailto:help@geni.net GENI help] with any questions.
    1010
    1111= Implementations =
    1212The !PlanetLab implementation is live on PLC and PLE. ProtoGENI and PLC have also swapped root certificates, meaning that ProtoGENI users can use the API to reserve !PlanetLab resources at PLC.  To run the GENI API on your MyPLC instance, simply install the latest release of SFA.  Use the mailing list: devel@planet-lab.org for questions.
    1313
    14 The ProtoGENI implementation is live in Utah and Kentucky, and is part of emulab-stable. ProtoGENI has trusted the !PlanetLab root certificate (it is included in their standard certificate bundle that all ProtoGENI installs receive), meaning that !PlanetLab users can use the GENI API to reserve ProtoGENI resources. Contact the mailing list (geni-dev@emulab.net) with questions on using the API at ProtoGENI.
     14The ProtoGENI (InstaGENI) implementation is live in most ProtoGENI installations, and is part of emulab-stable. ProtoGENI has trusted the [http://groups.geni.net/geni/wiki/GeniTrustAnchors standard GENI trust anchors]  (they are included in their standard certificate bundle that all ProtoGENI installs receive), meaning that for example !PlanetLab users can use the GENI API to reserve ProtoGENI resources. Contact the mailing list (geni-dev@emulab.net) with questions on using the API at ProtoGENI.
    1515
    1616The !OpenFlow team has built an aggregate manager called [https://openflow.stanford.edu/display/FOAM/Home FOAM], which is currently operating in all GENI aggregates that support OpenFlow.  FOAM exposes the GENI API to reserve !OpenFlow slivers, and implements several support functions for aggregate administrators.To learn more about FOAM, see [https://openflow.stanford.edu/bugs/browse/FOAM the FOAM developer's site].
    1717
    18 The ORCA team implements the GENI AM API in a plug-in controller for the ORCA [https://geni-orca.renci.org/trac/wiki/deploy-sm Slice Manager (SM)], which exports various XMLRPC interfaces to external tools.  An SM running the XMLRPC controller exposes all resources visible to that SM as a single GENI aggregate.  The native AM protocol in ORCA depends on features that are not yet available in the GENI AM API: it uses tickets and leases for resource management, supports multiple slivers per slice, and uses property lists to drive various configuration options.
     18The ORCA/ExoGENI team implements the GENI AM API in a plug-in controller for the ORCA [https://geni-orca.renci.org/trac/wiki/deploy-sm Slice Manager (SM)], which exports various XMLRPC interfaces to external tools.  An SM running the XMLRPC controller exposes all resources visible to that SM as a single GENI aggregate.  The native AM protocol in ORCA depends on features that are not yet available in the GENI AM API: it uses tickets and leases for resource management, supports multiple slivers per slice, and uses property lists to drive various configuration options.
    1919
    2020The GPO has developed a [http://trac.gpolab.bbn.com/gcf reference implementation of the GENI AM API], particularly demonstrating the use of certificates, credentials and credential verification. Also provided is a reference client, [wiki:Omni omni]. [wiki:Omni Omni] communicates with each clearinghouse in its 'native tongue', and then calls the Aggregate Manager API at any compliant Aggregate. These packages are available together for [http://www.gpolab.bbn.com/local-sw/ download].
     
    4848
    4949= Contact =
    50 Questions? Comments? Suggestions? Contact Tom Mitchell (tmitchell) or Aaron Helsinger (ahelsing) or Sarah Edwards (sedwards) at geni.net
     50Questions? Comments? Suggestions? Contact Tom Mitchell (tmitchell) or Aaron Helsinger (ahelsing) at geni.net