Below blog will provide our experience in migrating our workloads from HP Public cloud to Auro Public Cloud (Both powered by Openstack)
HP has announced that HP Helion Public Cloud will cease providing services to customers on
January 31, 2016. HP has been sending alerts to all its customers to migrate their instances and
workloads to different clouds well ahead of this time. Since HP Cloud is an OpenStack powered
Public Cloud, the first choice for users would be to move to a different OpenStack powered
Private / Public Cloud.
We were running some of our workloads in HP Cloud which we have migrated to Auro Cloud, a
Canada based OpenStack powered Public Cloud. The migration was done using CoreStack, a
Converged Orchestration Engine which provides a Template driven mechanism for migration and
any orchestration functions for that matter. This blog explains the procedure on how we did the migration
TYPICAL STEPS INVOLVED IN THE MIGRATION WHEN DONE MANUALLY:
- Identify the resource types and actual list of resource that need to be migrated
- Capture the details such as Name, Configuration and other meta data related to each of the
- Identify inter-relationships between resources such as Key pair, Security Group, Image related
to a specific instance
- Create VM snapshots in the source cloud and upload images to the target cloud
- Refer the resource list and definitions and create similar resources in the target cloud
- Configure relationships between resource types such as Instances, Volumes, Keypairs etc.,
- Configure Private and Public Networks in the target cloud
- Move data from the Volumes in the source cloud to similar volumes in the target cloud
- Test the workloads from the target cloud and switch DNS settings as required
- Purge all resources in HP Cloud
MIGRATION USING CORESTACK
When we perform the migration with an orchestration framework such as CoreStack, most of the
above steps can be automated. CoreStack provides pre-built templates that can perform these
steps. Some of the key aspects that help are:
- Resource Discovery feature helps discover and list all resources in the source cloud
- Template Generator feature can be used to generate a template that can re-create the selected set of resources in a target cloud.
- The generator takes care of capturing the name, meta data, relationships and other characteristics of the resources while building the template.
- The generated template can simply be executed in the target environment to provision the resources with exactly the same characteristics.
STEPS FOR MIGRATING FROM HPCLOUD TO AURO CLOUD USING CORESTACK
- Login to CoreStack (https://cloud.corestack.io). You can sign-up for a FREE TRIAL if you
do not have a user account
- Add Service Accounts for HP Cloud and Auro Cloud (or any OpenStack powered Cloud)
a. Service Accounts provides Authentication to the respective Clouds. This helps CoreStack to orchestrate these clouds without requesting for credentials for each template execution.
- Run the template “HpCloud_Download_VM_Snapshot_for_Migration” from the Templates page.This template performs the following actions for Image download.
a. Create a VM Snapshot for the selected VM
b. Launches a Temporary instance in HPCloud
c. Configure Glance client and set-up credentials using Chef
d. Download the VM Snapshot image into the Temp Instance
- Run the Template “AuroCloud_upload_VMimage_from_HpCloud” to upload the snapshotted image to Auro Cloud Glance Repository as a Private image
- Generate Templates for all the resources such as Keypairs, Security Group, Private Network,
Volume in Corestack using Resource discovery and Template Generator
- Execute the generated templates in Auro cloud (Choose Auro Cloud as the Service Account
while executing the Template).
- Run the Template “Launch_VM_in_PublicOpenStack” to create the VM in the target
cloud. While executing the template, all available images including the private image that
we uploaded will be listed in the dropdown for selection.
- Note that Public and Private IP of the instances get changed in Auro cloud. Need to configure
these new IP in all references such as DNS settings for your URL, configuration files
The migrated workload should now be ready for use. You can refer this video link for a quick walkthru
of the above procedure.
Once you have tested your workloads from the target cloud, you can now purge the resources
running in HP Cloud. There are templates available for this purpose as well. Just search for “Terminate”
or “Purge” and you should find them. You can also migrate data in Volumes using Rsync
The best part about doing this using a Template driven orchestration tool is that you can repeat this
multiple times to different clouds, including your own private clouds if you need to create more environments
for QA, Staging etc.,
CoreStack also offers integration with host of other tools to set-up Monitoring, Log Management,
Schedule Back-ups, Continuous Deployment if you would like to extend these actions for your
To view a demo of the same please click https://youtu.be/tsDvzfAQa_M