Velostrata Configuration issues
Ramu Naik
AWS as source and GCP as destination we had used the GCP native tool “Velostrata” for migration activity and followed steps by step procedure suggested by Google Cloud, even though during the migration we had faced few challenges and showstoppers in achieving the successful migration. Would like to bring to your notice regarding the steps that we had followed for the migration activity.
Below Steps are followed for the Migration Activity
1. Launched the Cloud Market Place and installed Velostrata Manager from GCP console
2. Deployed Velostrata manager and configured following services ( Velostrata Manager Service Account, Velostrata Cloud Extension Service Account, Velostrata Manager and API password and Private key encryption password)
3. Configured Service accounts and provided required permissions in GCP with these roles ( Owner, Compute Admin and Organization Administrator)
4. Configured GCP Network Firewall rules
5. Created GCP Credential File in JSON format
6. Validated Velostrata instance created on GCP console (Verified and were able to login with external IP)
· To access Velostrata management server in GCP we had configured firewall rules
7. Created instance(VM) in AWS and also created AWS IAM roles and provided the access
8. Created source cloud (AWS) credentials & cloud details
9. Deployed cloud extensions in source (AWS) and target (GCP)
10. Installed the pre-package on the source (AWS)
Step by Step Migration Details
|
Activities Performed |
AWS(Source) |
GCP (Target) |
|
|
|
|
|
Launched Cloud Market place and installed Velostrata Manager |
NA |
Configured |
|
Deployed Velostrata manager and configured following services |
NA |
Velostrata Manager Service Account, Velostrata Cloud Extension Service Account, Velostrata Manager and API password and Private key encryption password) |
|
Configured Service accounts and provided required permissions in GCP with these roles |
NA |
Owner, Compute Admin and Organization Administrator |
|
Configured GCP Network Firewall rules |
Created |
Created |
|
Created GCP Credential File in JSON format |
NA |
Configured |
|
Validated Velostrata instance created on GCP console |
NA |
Verified and were able to login with external IP |
|
Created VM using EC2 |
Configured |
NA |
|
Created IAM Roles and provided access for EC2 instance |
Configured |
NA |
|
Created Source Cloud Credentials and Cloud Details |
Configured |
NA |
|
Deploy Cloud Extensions |
Configured |
Configured |
|
Installed Pre-Package |
Configured |
NA |
Showstopper & Challenges
· While Configuring the source cloud extensions unable to populate the GCP cloud provider to provide the GCP cloud credentials in the Velostrata Manager UI.
· Below is the screenshot for the reference of AWS cloud and in the similar way it has to populate for the GCP cloud provider and we will be able to give the credentials once populated.
· GCP is not populated as AWS populated. Above is the screenshot for reference.
Harmit Rishi
For the purpose of clarity, would you be able to specify an issue you encountered (if any)? I ask this because there doesn't seem to be any indication of a question being asked. However, if this thread was created for the purpose of sharing knowledge and your experiences with the migration process then I would like to thank you for providing such detailed steps to the GCP community.
