Changes between Version 25 and Version 26 of GeniApi

Timestamp:

11/03/11 15:35:01 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GeniApi

@@ -14 +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.
 
-The !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.
+The !OpenFlow team has built an aggregate manager called [https://openflow.stanford.edu/display/FOAM/Home FOAM], which is currently in beta testing. FOAM will be available for wide use in late November 2011. FOAM will replace an !OpenFlow 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.
 
 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.
@@ -21 +21 @@
 Documentation is available on the [http://trac.gpolab.bbn.com/gcf gcf wiki] along with [http://trac.gpolab.bbn.com/gcf/wiki/GettingGcf source code] and [http://trac.gpolab.bbn.com/gcf/report/1 open tickets].
 
+= API Evolution =
+
+The current version of the Aggregate Manager API is documented on the [wiki:GAPI_AM_API GENI Aggregate Manager API Wiki Page]. The API will evolve over time as issues, gaps, or new requirements are identified. Those changes are documented on the [wiki:GAPI_AM_API_DRAFT Draft API Changes wiki page]. The API will also be the subject of periodic sessions at GEC conferences, as needed. There was an AM API session at GEC12, whose [wiki:GEC12GeniAmAPI wiki page] contains slides and session notes. That session defined version 2 of the API.
+
 = Documentation =
  * [wiki:GAPI_AM_API GENI Aggregate Manager API Wiki Page]
+ * [wiki:GAPI_AM_API_DRAFT GENI Aggregate Manager API Draft Changes wiki page]
  * [wiki:GeniAggregateManagerApiDoc GENI Aggregate Manager API Document]
  * [wiki:GeniApiIdentifiers GENI Identifiers]
@@ -29 +34 @@
  * [wiki:SliceFedArch SFA 2.0 Draft]
  * [https://www.protogeni.net/trac/protogeni/wiki/GeniAggregateManager The ProtoGENI API Implementation]
- * [GeniApiInstallationMyPlc Installing the API in MyPLC]
 
 = Software =
@@ -41 +45 @@
  * [https://geni-orca.renci.org/trac/ ORCA-BEN]
  * [http://www.orbit-lab.org/ Orbit / OMF]
+ * [https://openflow.stanford.edu/display/FOAM/Home FOAM]
 
 = Contact =