Bug 1026128

Description of problem:
In RHQ 4.9 there is nothing to prevent you from deploying multiple storage nodes simultaneously, but it is strongly discouraged as it has not been tested and likely will not work as expected. Cassandra can handle multiple nodes joining the cluster simultaneously, but the storage node deployment process will require some changes to work.

In a normal production environment, storage nodes will be running on their own dedicated machines with their own agents each of whom send separate inventory reports to the server. Even if multiple storage nodes are imported into inventory in parallel, it will be in separate transactions. If a user wants to deploy multiple nodes, there needs to be a mechanism for queueing up the nodes that are to be deployed. I think the solution here is to disable automatic deployment, and then the nodes will be created with an operation mode of INSTALLED, meaning that they will not be part of the cluster. After the nodes are installed, the user can select multiple node via the UI or from the remote API to be deployed.

Some code changes will be necessary to support this as well as a good bit of testing.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: