Differences

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

Link to this comparison view

public:experimenters:start [2016/11/21 15:53]
ibaldin [The Tools]
public:experimenters:start [2017/10/19 09:31] (current)
ibaldin [Selecting which ORCA actor to request resources from]
Line 26: Line 26:
   - ExoGENI offers two broad categories of compute nodes. You can get [[:public:experimenters:resource_types:start | KVM virtual machines]] of multiple sizes and [[:public:experimenters:resource_types:start | bare-metal nodes]]. This contrasts with e.g. OpenVZ or other container types available in other testbeds. Compute instances in ExoGENI can behave differently, than in other testbeds    - ExoGENI offers two broad categories of compute nodes. You can get [[:public:experimenters:resource_types:start | KVM virtual machines]] of multiple sizes and [[:public:experimenters:resource_types:start | bare-metal nodes]]. This contrasts with e.g. OpenVZ or other container types available in other testbeds. Compute instances in ExoGENI can behave differently, than in other testbeds 
      * They are well-isolated from other slices and represent completely separate compute nodes with their own operating system, on which the slice owner is root.      * They are well-isolated from other slices and represent completely separate compute nodes with their own operating system, on which the slice owner is root.
-     * Command-line reboots are not guaranteed to succeed (however they do if no errors in boot process are present). 
   - ExoGENI does not oversubscribe its resources: each rack site has a certain number of CPU cores dedicated to launching virtual machines. Each VM can have [[:public:experimenters:resource_types:start | multiple cores]]. When all the cores in the rack are exhausted, no more compute instances can be created on this rack. This is done to improve performance isolation between experiments.   - ExoGENI does not oversubscribe its resources: each rack site has a certain number of CPU cores dedicated to launching virtual machines. Each VM can have [[:public:experimenters:resource_types:start | multiple cores]]. When all the cores in the rack are exhausted, no more compute instances can be created on this rack. This is done to improve performance isolation between experiments.
   - ExoGENI is a [[:public:experimenters:images | 'Bring Your Own Image' (BYOI) testbed]]. You can build your own image outside the testbed, post it on any webserver (or use Dropbox), create an image description file and launch your slice with this image. ExoGENI **does not have its own image hosting service**. While we offer a number of images to the community, these are merely examples. We encourage experimenters to build their own images, upload them to their own webservers and [[public:experimenters:images | list them with us]].    - ExoGENI is a [[:public:experimenters:images | 'Bring Your Own Image' (BYOI) testbed]]. You can build your own image outside the testbed, post it on any webserver (or use Dropbox), create an image description file and launch your slice with this image. ExoGENI **does not have its own image hosting service**. While we offer a number of images to the community, these are merely examples. We encourage experimenters to build their own images, upload them to their own webservers and [[public:experimenters:images | list them with us]]. 
Line 66: Line 65:
 |[[https://geni-orca.renci.org/trac/wiki/flukes#Nodes | ExoGENI nodegroups]] | Yes | No | No | No | |[[https://geni-orca.renci.org/trac/wiki/flukes#Nodes | ExoGENI nodegroups]] | Yes | No | No | No |
 |[[ http://www.exogeni.net/2016/01/using-exogeni-slice-modifydynamic-slice-capabilities/ | ExoGENI slice modify]] | Yes | No | No | No | |[[ http://www.exogeni.net/2016/01/using-exogeni-slice-modifydynamic-slice-capabilities/ | ExoGENI slice modify]] | Yes | No | No | No |
-|[[ http://www.exogeni.net/2016/11/using-exogeni-slice-stitching-capabilities/ | Using ExoGENI Slice Stitching capabilities]]| Yes | No | No | No |+|[[ http://www.exogeni.net/2016/11/using-exogeni-slice-stitching-capabilities/ | Using ExoGENI Slice-to-slice Stitching capabilities]]| Yes | No | No | No |
 |[[ https://geni-orca.renci.org/trac/wiki/velocity-templates | ExoGENI templated post-boot scripts]] | Yes | Yes ((manual rspec edits and using <pbs:services_post_boot_script type="velocity"> service)) | Partial (('execute' service allows for variable substitutions, but does not allow macros and automatic code generation)) | Partial (('execute' service applied in ExoGENI allows for variable substitutions, but does not allow macros and automatic code generation)) | |[[ https://geni-orca.renci.org/trac/wiki/velocity-templates | ExoGENI templated post-boot scripts]] | Yes | Yes ((manual rspec edits and using <pbs:services_post_boot_script type="velocity"> service)) | Partial (('execute' service allows for variable substitutions, but does not allow macros and automatic code generation)) | Partial (('execute' service applied in ExoGENI allows for variable substitutions, but does not allow macros and automatic code generation)) |
 |[[https://geni-orca.renci.org/trac/wiki/flukes#StitchPorts | Stitching to campus networks ]] | Yes | No | No | No | |[[https://geni-orca.renci.org/trac/wiki/flukes#StitchPorts | Stitching to campus networks ]] | Yes | No | No | No |
Line 106: 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