Differences

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

Link to this comparison view

public:software:start [2015/09/21 13:53]
ibaldin [Resource monitoring]
public:software:start [2018/04/23 09:44] (current)
ibaldin [GENI Software]
Line 46: Line 46:
 Each rack uses [[public:software:aux_infrastructure:start | several additional components]] external to ORCA but integrated into its operations: Each rack uses [[public:software:aux_infrastructure:start | several additional components]] external to ORCA but integrated into its operations:
   * [[https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=ImageProxy | ImageProxy]] – is a component that helps distribute user-created filesystem/kernel/ramdisk images to different sites. Today’s cloud software (Eucalyptus, OpenStack, xCAT) is built on a single site model in which each site has a separate image repository from which compute instances are booted. When multiple sites are involved, a user must somehow specify which image is to be used and the image must be registered with the selected sites. ImageProxy fulfills this function by allowing the user to specify a URL of the image descriptor meta-file and its hash (for security purposes). When ORCA processes a slice request and decides on a slice binding to particular sites, the ImageProxies at those sites download and register the user image based on a URL of the metafile so the user’s image can be booted on compute slivers within the slice.   * [[https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=ImageProxy | ImageProxy]] – is a component that helps distribute user-created filesystem/kernel/ramdisk images to different sites. Today’s cloud software (Eucalyptus, OpenStack, xCAT) is built on a single site model in which each site has a separate image repository from which compute instances are booted. When multiple sites are involved, a user must somehow specify which image is to be used and the image must be registered with the selected sites. ImageProxy fulfills this function by allowing the user to specify a URL of the image descriptor meta-file and its hash (for security purposes). When ORCA processes a slice request and decides on a slice binding to particular sites, the ImageProxies at those sites download and register the user image based on a URL of the metafile so the user’s image can be booted on compute slivers within the slice.
-  * [[https://geni-orca.renci.org/trac/wiki/shorewall-with-orca | Shorewall DNAT Proxy]] – is component that helps sites with limited public IP address availability to proxy services on TCP/UDP ports running on compute slivers using a single IP address. Its operation is fully integrated with ORCA and is configurable by the site operator. +  * [[https://geni-orca.renci.org/trac/wiki/shorewall-with-orca | Shorewall DNAT Proxy]] – is an optional component that helps sites with limited public IP address availability to proxy services on TCP/UDP ports running on compute slivers using a single IP address. Its operation is fully integrated with ORCA and is configurable by the site operator. 
   * [[https://github.com/RENCI-NRIG/nodeagent2 | NodeAgent2]] - a component that makes it possible to place remote calls onto substrates. Designed with OSCARS and NSI support in mind, it works for other types of substrates as well.   * [[https://github.com/RENCI-NRIG/nodeagent2 | NodeAgent2]] - a component that makes it possible to place remote calls onto substrates. Designed with OSCARS and NSI support in mind, it works for other types of substrates as well.
   * FlowVisor – the software provided by Stanford for creating OpenFlow slices. ORCA communicates with FlowVisor directly via its XMLRPC interface.   * FlowVisor – the software provided by Stanford for creating OpenFlow slices. ORCA communicates with FlowVisor directly via its XMLRPC interface.
Navigation
Print/export