Migration¶

The migration to the new ScienceCloud has started and technical contacts will be contacted to facilitiate this move. This section will be expanded to include guides that allow users to migrate their project assets (virtual servers, volumes, snapshots, and so on) from the current old ScienceCloud to the new one.

The instructions on how to prepare your machine will be added soon, in the meantime consult with FAQs.

Migration instructions¶

When we discuss migration, we are discussing moving snapshots of your data and your instances. That means we will never touch your running instances nor your data, but that also means that you will need to prepare what is it that you want to move to the new cloud.

The process will be an coordinated effort between you and the Science IT. Please follow the next steps to prepare for it, once you have been contacted to initiate migration.

Pre-migration (you)¶

Snapshots¶

Check all of your existing snasphots of instances. The ones you want to move to the new cloud, rename to migration_ (e.g. migration_instance1).

Instances¶

To create snapshots from existing instances, please follow the steps outlined here. It is recommended to shut down your instance prior to the snapshot and keep yourself a note on the flavor used in order to use new flavor of similar specs. Also, unmount the volume within the instance and detach it via cloud interface (managing attachments - detach).

Warning

⚠️ Due to change in flavors on the new cloud, in case you have flavor ending with -server or -hpcv2, you will need to resize it before creating a snapshot. You can find instructions for resizing here.

After creating the snapshots, rename them to migration_ (e.g. migration_instance1).

Volumes¶

There are 2 options regarding the volumes:
1. Rename them to migration_volume_ (e.g. migration_volume_data1) and we will do the transfer for you at the later timepoint (up to few weeks)
2. Migrate data yourself via rsync command. For more information, check FAQs.

SWIFT containers¶

Data in SWIFT containers that you want to move, please let us know about to do it for you.

Migration (Science IT)¶

Once your snapshots are prepared, we will together define the time slot in which they will be transferred to the new cloud. We will download the snapshots, convert them to appropriate format and upload to the new cloud. Also, once everything is uploaded, you will get a notification from us.

In case there are security groups that you would like to get migrated, please let us know.

Post-migration (you)¶

Once your snapshots are in the new cloud, as a final step you will need to add your keys. You can use your old keys for the cloud, or just create new ones by following instructions outlined here.

FAQ¶

For any further communication, please write to us at help@s3it.uzh.ch.

General information¶

I want to open a project on the new ScienceCloud¶

If you are using ScienceCloud for the first time, your project will be created directly on the new cloud. Please contact us for an initial discussion.

I want to start new instances that I won't need to move. Can I already have a project on the new ScienceCloud?¶

Yes, you can. Please contact us so we can create a new project for you. Over time, all instances from the old cloud will be migrated to it.

I have been contacted about migrating our projects. Although our project is inactive, we have snapshots that we occasionally use.¶

Please reply to the initial email to request an earlier migration of your snapshots.

I am no longer the technical contact.¶

Please reply to the initial email, CC-ing the new technical contact and/or project owner so we can update our records.

Migration information¶

Will all images, snapshots, volumes and security settings be migrated?¶

No, only the ones you prepare for migration. Please refer to the information provided above on how to prepare for migration.

Will we need to modify images and snapshots to make them work on the new cloud?¶

Only if your snapshots were created using the hpcv2 flavor. These should be resized to the hpcv3 flavor before taking new snapshots. Additionally, on the new cloud, snapshots will be in a different format (.qcow2 instead of .raw).

What happens to running instances?¶

We will never modify your running instances. As mentioned above, you will need to create snapshots of them to migrate them to the new cloud.

What flavors will be available on the new cloud?¶

We will offer several flavors on the new cloud, ranging from small ones like 1cpu-4ram-hpcv3 to large ones like 120cpu-480ram-hpcv3. Here you can see the list of available flavors.

What happens to reserved IPs, will they be migrated with the project?¶

Currently, this is not possible, as the new cloud uses a different IP range. If you require reserved IPs, please mention this during the migration discussion.

Will all scripts work on the new cloud?¶

Scripts linked to your instance should continue to work. However, scripts that interact with the OpenStack command line may require modifications. If this applies to you, please contact us so we can assess your needs and provide guidance.

Can we run old and new cloud in parallel?¶

Initially, it is advisable to run both clouds in parallel for 1–2 weeks. However, since the hardware also needs to be migrated to the new cloud, we do not recommend keeping them both active for an extended period.

Do I need to import my own keys?¶

Yes, you will need to import your keys or create new ones.

I have SWIFT containers to move to the new cloud, how to do it?¶

In case you have containers to transfer, please let us know to do it for you.

I want to move my data via rsync. How to do it?¶

To do that, follow these steps:

On the old cloud:
Create a small instance (or reuse existing one) and attach the volume you want to transfer.
Login to instance and create a new ssh key. In case you are not sure how to do it, follow this instruction.
Get the content of your newly created key
cat <key_name>.pub
On the new cloud:
Create a volume same size as the one you want to transfer from the old cloud.
Create a small instance and attach previously created volume. If you are not familiar with it, follow this protocol.
Login to instance and run the following code, that will establish a connection between the instances:
mkdir -p ~/.ssh # creates the .ssh folder
echo "your-public-key-here" >> ~/.ssh/authorized_keys # copy the full content of your previously created ssh key (previous command)
chmod 600 ~/.ssh/authorized_keys
chmod 700 ~/.ssh
Transfer:
Make sure to correctly target the folders on both machines and run the following command on old cloud instance:
rsync -avz -e "ssh -i <key_name>" <old_cloud_mounted_folder>/ ubuntu@<new_cloud_instance_IP_address>:<new_cloud_mounted_folder>