Add a Cloud Extension

Adding a Cloud Extension from vCenter

Using this installation method will only support migrations of VMs from on-prem into a target cloud.

To add a Cloud Extension to GCP:

Installation of this Cloud Extension will support migration of VMs:

  • From on-prem to GCP
  1. On the vSphere vCenter Web Client, right-click Datacenter and select Velostrata Operations > Add Cloud Extension. The Cloud Access Credentials page appears.
  1. From the Cloud Provider drop-down list, select GCP.
  1. For the Cloud Credential,:
  • Choose Select from existing credentials and select one of the saved credentials.

or

  • Select Create a new credential and enter the Credential Name and click Choose File, select the JSON file, and then click OK.

Note: The JSON file is automatically downloaded when creating the service account in Google.

  1. Click Next.
  1. Select the Project to deploy the CE.
  2. Select the required Region.
  3. Select the required VPC.
  4. Enter the Edge Network Tags in a comma-separated list. These are for the cloud edges. The list may include network tags that do not exist yet but will be added to the FW later.
  5. Enter the Default Network Tags for Workloads in a comma-separated list. These are the default network tags assigned to the workloads (unless other network tags are specified when running in cloud) . These are used by networks to identify which VM instances are subject to certain firewall rules and network routes. For example, if you have several VM instances that are serving a large website, tag these instances with a shared word or term and then use that tag to apply a firewall rule that allows HTTP access to those instances. The tags must be validated by GCP, for example, tag  values can only contain lowercase letters, numeric characters, and dashes, and must start with and end with either a number or a lowercase character.
  6. Select the Default Destination Project for Instances to set the default project to run the migrated workload instances in.
  7. Select the Default Service Account for Velostrata Worker to set the default service account which will perform the Velostrata migration operations.
  8. Select the Default Service Account for Instance to set the account that will manage the workload instance in GCP.
  9. To use an HTTP Proxy, select Use HTTP Proxy and complete the FQDN or IP, the Port and select whether to Use proxy also for object store access (performance requirements apply).
  10. Click Next.
  1. Enter the Cloud Extension Name.
  2. Select the Service Account for Cloud Edge (the Storage Object Admin role must be granted to this service account).
  3. Select the required Cloud Extension Size (either Large or Small) and then click Next.
  1. For Node A and Node B, select the Availability Zone and Edge Subnet.
  2. Select the Default Workload Subnet. This subnet will be the default selection used in the Run-in-Cloud wizard. When Cloud Edge nodes (A, B) are placed in different AZs, the Cloud Edge node in the same AZ as the selected subnet is automatically used.
  3. Click Next.
  1. If required, add a custom tag by entering a Key and Value and then clicking Add.  Use lowercase characters, numbers, hyphens and underscores only. A key must start with a lowercase character. Unicode characters are allowed.
  2. Repeat for as many tags as required.
  3. Click Next.
  1. Review the summary and click Finish.
To add a Cloud Extension to AWS:

Installation of this Cloud Extension will support migration of VMs:

  • From on-prem to AWS
  1. On the vSphere vCenter Web Client, right-click Datacenter and select Velostrata Operations > Add Cloud Extension. The Cloud Access Credentials page appears.
  1. Select Velostrata Issued or Marketplace.  If you selected Marketplace, make sure to subscribe to Velostrata Product in the Marketplace - Navigate to the AWS Marketplace and search for Velostrata Hybrid Cloud Software, or use the direct links below:

Note: For more information, see Marketplace Support.

  1. For the Cloud Credential, choose Select from existing credentials and select one of the saved credentials, or select Create a new credential and enter the Velostrata Manager IAM user information into the fields.

