Successfully tested the fourth patch, the following test were done: -) cluster creation with one corosync network (NO RRP) -) cluster creation with RRP in passive mode on two diffrent networks -) addition of nodes to the setups two from above
This series has the intention to simplify and solve some bugs when running corosync on a completely independent network. Also enables the use of ring 0 and 1 for pvecm node addition commands (also useful when corosync is on its own network). changes since v2: -) fixed memory leak in first patch -) more testing (esp. 4th patch) changes since v1: -) combined previous patches into one series -) RRP support on cluster creation (new) -) better parameter names and support for ring 0 and 1 addresses when adding a node -) small cleanup of error handling (no behaviour changes) in pmxcfs Thomas Lamprecht (4): prefer 'name' subkey over 'ring0_addr' for nodename clean up some error handling use 'name' over 'ring0_addr' and prepare for rrp improve RRP support and use 'name' subkey as default data/PVE/CLI/pvecm.pm | 182 +++++++++++++++++++++++++++++++++++++++++++++----- data/src/confdb.c | 9 +++ data/src/dcdb.c | 6 +- data/src/dfsm.c | 21 +++--- data/src/quorum.c | 23 +++---- 5 files changed, 198 insertions(+), 43 deletions(-) -- 2.1.4 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
