Add a script that starts and stops database load

[GoogleCodeExporter]

1. To which tool/application/daemon will this feature apply?

The Tungsten installation Cookbook 

2. Describe the feature in general

a script that starts a database load using the information provided by the 
cookbook infrastructure.

3. Describe the feature interface

A script that starts or stop a load, with minimal info provided by the user.

4. Give an idea (if applicable) of a possible implementation

The script gets the infrastructure info from the USER_VALUES and the NODES_* 
files, then uses that info to call the concurrent_evaluator from Bristlecone, 
sending the load to all masters.

5. Describe pros and cons of this feature.

5a. Why the world will be a better place with this feature.

Users will be able to create a load for a cluster with a simple command

5b. What hardship will the human race have to endure if this feature is
implemented.

Running a switch when this tool is operating may break replication. 

Original issue reported on code.google.com by g.maxia on 6 Mar 2013 at 10:19

[GoogleCodeExporter]

Original comment by g.maxia on 7 Mar 2013 at 8:50

• Changed title: Add a script that starts and stops database load

[GoogleCodeExporter]

A new script was added to the cookbook.
load_data.sh

Syntax: 
./cookbook/load_data.sh {start|stop|print}

The script detects the current topology, and starts a Bristlecone load in each 
node containing a master service 

Original comment by g.maxia on 7 Mar 2013 at 8:53

• Changed state: Fixed

[GoogleCodeExporter]

We'll use 2.1.0 instead of 2.0.8, hence moving the issues.

Original comment by linas.vi...@continuent.com on 27 Mar 2013 at 3:14

• Added labels: FixedIn-2.1.0
• Removed labels: FixedIn-2.0.8