Posts

Posted on

Processor input for workload(s)

What is this feature all about? 

Now Sizer provides an option to select the type of processor the workload (existing or proposed) is running on. This gets factored in while sizing for the workload adding precision to the sizing and overall recommendation.

To give an example of how it helps.. an existing worklaod (say Server Virt, 100 of them) running on a weak processor (say a Haswell 2699v3, specint-38.58) would require less cores in sizing than the same 100 VMs running on a high performing CPU( like Skylake 8156 specInt -68.85).

Previously, the processor for existing workload was not taken into account, though Sizer always used a baseline processor[E5 2680v2] . So irrespective of whether the current worklaod is running on a slowest processor or the fastsest one, sizings used to remain the same.

With this new addition, there is a lot more precision added to sizing as we account for the incremental changes due to different type of processors.

 

How do we handle the processor input during sizing? 

Here is an example: input processor Broadwell E5 2690v4[46.43 specInt]

  • Lets say sizing comes to 32 cores 
  • This sizing is at the baseline [E5 2680v2, 42.31 specInt]  – Sizer defualt used until now
  • This has to be adjusted against the input processor E5 2690v4
  • 32*[46.43/42.31] = 35.11
  • The way to read this: 
    • If your existing processor was E5 2680v2(42.31), then the workload would require 32 cores 
    • If your existing processor(E5 2690v4) is stronger than the above baseline (specInt wise), you would need more cores

 

Where do we select the processor input for the workload? 

In the page where we give the workload name and select the type of workload, there is a dropdown to select the processor the workload is running on.

Currently, we support only one processor type per workload , however, there are chances that sometimes a workload can be running on mixed CPUs. In that case, it is advisable to go with the processor with better performance among the two.

Please note: This feature only deals with sizing based on the selected processor. It does not reflect or has any influence on the type of processor chosen for the recommended hardware. The HW recommendation continues to be driven based on the optimal HW solution based on the resources required (cores/flash/capacity)

Posted on

June 2019 Sprints

The second sprint in June has  following key items

  • HPE DX . We went live with this last week and so a reminder that Sizer has the DX models.
  • D N+0 threshold changed to 95%. In automatic or in manual we need to know what is the acceptable N+0 level for a cluster in regards to CPU, RAM, HDD, and SSD utilization.  Thus we have thresholds to define what is still acceptable for N+0 . Here we simply tightened the SSD threshold to from 98% to 95% at N+0.  CPU, RAM, SSD are now all 95% and HDD is 90%

 

  • Warning/Suggestion to enable Erasure Coding for Files workload. There is concern in the field on safety of using ECX in their workloads.  However, in case of Files Storage it often is quite large (200TiB+) and very few writes (which is where the concern for ECX is at).  In this case the savings with ECX can be very significant yet low risk.  Thus we give you a warning that you are opting out of a tremendous cost savings.  You can keep ECX ON or OFF

 

  • VDI Profile type enhancement for Collector imported workloads. In VDI we have always had the notion of user profiles like task workers or power users.  However, when pulling in actual customer workload data from Collector, we do not need profile type to come up with workload requirements. We know that through actual data. Hence, while sizing a VDI through Collector, we should skip the profile type attribute.

 

  • Complete Sizer Proposal (one presentation file). Now one slideset to use with your customer

 

  • Detailed error for manual sizing validations (invalid node) We enhanced our error messages while in Manual

 

In the first sprint in June we had following key enhancements

 

File Services- Major update to File Services.

 

First, Home directory and Department Shares have been combined to File Storage.  They are often large workloads but with few writes.  Most were home directory and so made sense to combine given the similarities.  The one big change is we derive the working set

 

Application storage went through major update.  We now have random I/O as well as the sequential I/O we had previously.  We ask for  throughput and time window for keeping data in hot storage and then derive the working set.  This update reflects all the latest lab testing.

Here is info

https://sizer.nutanix.com/#/help/topics/17

Oracle Sizing Improvements – We now go with the fatest cpu in a node.  They have to be >= 60 specint anyhow but now we go with the fastest

Posted on

Cold tier data adjusted in Hot tier

Sizer always finds ways to propose the most optimal solution in terms of resources and cost.

As part of this effort, in certain cases , Sizer adjusts the workload data suposed to be sitting on the cold tier storage(HDDs) onto the hot tier storage(SSDs).

