Changes between Version 25 and Version 26 of deploy-sm

Show
Ignore:
Timestamp:
10/07/11 10:06:47 (8 years ago)
Author:
chase (IP: 71.65.212.97)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-sm

    v25 v26  
    1 = Deploying a Service Manager = 
     1= Deploying an SM (Slice Manager or Service Manager) = 
    22 
    33== Overview == 
    44 
    5 A Service Manager is the actor representing ORCA users. It can run a number of controller plugins that implement different resource management policies. Controller plugins can exhibit different interfaces - programmatic or GUI. 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. By installing an ORCA Service Manager actor in a container you gain access to this controller and can request resources from other ORCA actors. 
     5An 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 Installation can be performed on any host with a public access to the Internet (to allow communication with other ORCA actors and remote actor registry).  
     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 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. 
    88 
    9 == Deploying ORCA Container with a Service Manager actor ==  
     9You 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).  
     10 
     11== Deploying ORCA Container with a SM actor ==  
    1012 
    1113 * [wiki:databaseSetup Create a MySQL database] 
    12  * [wiki:orca-home Create ORCA configuration file structure]. Generate one GUID for the new container and one GUID and certificate for a new actor and take note of the actor GUID. [wiki:configure-with-registry Configure this container] to use remote actor registry. If there are multiple brokers that this Service Manager might talk to and you want to use one of these brokers as the default broker, follow directions to [wiki:configure-default-broker configure default broker for this Service Manager] . 
     14 * [wiki:orca-home Create ORCA configuration file structure]. Generate one GUID for the new container and one GUID and certificate for a new actor and take note of the actor GUID. [wiki:configure-with-registry Configure this container] to use remote actor registry. If there are multiple brokers that this SM might talk to and you want to use one of these brokers as the default broker, follow directions to [wiki:configure-default-broker configure default broker for this SM] . 
    1315 * Use [source:config-files/trunk/geni.renci.org-config.xml this file] as a template for the actor configuration. Substitute the actor name and guid in it for your unique name and guid and modify the description. 
    1416 * Place the file under $ORCA_HOME/config/config.xml