1

I have 4 Rancher servers: one for each environment: dev, sandbox, staging & prod.

3 of them are of an older Rancher 1.4 version (sandbox, staging, prod) & are hosted on OVH hosting, the one left (dev) is on thr latest 1.6.14 & AWS.

I need to move 3 hosts from OVH to AWS & attach all of them to the only one aws Rancher server which already has 1 dev host.

If I stop rancher-agent on one of OVH rancher hosts & reconfigure it to point to aws, then it appears there in the console, but the config for stacks & etc is lost, as it’s, probably, stored in mysql of the original rancher server.

If I deploy a host from each of the OVH rancher servers to AWS, then I’m stuck with the same problem, after I switch the new hosts agents to the only aws rancher server the configurations for stacks & etc will be lost.

Please advise on the strategy to merge all that into single aws rancher server + 4 hosts: one for each environment. I’m trying not to recreate all 3 environments on aws manually, to avoid downtime & a lot of manual work.

Thanks!

1 Answers1

1

First of all you need to support HA mode. You will need:

  1. external MySQL DB (e.g. AWS RDS Aurora)
  2. external load balancer (e.g. AWS ELB)
  3. 2 additional Rancher Server Nodes (to support quorum of 3)

Once you will be ready with external DB Rancher would ask you to backup & restore his database in it. After that you'll be asked to redeploy Rancher Server with additional params for external DB connection. Then you'll be able to run two more Rancher Server Nodes (e.g. using AWS ELB).

When previous steps have finished you would be able to add more Rancher Agent Nodes in AWS directly from Rancher Hosts tab. After that you can just switch off OVH nodes - payload would be transferred to AWS automagically.

Make sure to backup & restore all databases or data-sensitive instances on OVH hosts.

More information such as HA Requirements etc. can be found in documentation.

Maksim
  • 329
  • 1
  • 4