Hello Experts,
I have 10 esxi host on-premise and will be planning to move on AWS. I can easily do the sizing and calculate TCO of my VM's by using below VMware quick sizing tool. However, I am not able to find the sizing and cost for my esxi hosts on AWS?
https://vmc.vmware.com/sizer/quick-sizing
https://cloud.vmware.com/vmc-aws/pricing
Regards
PK
Hi PK,
the better the data source available, like RV Tools, the better you can size the environment, correct.
You'd still need to take into account VMs and workloads which may have some limitations when running in a cloud Environment.
Thinking about larger DBs, for example, which may need their own cluster, etc.
These resources shouldn't be "mixed&matched" with other workloads.
Potentially, in some cases, you may also want to have some additional resilience for certain workloads, for which you'd want to have a stretched Cluster instantiated. Those workloads should also be individually taken care of, when sizing the environment.
And I'd also like to point out the need to plan for SLA compliance, depending on the size of the clusters, to be eligible for SLA refunds, in case of an unlikely failure event. (Read more about SLA and refunds here: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.getting-started/GUID-5BE7...)
To conclude: the VMC sizer can give you a good baseline for sizing your environment, but can't really take any "special needs" into account.
On other news: I've received feedback from our Product Management Team, that they are working on a joint Sizer/Cost/TCO Tool, so that one does not need to look in different places. 🙂
Hope this helps,
Rick
Thanks Rick for your help!
Hi PK,
thanks for reaching out with your question.
I suppose you are asking about the licensing of your ESXi Servers, are you?
If this is the case, then you'd be happy to learn that there are no licensing costs for ESXi itself.
You are opting in for a fully managed solution, which has all the licenses needed included.
Among other things this is true for ESXi, NSX-T (within the SDDC), HCX, and more.
We used to have a program for early adopters to get a discount if they'd have certain licenses, but this initiative is no longer running, I'm afraid.
With that being said, and if I understood your ask correctly, you'd no longer "need" your currently owned ESXi licenses.
Feel free to reach out again, if I misinterpreted your question, or if you have any additional asks.
Edit:
In regards to the sizing: the sizing tool should give you an idea of how many Nodes you'd need within VMware Cloud on AWS.
The pricing would then depend on the Type of Node you are using, as well as the Region you'd like to deploy an SDDC in, as there are differences among them.
Also, the final pricing does depend on the time you are planning to use those nodes. Like you are saving up to 50% on a 3 year subscription, compared to on-demand costs.
This Info should be available in the pricing Info you've posted in your opening post.
Be well and stay safe,
Rick
Hi Rick,
Thanks for the information.
I understand the ESXI hosts licensing on VMC. However, I would like to get the basic idea about the VMC pricing.
For ex: I have below specifications on prim and now I want to calculate the TCO or pricing on VMC.
CPU/ vCPU | RAM, GB | Server Qty | TOTAL vCPU | TOTAL RAM, GB | Hypervisor type |
2 | 4 | 19 | 38 | 76 | VMC |
2 | 8 | 3 | 6 | 24 | VMC |
8 | 16 | 18 | 144 | 288 | VMC |
8 | 32 | 41 | 328 | 1312 | VMC |
I tried using VMC pricing link https://cloud.vmware.com/vmc-aws/pricing/calculator but here I don't know the number of host I would require on VMC and that's what I wanted to know.. along with pricong?
Another link is for VMC sizing https://vmc.vmware.com/sizer/quick-sizing where it shows how many esxi host we would require on VMC but no cost?
I also tried VMC on AWS TCO calculator https://vmware.valuestoryapp.com/vmwarecloud/ and it is asking to enter number of vcpus/VM, vRAM/VM but I do have these numbers in total as per the above table. Can't we mention total number of cpu and RAM instead per VM?
Regards
PK
Hi PK,
I've just took the numbers you've provided (thanks for this) and based on the values (not including any Storage details) the calculator comes up with an estimate of 8 i3 Nodes, or even 3 i3en Nodes:
With those numbers, you could then check the pricings for the Region you'd like to deploy in.
In the above example, 8 Nodes i3 in U.S. East would be like:
- on demand, 12 month term: Estimate Cost: $586,433.86
- subscription, 1 year: Estimate Cost: $415,896.00 (when paid upfront)
Please keep in mind that these are only assumptions, as in no way I'd be able to know if this would really suit your needs.
Like I have no knowledge of availability needs (do you need a stretched cluster, maybe?), nor the actual amount of Storage needed, etc. It is only meant to be a rough guideline on how to get a better understanding how sizing/pricing may look like.
But I totally agree that it would be nice to have one go-to sizing/pricing tool, where a customer can view all relevant estimates in one view.
I will feed this back to the team who are supporting the sizing tools available.
In addition, I would recommend to reach out to your Sales Account Team, as they can also help you to get validated numbers and can help you in analysing your current environment, to match with the best Node Type(s) for your needs.
Hope this clarifies it a bit better. If not, happy to discuss this further.
All the best and stay safe,
Rick
Hi Rick,
I did exactly same way!
Thanks for the confirmation. By the way how did you take vcpu count as 1?
Regards
PK
Hi Rick,
As per my understanding, we don’t size the VMs on total allocation or like the native instance VMC don’t fixed allocated sizing. as it’s not an effective/efficient method of sizing. I believe we always size the VM’s on VMC depending on the average resource utilization, i.e.. Average RAM utilization over a week (for example)?
Would it be better to ask for below reports for sizing:
1. RV tool data showcasing exact utilization of resources
2. Need details on Storage, basis that entire landscape on sizing can get change
Regards
PK
Hi PK,
the better the data source available, like RV Tools, the better you can size the environment, correct.
You'd still need to take into account VMs and workloads which may have some limitations when running in a cloud Environment.
Thinking about larger DBs, for example, which may need their own cluster, etc.
These resources shouldn't be "mixed&matched" with other workloads.
Potentially, in some cases, you may also want to have some additional resilience for certain workloads, for which you'd want to have a stretched Cluster instantiated. Those workloads should also be individually taken care of, when sizing the environment.
And I'd also like to point out the need to plan for SLA compliance, depending on the size of the clusters, to be eligible for SLA refunds, in case of an unlikely failure event. (Read more about SLA and refunds here: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.getting-started/GUID-5BE7...)
To conclude: the VMC sizer can give you a good baseline for sizing your environment, but can't really take any "special needs" into account.
On other news: I've received feedback from our Product Management Team, that they are working on a joint Sizer/Cost/TCO Tool, so that one does not need to look in different places. 🙂
Hope this helps,
Rick
Thanks Rick for your help!