Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

There are few scenarios when you may need to migrate existing Roost setup like

  • Team size has changed and control-plane needs to be right-sized

  • Availability issues related to the current region/zone

One will need to identify the EBS volume associated with Roost Controlplane. And then plan for a approximately 2 hour downtime.

  1. Establish SSH session to the controlplane

  2. Bring down the Roost services 

    sudo docker-compose /var/tmp/Roost/docker-compose.yaml down

  3. Take EBS snapshot using AWS dashboard (EC2 Service, Volumes)

  4. Unmount the EBS volume 

    sudo umount /var/tmp/Roost

  5. Detach the volume (EC2 Service, Volumes)

  6. Launch the new EC2 instance

  7. Attach the same volume to this new EC2 instance (the volume and EC2 have to be in the same availability zone)

  8. Run the Roost Controlplane 

    /var/tmp/Roost/roost-enterprise.sh -c /var/tmp/Roost/config.json -i roost

  • No labels