Note: To delete a credential using PowerShell. See Remove-VelosCredentials.

  1. Select the Tenancy Type: Default (inherited from VPC setting) or Dedicated instances.
  2. Click Next.
  1. Select the required Cloud Extension Size (either Large or Small) and then click Next.
  1. Select the required Region.
  2. Select the required VPC.
  3. Enter the Cloud Extension Name.
  4. From the IAM Role for Cloud Edge dropdown list, select the IAM role created for use by the Velostrata Cloud Edge nodes (for example, if using the reference CloudFormation template: <VPCName>-VelosEdgeRole).
  5. From the Edge Security Group dropdown list, select the security group to contain the Velostrata components. (for example, <VPCName>-sgVelostrata-…).
  6. From the Default Security Group for Workload dropdown list, select the security group to be used for generic workloads (for example, < VPCName>-sgWorkloads-…).
  7. To use an HTTP Proxy, select Use HTTP Proxy and complete the FQDN or IP, the Port and select whether to Use proxy also for object store access (performance requirements apply).
  8. Click Next.
  1. For Node A and Node B, select the Availability Zone and Edge Subnet (this subnet is considered “public” in AWS terms, and must be routed through an AWS Internet Gateway to allow access to AWS services and to the Velostrata Telemetry Service).
  2. Select the Default Workload Subnet. This subnet will be the default selection used in the Run-in-Cloud wizard. When Cloud Edge nodes (A, B) are placed in different AZs, the Cloud Edge node in the same AZ as the selected subnet is automatically used.
  3. Click Next.
  1. If required, add a custom tag by entering a Key and Value and then clicking Add.  Use lowercase characters, numbers, hyphens and underscores only. A key must start with a lowercase character. Unicode characters are allowed.
  2. Repeat for as many tags as required.
  3. Click Next.
  1. Review the summary and click Finish.
To add a Cloud Extension to Azure:

Installation of this Cloud Extension will support migration of VMs:

  • From on-prem to Azure

Cloud Extension Info details naming on the different Azure Interfaces

  1. On the vSphere vCenter Web Client, right-click Datacenter and select Velostrata Operations > Add Cloud Extension. The Cloud Access Credentials page appears.
  1. From the Cloud Provider drop-down list, select Azure.
  2. Select Velostrata Issued or Marketplace.  If you selected Marketplace, make sure to subscribe to Velostrata Product in the Marketplace by navigating to the Azure Marketplace and searching for Velostrata, or using the direct links below:

Note: For more information, see Marketplace Support.

  1. For the Cloud Credential, choose Select from existing credentials and select one of the saved credentials, or select Create a new credential, enter the Credential Name, paste the Subscription ID, App Owner Tenant ID, App ID, and App Secret Key retrieved before you started this procedure (see Pre-requisites for Adding a Cloud Extension).

Note: To delete a credential using PowerShell. See Remove-VelosCredentials.

  1. Click Next.
  1. Select the required Cloud Extension Size (either Large or Small) and then click Next.
  2. Click Next.
  1. Select the Location: The Azure location in which the Cloud Extension will be deployed.
  2. Enter the Cloud Extension Name: The name for the Cloud Extension to be created.
  3. Select the Subnet Id: The subnet in which the CloudExtension will reside.
  4. Select the Network Security Group (NSG) for Cloud Edge: The security group to which the Cloud Extension will belong.
  5. Select the Default Network Security Group for Workloads: The security group to which the workloads will belong.
  6. Select the Default Subnet for Workloads: The subnet in which the workloads will reside.
  7. Select the Default Resource Group for Workloads: The resource group where the workloads will be placed.
  8. To use an HTTP Proxy, select Use HTTP Proxy and complete the FQDN or IP, the Port and select whether to Use proxy also for object store access (performance requirements apply).
  9. Click Next.
  1. If required, add a custom tag by entering a Key and Value and then clicking Add.  Use lowercase characters, numbers, hyphens and underscores only. A key must start with a lowercase character. Unicode characters are allowed.
  2. Repeat for as many tags as required.
  3. Click Next.
  1. Review the summary and click Finish.
To view the Cloud Extension creation status:

The process of creating the Cloud Extension can be viewed in the Velostrata Cloud Extension portlet on the Datacenter Summary page, and by monitoring the created vSphere task. Once the Cloud Extension has been created, the status is Active.

Adding a Cloud Extension from Velostrata Web Manager

Using this installation method will support migrations of VMs from AWS into GCP.

To add a Cloud Extension to GCP:

Installation of this Cloud Extension will support migration of VMs:

  • From on-prem to GCP
  • From AWS to GCP

