Turbo Tip: Enabling Projections

Document created by will.searle Expert on Jul 27, 2016Last modified by fran.schwarzmann on Aug 15, 2016
Version 2Show Document
  • View in full screen mode

Most of the time, the plan tab within the platform is used on a project basis.  In other words, maybe you have a large EMR rollout or a hardware refresh in the near term future.  But what if you just want to know when to buy hardware based on historical growth?  Well, that's where projections come into play...

 

Projections calculate infrastructure requirements into the future, so your environment can accommodate changes to workload requirements over time. You can specify the scope of the plan, frequency, and distance into the future. For example, let say executives need help budgeting for the next few years on hardware.  You could run a monthly projection for two years into the future where VMTurbo will decide for you the right time to increase compute and storage capacity. 

 

To begin a projection, first you will want to set the scope. Click edit in the upper-left config panel to run projections on a cluster level or the entire infrastructure.  Then you will want to enable the projection by clicking edit on the projection widget.  This will pop open a window where you can set the end date and monthly frequency of the plan. 

Now, you can either click the run button and VMTurbo will simply use the average growth rate to project when to buy capacity...or you could specify which VMs you would like VMTurbo to use.  If the later is the case, simply edit the demand widget and select the VMs for VMTurbo to use in the projection. 

 

Once the plan completes you can review the data and/or export it to a report!

 

To summarize what each tab is showing in the results the two charts on top are pretty simple and show you compute (mem + cpu) and storage (space, thin prov space, and IOPS) utilization into the future. 

 

The table in the bottom left illustrates the changes made at each iteration in the plan. 

For example, in the screenshot above the Virtual Machine columns says +10,+20,+30 because based on historical growth we are adding roughly 10 VMs each month.  The host column represents a similar value.  In August I will need one more host, and in November I will need six.  Note that if the physical machine column illustrates +1 for consecutive months it does not mean that you need to add one host each month.  It simply means you will only need 1 more host total for those months.  Also, if you are seeing a negative value in the table, this means you can actually get away with running less hardware in the environment.

 

The other three charts on the right show current capacity in relation to when we will exceed it.  Take the example of the datastore chart on the far right.  The green bar shows the current number of datastores and each bar shows how many we need at each month.  So, through October we can fit all the VMs on just two datastores, but by November the environment will need to scale to three (the bars turn red for hosts and storage when you exceed your current capacity). 

Attachments

    Outcomes