D
Deleted member 205422
Guest
I do want to just GENERALLY note that proxmox (like other clustered software) does not look at individual nodes as important. the principal of "cattle not pets" applies here- individualistic elements such as names and IPs are not really important. The "proper" way to deal with any changes is to get rid of a node and add a new one, and I agree that means that a lot of customization is left to user provided automation means. In that respect, other clustered options (Xen, VMware) maintain a dedicated management instance that doesnt need changing has benefit over managing your api heads seperately; I also agree with you that using name/ips as unique identifiers is not ideal.
While I am one of those that does like the mgmt instance (or a few put where suitable, not necessarily on the nodes even), it would be perfectly fine to have all nodes equal in this which is how the GUI w/API was built. I would even IP range scan for open 8006s if need be.
But having said all that, once you understand those design criteria, the system is completely workable and doesnt pose any ACTUAL limits. There isnt any NEED to have replacement nodes named the same as prior- they're cattle, not pets.
Correct, but it's a bit like saying there's no need to put lids on manholes, just pedestrians need to stop sleepwalking staring into their cellphones.
This is true FOR ANY CLUSTER. why would you ever do that?! dont move clusters. stand them up anew.
Sometimes you do not move cluster, sometimes it gets "moved" by your helpful network folks because those are separate people from you. If it's environment where you have full control and you needed to move it, you can even SNAT/DNAT the addresses, but if you are put in front of a situation that from tomorrow your network segment is to be different prefix oh and btw no worries the DHCP/RA will be dishing it out accordingly ... but then you realise yours is a PVE cluster...