Installing a parallel AWS instance of Ignition to upgrade versions

Ignition
1

We want to update our front end Ignition from 8.1.48 to 8.1.53. Although this is a minor update and should be relatively seamless IT has chosen that they would prefer to spin up a parallel instance, do the full install on there and validate everything works in a read-only mode then update their load balancers to point at the new server and I would transfer the Ignition license.

My main concern is on the server naming, historian side of things to try to make this seamless. Preferably I'd have the Ignition name be identical to do the transfer but that will cause issues on the gateway network. Having a new server name would affect the SQL drv and such records. So I'm not sure how to approach this.

This process does speak to the merit of moving to a docker setup, that's going to be the plan for the 8.3 migration but for now they just want to update with no structural changes.

2

Deactivate license. Shutdown old server. Change name of new server to match. Activate. Update DB connection(s) to writable.

3

Thanks, presumably I'll have to also re-approve the gateway network connections after the rename? I'm just trying to complete a list of all the necessary steps for the cutover

4

Hmm. Maybe. I think they are uuid-based and may carry through a rename.

If the todo list gets long, re-consider an in-place upgrade after testing. With good backups, I would think that would be lowest risk and quickest resumption of operation. No mucking around with GAN or DB.

5

Yeah, I suggested that but you know IT does IT things and makes it more complicated than it needs to be unfortunately.