Changes between Version 24 and Version 25 of GeniApi
- Timestamp:
- 10/07/11 10:18:57 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniApi
v24 v25 18 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. 19 19 20 The GPO has developed a [http://trac.gpolab.bbn.com/gcf reference implementation of th isAPI], 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].20 The 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]. 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]. 22 22