Hi,
You can use ansible, or automate the deployment using scripts
If the cluster does not form, I would suggest to double check the values you are using for the option --starter.join
Assuming you have 3 machines, A, B and C, you can use a comma separated list of values for the --starter.join option, i.e. --starter.join=A,B,C
A,B and C can be IPs or host names
If you are using 3 different machines, obviously you can use the same directory name for the option --starter.data-dir . What Omar had in mind when he wrote to use a different directory (db1, db2 and db3) was a local test. When using asible you probably would like to have identical machines and commands. Assuming you are using a fast local SSD disk for your data directory (recommended) you can pass to the --starter.data-dir the mount point of this disk, e.g.
--starter.data-dir=/data
I would also strongly suggest to use the option to use RocksDB as engine: --server.storage-engine=rocksdb
Useful option is also --log.dir=path-to-log-dir
So a possible command to be run on each machines to form the cluster could be similar to the following:
arangodb --starter.data-dir=path-to-data-dir --starter.join=A,B,C --server.storage-engine=rocksdb --log.dir=path-to-log-dir
Execute the above command on machines A,B and C
Please could you try a fresh start (delete old database directories) and see if it now works. If you can send us the errors you see, from the starter shell and the log files, that can help with understanding next step
Hope this helps,
Santo