Feb 2023 (HW Template)

What is a HW Template in Sizer ? 

HW (Hardware) templates are pre-defined node configurations that can be created and saved by user. These will appear in their list of saved HW templates and can be used/applied while current or future sizings.

Similar to Cluster templates, HW template is a user-defined settings, only difference being HW templates allows to create exact specific HW config whereas Cluster templates provides attributes or settings guiding the sizer to pick up best configuration.

How can one create a HW Template?

There are two ways to define your fixed configuration of node via HW templates:

One – Upon landing to sizer (my scenario) dashboard, users can click on “Templates” and select HW Templates which opens up the HW configuration page ( similar to Manual mode page) where they can choose the vendor / platform and everything else (CPU/MeM/SSD/HDD/NICs/GPU)

Second – In order to save the effort, users can also create the HW templates while in the midst of a current sizing. While in a sizing exercise, in manual mode, when users would be defining a configuration , they can also quickly save it as a HW template in one additional step by giving it a name (either for a workload or by customer for example: HW Template-Databases, or HW Template-BestBuy)

How to use the HW templates ?

The objective for HW template is that you create once and use every time for that particular situation ( by workload or for a particular customer or any other scenario).

After creating the workload, when users are presented the Cluster settings/Sizing options screen, it shows them the option of HW Templates which can be applied for that sizing. This is in along with the other Cluster / SW settings they would like to use for that scenario. Sizer , then, iterates through the different solutions meeting the workload criteria and the cluster settings but restricting itself to only the HW Template(s) that the user selected for that sizing. Sizer would then recommend the right number of nodes (of the selected HW template(s)) meeting all the workload and cluster settings criteria.

How is HW Templates useful ? 

The biggest advantage for HW Templates is that it optimizes the sizing activity for situations where their is a fixed BOM involved. That could be whether based on a customers existing server farm or a Service Provider or a reseller/distributor with a fixed BOM(like Arrow with custom built HPE configs) or simply SE preferred config for a given workload.

Another use case can be for upgrades. SEs can define the NG8 equivalent of their older HW upgrades(like NX G5) and always map the existing cluster on older models to a mapped one via Templates.

Once the config is fixed, Sizer then comes up with number of nodes avoiding any back and forth for number of nodes of that BOM to meet the criteria.

Also, for future sizings for the similar criteria, users need not do all the manual exercise all over again (and even run the risk of manual errors) but simply import the HW Template for that criteria and get uniform/consistent sizing in one single click.

While creating the fixed BOM configuration, HW Templates also ensures all the platform rules are adhered to.   Additionally, after importing the templates, users can edit/modify configs and tweak it from the original template and before going ahead with the sizing, can save the edited template with a different name.

 

Here is a short demo on HW Templates, how to create and use : 

January 2023

Major highlights for January : 
Upgrade sales flow :
  • Now upgrade flow also supports HPE DX
  • You can recreate existing cluster with older DX configs (just as NX)
  • This will be a manual exercise though (like NX) but auto recreate will be coming soon
Imported workload enhancements:
Storage for powered Off VMs
  • Option to consider the storage for powered Off VMs (even if sized for only powered ON VMs)
  • This is applicable across Collector/RVTool/Insights imports
  • Checked by default but can opt-out
Retain cluster mapping
  • This will retain the source cluster and the VMs mapped to accordingly to the sizing
  • Instead of consolidating all VMs to default Cluster-1
  • Not checked by default so need to opt-in

November 2022

Here are the latest release with the following updates on SW/Platform:
  • Snapshots: RPO frequency updates for AOS 6.5.1
  • One-hour supported for up to 136TB for hybrid nodes  plus other rule changes
  • Adding 2% buffer for max capacity restrictions
  • 15.36TB NVMe SSDs support / Storage Capacity calculator
  • Lenovo Rule: Limit CPUs with wattage <=205W
Licensing update:
  • NCI : Handling the free TiBs of Files / Objects with the NCI license (also for Legacy)
  • EUC : Handling free GBs per user for Files with per user VDI license
Usability :
  • My scenarios dashboard:  Dynamically adjustable columns
  • Makes search by name easier
  • Including shared scenario dashboard
  • Partner login:
  • Updating deal registration-based validation for partner flow
  • Allow sizing for all approved deal registration ids
  • NCP bundle:
  • Highlighting individual licenses across tiers

October 2022

Here are the updated on two new features:
TCO in Proposals:
  • A new section on TCO in the Proposal deck
  • It has charts comparing the total cost of the solution on NX vs AWS
  • It is based on pre-build scenarios of standard sizes that is closest to the one being sized
  • For example: for a sizing of 450 VDI users, it will pick a pre-build scenario of 500 VDI users
  • It’s an optional and editable section in the proposal ,and hope it serves as a good conversation starter
  • The section also has guide on where and how to reach out to TCO team for a more detailed analysis/questions
CVM modes :
  • To address wide range of requests and different use cases, introduced two modes for allocating CVM cores
  • Regular mode: It is the current behaviour (and default option) so no changes
  • Performance mode: If selected, it doubles up the cvm cores
  • For example: for a regular VDI sizing, sizer allocates 4 cores , but if performance mode, will allocate 8 cores
  • Particularly helpful in addressing the resources required for certain configs, for example: NVMe nodes
  • NVMe nodes are used even for non-performance critical use case due to price parity with SSDs so regular allocation should be fine
  • In cases where it is used for performance , selecting the mode will ensure higher cores are provisioned
Other updates:
  • Updated HPE DX HW pricing for budgetary quotes (for DX BOM)
  • Lenovo product updates

August 2022

