Changes between Version 19 and Version 20 of GeniApi


Ignore:
Timestamp:
10/27/10 08:52:55 (9 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniApi

    v19 v20  
    77[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. This was initially demonstrated at GEC8, and was used to reserve the resources used in the plenary session demos at GEC9.
    88
    9 The ProtoGENI implementation is live in Utah, and is part of emulab-stable. ProtoGENI has trusted the !PlanetLab root certificate, 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.
     9The 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.
    1010
    1111The !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.
    1212
    13 Contact !OpenFlow for availability of the !OpenFlow implementation of this API.
     13The !OpenFlow team has built a combined client/clearinghouse/aggregate manager called Expedient. Expedient exposes the GENI API to reserve !OpenFlow slivers. To learn more about Expedient, see [http://yuba.stanford.edu/~jnaous/expedient/ the Expedient developer's site]. Expedient has been installed at multiple campuses. Contact !OpenFlow for further availability information.
    1414
    15 The GPO has developed a reference implementation of this 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 download here: [http://www.gpolab.bbn.com/local-sw/ Download Sample Code], with source code and our open ticket issues [http://trac.gpolab.bbn.com/gcf available and public here].
     15The GPO has developed a [http://trac.gpolab.bbn.com/gcf reference implementation of this 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 download here: [http://www.gpolab.bbn.com/local-sw/ Download Sample Code], with source code and our open ticket issues [http://trac.gpolab.bbn.com/gcf available and public here].
    1616
    1717Experimenters should 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.
     
    1919Full details on the API specification are available here: [wiki:GAPI_AM_API GENI Aggregate Manager API]
    2020
    21 Questions? Comments? Suggestions? Contact Tom Mitchell (tmitchell) or Josh Karlin (jkarlin) or Aaron Helsinger (ahelsing) at geni.net
     21Questions? Comments? Suggestions? Contact Tom Mitchell (tmitchell) or Josh Karlin (jkarlin) or Aaron Helsinger (ahelsing) or Sarah Edwards (sedwards) at geni.net
    2222
    2323== Useful Links ==