Month: January 2019

Posted on

Introduction

Sizer Users can can size for different type of business requirements which may require sizing for:

  • NX Appliances
  • NX Core
  • Software Only Vendors

Sizer Users, both Nutanix Employees and Partners (resellers and distributors), can generate following documents with the help of Sizer for any of the above mentioned scenarios:

  • BOM
  • Budgetary Quote
  • Salesforce Quotes

Contents of these documents (BOM, Budgetary quote and Salesforce Quote) change significantly based on whether one is sizing for NX-Appliance, NX-Core or CBL (Software Only vendors, Dell XC, HX Certified). Most of these changes are related to license and support products. Sizer uses information present in Salesforce Account and Opportunity to determine the correct license and support options. Following flowchart diagram explains how we make such decisions:

 

Posted on

Partners: BOM and Salesforce Quotes

Requirements

  • In order to generate correct BOM, Budgetary quote and Salesforce Quote, user must enter the Opportunity ID or Deal Registration Approval ID.
  • In case of Nutanix models, Opportunity value helps Sizer determine if the sizing needs to be done for appliance or hardware disaggregated. Based on the opportunity value,  user will be presented with support and license selection page which is applicable to software choice or appliance sizing.
  • Opportunity value plays a significant role when sizing with Non Nutanix Software only Vendors. If Opportunity is marked for Software only, then then user will be presented with support and license selection page which is applicable to CBL, otherwise user won’t see any support and license selection page.
  • Opportunity is a required field when creating a Salesforce Quote. It also ensure that Sizer isn’t sending quotes creating for velocity program to non-velocity opportunities.
  • If user doesn’t have the opportunity information but would still like to size for CBL/Software choice, one can do so my selecting “Software Choice Only” option from the create scenario page.

Steps to push BOM & Quote to Salesforce

  • Linking scenario to an opportunity or deal reg. Two features are enabled for the distributors
    • Upload BoM to Salesforce from Sizer
    • Generate Salesforce Quote from Sizer
  • In Salesforce, BoM and Quote are dependent on an opportunity, so to upload a BoM or to generate a Salesforce Quote, Sizer needs to know which opportunity to use. A user can provide opportunity information on the scenario creation page. Any of the following IDs/numbers is acceptable:
    • 15- or 18-character Opportunity ID
    • Deal registration approval ID
  • Opportunity & Deal registration approval ID can be found from DQT opportunity

  • Once the sizing is completed by adding the workloads, selecting & modifying financial assumptions, proceed with the actions to generate BoM, Generate Budgetary Quote, Push BoM to Sales force, Generate Salesforce Quote
  • On the left panel/sidebar of Scenario detail page, there are actions (generate BoM, Generate Budgetary Quote, Push BoM to Sales force, Generate Salesforce Quote) can be found

  • Clicking on “Push BoM to Salesforce” will launch a modal/pop-up. User can confirm the opportunity and push the BoM to Salesforce. Successful upload will close the modal and display a message on the page

  • Clicking on the “Generate Salesforce Quote” will launch a modal/pop-up. User can confirm the opportunity a license/support options before generating the Salesforce Quote. Successful upload will close the modal and display a message on the page

  • The opportunity information can be modified (removed, updated) only by clicking on the “Edit Scenario” action
  • Email notifications, containing link to opportunity in case of BoM upload and link to quote in case of Quote, will be sent to Users (Distributor, Opportunity Owner, Primary SE)
Posted on

Advice for Large File workloads

Please contact  vikram.gupta@nutanix.com for assistance

Here is the Nutanix Files Sizing Guide

Nutanix Files Sizing Guide

 

Adjusting nodes manually

In case you are doing a manual sizing you want to make sure it meets N+1 resiliency.

This is easy to check and adjust if needed.

Go to manual sizing and decrement the node count.

 

