ExoGENI Wiki

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2012/04/17 19:04]
jonmills
start [2021/01/02 06:10] (current)
Line 1: Line 1:
 ====== Introduction ====== ====== Introduction ======
  
-ExoGENI is based on an extended Infrastructure-as-a-Service (IaaS) cloud model with coordinated provisioning across multiple sites and a high degree of control over intra- and inter-site networking functions.   Most researchers will use a standard cloud computing stack to instantiate and manage virtual machines. +[[http://www.exogeni.net | ExoGENI]] is based on an extended Infrastructure-as-a-Service (IaaS) cloud model with coordinated provisioning across multiple sites and a high degree of control over intra- and inter-site networking functions.   Most researchers will use a standard cloud computing stack to instantiate and manage virtual machines. 
 The sites federate by delegating certain functions for identity management, authorization, and resource management to common coordinator services offered by the ExoGENI federation; ExoGENI in turn delegates some of these functions to the GENI federation and to identity systems operated by participating institutions (Shibboleth/inCommon). The sites federate by delegating certain functions for identity management, authorization, and resource management to common coordinator services offered by the ExoGENI federation; ExoGENI in turn delegates some of these functions to the GENI federation and to identity systems operated by participating institutions (Shibboleth/inCommon).
  
Line 10: Line 10:
  
   * Provisioning individual compute resources (virtualized and bare-metal) from rack resources. Users will be able to supply boot images for virtualized instances; bare-metal instances will be limited to a few vetted images.    * Provisioning individual compute resources (virtualized and bare-metal) from rack resources. Users will be able to supply boot images for virtualized instances; bare-metal instances will be limited to a few vetted images. 
-    * We plan to support Linux (bare-metal and virtual) and Windows (virtual, possibly also bare-metal). Other operating systems will require further study.+    * We support Linux (bare-metal and virtual) and Windows (virtual, possibly also bare-metal). 
   * Creating, modifying and destroying slices consisting of compute resources belonging to one or more racks, tied together with VLANs provisioned from rack switches and intermediate circuit providers.   * Creating, modifying and destroying slices consisting of compute resources belonging to one or more racks, tied together with VLANs provisioned from rack switches and intermediate circuit providers.
   * Create slices with user-driven packet forwarding control via OpenFlow. OpenFlow slices will be restricted to VLANs provisioned within and between the racks.   * Create slices with user-driven packet forwarding control via OpenFlow. OpenFlow slices will be restricted to VLANs provisioned within and between the racks.
Line 16: Line 16:
   * Create slices that combine ExoGENI resources with other GENI resources (e.g. meso-scale OpenFlow and WiMax testbeds; via our switch at the StarLight facility we plan to create experimental L2 topologies that involve international partners).   * Create slices that combine ExoGENI resources with other GENI resources (e.g. meso-scale OpenFlow and WiMax testbeds; via our switch at the StarLight facility we plan to create experimental L2 topologies that involve international partners).
  
 +Depending on your interests, please use the links to the left to find information you're interested in.
  
Navigation
Print/export
QR Code
QR Code start (generated for current page)