Migrate an Instance to a New Project
Note
Red Cloud 2 is currently in beta testing and not available to all users. If you are not a Red Cloud 2 beta tester, use the production Red Cloud instead. This Red Cloud 2 documentation is still under development.
Beta testers: Report all problems to CAC Help. Please specify Red Cloud 2 when reporting problems. Thank you!
There will be times when you have an instance in one Red Cloud 2 project and would like to migrate it to a different project. For example, if you have been working in an exploratory project and are transitioning to using a permanent project, you may want to bring along the instances you have created. Migrating an instance between projects can be done through the Red Cloud 2 (Horizon) web interface and is a three-stage process:
- Prepare the volume of your source instance.
- Transfer the volume to the destination project.
- Create an instance in the destination project from the shared volume.
The first and second stages must be performed by a user with access to the 'source' project, and the second and third stages must be performed by a user with access to the 'destination' project. The following instructions assume you are comfortable managing an instance through the Horizon web interface.
Preparing the Source Volume
In this stage, you will be working with the "volume" upon which your instance is based. Since the volume is currently In-Use by your instance, you will need to delete the instance to make the volume Available for sharing. Note that the volume containing the essence of your instance will actually be "moved" from the source project to the destination project. If you would like to have copies of the instances in both projects, there is an optional step at the end of stage 1 that lets you do so.
Follow these steps:
-
Log in to the Red Cloud 2 Horizon web console and select the source project.
-
In Instances in the Compute tab, identify the instance you would like to migrate.
-
Flush all cached changes back to the disk and detach all additional volumes attached to the instance. These must be migrated separately and reattached in the destination project. You will not see the option to detach volumes if your instance is shelved.
-
Using the instance's dropdown menu,
Shut Off
the instance. -
Click the instance's name in the list to see its details. Scroll to the bottom to find Volumes Attached and click on the instance's volume (at this point, there should only be one).
-
In the volume's page, click
Edit Volume
. In the dialog, change the volume's name to something you will recognize, then clickSubmit
. -
In Volumes in the Volumes tab, use the renamed volume's dropdown menu to
Create Snapshot
. Give the snapshot a name you will recognize and clickCreate Volume Snapshot
.- By default, when an instance is deleted, its volume is not deleted. In case that default was overridden when the instance was created, the snapshot preserves the volume from being deleted.
-
In Instances in the Compute tab, use your instance's dropdown menu to
Delete Instance
. -
If you do not need to create copies of the volume or instance, you may delete the snapshot and continue from Transfer the Source Volume.
-
If you would like to keep a copy of the volume or instance in this project, make a new volume from the snapshot.
-
Go to Snapshots in the Volumes tab, find the snapshot you created and click
Create Volume
. If you want to keep a copy of the instance in this project, go to Volumes in the Volumes tab and find the newly created volume, and use its dropdown menu toLaunch as Instance
. -
The new volume is dependent on the snapshot, and it prevents the snapshot from being deleted. However, we can still migrate the original volume to the destination project. If you do, the snapshot will also migrate to the destination project.
-
If you want to delete the snapshots or volumes and you're unable to, please contact CAC Help.
-
Transfer the Source Volume
For step by step instructions on transfering volumes with visuals, see Volumes.
-
In Volumes in the Volumes tab, the volume you want to transfer should now have status Available. Before you proceed, make sure this volume is no longer needed in this project. Any transferred volumes will be inaccessible from the source project.
-
Use your volume's dropdown menu to
Create Transfer
. In the dialog, give the transfer a name and clickCreate Volume Transfer
. -
Save the information in the following page by clicking
Download transfer credentials
. This information will be needed soon. -
If you detached any volumes in stage 1 that you wish to migrate, you can create separate transfers now for each of them.
-
Change your active project to the destination project in the project dropdown.
-
In Volumes in the Volumes tab, click
Accept Transfer
. -
In the dialog, paste the Transfer ID and Authorization Key, then click
Accept Volume Transfer
. -
You should now see the transferred volume, which has the name you assigned to it in stage 1.
Creating a Destination Instance from the Shared Volume
-
Create a security group and a key pair for your migrated instance. If needed, You may optionally create a private network and floating point address.
-
Use the volume's dropdown menu to
Launch as Instance
. -
In the dialog, give the instance a name, then select a flavor, a network, a security group, and a key pair. In the dialog's Source tab, notice that Select Boot Source is set to Volume, and your transferred volume has been selected. Do not change these values. When you have updated all the necessary settings, click
Launch Instance
. -
In Instances in the Compute tab, your new instance should be starting up.
-
If you want to migrate additional volumes, accept each of their transfers now and attach the drives to the new instance.