Clustering indicates an inability to change IP addresses after...does this mean...

[arretx]

...does this mean that the internal IP address of the node can never be changed, or, in the case of two remote nodes being part of a cluster, does it refer to each node's public IP address?

I'm okay with designating a permanent internal IP for my nodes, but I just want to make sure since it's more likely that the public IP would change at some point than the internal. Thanks!

 

[aaron]

in the case of two remote nodes being part of a cluster

Wait a second, what do you try to build? Keep in mind that for a PVE cluster corosync is used, and it really wants low latency. This could be a problem depending on how far apart the nodes are.

How do the nodes talk to each other? With the public IP or the internal? This "restriction" comes from the fact that the nodes IP addresses are used in quite a few places in a cluster setup (corosync conf, different ssh files,...) and thus changing them without disrupting any services is hard to get right.

 

[arretx]

Ahh...well, that's good to know.

I'm running two nodes, both at different locations in the same city. I was just thinking that clustering them would allow me to manage them remotely without needing two endpoints for login. If this isn't the inherent design, I'll ditch the idea and just make each accessible remotely independently.

 

[aaron]

Okay, running them independently will save you from potential pain then

Having the possibility to manage multiple cluster from one interface is on the long term roadmap.