Version 47 (modified by ibaldin, 8 years ago)

--

Deploying an Authority

Overview

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).

The configuration of an ORCA site authority for Eucalyptus consists of the following steps:

  • Set up a Eucalyptus cluster
  • Set up Image Proxy
  • 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.
  • Create an ORCA configuration directory ($ORCA_HOME) and populate it with configuration files
  • Download and customize the tomcat
  • Deploy ORCA in Tomcat

Deploying an Eucalyptus/NEuca authority

Deployment Overview

  • 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.
  • 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.
  • ssh DNAT proxy must be set up on the host with a publicly routable IP address and a route to the Eucalyptus head node

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.

Setup Eucalyptus

We have modified Eucalyptus to be more friendly to network experimenters. Follow instructions for setting up Eucalyptus with NEuca patches at Eucalyptus 2.x setup with NEuca.

There are instruction on how to use NEuca with ORCA, which we will be referring to throughout this document, so it is useful to read through it.

Prepare $ORCA_HOME directory

Follow instructions on how to set up ORCA configuration directory structure, generate one GUID for the new container and two GUIDs and certificates for new actors (make note of actor GUIDs). Be sure to enable remote actor registry in container.properties file.

After that create additional directories for storing Eucalyptus site properties and credentials (ec2.site.properties, ec2.cred.properties files) and Euca site resource description files (in NDL-OWL):

$ mkdir $ORCA_HOME/ndl
$ mkdir $ORCA_HOME/ec2

Eucalyptus credentials

Create user 'orca' or similar in your Eucalyptus cluster portal. Go to the portal and download the users credentials zip file. Unzip the contents euca credentials zip file into $ORCA_HOME/ec2.

$ cd $ORCA_HOME/ec2
$ unzip ~/euca2-orca-x509.zip 

Comment out the first line in $ORCA_HOME/ec2/eucarc (ORCA uses native EC2 tools to talk to Eucalyptus, rather then eucalyptus user tools; the first line confuses EC2 tools):

#EUCA_KEY_DIR=$(dirname $(readlink -f ${BASH_SOURCE}))

Generate a key-pair for Euca for the Eucalyptus 'orca' user created above. The name of this keypair is used later to populate the "ec2.ssh.key" property in ec2.site.properties file below.

$ source $$ORCA_HOME/ec2/eucarc
$ euca-add-keypair orca
$ cat <output_previous_command> > $$ORCA_HOME/ec2/orca

Generate and store resource representations for the Eucalyptus Site

Generate the NDL resource description of the Eucalyptus site and store it in $ORCA_HOME/ndl. Example of an Eucalyptus site NDL resource description can be found here. Consult RENCI staff on how to generate this. Let ORCA_SRC be the root of the downloaded ORCA source. Actor config.xml file will reference this file later.

$ cp $ORCA_SRC/network/src/main/resources/orca/network/rencivmsite.rdf $ORCA_HOME/ndl/.
$ cp $ORCA_SRC/network/src/main/resources/orca/network/renciNet.rdf $ORCA_HOME/ndl/.

Additional components

In addition to Eucalyptus we have developed several components that make a Eucalyptus site more ORCA- and GENI- friendly. These components are:

  • 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.
  • 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).

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.

Image Proxy

ORCA provides the capability for the user to specify urls for the filesystem image, kernel (optional) and ramdisk (optional) in their resource request. The user images would then be used to stand up the vms across potentially multiple independent Eucalyptus sites under ORCA control. The Image proxy is used to serve this purpose. Follow instructions on https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=ImageProxy to setup and run Image proxy. To configure ORCA to use the Image proxy, follow instructions on ImageProxy with ORCA.

Image Proxy is typically deployed into a separate Axis2 container on the Eucalyptus master host. If not, it can be deployed on a separate host that

  • Has a routable path to Eucalyptus head node
  • Has Eucalyptus user tools installed

Image Proxy with Eucalyptus/NEuca

ssh DNAT Proxy Tunneling and Using Shorewall

When you need access to vm instances created in a private address space separated from the public Internet, ssh proxy tunneling can be used. We support Shorewall-DNAT proxy for this purpose. Install and run Shorewall on a machine (the NAT host) that is accessible via the public internet by following instructions at Shorewall setup. To use Shorewall with ORCA, follow instructions for Shorewall configuration for ORCA.

The DNAT Proxy must be installed on the host that has publicly routable IP address and has a route to the Eucalyptus head node. DNAT Proxy is only needed if the Eucalyptus head node has no publicly routable IP address or has no public IP addresses to give out to the VMs.

DNAT Proxy

ORCA Configuration

$ORCA_HOME/config/config.xml

An example of a configuration file for a container with site authority actors managing an Eucalyptus/NEuca cluster and a network switch can be found here. Please modify this file to tailor to your installation. Use the GUIDs generated above for each actor. Name this file 'config.xml' and place it in $ORCA_HOME/config

$ cp $HOME/euca-m.renci.ben-config.xml $ORCA_HOME/config/config.xml 

$ORCA_HOME/ec2/ec2.site.properties

Modify orca/trunk/handlers/ec2/ec2.site.sample.properties for your installation. For the shorewall proxy section, see shorewall-with-orca. For the Image proxy section, see "Handler Integration" in image-proxy-with-orca. Name this file 'ec2.site.properties' and place it in $ORCA_HOME/config .

$ cp $HOME/ec2.site.sample.properties $ORCA_HOME/config/ec2.site.properties 

$ORCA_HOME/ec2/eucanet.cred.properties

Look up the "Credentials" sub-section of the section "Eucanet handler" to populate eucanet.cred.properties file and place it in $ORCA_HOME/config .

Set up Tomcat and deploy the webapp

Download the binary ORCA webapp war file. Folow instructions for setting up Tomcat and deploying a binary webapp.

Some troubleshooting tips

Attachments