Ignition redundancy failover during server updates

Hey folks,

I am looking for some best practice advice. I was talking with our systems guy this morning, and he wants to set up an automatic server patching plan on our Ignition environment. I am running version 8.1.47 with a primary server and cold swap back up. The thought was, patch the backup server and reboot. Once the backup is online, force a fail over, patch the primary, reboot, and fail back to the primary. I was looking through the documentation on GWCMD, but I don’t see anything related to forcing a failover. So my question is, what’s the best plan of attack for this request? Do I just stop the Ignition service on the primary before patching, or is there another way to switch to the back up?

The web UI includes buttons to deliberately fail over. Do note that failover is not seamless, so you should not do it at arbitrary times for planned reasons.

In v8.3, the OpenAPI can be used instead of the buttons.

ok that is good to know