Two things to keep in mind

  1.  The minimum number of nodes for Files is 4 as there is a FSVM on three nodes and 4th node is needed for N+1  (one node can be taken offline and still 3 nodes to run the 3 FSVMs).  So 4 nodes are needed independent of capacity.
  2. Second, like any Nutanix cluster you want to make sure you still are at N+1.  Here is table that shows you max HDD utilization (Files is a HDD heavy workload) you want to assure N+1.   For example, if you have 6 nodes and the HDD utilization is UNDER 75% you can be assured that you are at N+1.  Here the N+0 target (utilization after lose a node) is 90%, meaning with a node offline the utilization is 90% or less.
Node N+0  Utilization Target Max Threshold  for N+1
4 90% 67.50%
5 90% 72.00%
6 90% 75.00%
7 90% 77.14%
8 90% 78.75%
9 90% 80.00%
10 90% 81.00%
11 90% 81.82%
12 90% 82.50%
13 90% 83.08%
14 90% 83.57%
15 90% 84.00%
16 90% 84.38%
17 90% 84.71%
18 90% 85.00%
19 0.9 85.26%
20 0.9 85.50%
21 0.9 85.71%
22 0.9 85.91%
23 0.9 86.09%
24 0.9 86.25%
25 0.9 86.40%
26 0.9 86.54%
27 0.9 86.67%
28 0.9 86.79%
29 0.9 86.90%
30 0.9 87.00%

 

 

Posted on

Adjusting Nutanix File node count in Manual

Right now Sizer’s automatic sizing does not take into account Erasure Coding savings when it figures out the recommendation.  Fortunately the savings is taken into account in terms of HDD utilization.

So the usable capacity and the utilization is accurate, but the recommended node count could be high depending on the settings for compression among other things

This is easy to check and adjust if needed.

Go to manual sizing and decrement the node count.

 

Two things to keep in mind

  1.  The minimum number of nodes for Files is 4 as there is a FSVM on three nodes and 4th node is needed for N+1  (one node can be taken offline and still 3 nodes to run the 3 FSVMs).  So 4 nodes are needed independent of capacity.
  2. Second, like any Nutanix cluster you want to make sure you still are at N+1.  Here is table that shows you max HDD utilization (Files is a HDD heavy workload) you want to assure N+1.   For example, if you have 6 nodes and the HDD utilization is UNDER 75% you can be assured that you are at N+1.  Here the N+0 target (utilization after lose a node) is 90%, meaning with a node offline the utilization is 90% or less.
Node N+0  Utilization Target Max Threshold  for N+1
4 90% 67.50%
5 90% 72.00%
6 90% 75.00%
7 90% 77.14%
8 90% 78.75%
9 90% 80.00%
10 90% 81.00%
11 90% 81.82%
12 90% 82.50%
13 90% 83.08%
14 90% 83.57%
15 90% 84.00%
16 90% 84.38%
17 90% 84.71%
18 90% 85.00%
19 0.9 85.26%
20 0.9 85.50%
21 0.9 85.71%
22 0.9 85.91%
23 0.9 86.09%
24 0.9 86.25%
25 0.9 86.40%
26 0.9 86.54%
27 0.9 86.67%
28 0.9 86.79%
29 0.9 86.90%
30 0.9 87.00%
Posted on

December 2018 Sprint

In month of December we made following enhancements

  • Partners can now generate Salesforce Quote for Nutanix Appliance. This is first time they can create the quote and then their distributor applies discounts and request approvals in the Distributor Quote Tool. We will enable quoting for Nutanix Disaggregated, XC Core, HX Core, CBL in January.
  • Sizer now integrate with Hardware Compatability List for all SW vendors including HP, Cisco and Dell PE. The benefit is we can keep Sizer in sync with the changes more consistently.
  • Nutanix Files enhancements

 Increased maximum capacity to 10 PB (Petabytes)

Support for Nutanix File licenses. The budgetary quote, quote and BOM includes the new licenses

  • HX Core support
  • Intel server support (new vendor)
  • NX-5155-G6 in Sizer
  • ECX and Block Awareness together supported
  • Sizer Wiki Search – find information faster
  • Budgetary Quote changes for CBL
  • Oracle AWR tool support