Vmware Cloud On Aws Sizer – Our Sizer and TCO tool can help you estimate the number of hosts needed to run VMs in the VMware Cloud on AWS – but sometimes a ballpark figure won’t do. Sizing is an art, and in this blog post we take 7 steps to get you the most accurate data so you can inform cloud migration decisions.
The VMware Cloud and TCO tool on AWS Sizer helps customers estimate the number of hosts they need to run their VMs on VMware Cloud in an AWS environment. A typical user wants to move workloads from on-premises to the cloud and estimates how many hosts are needed. To get familiar with the basics of the Sizer and TCO tool, please see: How to Get VMware Cloud on AWS Sizing and TCO Model.
Vmware Cloud On Aws Sizer
If you’re just looking to get a ballpark VMware Cloud on AWS sizing estimate, it’s usually enough to enter your on-premises numbers and accept all the sizer defaults for the numbers you don’t have. This is often required in the early stages of a cloud migration project. But if you want more accuracy, you have to do more work.
Vmc Sizer: Understand Your Vmware Cloud On Aws Costs
To get the most accurate size estimate, it’s important to first determine whether your workload is storage, memory, or CPU bound. This will be the driving factor for quantity calculation. Next, we’ll get into the details of each of these possibilities. Regardless of what drives the sizer calculation, this article describes a general pattern to use for sizing.
Sizing is often an art. It is important to consider as much information as possible, make reasonable assumptions, and distill it all into a model that leads to reasonable conclusions. It’s impossible to be exact when sizing, so all we can do is produce a fair amount of estimated range. The following is a series of steps you can take to accurately size your VMware Cloud on AWS deployment.
It goes without saying that the first thing we need to do is determine the workloads we plan to move to the cloud. There are various ways to collect information about workloads, from using vRealize Operations to other tools such as LiveOptics and RVtools. Whichever way you choose to get the data, you need to know how much you can do to get the most accurate results from the sizer. Below is the screenshot showing the required input values. If you don’t have a specific value, you can use one of the VMC sizer defaults.
Different types of workloads have different characteristics. For example, your databases may behave differently than your application workloads. Averages across workloads with different characteristics increase the variance, leading to a less accurate size estimate. To tighten sizing, it’s usually a good idea to categorize workloads based on their characteristics. In this context, we divide databases and applications into separate profiles.
Prepare For Vmware Cloud On Aws By Right Sizing Your Workloads
You can enter each workload category as a separate profile in VMC Sizer. As you can see below, the application profile is different from the database profile. You can enter different workload CPU, storage, and memory values for each profile.
Now that you have data on your premises, you can get a good size estimate. If there is no good reason to set the RAID level manually, select Auto-Auto for host failure tolerance and fault tolerance method. This allows the sizer to select the optimal settings that meet the SLA requirements. Then, enter the workload values for each profile.
On the Recommendations page, you estimate the number of hosts needed to run your workload on VMware Cloud on AWS, along with lots of other information about CPU, storage, and memory usage. We could stop here and use this value, but there are a few more things we can do to increase confidence in our size.
In the previous step, Sizer assumed that you maximize the number of VMs per SDDC. But this may not be what you want to do. Instead, you may want to split your workload across multiple SDDCs based on application type. Or, if you’re close to the configuration maximums for an SDDC, you might want to give yourself some headroom and split your workload across two SDDCs.
Vmware Cloud On Aws: What’s New In Apr 2022
The reason this is important is because each SDDC has the management overhead of running vCenter, NSX, vSAN, etc. You can find the overhead cost on the sizer tool’s recommendation page:
Obviously, if you have two SDDCs, the maintenance overhead needs to be factored in twice. Also, if you don’t max out SDDC, you might not pack that many VMs per host. Currently, the way to manually split VMs into multiple SDDCs in VMC Sizer is to run it twice, once for each SDDC.
Note that this step is optional. Sizer automatically adds management VM overhead for you for as many SDDCs as you need. But this assumes you want to pack as many VMs as possible into each SDDC, which may not be what you want.
Our next step is to get an upper estimate for our size. We do this to understand how far off our estimate is. First, determine if you are CPU, storage, or memory bound. This is easy to do, as the Sizer tool tells you on the recommendation output page:
Cloud Automation Services
Next, set the limiting factor (in this case storage) to the most conservative value that still makes sense to you. For example, you can set Dedup=1 to assume that you get no benefit from dedup and compression.
In the next step, you can test your assumptions by actually running some sample workloads in the cloud.
You already have on-premises data about your workloads, so you already have solid information about what to expect in VMware Cloud on AWS. To gain more confidence that your workload will behave similarly in the cloud, you can take a small sample of applications, move them to a small VMC cluster as a single host, and see what happens. Are you seeing a similar usage pattern in the cloud as in your on-premises environment? How many VMs can you deploy in a VMware cloud on an AWS host before you run into issues?
Getting real data from an actual VMC target environment gives you more confidence in the assumptions you use to size your deployment.
Webinar: Optimize Your Vmware Cloud On Aws
You now have a size estimate based on your on-premises data, an estimate from your upper bound calculation, and an estimate based on data from running a small experiment in the VMware cloud on AWS. If your experiment shows the same behavior as on-premise, you can be very confident with your on-premise predictions. On the other hand, your experiments may take you closer to your upper bound values. In either case, you now have a lot more data to be confident in your size estimate.
Sizing is an estimate based on assumptions. Assumptions are rarely perfect; Therefore, you cannot expect the size estimate to be accurate. Consider instead:
If you overestimate, you artificially increase the cost of the project. If you underestimate, you may face budget problems in the future.
Also consider that unlike your on-premises environment, hosts in the VMware Cloud on AWS can be added in a matter of minutes. It is the force that moves in the cloud. If you underestimate the number of hosts you need, or if you need more hosts for some reason in the future, you can quickly add hosts. And if you find you don’t need as many hosts as you anticipated, you can easily delete hosts.
Aws Managed Services, Migration, Storage Services
There are different strategies for buying hosting subscriptions and only you know which strategy will work best in your case. Given your on-premises workload data, upper bound calculation for hosts, and actual data from running sample workloads in VMware Cloud on AWS, you should have enough information to make a good decision.
AWS VMware Explore 2022 on VMware Cloud and AWSA’s Multi-Cloud Strategies As the latest networking and security for VMware Cloud continue to evolve, cost will continue to be an important factor in the decision to move to the cloud. To better understand total cost of ownership (TOC), VMware has created a simple cost estimation tool for cloud customers on AWS. Introducing VMC Sizer. With VMC Sizer, you can choose your workload type (VDI, databases (Oracle or MSSQL) or general VMs), as well as VM specifics such as vCPU, vRAM, IO, storage requirements and more. With this tool, we’ve taken the guesswork out of understanding the costs associated with running workloads in the VMware cloud on AWS. To get a comprehensive view of costs, you have the option to add several workload profiles to your profile
Aws on premise cloud, vmware cloud on aws, vmware on google cloud, vmware cloud on dell, vmware cloud on aws outposts, vmware aws hybrid cloud, vmware cloud on azure, vmware on aws architecture, vmware on aws pricing, vmware vmc on aws, aws vmware cloud pricing, vmware cloud on aws pricing