Version 107 (modified by vjo, 8 years ago)



Software prerequisites

Deploying an ORCA Actor Container in Emulation

Orca actors run within servlet containers (JVMs). This document is intended to assist you in getting a container up and running quickly, with instances of each of the three actors (Service Manager, Broker, and Aggregate Manager) operating in emulation mode.

Emulation Mode Setup

1. Follow the instructions in the setup section of the $ORCA_HOME directory structure page.

2. Download the attached sample emulation configuration and extract it into $ORCA_HOME.

3. Download our slightly-modified Tomcat and extract it into $ORCA_HOME.

3. Make sure MySQL is running on your system.

NOTE 2: For Mac OS X you can use fink to install mysqld and then

$ cd /sw/bin
$ sudo ./mysqld_safe

This will make sure mysqld is running as long as you don't exit this shell

4. Create a mysql database and populate it These instructions help set up a local Tomcat container with an example inventory of substrate that allows ORCA to run in emulation mode. This step is highly recommended before running with real resources to make sure your setup is correct.

3. Copy to $ORCA_HOME and then customize (if necessary; for emulation nothing should be necessary) the container configuration files ( etc.) under webapp/config:

$ cd $ORCA_SRC/webapp
$ cp -r config $ORCA_HOME
$ vi $ORCA_HOME/config/

4. Configure actors for your container by customizing a config.xml. For emulation mode, copy config-all-local.xml to config.xml. The config.xml is then installed to ORCA_LOCAL by generating and deploying the webapp (see below). Edit the new config.xml so that NDL substrate file property of the Euca site actor points to the right file (download the attached uncvmsite.rdf NDL file and put it under $ORCA_HOME/ndl; figuring out the property name in the file and appropriate value for it is left as an exercise to the reader):

$ cd $ORCA_SRC/webapp/actor_configs
$ cp config-all-local.xml config.xml
$ vi config.xml

NOTE: About the config-all-local.xml configuration file: this file describes three actors (a broker, a slice manager and a Eucalyptus site authority) that go into the container. The authority actor automatically delegates 10 instances of virtual machines and 1000 instances of internal vlans to the broker.

Before packaging the webapp, the webapp config directory should be populated with configuration files for ORCA_LOCAL, as described above. Before deploying the webapp, the tomcat container should be configured with a proper ORCA_HOME populated with configuration files as described above.

NOTE: as of Bella 2.0 container administrator login/password credentials are located in

Testing Emulation Mode

Videos attached to this page show how the system works once it is installed (no audio). A simple test with the default actor configuration described above is to

  1. Login to the ORCA portal
  2. Go to Admin tab and click 'View Actors'. Verify that 3 actors are Online.
  3. Go to User tab (Slice Manager). Click on 'Create Reservation'. Select 'Eucalyptus Virtual Machine' from the drop-down menu corresponding to 'Resource Pool'. Change the number of Units from 1 to something else (for anything greater than 10 you will receive only 10 units as that is the size of the initial delegation)
  4. Click 'Create' button
  5. Click 'View All Reservations'. Click refresh button of your browser until the reservation goes into 'Active' state.
  6. You can optionally close the reservation by selecting a check-box next to it and selecting 'Close' from the Action menu.

Testing the sample XML-RPC controller in emulation mode

See section on XMLRPC controller for information.