Deploying the Velostrata Management Server in GCP

Deploying the Velostrata Management Server into GCP gives you the capability to migrate VMs directly from Amazon Web Services (AWS) into GCP. If you are looking to migrate VMs from on-premises to GCP, you will also need to complete our on-premises deployment

To deploy your Velostrata Management Server in GCP, follow these steps:

1. Login to your GCP Dashboard.

2. Navigate to the Compute Engine section.

3. Click the create new instance option.

4. Give your appliance a name, perhaps "velostrata-mgmt-GCP"

5. Pick any region and zone you prefer, but be sure that your VPC has subnets in each, and that those subnets are where you also plan to deploy your Velostrata Cloud Extension. 

6. Select your instance type. We currently recommend n1.standard2, which comes with 2 vCPUs and 7.5 Gb of RAM.

7. Scroll down to the Firewall group and check the box for "Allow HTTPS traffic".

8. Click the Boot Disk settings

A. Click 'change'

B. Select CENTOS6 image from standard image  library (we will replace the image later on in the procedure)

C. Change disk size to 60GB

D. Click the SELECT button at the bottom to finish.

9. For the network tab:

A. The default network is selected but you can pick a different VPC if desired based on where you plan to deploy this appliance and your Cloud Extensions.

B. For the primary internal IP, you can pick ephemeral or static. 

C. For the external IP, you can do either of the following:

i. Pick ephemeral or static

ii. Pick 'none', but then be sure to have a proxy setup in your VPC that will provide this appliance with external access, which is required to migrate VMs between AWS and GCP.

10. For the management tab:

A. [optional] Add labels so you can recognize this VM

B. For metadata, you will need to add the following key-value pairs: 

Label

Value

Notes

{region_name}_dns-servers

{comma separated list of IPs} (Represents the list of DNS servers)


{region_name}_dns-domain-suffixes

mydomain.com, myseconddomain.com (Represents list of DNS suffixes to add to Linux machines)

The system will also support the following key:values for a default configuration to machines without explicit region configuration:

Default_dns-servers        

{comma separated list of IPs}


default_dns-domain-suffixes

mydomain.com, myseconddomain.com

Region setting will take priority over Default setting.


Furthermore, these settings of the KEY: Values will be applied as follows:

  • dns-servers: Will prepend the list of DNS in resolv.conf file

  • dns-domain-suffixes: will prepend the list of DNS suffixes in resolv.conf file


Notes:

  • Persistence: The DNS setting made by the user are to persist after Reboots

  • Updates to metadata keys will be applied to instances after a reboot.

  • To Opt-Out:

    • No change to instance setting – If user delete all DNS related metadata added to the Project, no action will be taken.

    • Reverting back to DHCP – If Keys exist with empty values, we will revert the DNS setting to DHCP


Once you are done, your Metadata lists will look something like this (with your values provided):

11. Click on "command line" at the end of the page and copy/paste all of the contents into a text editor.

12. From the text editor, find the following parameters (--image and --image-project), example below:  

--image=centos-6-drawfork-v20180327 --image-project=eip-images” 

13. Replace the values for --image and --image-project in this command line so that it looks as follows:

--image=velostrata-mgmt-3-5-0-20182-30875-os --image-project=velospublic”

14. Copy all of the updated commands out of the text editor and paste it into the cloud shell. Then execute those commands.