In my earlier post describing NX-8170-G7 and NX-3170-G6 DPTPB Nutanix Dynamic Visio shapes, I was hoping more supported disk layouts for NX-8170-G7:
“I am happy to finally see option to have a all-NVMe setup for the most I/O hungry workloads. But it is my sincere hope that Nutanix will add more supported disk layouts for NX-8170-G7. Or at least give us option to partially populate the NX-8170-G7 with NVMe drives.”
It seems that my wish has been granted 🙂 As of AOS 5.18 partial population of NVMe disk bays is now supported. (Only with with AHV, not with ESXi or Hyper-V, not sure why)
Making this update was fairly straightforward. Only one line of code changed, a list containing supported disk configurations for NX-8170-G7. The dynamic nature of DPTPB shapes took care of the rest.
Continue reading “Unofficial DPTPB Nutanix Dynamic Visio Shapes: NX-8170-G7 with partially populated NVMe bays”
In my earlier post describing NX-8170-G7 and NX-3170-G6 DPTPB Nutanix Dynamic Visio shapes, I was surprised to see that NX-8170-G7 only supported NVMe drives and I was missing a direct G7 generation equivalent for NX-3170-G6. It seems that I wasn’t the only one missing NX-3170-G7 and after all Nutanix decided to introduce NX-3170 also with G7 generation.
So it is time for me to update my Unofficial DPTPB Nutanix Dynamic Visio shape collection. Additionally there has been some changes in supported disk / NIC combinations for existing G7 generation NX appliances and I’ve modified the shapes to reflect these changes.
Continue reading “Unofficial DPTPB Nutanix Dynamic Visio Shapes: NX-3170-G7 & Minor updates”
When I originally designed DPTPB Nutanix Dynamic shapes, I intentionally left out validity checks for disk sizes. This was done to save some time when making the shapes and reduce complexity in both using and making the shapes.
Supported disk sizes with NX appliances are changing over time, not just when a new hardware generation is released, but also with new AOS releases as more drives are qualified to be used with NX appliances. These changes in supported disk sizes should also be carried to the DPTPB Nutanix Dynamic shapes, by making updates to “disk size” lists and code associated with them.
This update requirement also meant that if I was lagging behind or skipping “disk size” updates, the shapes would slowly deteriorate and might be frustrating to use, especially if more stringent disk size usage rules or validity checks were in place. To give some freedom to end-users with the original dynamic shapes, there were no rules with mixing disk sizes, all supported disk sizes per platform were available to mix and match freely.
With disk size validity checks users might not be able to fully document environments if the Nutanix spec sheets were updated with new “disk usage rules” and the dynamic shapes lagged behind with updating this information.
But hold on.
Now that there is possibility to use custom disk sizes with the dynamic shapes, changes in supported disk sizes and updates to the dynamic shapes lagging behind would not be such a huge problem. Users could use custom “Generic” and “Manual Entry” disk sizes and get the drawing done with correct disk sizes while waiting for me to update the shapes. While not a perfect solution as you might end up with unsupported combination, but a feasible workaround.
Hmm, Maybe I should consider “disk size” validity checks again…
Continue reading “Unofficial DPTPB Nutanix Dynamic Visio Shapes: Disk Size Validity Checks”