Cloud Extension Overview

Background

Adding a Cloud Extension (CE) deploys Velostrata Cloud Edge nodes, A and B. In GCP (and AWS), a different availability zone should be selected per Edge Node. In Azure, an availability set is used. 

To allow flexibility in deployment and enable you to deploy a CE with a size that corresponds to the intended activity, you can select whether to add a small or large CE. In this release, a typical load for a single Cloud Extension is 50 concurrent VMs for a large CE and 10-15 VMs for a small CE. Depending on actual IO load this can be increased. You can deploy additional Cloud Extensions for increased total VM capacity or to dedicate more IO throughput to specific VMs. You can also deploy Cloud Extensions in different Cloud providers/regions /VPC/VNets for a diverse geographical presence, project isolation, and so on.

You can add custom labels to a Cloud Extension. These custom tags are applied to all instances that are created in the Cloud Extensions, and are used to label the Velostrata Edge Nodes, Exporter, Importer, and wokload instances.

Deployment Options

There are two methods which you can use to deploy Cloud Extensions for Velostrata:

  1. Through the vCenter web plug-in, you can use the Velostrata wizard to deploy Cloud Extensions for GCP, AWS, or Azure. This supports any use cases for on-prem to cloud migration. 
  2. Through the Velostrata appliance web manager, you can create and configure Cloud Extensions for GCP only. This supports only use cases for AWS to GCP migrations.

This table outlines these options:

Source Target Administration Options
On-Prem GCP, AWS, Azure vCenter Only
AWS GCP Web Only
On-Prem and AWS GCP Both vCenter and Web Required

Cloud Extension Sizes

When you create a Cloud Extension you can select the size.

  • Large is the default Cloud Extension size when creating a Cloud Extension and is performance optimized.
  • Small is an alternative Cloud Extension size that is cost optimized.

Note: A Cloud Extension automatically shuts down after one hour of idle time to save costs, in both small and large sizes, and it will automatically power on when a Run-in-Cloud is executed.

Cloud Extension Instance Recommendations

 

Small Cloud Extension (10-15 concurrent migrations)

Large Cloud Extension (50 concurrent migrations)

Cloud Vendor

Instance Type

Cache Size

Temp Storage Size

Core Disk Size

Instance Type

Cache Size

Temp Storage Size

Core Disk Size

GCP

n1-highmem-2

250 GB

100 GB

200 GB

n1-standard-8

1024 GB

250 GB

100 GB

AWS

r4.large or* m4.large

250 GB

100 GB 

20 GB

m4.2xlarge or* r4.2xlarge

1023 GB

250 GB 

100 GB

Azure

Standard_DS11_v2 or*

Standard_DS11

256 GB

28 GB

20 GB

Standard_DS12_v2

or*

Standard_DS12

1023 GB

56 GB

100 GB

 

* Depending on the region

 

 

 

 

 

Tenancy Mode

This only applies to deployments with Azure.

Some regulations and corporate policies may require enterprises to use certain tenancy models when working in a public cloud, mainly for privacy considerations.

Note:  Velostrata supports adding a Cloud Extension in Microsoft's AzureGov cloud. For assistance with this, contact Velostrata Support. Note than an account in AzureGov is required.

You can, when working in AWS, define tenancy mode "dedicated instances". In this mode, hardware is shared only with instances of the same AWS account. This configuration is available per Cloud Extension, and applies to both Cloud Extension instances (Edge Nodes, Exporter), as well as to the workload VM instances that are instantiated in the cloud. The following tenancy type options can be selected when creating a Cloud Extension:

  • Default (inherited from VPC setting)
  • Dedicated instances

All the disks of the Cloud Extension VMs, as well as cached data on S3 are encrypted.