[pve-devel] [RFC pve-cluster] prefer 'name' subkey over 'ring0_addr' for nodename

[Thomas Lamprecht]

I ran into trouble when switching the corosync communication to an own network, under the condition that I didn't want to move the webinterface address/communication with it.
As a reference I followed roughly this procedure:
I configured my new NIC/interface, added a new /etc/hosts entries for my static addresses where corosync should run, then changed the 'ring0_addr' from my nodes and the bindnetaddr from my totem respectively, followed by a reboot.
It worked besides that pmxcfs uses ring0_addr for the nodenames, so .members had "wrong" nodename entries and the ha-manager (for example, there are more problems) couldn't find the lrm_status'es anymore (as it searched for the wrong /etc/pve/nodes/<...>) directory.

As corosync.conf allows a node entry 'name' this should be used if defined, else we keep current behaviour and fall back to 'ring0_addr'.
FYI, pacemacer also uses the name key, but only when ring0_addr is an IP address and not a hostname.

Any objections? Else I will integrate those changes in pvecm, to ease up configuration for separated cluster communications and redundant ring protocol use.

Thomas Lamprecht (1):
  Prefer name key from corosync config for nodename

 data/src/confdb.c | 6 ++++++
 1 file changed, 6 insertions(+)

-- 
2.1.4