Changes between Version 82 and Version 83 of deploy-am

Show
Ignore:
Timestamp:
07/26/12 14:19:59 (7 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-am

    v82 v83  
    55== Overview == 
    66 
    7 An 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).  
     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 an !OpenStack or Eucalyptus cloud site. The setup presumes that the container with ORCA is deployed on the head node of the !OpenStack or Eucalyptus cluster (although this is not a firm requirement).  
    88 
    9 The configuration of an ORCA site authority for Eucalyptus consists of the following steps: 
     9The configuration of an ORCA site authority for !OpenStack/Eucalyptus consists of the following steps: 
    1010 
    11  * Set up a Eucalyptus cluster 
     11 * Set up an !OpenStack or Eucalyptus cluster 
    1212 * Set up Image Proxy 
    1313 * Optionally setup ssh DNAT Proxy. This component is needed only if the cloud site has no publicly routable IP addresses to assign to VMs. 
     
    1616 * Deploy ORCA into Tomcat container 
    1717 
    18 == Deploying a Eucalyptus/NEuca authority == 
     18== Deploying a !OpenStack/Eucalyptus/NEuca authority == 
    1919 
    2020=== Deployment Overview === 
    2121 
    22 Here are some suggestions for possible Eucalyptus cluster [https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=EucaHardwareConfiguration hardware configurations]. 
     22Here you can look at [https://wiki.exogeni.net/doku.php?id=public:hardware:start ExoGENI OpenStack/xCAT hardware configurations]. Alternatively, a less expensive option for !OpenStack/Eucalyptus cluster [https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=EucaHardwareConfiguration hardware configuration]. 
    2323 
    24  * 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. 
    25  * 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. 
    26  * ssh DNAT proxy must be set up on a host with a publicly routable IP address and a route to the Eucalyptus head node 
     24 * The ORCA container is typically set up on the !OpenStack/Eucalyptus head node.  It can be set up on any host with a route to the head node. 
     25 * Image Proxy is typically set up on the head node. It can be set up on any host with a route to the head node. Eucalyptus user tools (euca2ools) must be installed on this host. 
     26 * ssh DNAT proxy must be set up on a host with a publicly routable IP address and a route to the head node 
    2727 
    28 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, the ssh DNAT Proxy is not needed and the ORCA container and Image Proxy can be installed on the Eucalyptus head node.  
     28For example in the simplest case, when a 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 head node.  
    2929 
    3030For creating slice dataplane (Layer 2 network connecting nodes within a slice) within a cluster or between clusters, ORCA can use one of the following approaches: 
     
    3333 * The cluster is given a pool of VLANs by the network administrator 
    3434 
    35 Each Eucalyptus cluster is usually managed by two ORCA actors - one for creating intra-site topologies (named xxx-vm-site), which manages both the Eucalyptus cluster and the switch. The other (named xxx-net-site) is used for connecting to connecting slivers from this site to other sites at Layer 2, if the Eucalyptus cluster has access to a dynamic circuit network (NLR, ION, ESnet) either via direct peering or via a pool of static vlans.  
     35Each !OpenStack/Eucalyptus cluster is usually managed by two ORCA actors - one for creating intra-site topologies (named xxx-vm-site), which manages both the cluster and the switch ([https://wiki.exogeni.net/doku.php?id=public:software:start ExoGENI uses a more sophisticated configuration] of actors). The other (named xxx-net-site) is used for connecting to connecting slivers from this site to other sites at Layer 2, if the Eucalyptus cluster has access to a dynamic circuit network (NLR, ION, ESnet) either via direct peering or via a pool of static vlans.  
    3636 
    3737=== Setup Eucalyptus ===