Differences

This shows you the differences between two versions of the page.

Link to this comparison view

public:experimenters:start [2017/10/19 09:29]
ibaldin
public:experimenters:start [2017/10/19 09:31] (current)
ibaldin [Selecting which ORCA actor to request resources from]
Line 105: Line 105:
 ===== Selecting which ORCA actor to request resources from ===== ===== Selecting which ORCA actor to request resources from =====
  
-ORCA actors named 'SM' (Service Manager) are available from [[public:experimenters:orca_sm | multiple locations]]. They implement the same logic and present similar API (ORCA native API, usable by Flukes and GENI AM API, usable by Omni and Flack), but have different levels of resource visibility. Each rack presents an SM actor that has visibility only for the resources in that rack. An actor called 'ExoSM' has global visibility across all racks and all interconnecting networks between them. +ORCA controllers, to which slice requests can be submitted are available from [[public:experimenters:orca_sm | multiple locations]]. They implement the same logic and present similar API (ORCA native API, usable by Flukes and GENI AM API, usable by Omni and GENI Portal/Jacks), but have different levels of resource visibility. Each rack presents a controller that has visibility only for the resources in that rack. An actor called 'ExoSM' has global visibility across all racks and all interconnecting networks between them. 
  
-Rack SMs can create topologies only within a single rack. ExoSM can create topologies consisting of resources from many ExoGENI racks. Bare-metal nodes are available only through ExoSM. +Rack controllers can create topologies only within a single rack. ExoSM can create topologies consisting of resources from many ExoGENI racks. Bare-metal nodes are available only through ExoSM. 
  
 Reasons to use ExoSM: Reasons to use ExoSM:
Navigation
Print/export