Deploying the Velostrata Management Server Appliance

The VMware Client Integration Plug-in must be installed to enable OVF functionality. If it is not installed you will be prompted to install it.

Resources required for the management virtual appliance depends on the scale of migration planned. Below are  the recommended specifications:

Medium scale:  
Up to 100 concurrent migrating VMs and under 1Gbps available migration bandwidth.
Required resources: 2vCPU, 4GB RAM

Large Scale:
Over  100 concurrent migrating VMs or over 1Gbps available migration bandwidth.
Required resources: 4vCPU, 8GB RAM

Note: Fully cached VMs should not be considered for the scale estimation

To deploy the Velostrata Management Server Appliance:

  1. Download the latest version of the Velostrata Manager Virtual Appliance from: http://tiny.cc/velos-v3-ova-latest
  2. In the vSphere Web Client, right-click an object and select Deploy OVF Template...
  1. On the Select Source page, enter the URL or click Browse, select the OVA file and then click Open.
  1. Click Next. The Review details appear.
  1. Enter a Description if required and then click Next.
  1. In the Select name and folder page, enter a Name for the Velostrata Manager Virtual Appliance.
  2. Select a folder or datacenter on to which the OVA will be deployed.
  3. Click Next.
  1. On the Select a resource page,  select a location to run the deployed template.
  2. Click Next.
  1. On the Select storage page, select the virtual disk format. Typically keep the default selection (can be customized).
  2. Select the VM Storage Policy.
  3. Select the destination storage to use for the VM.
  4. Click Next.
  1. On the Setup networks page, configure the networks the deployed vApp should use. 
  2. Click Next.
  1. On the Customize template page, enter the Subscription ID. The Subscription ID is unique and has been provided to you with the Velostrata solution welcome kit.

Note: You may deploy different Velostrata Manager Virtual Machines for different vCenter servers. As long as you use the same Subscription ID across all Velostrata Manager Virtual Machines, the licensed capacity for that subscription is shared and the total Virtual Machines running in cloud will be counted across.

  1. Deselect Enable pro-active support, if you want to opt out of Velostrata's pro-active support.
  2. Expand the General section.
  3. Expand the Networking Properties section.
  1. Enter the Hostname for the Virtual Appliance.
  2. Enter a static IP Address, Netmask, Default Gateway and DNS server for the Velostrata Manager Virtual Appliance.

Note: While DHCP is supported, persistent address reservation on the DHCP server is required as the registration with vCenter is static. Otherwise, the plug-in will need to be unregistered and re-registered every time the DHCP IP address changes.

  1. If you are using an HTTP proxy, enter the HTTP Proxy parameter. Proxy authentication is not supported.
  2. Optional: If your VPN to AWS/Azure is not configured as a routed destination on your LAN switch or router, you may enter the Static network route to reach the subnets on Azure. The address is in the form x.x.x.x/x y.y.y.y, where x.x.x.x/x is the AWS VPC/Azure VNet CIDR, followed by a space and y.y.y.y is the VPN Gateway IP.
  3. Click Next.
  4. Review the Ready to complete page.
  1. Select Power on after deployment to power up the Velostrata Manager Virtual Appliance VM right away.
  2. Click Finish. The Deploy OVF template task appears.
  3. Once the OVF Deployment completes, you must login to the Velostrata Web Manager to accept the EULA. Follow the steps here to perform that final step.