Follow these steps to create your GCP Cloud Extension:

1. Login to your Velostrata web appliance at: HTTPS://IP_OF_VELO_APPLIANCE

2. Click the Target Cloud button.

A. If you are prompted for login credentials, you must use 'apiuser' as the username and your password is your Velostrata subscription ID or your GCP billing ID. 

3. Click the Create button. 

4. The Create New Cloud Extension window appears, which has multiple sections you will need to complete. Begin with the Network Settings tab, below. 

Parameter Description Auto-populated Drop Down
Credentials The credentials that you created from within GCP. Yes
Project The project that you are deploying your Cloud Extension (CE) to, and thus where VMs will be migrated into. Yes
Region The region that you are deploying your Cloud Extension (CE) to, and thus where VMs will be migrated into. Yes
VPC The VPC you'll leverage for these migrations. Yes
Edge Network Tags Alert the firewall which rules apply to this Cloud Extension.  No
Defaults:
The following are default options, which means when you perform operations that rely on a default, these are the values that will be populated. For example, when you create a runbook inventory file, you are asked if you'd like to use default target network options. These are the values queried to populate those defaults. 
Default Network Tags Any firewall or port rules for a particular workload being migrated which you wish to be populated by default
No
Default Destination Project for Workloads The destination project (often contained within the host project, above) where migrated VMs will be created.  Yes
Default Service Account for Workloads The GCP service account with proper roles/permissions to perform migration. Yes
Default Service Account for Destination Project The GCP service account with proper roles/permissions to create VMs in the destination project. Yes
Networking options:
Use HTTP Proxy For when you need to leverage an HTTP proxy for access. No
FQDN or IP If this is a static value for the Cloud Extension you are creating No
Port If you must use a specific port for the Cloud Extension you are creating. No
Access object store via proxy Check if applicable. No

5. Complete the Cloud Extension section:

Parameter Description Auto-populated Drop Down
Cloud Extension Name Give your Cloud Extension a name. No
Service Account for Cloud Edge The GCP service account that you previously defined: velo-ce-sa Yes
Cloud Extension Size Small (for less than 50 VM migrations in parallel) or Large (for more than 50 VM migrations in parallel).  Yes

6. Complete the Zones section:

Parameter Description Auto-populated Drop Down
Node A Availability Zone Select two Availability Zones for your CE to exist within for high availability and redundancy. You can deploy both to the same AZ if desired. Yes
Node B Availability Zone Yes
Node A Subnet Select the appropriate subnets based on your Availability Zone selections above. Yes
Node B Subnet Yes
Default Workload Subnet This is the workload subnet that will be used when default values are queried.  Yes

7. Complete the Labels section, where you can define the specific values that named labels will receive. This section is optional.

Any object that is created by the Cloud Extension (CE) will get these labels, which makes it easier to view in networking logs. For example, if you define a label group department (name) and marketing (value), all VMs migrated from this Cloud Extension would have that label for you to see. 

8. Once you are done, click OK to create your Cloud Extension. 

Your Cloud Extension is now created.

The final step is creating a Cloud Details object for AWS, which will represent the AWS object where you are migrating VMs out of. To do this, follow these instructions:

9. Click the Home button to return to the main menu. 

10. Click the Source Cloud icon.

11. Click the Create button.

12. Give this group of cloud details a name.

13. Use the drop down menus to populate the remaining variables which include:

Parameter Description Auto-populated Drop Down
Name The name of this cloud details object (Example: AWS-WEST). No
Credentials Select the AWS account you'll be migrating VMs from. Yes
Region Select what region this AWS environment is located in. Yes
VPC Select what VPC this AWS environment is leveraging. Yes
Security Group Select the security group that we will use to assign to the Velostrata worker service accounts (to perform the migrations from AWS). Yes
Worker subnet for availability zone (1 of 2) Select the first and second subnet where the Velostrata worker service accounts should be created.

Note: these Velostrata worker service accounts will be deleted automatically once the migration operations are complete.
Yes
Worker subnet for availability zone (2 of 2) Yes

Once you are done, click OK. You are now ready to migrate VMs from AWS into GCP.