Changes between Version 26 and Version 27 of GeniApi


Ignore:
Timestamp:
03/05/12 09:18:07 (7 years ago)
Author:
hdempsey@bbn.com
Comment:

update OpenFlow aggregate info form Expedient to FOAM

Legend:

Unmodified
Added
Removed
Modified
  • GeniApi

    v26 v27  
    1414The 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.
    1515
    16 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.
     16The !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
    1818The 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.