I have applied a RPI 3 as a third node for quorum-only to my cluster and it has been running stable for 3 weeks. I therefore consider it ready to release install instruction into the wild
Step guide:
pve-manager is missing so don't add to /etc/pve/corosync.conf.
PS. if new node is added pve-manager will overwrite /etc/corosync/corosync.conf
PPS. I give no guaranty so everything above is at your own risk.
Step guide:
Code:
0) Login as root on your Pi
1) Install Debian Jessie (Standard system utilities and SSH server)
2) echo "deb http://ftp.debian.org/debian jessie-backports main contrib" > /etc/apt/sources.list.d/jessie-backports.list
3) gpg --keyserver pgpkeys.mit.edu --recv-key 7638D0442B90D010 && gpg -a --export 7638D0442B90D010 | apt-key add -
4) gpg --keyserver pgpkeys.mit.edu --recv-key 8B48AD6246925553 && gpg -a --export 8B48AD6246925553 | apt-key add -
5) apt-get update
6) apt-get -t jessie-backports install corosync
7) sed -i 's/without-password/yes/' /etc/ssh/sshd_config && systemctl restart ssh
8) scp <ip of pve node>:/etc/corosync/* /etc/corosync
9) add new node under nodelist in /etc/corosync.conf (copy one of the current and adjust)
10) for NODE in <ip of pve node 1> <ip of pve node 2>; do
scp /etc/corosync/corosync.conf $NODE:/etc/corosync
done
11) ssh <ip of pve node 1> systemctl restart corosync
12) ssh <ip of pve node 2> systemctl restart corosync
13) systemctl start corosync
14) run corosync-quorumtool to check all three nodes er registret as online and that there is quorum: Quorate: Yes
PS. if new node is added pve-manager will overwrite /etc/corosync/corosync.conf
PPS. I give no guaranty so everything above is at your own risk.