When MDB_CLUSTER_SIZE is exported in config.sh or the shell, X number of data mounts and VM's are created.
The new script, cluster.sh is not yet automated, and needs to be documented.
Replication is configured.
The basic process is, set the cluster size, create the VM's, set the api key on the primary, then add the replicas:
export MDB_CLUSTER_SIZE=3
vagrant up
./cluster.sh set
./cluster.sh add 192.168.50.12
./cluster.sh add 192.168.50.13
./cluster.sh status
What does not yet work?
CMAPI errors related to config distribution when adding nodes.
Vagrant often struggles when handling dynamic number of multi-machines.
Need to re-enable apparmor after a successful install and cluster config.
What works?
When MDB_CLUSTER_SIZE is exported in config.sh or the shell, X number of data mounts and VM's are created. The new script,
cluster.shis not yet automated, and needs to be documented. Replication is configured.The basic process is, set the cluster size, create the VM's, set the api key on the primary, then add the replicas:
What does not yet work?