This happens in circumstances where there is surplus of SSDs in the BOM which is unutilized. The unutilised flash capacity is used for cold tier data if it helps reduce the overall number of nodes or if it helps avoid adding additional disks to met large HDD requirement if the extra SSD capacity can meet the same. The defined threshold levels are maintained and does not change for this adjustment in particular.

The same can be seen in a separate row in the calculation table and the Sizer BOM . Sample below:

 

Posted on

May 2019 Sprints

We launched our second sprint for May and it is a BIG one

Key Enhancements

Super Auto  Automatic goes through all the options and finds the optimal sizing.  Often SEs will say Auto is a good start but I want play with it.  Increase or decrease nodes and see impact of dials.  Increase/decrease Cores, RAM, etc and again see that impact.

Well now we have Super Auto where right in where you see the recommendation and the dials you can make those changes and get the update for the dials.  Better yet you see % change in cost vs optimal.  Manual is still there but now you can do a lot more in Automatic sizing.

Here is info and snapshots

https://sizer.nutanix.com/#/help/articles/592

 

Proposals  We had the sizer screen shots for a few months now, but we worked with the Field Enablement team and Product Marketing to deliver the latest in corporate overview and product/ solution benefits.  Don’t have to hunt around for the latest.  Do your work in Sizer and the latest PowerPoint is available under Download Proposals.  We see this evolving but you can be assured you got the latest.

Oracle updates  Oracle often is used in larger Enterprise applications and they charge for all cores in a node running Oracle.  Given that we now require high speed processors (greater than or equal to 60 spec ints which is about 3Ghz) but do allow a VM to cross sockets in a node.  This way you can have a large Oracle VM and know it will be fulfilled with a high speed cpu with fewer cores to give you a higher end system and lower Oracle license costs.

Miscellaneous

  • Heterogeneous cluster support for N+1 in Storage Calculator.  We had been taking one node off the first model defined and now we take it off the largest node in the cluster.
  • Appliances can have addons like Prism Pro, Flow, Calm.   This was for decoupled nodes in the past

First sprint for May

Key Enhancements

Backup Sizing.  Now all workloads for Nutanix sizings can have backups in a separate backup cluster.  You can define the backup policy and target either Files Pro or Buckets Pro. The intent is that  the backups are in the backup cluster managed by 3rd party backup software.  Sizer sized for the backups, included either Files PRO or Buckets Pro, and allocated space for the backup software.  In near future, there will be dedicated Backup hardware that can be used in the backup cluster instead of Files PRO or Buckets Pro.  Here is the details

https://sizer.nutanix.com/#/help/articles/585

Miscellaneous

  • Compression is now allowed for Starter license
  • Buckets can have RF3.
  • Robo VM can now have more than 2 TiB of storage

Collector and Tools

  • VDI workloads created by Collector are now better fine-tuned to meet different usage levels (edited)
Posted on

Backup Sizing

All  Nutanix workloads now support backups.    This does the following

  • For any workload you can define backup policy in terms of number of full and incremental backups.
  • When invoked Sizer computes the backup storage that is needed and puts that in a standalone cluster.  Only backup workloads can be included in the backup standalone cluster(s)
  • Sizer also allocates cores, ram and storage for 3rd party backup software in the backup cluster
  • In future,  you can specify the backup hardware that is to be used in the backup cluster(s).
  • Alternatively we do offer Files Pro and Buckets Pro standalone clusters as targets

The inputs are as follows

  • Recovery Point Objective – the time between last backup (be it incremental or full backup).  This represents what point in time you can recover data.
    • For example, you want to recover some information.  The last backup will have occurred less than or at most 24 hours ago
  • Backup cycles.  This would be the number of cycles you want retained
  • Full backups in a cycle.  Typically 1 but can be more.  Here all the data in the workload is backed up
  • Incremental backups in a cycle.  Typically several and amount of data is the % percent change * workload data
  • Retention in Days – Backup cycles * (Full Backups per cycle + Incremental backups per cycle)
  • Rate change – Percent change expected between incremental backups
  • Backup Target –  options for holding the data such as Files Pro
  • Standalone Cluster – Name of cluster that will hold the backups
Posted on

April 2019 sprints

We now have two sprints a month

