* create_key: If defined to True then ssh-keygen is called on local machine and then:
***create_key**: If defined to True then ssh-keygen is called on local machine and then:
private key copied to ~/.ssh on management node
private key copied to ~/.ssh on management node
public key inserted into authroized_keys on SQL_BK_DEST_HOST
public key inserted into authroized_keys on SQL_BK_DEST_HOST
* SQL_BK_DEST_HOST: IP number of Machine where we store mysql dumps
***SQL_BK_DEST_HOST:** IP number of Machine where we store mysql dumps
* SQL_BK_DEST_DIR: Directory on backup machine for mysql dumps. Note this is owned by ec2-user and is manually created. It should be cluster-specific, i.e. different for each cluster
***SQL_BK_DEST_DIR:** Directory on backup machine for mysql dumps. Note this is owned by ec2-user and is manually created. It should be cluster-specific, i.e. different for each cluster
* SQL_IP: IP number of slurm mysql machine
***SQL_IP:** IP number of slurm mysql machine
* sqlUsername,sqlPasswd Mysql username/password, same as in slurmdbd.conf
***sqlUsername,sqlPasswd** Mysql username/password, same as in slurmdbd.conf
Other VARIABLES:
Other VARIABLES:
defined in default/main.yml
defined in default/main.yml
* BIN_DIR: "/root/bin" #where the backup shell script and mysql.conf exists on Management Node
***BIN_DIR:** "/root/bin" #where the backup shell script and mysql.conf exists on Management Node
* SQL_BK_DATA_DIR: "/tmp" # where the inital dump exists on the management node. The file is deleted after a scp so it should not fill up disk
***SQL_BK_DATA_DIR:** "/tmp" # where the inital dump exists on the management node. The file is deleted after a scp so it should not fill up disk
* SQL_USER: "ec2-user" The user account on SQL_BK_DEST_HOST. Normally ec2-user but could be something else for security reasons
***SQL_USER: "ec2-user"** The user account on SQL_BK_DEST_HOST. Normally ec2-user but could be something else for security reasons