Here are the major highlights listed below :
Products:
  • Proposals – includes NG8 and HPE DXG10Plus models
  • HPE DX HW BOM – pricing update for budgetary quote
  • NCM Cloud add-on in Solutions
  • NUS add-on to NCI update (can add to all tiers)
  • NC2(AWS) – heterogeneous cluster support (mixing of different server types)
  •  NVME nodes CVM update (parity with SSD node type) – regular use case
Platform:
  • NX NG8 NIC changes : support for configurable LOM(AIOM)
  • Fujitsu – additional memory configs support

February 2022 release

 

Sizer went live with current sprint with below major updates :

 

  • Proposals for Portfolio 2.0:

    • Updated SW license section with Portfolio 2.0 structure
    • A slide on HW support and Cloud services

 

  • Cluster rules update

    • Restrictions around mixing different node types
    • For ex: Hybrid + NVMe nodes not supported
    • Handling unbalanced memory qty for IceLake
    • Allowing single socket for storage heavy nodes

 

  • Reference scenarios : Reworked on NX-G8 (was on G7 earlier)

  • Support for Frame licenses with Portfolio 2.0 flow

  • Platforms

    • GPU related rules for Fujitsu
    • New vendor- OVH Cloud

 

 

December 2021 sprints

Sizer went live with the sprint and some important features to start the year :

Upgrades quoting:

  • Now quoting for upgrades scenarios is possible and the quote button for upgrade flow is enabled.
  • The nodes are marked as existing or new by sizer (or can also be done manually) and can generate FL quotes for the newly added nodes
  • More on Upgrades is coming with Insights integration soon !!

Performance :

  • This is a big one and we all should see a significant performance improvement and sizing speed while coming up with the node recommendation.
  • Depending on the complexity and size of the workload, over 70% improvement in performance has been observed on an average compared to earlier.
  • A change in the technical implementation of sizing mechanism is driving bulk of the improvements.

Reference scenarios:

  • Sizer has come up with a concept of Reference scenarios (a tab called ‘reference scenario’ on the dashboard screen).
  • These are pre-sized scenarios by experts across workloads (For ex: Files 50TB,250 users, 250TB, 750 users , VDI 300/500 mixed user types etc)
  • These reference scenarios serve as a guide/reference purpose only for a similar workload requirement (and not encouraged to clone as is)
  • The feature has been widely successful with one of the partners (cdw) and now opening up for everyone

Others:

  • Proposals has been updated with the latest Q1 financials/Gartner’s slides and newly added G8 models
  • Default input processor set to Gold 5220 for VDI/VDA workloads for matching the real time(lab) performance numbers
  • Platforms that went live:
  •  NX-1175S-G8
  • Dell XC ICX or 15G Phase 2 Platforms
  • A30/A100/A16 GPU cards and related vGPU profiles for VDI/VDA

November 2021 sprints

In November, we went live with current sprint .. below are the major highlights..
Cluster settings:
  • Storage filter: Added separate filters for All NVMe and NVMe+SSD storage options
  • Sizer to consider onboard(LOM) NICs along with external ones
Workloads:
SQL:
  • Profile info: Mx RAM up from 1024 GiB to 2048 GiB
       Files:
  • Optimizing the FSVM resource requirements
RVTool:
  • Support for latest version 4.1.4
Proposals:
  • Updated with latest HW specs and images for G8 models
Usability:
  • Changes to the dials and the legends(Red, Green dots at the bottom)
Platforms:
  • AMD Milan : HPE DX Gen10 Plus v2 models [DX325 & DX385] – manual mode
  • Lenovo: IceLake models- HXxx31 , AMD Milan model- HX3376 10SFF
  • HPE DX- New GPU rules
  • NX: New platforms: NX-8035-G8

October 2021 sprints

October 1st sprint: 

We went live with the current sprint with some major enhancements around XenApp and Bulk Edit for Data Protection which were eagerly awaited.. : )Virtual Apps and Desktops (earlier called XenApp in sizer)
  • Added VMWare Horizon Apps support
  • Updated numbers with latest OS support (Windows 2019)
  • Updated profile info (based on User Type by VDI broker)
Bulk Edit : Data Protection
  • Now Bulk edit also supported for Data Protection
  • Both Local and Remote snapshots/DR allowed for bulk edit
  • All VMs being edited for DP need to be part of the same cluster
Other changes:
  • Rack Awareness – user specified rack count
  • Helps to spread the nodes across multiple racks if power limitation/rack at site
  • Lenovo HW(HX) quoting from Sizer/FrontLine now available for all regions(worldwide)
  • HPE DX Ice Lake platforms: DX380 Gen10 Plus 8SFF & DX380 Gen10 Plus 24SFF (in manual mode for now )

October 2nd sprint:

We did go live with new sprint for Sizer today. Big thing is Sizer now supports RF1 since AOS 6.0 supports RF1. RF1 fits best in certain situations where the data resiliency of RF2 is not critical.  We allow it for certain workloads as an option
  • Server Virtualization
  • Cluster(Raw) sizing
  • SQL DB (non business critical)
The following tooltip is worth noting as RF1 should be used with cautionSelect RF1 only if the application is SAAS Analytics or Hadoop, RF1 is used when workload does not require data resiliency or the data resiliency is handled at application level and currently supported for SAS Analytics or Hadoop.
Other enhancements:
File Services : There is an optimisation to the Files sizing which leads to fewer cores required. The FSVM is optimized to account for the the resources across all the FSVM(minimum 3) to meet the cores requirement and choose the FSVM profile accordingly. For smaller deployments, this becomes efficient as the FSVM size would not only depend based on 1 but a minimum 3 VMs to meet the resource consumption.
Platform Alignment
DX new GPU rules
Remove rule around 128GB DIMM & L CPU
HPE-DX IceLake platform DX360-Gen10Plus-10NVMe – Phase 2a
New platforms – NX-1175S-G8 & NX-8035-G8