Changes between Version 30 and Version 31 of deploy-sm

Show
Ignore:
Timestamp:
12/03/11 22:18:56 (8 years ago)
Author:
ibaldin (IP: 152.54.15.223)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-sm

    v30 v31  
    55An SM is the actor representing ORCA users. It acts as a client to request, launch, and monitor slices, and receives notifications pertaining to the slice.  An SM can run any of a number of controller plugins on a per-slice basis.  The controllers implement different resource management policies or choices for the slice. Controller plugins can export external interfaces (programmatic or GUI) for users or external tools to drive the choices. 
    66 
    7 In the GENI project, we deploy a default standard SM controller called XMLRPC controller for all slices.  The XMLRPC controller exports programmatic APIs defined in the GENI project, for use by external tools.  Currently the two most common interfaces are [http://groups.geni.net/geni/wiki/GeniApi GENI AM API] and ProtoGENI AM API. The ORCA XMLRPC Controller plugin implements both of those.  An SM running the ORCA XMLRPC controller exports all resources offered by brokers that are visible to the SM.  In essence, it exposes an ORCA networked cloud as a single GENI aggregate.  The actual ORCA AM protocol uses tickets and leases to implement resource management functions that are not yet available in the GENI AM API. 
     7In the GENI project, we deploy a default standard SM controller called XMLRPC controller for all slices.  The XMLRPC controller exports programmatic APIs defined in the GENI project, for use by external tools.  Currently the most common interface is [http://groups.geni.net/geni/wiki/GeniApi GENI AM API]. ORCA also has a native XMLRPC interface for tools to create slices. The ORCA XMLRPC Controller plugin implements both of those.  An SM running the ORCA XMLRPC controller exports all resources offered by brokers that are visible to the SM.  In essence, it exposes an ORCA networked cloud as a single GENI aggregate.  The actual ORCA AM protocol uses tickets and leases to implement resource management functions that are not yet available in the GENI AM API. 
    88 
    99You can install an SM on any host with a public access to the Internet (to allow communication with other ORCA actors and remote actor registry).