Version 26 (modified by chase, 7 years ago)

--

Deploying an SM (Slice Manager or Service Manager)

Overview

An 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.

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 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.

You 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).

Deploying ORCA Container with a SM actor

Operation

The GUI Portal allows you to place reservations for individual slivers directly. If you want more sophisticated operation, consult documentation on ORCA XMLRPC controller on how to use the GENI and ProtoGENI AM XMLRPC API.

The page with emulation mode operation has videos that show ORCA web portal operation.

Attachments