Advanced Nutanix: Series Introduction
This will be a running series of posts that outline the tips and tricks for administering and optimizing Nutanix I personally use in my environment as well as any findings that I think are useful for others!
One of the key items I’m responsible for is taking 3rd party products/tools and creating the ideal architecture and combination of the two which is published via a reference architecture (RA) or best practices (BP) document. Being in this position I have amazing the opportunity to be hands on with both products and see a great deal of workloads and IO footprints on the Nutanix platform.
Now, coming from a tech consulting background I’ve seen a great deal of consultants who talk a lot of “fluff” as I would call it. Let me tell you, I’m not that way, nor can I stand it!
To create a reference architecture or best practices document, it is absolutely critical you know the in and outs of the very products you’re dealing with (both Nutanix and the others). This not only ensures you can architect/optimize the solution correctly, but enables you to provide meaningful data and structure to the consumers of these documents (partners, administrators, engineers, architects, etc.). After all, they’re referring to these documents to help them with their sizing and deployments, they better be spot on!
I hope you all enjoy!