Score:0

Replacing pacemaker ip addresses with static IPs and then back again

in flag

Looking to upgrade corosync/pacemaker, a problem is that version 2 and 4 of corosync cannot communicate.

Having 3 nodes, on Ubuntu 20.04, seems like it will lead to a momentary split brain, will all nodes upgrade and come back on, even if I carefully put them on standby and everything falls over to 1 host.

So I'm thinking: what if I:

  1. Made those IP addresses static
  2. Do the upgrade on all machines
  3. Have pacemaker take over again. Meaning: ip addresses are no longer static but virtual/floating.

Problem is: I can't seem to find documentation on this. SEO seems to just send me to general articles about pacemaker.

I'm at a loss for how to do this, maybe someone here knows or can steer me in the right direction?

Any help is appreciated.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.