Version 2 (modified by ibaldin, 9 years ago)

--

Best practices for setting up a distributed production environment

Introduction

Setting up a production ORCA configuration requires careful and meticulous approach to avoid common problems. This document attempts to summarize best practices used at RENCI for deploying ORCA.

Prerequisites

Software prerequisites

Build ORCA from source

Understanding container configuration: ORCA_HOME, ORCA_LOCAL, and all that

Actor configuration

Preparation

First you must decide and document the topology of the ORCA actors in the future deployment - how many Tomcat containers you will have, which hosts they will be located on and which actors will be deployed in which container.

The canonical way, in which RENCI sets up ORCA is to have $ORCA_HOME=/opt/orca on each of the deployment hosts. ORCA-modified tomcat is installed under $ORCA_HOME/tomcat and $ORCA_HOME/tomcat/start.sh and $ORCA_HOME/tomcat/stop.sh scripts are modified to reflect the $ORCA_HOME setting by prepending them with

export ORCA_HOME=/opt/orca

MySQL database on each of the hosts must be databaseSetup initialized? with the schema. Loading inventory files is optional.

$ORCA_HOME should also contain

The deployment can use a single source tree located on the machine, where you build ORCA, which has Java, Ant and Maven. The hosts with Tomcat containers should have the same version of Java as is used on the build machine.

Attachments