Second sprint released April 29

Key enhancements

  • Allow Disabling workloads in scenario.

Bet you like to see the effect an extra workload has on your sizing.?  Betting you do that multiple times when you work with Sizer?  Well now you can disable a  workload and it is like it has been deleted.  Flip the switch and voila it is back.

The use for this feature is tremendous.  Certainly to add a workload and see impact.  Coupled with ability to clone and edit workload and then could have a couple levels (say small and large).  Then toggle each one to be disabled and see the impact the difference in workloads make.

We took care in how we handle disable workloads as follows

o    You get a warning on top that one or more workloads are disabled so you don’t forget.

o    Since the sizing is based on just enabled workloads the BOM, budgetary quotes and quotes are based on what is enabled

o    You can clone the scenario and the current state of enabled/disabled workloads are preserved in the new scenario.  So can have multiple scenarios from there with some enabled and other disabled

  • Capacity growth for Files – this is important as File capacity is always growing and now can size for up to next 5 years

Collector and Tools

  • Warn you if too few of VMs can’t be sized (eg. Many are powered OFF). This is to inform you that the sizing could be undersized given the data
  • SpecInt core adjustment for Collector import
  • Default selections for VDI workloads by Collector Import (Also enable Files by default)
  • RVTools 3.11 Import support

Miscellaneous

  • Updated Calm as no longer offers a free 25VM pack
  • Product updates for NX, SW only vendors, and Dell XC
  • Validator Product Updates
  • Failover Capacity Indicator improvements for ECX and Block Awareness enabled scenarios
  • Oracle: Node allocation to DB VMs
  • Automatic Sizing with CBL improvements for Standalone cluster sizing

First Sprint released April 16

Key Enhancements

  • Auto Sizing with CBL – We take into account the CBL license cost in our Auto Sizing which is key as most value is now in the licenses.  We also moved to List Price Sizing for NX hardware  instead of COGS
  • Manual Sizing Warnings based on Failover indicators. We leverage the new N+0 warnings in our UI but also BOM, Budgetary quote, Quote
  • 120TB Cold Storage support for 5.11. Models will be coming that support this but we are ready
  • Two node ROBO sizing for Files for N+1 failover. This is great for lower end file server market
  • Add Files/Buckets SKUs for quotes for non-decoupled accounts – So now can have a Files or Buckets license with an appliance sale.
  • ROBO VM Limit changes – PM did update the limits and so now:  no limits on cores, 32GB RAM per VM, 2 TiB of combined HDD/SSD storage per VM, and 50 TiB total HDD/SSD storage per cluster

Miscellaneous

  • Default NIC Selection for ALB/Non-ALB Countries (Auto Sizing). We take care of this nuisance where have to have the right NIC SKU for Arab League and non Arab League countries.  We look at the country for the Account you are sizing for.
  • Oracle Workload only in dedicated clusters. This is best practice given Oracle charges for all cores on nodes with Oracle.
  • Require an external NIC card for Bucket workloads
  • New UX Implementation for allowing decoupled quote for non-decoupled accounts – We want to make easier to sell a CBL deal to non-decoupled accounts
Posted on

March 2019 sprints

Second Sprint

  • Optimal VDI Sizing with Collector-  This is huge innovation.  We started Collector to get the best customer requirements and now that is reality for our top workload – VDI.

Here you run Collector at the customer’s site and it will collect 7 days of performance data from VCenter.  The information is already in VCenter and so it does not take long to grab that information (about 5 min).  In Collector you can specify if want to find the median value, average, peak or some percentile like 80% for each VM.  For example, 80th percentile means you are getting the cores and RAM utilization level that covers 80% of all the data points from last 7 days.  There you can be assured it is well sized as not all VMs will run that hot all the time.  That is what I would advise.

With that data going to Sizer we can then “right size” the VM so you don’t undersize or oversize it.  All the details are here

https://services.nutanix.com/#/help/articles/532

This is our first workload.  I don’t mean this as hype  but Collector will radically change sizing and in the process allow Nutanix to be more competitive  Why?  Because we will have precise customer data to size with.

