rsnt_translations
56,430
edits
Arbutus Migration Guide: Difference between revisions
no edit summary
(updating links) |
No edit summary |
||
| Line 28: | Line 28: | ||
<!--T:9--> | <!--T:9--> | ||
# '''IMPORTANT''': Back up any critical data! While the Cloud has redundant storage systems, no backups of any instances are taken. | # '''IMPORTANT''': Back up any critical data! While the Cloud has redundant storage systems, no backups of any instances are taken. | ||
# Get RC files (used to set environment variables used by the OpenStack command-line tools) after logging in to the URLs above with your | # Get RC files (used to set environment variables used by the OpenStack command-line tools) after logging in to the URLs above with your account credentials: | ||
#* West Cloud: Under Compute -> Access & Security -> API Access tab, select the “Download OpenStack RC File” button. | #* West Cloud: Under Compute -> Access & Security -> API Access tab, select the “Download OpenStack RC File” button. | ||
#* Arbutus Cloud: Under Project -> API Access -> Download OpenStack RC File (use the OpenStack RC File (Identity API v3) option. | #* Arbutus Cloud: Under Project -> API Access -> Download OpenStack RC File (use the OpenStack RC File (Identity API v3) option. | ||
# Copy the OpenStack RC files to the migration host ''cloudmigration.computecanada.ca''. Use your | # Copy the OpenStack RC files to the migration host ''cloudmigration.computecanada.ca''. Use your account credentials for access. | ||
# Open two SSH sessions to the migration host: One for the legacy cloud and one for the new cloud. We recommend that you use the <code>screen</code> command in your sessions to maintain them in case of SSH disconnections. (Consult the many [https://www.google.com/search?q=screen+ssh screen tutorials] available on the Internet if you have never used screen before.) In your legacy SSH session, source the RC file (<code>source oldcloudrc.sh</code>) from the legacy cloud, and in the other SSH session, source the RC file from the new cloud (<code>source newcloudrc.sh</code>). Test your configuration by running a simple openstack command, e.g. <code>openstack volume list</code> | # Open two SSH sessions to the migration host: One for the legacy cloud and one for the new cloud. We recommend that you use the <code>screen</code> command in your sessions to maintain them in case of SSH disconnections. (Consult the many [https://www.google.com/search?q=screen+ssh screen tutorials] available on the Internet if you have never used screen before.) In your legacy SSH session, source the RC file (<code>source oldcloudrc.sh</code>) from the legacy cloud, and in the other SSH session, source the RC file from the new cloud (<code>source newcloudrc.sh</code>). Test your configuration by running a simple openstack command, e.g. <code>openstack volume list</code> | ||
# Migrate SSH keys: | # Migrate SSH keys: | ||
| Line 90: | Line 90: | ||
<!--T:19--> | <!--T:19--> | ||
# Open two SSH sessions to the migration host ''cloudmigration.computecanada.ca'' with your | # Open two SSH sessions to the migration host ''cloudmigration.computecanada.ca'' with your account credentials. | ||
# In one session, source the OpenStack RC file for West Cloud. In the other session, source the OpenStack RC file for Arbutus Cloud. As mentioned earlier, use of the <code>screen</code> command is recommended in case of SSH disconnections. | # In one session, source the OpenStack RC file for West Cloud. In the other session, source the OpenStack RC file for Arbutus Cloud. As mentioned earlier, use of the <code>screen</code> command is recommended in case of SSH disconnections. | ||
# In the West Cloud web UI, create an image of the desired volume (Compute -> Volumes and Upload to Image from the drop down menu). We recommend choosing a volume that is not in use (inactive) but the ''force'' option can be used if the volume is active. Make sure to select QCOW2 as the disk format. The command line can also be used to do this: | # In the West Cloud web UI, create an image of the desired volume (Compute -> Volumes and Upload to Image from the drop down menu). We recommend choosing a volume that is not in use (inactive) but the ''force'' option can be used if the volume is active. Make sure to select QCOW2 as the disk format. The command line can also be used to do this: | ||
| Line 163: | Line 163: | ||
<!--T:27--> | <!--T:27--> | ||
# Open two SS sessions to the migration host ''cloudmigration.computecanada.ca'' with your | # Open two SS sessions to the migration host ''cloudmigration.computecanada.ca'' with your account credentials. | ||
# In one session, source the OpenStack RC file for West Cloud. In the other session, source the OpenStack RC file for Arbutus Cloud. As mentioned earlier, use of the <code>screen</code> command is recommended in case of SSH disconnections. | # In one session, source the OpenStack RC file for West Cloud. In the other session, source the OpenStack RC file for Arbutus Cloud. As mentioned earlier, use of the <code>screen</code> command is recommended in case of SSH disconnections. | ||
# In the West Cloud web UI, create a snapshot of the desired instance (Compute -> Instances and Create Snapshot from the drop down menu). The CLI can also be used: | # In the West Cloud web UI, create a snapshot of the desired instance (Compute -> Instances and Create Snapshot from the drop down menu). The CLI can also be used: | ||
| Line 204: | Line 204: | ||
There are several steps that need to be taken in order to make this work. The simplest method is to use Globus Connect Personal client with Plus subscription. Following is a list of steps required: | There are several steps that need to be taken in order to make this work. The simplest method is to use Globus Connect Personal client with Plus subscription. Following is a list of steps required: | ||
# '''Request a Globus Connect Personal Plus subscription:''' | # '''Request a Globus Connect Personal Plus subscription:''' | ||
## Send email to globus@ | ## Send email to globus@tech.alliancecan.ca with your information and ask to be added to the Globus Personal Plus subscription | ||
## Receive Globus Personal Plus invitation and follow the instructions within. | ## Receive Globus Personal Plus invitation and follow the instructions within. | ||
# '''On each cloud instance involved in the data transfer, enable Globus Connect Personal:''' | # '''On each cloud instance involved in the data transfer, enable Globus Connect Personal:''' | ||
| Line 222: | Line 222: | ||
<!--T:32--> | <!--T:32--> | ||
Contact [[Technical support]] (globus@ | Contact [[Technical support]] (globus@tech.alliancecan.ca) if any issues arise during this whole process. We also recommend you submit a support ticket in advance if you have very large volumes to move. | ||
=== Small data volumes: rsync + ssh === <!--T:33--> | === Small data volumes: rsync + ssh === <!--T:33--> | ||
| Line 239: | Line 239: | ||
<!--T:37--> | <!--T:37--> | ||
Support requests can be sent to the usual Cloud support address at [mailto:cloud@computecanada.ca cloud@ | Support requests can be sent to the usual Cloud support address at [mailto:cloud@computecanada.ca cloud@tech.alliancecan.ca] | ||
</translate> | </translate> | ||
[[Category:CC-Cloud]] | [[Category:CC-Cloud]] | ||