Suggestions for maintaining a standalone configuration file for a cluster of multiple co-located live-backup nodes

Issue

• We have 4 co-located live-backup nodes in the HornetQ cluster with one backup on each live node. For the deployment/setup of this in different environment we currently just maintain one standalone-full-ha.xml with all the cluster connectors and socket bindings defined. And replace the node names of live and backup for each node where necessary.

• However, this would work fine as long as we have only 4 nodes. But when we plan to either add/remove the nodes from the cluster we would have to change in all the node's standalone configuration file. We are looking for suggestions on a better cleaner strategy which would help in quick alteration as per the scalability need.