In compute oriented workloads we will be doing similar processing as we did here for VDI.  For capacity workloads, like Buckets or Files we want to analyze data to get us the best compression values.  So this is just the sta

  • Hot storage allocation with FATVM –  Here if you have a large working set for Files or buckets we allow the SSD (hot storage) to be dispersed over the cluster.  Usually we want it on the local node for best performance (e.g. a heavy compute intensive VM) but here it is not a concern.  So net result is you can have a lot of large hybrid models
  • Allow decoupled quotes on non-decoupled accounts for the partners* – This is allowed now and we got this functionality to partners
  • Various product updates* across HP, Lenovo, and Nutanix (edited)

First Sprint

Add N+0, N+1, N+2 indicator

o    This is a BIG sizing improvement in Sizer where Sizer will always tell you if you are at N+0, N+1 or N+2 for all resources (CPU, RAM, HDD, SSD) for each cluster

o    Now as you make changes in manual you always know if you have adequate failover.  Best practice is N+1 so you can take down any one node and customer workloads can still run.

o    This can be very hard to figure out on your own.  ECX savings for example varies by node count.  Heterogenous clusters mean you have to find the largest node for each resource.  Multiple clusters mean you have to look at each separately.  Sizer does this for you !!

o    Here is all the info on how this works.  https://services.nutanix.com/#/help/articles/512

  • Allow decoupled quotes on non-decoupled accounts (SFDC Users) – At first the rule was an account had to be decoupled to get decoupled quotes or quotes with Files Pro or Buckets Pro.  Now that rule has been lifted and we support that in Sizer quoting.  We just ask you if you want de-coupled quotes or not.
  • ROBO VMs Sizing (Quoting, BOM with ROBO SKUs) – Here can have the new ROBO VMs where you sell VMs as a license and separately have hardware
  • 3 Node sizing for N+1 for Files – This allows a 3 node cluster to be used for Files.  Was 4 nodes was the minimum to be N+1
  • Add missing terms for Appliance Only License and Support
  • Multiple Clusters Support for Collector Import – Now can put different VMs in different clusters in Sizer
  • Default NIC Selection for ALB/Non-ALB Countries (Manual Sizing)
  • High/Critical Security fixes
  • Various product updates for Sizer and Validator

 

 

Posted on

Data Center Addons (Prism Pro, Flow, Calm, Files)

Want to add on some cool Essentials  products to the HCI offering.  It is easy with Sizer

  • Prism Pro –  1 per node
  • Flow – 1 per node
  • Calm – ½ VM pack per node (rounded up)
  • Files – Capacity is 5TiB per node

It should be a decoupled quote (separate license and hardware).  We use the terms and support level for the software license.   However, Calm is ONLY Mission Critical level of support

 

 

Here they are in the budgetary quote

 

Posted on

Sizer for Customers

Customer Access to Sizer

In the right situations, Sizer can be very beneficial for technical customers planning deployments for the following reasons:

Collaborative sale

  • Customers can scope out new emerging projects and then later pull in SE
  • Customer confidence and ownership in a proposed solution increases when they are involved in sizing
  • Build a better bond with SE

Customers can do what-ifs

  • if add 100 more users how many more nodes needed
  • If certain application core usage spiked 2x what is the impact on a cluster

Requirements for Success

  • Customers have to understand Acropolis and the workloads they are sizing. Sizer does have profiles and offers guidance in the wiki, but we assume a knowledgeable user.
  • SE would need to provide training though there are videos on the wiki
  • SE would need to be front line support to explain nuances in AOS, workloads, sizing, and Sizer

By default,  when customers sign up on MyNutanix, they have access to the “Basic” version of Sizer. The basic access limits the hardware sizing to Nutanix NX hardware. 

Process to request access to the Advanced version of Sizer

1.   SE requests Sizer PM (sizerhelp@nutanix.com) to bump up the customer level to Sizer advanced

2.  SE agrees to be front-end and provide training (to complement videos)

Key things to note

  • SE has to provide support
  • We will need to know what vendors the customer can have access to like Nutanix, HPE, Cisco, etc.  We can offer almost any combination
  • Customers will see budgetary list pricing with the Budgetary quote option
    • Nutanix software pricing is available irrespective of the vendors
    • Hardware prices are available for Nutanix NX, HPE-DX and AWS Bare Metals
      • Nutanix and HPE-DX hardware prices are updated monthly and quarterly, respectively.
      • AWS Bare Metal and EBS Volume prices are fetched on the fly