Fixed:
  + Token Generation per Cassandra instance
  + Database comes up properly, with new init Token

Needs work:
  + Tokens get generated, but for some reason, they are not unique, I did some testing, and it seems to check out, must be something simple I need to look at.

Needs finishing:
  + YCSB Workload Gen script
Fixed the bug mentioned before, now all nodes join, with good keys.

Note: Ownership information does not include topology, please specify a keyspace.
Address         DC          Rack        Status State   Load            Owns                Token
                                                                                           169273719020049289134547954145910618441
                                                                                           10.0.0.20       datacenter1 rack1       Up     Normal  9.08 KB         100.00%             0
                                                                                           10.0.0.19       datacenter1 rack1       Up     Joining 4.58 KB         0.00%               112676359412003132998911472258008533725
                                                                                           10.0.0.21       datacenter1 rack1       Up     Joining 4.58 KB         0.00%               169273719020049289134547954145910618441
Old work I did when integrating DayTrader with Apache into CloudBench.

A lot of the pieces that IBM contributed are still lingering, but the

Code works with CloudBench -- It does a simple wget against the DayTrader Server.

Here is the CloudBench Config for the Daytrader-Open:
** Keep in mind, this is simply modified quickly to show DayTrader-Apache working **

** There are still some old bits in there which Marcio and Michael built **

[AI_TEMPLATES : DAYTRADER-OPEN]
SUT = client_daytrader->was->db2
LOAD_GENERATOR_ROLE = client_daytrader
LOAD_MANAGER_ROLE = client_daytrader
METRIC_AGGREGATOR_ROLE = client_daytrader
CAPTURE_ROLE = db2
LOAD_BALANCER = $False
LOAD_BALANCER_TARGET_PORT = 9080
LOAD_BALANCER_TARGET_URL = daytrader
LOAD_BALANCER_TARGET_CHILDREN = 2
LOAD_BALANCER_PORT = 9080
LOAD_BALANCER_URL = daytrader
LB_SETUP1 = cb_restart_loadbalancer.sh
LB_RESET1 = cb_restart_loadbalancer.sh
DB2_SETUP1 = cb_setup_ramdisk.sh
WAS_SETUP2 = cb_restart_was.sh
DB2_SETUP2 = cb_restart_db2.sh
WAS_RESET1 = cb_restart_was.sh
DB2_RESET1 = cb_restart_db2.sh
START = cb_daytrader-open.sh
LOAD_PROFILE = default
LOAD_LEVEL = uniformIXIXI1I10
LOAD_DURATION = uniformIXIXI90I120
Changes:

Feature: New and improved configure utility. The new utility generates specific command
line parameters, allowing each individual component that is part of the
dependency list to be installed using multiple methods (e.g, package-manager,
git, python easy_install) in a linux distro-specific manner. Information about
specific command line parameters and even dependency components versions are
extracted from the configs/templates/dependencies.txt file (a "private" version
of this file name [username]_dependencies.txt can also be created).

Feature: A more configurable method for fault injection. Now "fault" and "repair"
command pairs are specified in the [PROVENANCE]_fault_injection_situations.txt
file, being each pair associated to a "situation". When executing hostfail/hostrepair
commands, an experimenter uses the "situation" as one of the parameters, and the
appropriate command line (fault or repair) is then executed. An initial list of
"situations", applicable for OpenStack clouds, was put in place in the file
PUBLIC_fault_injection_situations.txt. These cover both the ability to simply
shutdown a service (<service>-ss) or to ungracefull kill the process that provides
the service (<service>-kp). There are new three new api calls, faultlist, faultshow
and faultalter, that can be used to manipulate the fault injection "situations".

Feature: [Change submitted externally by Michael Hines (mrhines@us.ibm.com)] This is a massive
 (but well-tested) merge which introduces core support for live migration and fault
 tolerance but without introducing any new objects. GUI support is available. CLI support
 is available. Migration over custom network interfaces is available. Migration in OpenStack
  is available. RDMA support is available (FTC only). FT support is available (FTC only).
Simcloud support is available (for regression testing).

Feature: [Change submitted externally by Michael Hines (mrhines@us.ibm.com)] OpenVPN support
 is available through the use of OpenStack meta-data service (config-drive, specifically)

Code Maintenance: [Change submitted externally by Michael Hines (mrhines@us.ibm.com)] Regression
test infrastracture has been made more portable to run as any user. The regression is now
able to mask all the random information in the golden output and properly compare it to the
 current output with little or no INFO messages

Code Maintenance: [Change submitted externally by Michael Hines (mrhines@us.ibm.com)] Many
 additional bugs fixes.
Update README.md
Update README.md
Update README.md
Quick bugfix correcting the URL for the repository for the "HTML" package
Merge branch 'master' of github.com:ibmcb/cbtool
Added code to enable sharding of data across cassandra nodes.
Merge branch 'master' of https://github.com/jtaleric/cbtool
Add shard to the Cassandra database
airesize working, added Apache2
Bugfix: If the resize of an AI (Vapp) fails, then make sure that the AI is brought
back from the "resize" to the "attached" state.
Bugfix: When attaching a new cloud, check if all mandatory parameters for each AI/Vapp
are properly defined, issuing an error if they are not.
Merge pull request #14 from jtaleric/master

Cassandra work
this stuff doesn't need to be here
merged with upstream
merged with upstream