Migration from a Bare Metal to a Cloud Native Deployment

Migrating from a bare metal MATRIXX deployment to a cloud native deployment (from the same MATRIXX version) requires temporarily using a hybrid platform made up of components from both deployments. This hybrid environment allows migration to the cloud native deployment without disruption of services.

The procedure is completed in phases. Configuration changes must be made to make communication between services on the two platforms possible. Once those changes are made, migration to the cloud native deployment is achieved one engine at a time.

The following steps give an overview of the process:

1. If necessary, reconfigure the bare metal deployment to use fully qualified domain names (FQDNs), inluding all installations of Traffic Routing Agent (TRA-PROC, TRA-PUB, and TRA-RT/DR.)
2. If necessary, reconfigure the cloud native deployment to use FQDNs, including load balancers.
3. Stop the standby MATRIXX Engine (E2) in the bare metal deployment.
4. Stop both engines, active and standby, in the cloud native deployment.
5. Set up (or request that network administrators set up) DNS aliases between the bare metal and cloud native deployments, and confirm that the aliases are working.
6. Start the standby cloud native engine (E2).
7. When the standby cloud native engine (E2) reaches the standby state, verify replay, object counts, and check for any errors in the logs.
8. Stop the active bare metal engine (E1).
9. Remove (or request that network administrators remove) the DNS aliases.
10. Start the standby cloud native engine (E2).