vROps Create a Custom Cloud Provider Rate Card for What-If-Analysis Migration Planning

You are a part of the VMware Cloud Provider Program and want send a future client the cost of migrating their on-premise VMs to you using vROps.

Download the cloudprovider_template_ratecard.xlsx and one for an existing provider Microsoft Azure_ratecard.xlsx for a working example of costs.
/ui/index.action#/administration/cost-settings/cloud-providers
Configuration / Cost Settings / Cloud Providers

The link to the template is hidden. You have to click add, fill in the name and logo to find the link on 2nd step.

Review both Instance_2.0 and Storage_2.0 tabs from the Microsoft Azure.
Items to note. Column D (Ram GB). If a VM has 256MB of RAM, fill in 0.25. 512MB is 0.5

I filled in the cloudprovider_template_ratecard.xlsx with VM’s in my lab to match the size.
Add the Cloud Provider. The logo size I have is 116 x 27 Pixels
TIP – The blue Azure logo is a .svg file 600 x 467 Pixels
Validate your saved ratecard.xlsx and Validate.

On the home page / Optimize Capacity / What-If-Analysis / Migration Planning: Public Cloud

SCENARIO APPLICATION PROFILE – Import from existing VM

SCENARIO NAME – VMscribble’s Lab
SELECT CLOUDS – VMscribble – West
Import from existing VM – I picked all the lab VM’s.
SAVE – RUN SCENARIO

Error for a windows VM that has 6 GB of RAM – Unable to identify a matching configuration instance in target location
Fix – ratecard.xlsx copy the Win 2×4 line and paste into a new row below. Edit the RAM from 4 to 6.
Save the sheet.
Edit the Cloud provider and upload the new xlsx. (you do not have to edit any of the saved settings in the wizard).

What-If Analysis – Save Sessions and re-run SCENARIO NAME – VMscribble’s Lab and the Win 2 x 6 will be filled in.

SCENARIO APPLICATION PROFILE – Configure
I picked a random amount of numbers. 55 vcpu / 341 RAM / 900 storage / 9 VMs.
Error – Unable to identify a matching configuration instance in target location
Yet, Microsoft Azure fills in the cost.
I searched for “E64I V3” on the Azure sheet and copied into mine, copied and replaced with my fake costs. The tip is to make sure the vCPU and RAM GB are higher then the 55/341.

Here is a link to download the rate card used in this lab.

Setup

You are a part of the VMware Cloud Provider Program and want send a future client the cost of migrating their on-premise VMs to you using vROps.

Download the cloudprovider_template_ratecard.xlsx and one for an existing provider Microsoft Azure_ratecard.xlsx for a working example of costs.
/ui/index.action#/administration/cost-settings/cloud-providers
Configuration / Cost Settings / Cloud Providers

The link to the template is hidden. You have to click add, fill in the name and logo to find the link on 2nd step.

Review both Instance_2.0 and Storage_2.0 tabs from the Microsoft Azure.
Items to note. Column D (Ram GB). If a VM has 256MB of RAM, fill in 0.25. 512MB is 0.5

Add Provider

I filled in the cloudprovider_template_ratecard.xlsx with VM’s in my lab to match the size.
Add the Cloud Provider. The logo size I have is 116 x 27 Pixels
TIP – The blue Azure logo is a .svg file 600 x 467 Pixels
Validate your saved ratecard.xlsx and Validate.

Migration Planning

On the home page / Optimize Capacity / What-If-Analysis / Migration Planning: Public Cloud

SCENARIO APPLICATION PROFILE – Import from existing VM

SCENARIO NAME – VMscribble’s Lab
SELECT CLOUDS – VMscribble – West
Import from existing VM – I picked all the lab VM’s.
SAVE – RUN SCENARIO

Error

Error for a windows VM that has 6 GB of RAM – Unable to identify a matching configuration instance in target location
Fix – ratecard.xlsx copy the Win 2×4 line and paste into a new row below. Edit the RAM from 4 to 6.
Save the sheet.
Edit the Cloud provider and upload the new xlsx. (you do not have to edit any of the saved settings in the wizard).

What-If Analysis – Save Sessions and re-run SCENARIO NAME – VMscribble’s Lab and the Win 2 x 6 will be filled in.

Scenario 2

SCENARIO APPLICATION PROFILE – Configure
I picked a random amount of numbers. 55 vcpu / 341 RAM / 900 storage / 9 VMs.
Error – Unable to identify a matching configuration instance in target location
Yet, Microsoft Azure fills in the cost.
I searched for “E64I V3” on the Azure sheet and copied into mine, copied and replaced with my fake costs. The tip is to make sure the vCPU and RAM GB are higher then the 55/341.

Here is a link to download the rate card used in this lab.

Menu