CAVEATS:
This is prerelease software that comes without any formal support and limited documentation. Please be aware of this when installing this software. This package may be completely rewritten in the not too far future. Please submit and changes and bugfixes back to us.

REQUIREMENTS:
This software requires the perl DBI module and has only been tested with MySQL as the RDBMS, so DBD:mysql is required for MySQL. If you are interested in using another RDBMS, you may need to debug the database logging on your own. The mailing pipes-users@internet2.edu mailing list may be a good resource for discussing alternative RDBMS backends. You will also almost certainly have to edit some of the source where the DBD:mysql module has been specified.

OWAMP, BWCTL and Iperf are required. (BWCTL currently requires Iperf.) OWAMP and BWCTL may be obtained from the End to End Performance Initiative web page at http://e2epi.internet2.edu; information on Iperf is available on this page as well. Iperf is an NLANR/DAST product. It is available at http://dast.nlanr.net/Projects/Iperf/.

INSTALL INSTRUCTIONS:
Below are simple instructions to install the ami distribution. The notes below also show how to specify destination paths different from the default. any text in quotes is entered at the prompt without the quotes.

1.  Ensure that you are in the top level directory. By default, pipes-0.1-alpha or
    whatever the current version of the distribution is.
	
2.  "perl Makefile.PL" and enter the appropriate values at the prompts.

3.  "make"

4.  Check to see if you have sufficient privileges to install to the specified
    installation directories. If not, get the required privileges and then
    "make install".

    To specify different install directories from the default:
    TBD
	
	To install everything in a non-standard directory:
    perl Makefile.PL PREFIX=
    e.g perl Makefile.PL PREFIX=/usr/ami

    To specify different directories for the perl modules and
    the other scripts:
    perl Makefile.PL PREFIX= LIB=
    e.g. perl Makefile.PL PREFIX=/usr/ami LIB=/usr/lib/perl5/site_perl/5.8.3

5.  Symlink /usr/local/bin/perl to /usr/bin/perl.
    "ln -s /usr/bin/perl /usr/local/bin/perl"
    Or alter the path to the perl executable on the first line of each
    installed script.

6.  Edit owmesh.conf located under PREFIX/etc by default to suit your
    configuration. When naming your nodes, do not use a '-' character in your
    node names. Ensure that the data directories that you have specified exist
    and that the specified user exists on the machine. Also, make sure that the
    username under which the test will be run can write to the data
    directories specified in the owmesh.conf file.

7.  On your beacon machines, ensure that owampd and bwctld are correctly
    installed and configured. Also, check to see if the appropriate policies are
    defined in the owampd.limits or bwctld.limits files. Start up owampd and
    bwctld; an example init script, called genericinit-redhat, is included in the
    sample distribution. As the name suggests, it has been tested on redhat
    linux. Read the init script for instructions on how to use the script.

    /owampd -c  (PREFIX/etc by default) -n 
    /bwctld -c  (PREFIX/etc by default) -n 

    Note: the -n  directive is optional and may not be required with
    all owmesh.conf files.

    Verify that you can run bwctl and owping tests between your beacons, by
    manually running the tests. Running powmaster.pl when owping cannot be done
    results in very high memory usage on the machine running owping.

8.  Create the databases you've named in your owmesh.conf config file. Grant
    the appropriate privileges to the users specified on the owmesh.conf
    config file.

    Then use the appropriate script to populate the created databases.
    They are named create***db where the * characters are replaced with
    the appropriate test type. e.g.

    /create_bwdb.pl -c  to populate the bwctl database

9.  Start up bwmaster.pl and powmaster.pl. The -c switch can be used to specify
    the full path to the owmesh.conf config file. If you get an error:
    "no valid paths found", use the -n switch to include the node name of the node
    on which you are starting the master script.

    /bwmaster.pl -c 
    /powmaster.pl -c 

    A sample init script pow.sh is also available in the contrib directory. It
    may be used with minor alterations to start both bwmaster.pl and
    powmaster.pl scripts.

10. On your database server, start collector.pl and bwcollector.pl, using the
    -c switch to specify the path to your config file e.g.

    /collector.pl -c 
    /bwcollector.pl -c 

    Check the logs in the machines in your meshe to see if any error messages
    are being logged.

    Check the data directory to see if the data files are being transferred to
    the database machine. Check the databases to see if data is being inserted
    into the database.