Changes between Version 57 and Version 58 of deploy-am

Show
Ignore:
Timestamp:
05/10/11 16:14:07 (8 years ago)
Author:
chase (IP: 152.3.68.8)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-am

    v57 v58  
    11[[TOC]] 
    22 
    3 = Deploying an Authority = 
     3= Deploying an Authority (Aggregate Manager/AM)= 
    44 
    55== Overview == 
    66 
    7 This section covers deployment steps for a typical ORCA site authority running a Eucalyptus site. The setup presumes that the container with ORCA is deployed on the head node of the Eucalyptus cluster (although this is not a firm requirement).  
     7An ORCA Authority actor runs on behalf of an infrastructure provider (e.g., a cloud site) and exports its resources through ORCA.  This section covers deployment steps for a typical ORCA site authority (AM) running a Eucalyptus cloud site. The setup presumes that the container with ORCA is deployed on the head node of the Eucalyptus cluster (although this is not a firm requirement).  
    88 
    99The configuration of an ORCA site authority for Eucalyptus consists of the following steps: 
     
    1212 * Set up Image Proxy 
    1313 * Optionally setup ssh DNAT Proxy. This component is needed only if Eucalyptus head node has no publicly routable interface or no public IP addresses to give out. 
    14  * Create an ORCA configuration directory ($ORCA_HOME) and populate it with configuration files 
    15  * Download and customize Tomcat servlet engine 
    16  * Deploy ORCA in Tomcat 
     14 * Create an ORCA configuration directory ($ORCA_HOME) and populate it with configuration files describing the cloud site and selected policies. 
     15 * Download and customize Tomcat servlet engine (container) 
     16 * Deploy ORCA into Tomcat container 
    1717 
    18 == Deploying an Eucalyptus/NEuca authority == 
     18== Deploying a Eucalyptus/NEuca authority == 
    1919 
    2020=== Deployment Overview === 
    2121 
    22  * ORCA container is typically set up on the Eucalyptus head node. Can be set up on any host with a route to the Eucalyptus head node. 
    23  * Image Proxy is typically set up on the Eucalyptus head node. Can be set up on any host with a route to the Eucalyptus head node. Eucalyptus user tools (euca2ools) must be installed on this host. 
    24  * ssh DNAT proxy must be set up on the host with a publicly routable IP address and a route to the Eucalyptus head node 
     22 * The ORCA container is typically set up on the Eucalyptus head node.  It can be set up on any host with a route to the Eucalyptus head node. 
     23 * Image Proxy is typically set up on the Eucalyptus head node. It can be set up on any host with a route to the Eucalyptus head node. Eucalyptus user tools (euca2ools) must be installed on this host. 
     24 * ssh DNAT proxy must be set up on a host with a publicly routable IP address and a route to the Eucalyptus head node 
    2525 
    26 For example in the simplest case, when a Eucalyptus head node has a publicly routable IP address and a pool of public IP addresses to give out to VMs, ssh DNAT Proxy is not needed and ORCA container and Image Proxy can be installed on the Eucalyptus head node.  
     26For example in the simplest case, when a Eucalyptus head node has a publicly routable IP address and a pool of public IP addresses to give out to VMs, the ssh DNAT Proxy is not needed and the ORCA container and Image Proxy can be installed on the Eucalyptus head node.  
    2727 
    2828=== Setup Eucalyptus === 
     
    3030We have [wiki:NEuca-overview modified Eucalyptus] to be more friendly to network experimenters. Follow instructions for setting up Eucalyptus with NEuca patches at [wiki:Eucalyptus-2.0-Setup Eucalyptus 2.x setup with NEuca].   
    3131 
    32 There are instruction on how [wiki:NEuca-in-orca to use NEuca with ORCA], which we will be referring to throughout this document, so it is useful to read through it. 
     32There are instructions on how [wiki:NEuca-in-orca to use NEuca with ORCA], which we will be referring to throughout this document, so it is useful to read through it. 
    3333 
    3434== Additional components  == 
    3535 
    36 In addition to Eucalyptus we have developed several components that make a Eucalyptus site more ORCA- and GENI- friendly. These components are: 
     36We have developed several components that make a Eucalyptus site more ORCA- and GENI- friendly. These components are: 
    3737 
    38  * Image Proxy - permits users to post the images for their VM slivers to be posted on HTTP/FTP/bittorrent and have ORCA automatically download and register this image with each site in a slice.  
    39  * DNAT Proxy - permits public SSH access to VMs/slivers on a Eucalyptus cluster that is hosted behind a firewall (i.e. even Eucalyptus public addresses aren't truly public).  
     38 * Image Proxy -  downloads and caches shared VM images from the network using HTTP/FTP/bittorrent, and registers them for use within the Eucalyptus site. The Image Proxy allows ORCA users to reference images from virtual appliance servers or distribute custom VM images for use at multiple cloud sites. 
     39 * DNAT Proxy - permits public SSH access to VMs/slivers even when they do not have public IP addresses (e.g., for a Eucalyptus cluster that is hosted behind a firewall).  
    4040 
    41 Image Proxy is a mandatory component, while DNAT proxy is optional. Both components are setup separately, however from ORCA perspective their configuration is managed through $ORCA_HOME/ec2/ec2.site.properties file. The following sections describe how to set up these components.  
     41Image Proxy is a mandatory component, while DNAT proxy is optional. Both components are set up separately and configured for use by ORCA through the $ORCA_HOME/ec2/ec2.site.properties file. The following sections describe how to set up these components.  
    4242 
    4343=== Image Proxy ===