This file is part of WEEVIL.
2007-11-30 16:22:36 

The experiment contained in this directory is used as an introductory
example in the Weevil manual.  Please, refer to the manual for
complete reference.

The aim of this simple example is to introduce the concepts and models
needed to specify an experiment run.

--------- WORKLOAD

Two automatically generated workload files are included:
  - MyWorkload.wkld
  - wkld_sequential.wkld

You can use them as-is for experiment runs, and consult them as an
example for automatic workload generation.  The actual workloads are
generated from MyWorkload.m4 and wkld_sequential.m4 using the
"weevilgen" command.  You might want to postpone the study of workload
generation to concentrate first on the experiment runs.

-------- EXPERIMENT

The configuration file for the the actual experiment run is
"experiment.m4". It specifies the different features of an experiment
such as: the testbed, the workload, the number and software for
components and actors. Once more, we warmly recommend you read the
Weevil manual (or the related conference papers) to get confident with
the concepts and terminology.

The experiment starts 3 instances of a Siena server and uses three
actors to impersonate the workload and provide stimuli to the servers.

Before running the experiment you should configure it to your
particular setup.  In particular, you should:

- change the WVL_SYS_Host definitions to match hosts you can access
  via ssh.  Also we recommend you setup the testbed so that you can
  use your public key to ssh to remote hosts.

- run ssh-add to open your keystore before launching the experiment

To run the experiment:

1. cd into the experiment directory

2. type "weevil setup-experiment"

3. If the experiment is set up correctly type "weevil run-experiment"

You can follow the experiment evolution with command:
# tail -f experiment.runlog

You should see something like:

###
deploying experiment files...
The deploy copy time is X seconds
starting S0...
starting S1...
starting S2...
monitoring hosts...
communicating with each host on the testbed to estimate the test start time...
The deploy time is 10 seconds
The test will start at 11/30/2007 16:4:59
The deploy and execution time is 23 seconds
killing processes...
stopping system components...
copying logs back...
###

Server logs and error output will be copied to the local directory, actors output
is in weevil-parallel/actorstartoutput/*/$ActorID.out


