Not sure if this is in the correct thread, I can repost as needed. Wanted to open this up as a discussion on information needed for VxRail Sizing and where some of the out-of-box reports are a little lacking to me on this venture.
I'll start with how i generally go about sizing and then highlight the gaps. Generally, I start most of my sizing with an RvTools export (and dpack perf data, and some reports from dpack) and i slice the data as follows:
I pivot table all of the VMs by:
|#vCPUs||#Number of VMs||Total Disk by profile||Total memory By profile||Memory per VM||Storage per VM|
**Memory per VM and Storage per VM are those total values / number of VMS
I can then use these values for the VxRail Sizer:
Now IOPS is still an issue, no matter how i slice it. I'm generally unconcerned as most configuration are going to be for All Flash and i take the number of overall iops (or target IOPS) and divid by the number of VMs with the environment. I'd spend extra time on this for hybrid environments to ensure we had enough IO to satisfy the requirements.
The gap is this, there is not (currently) a report (that i've found) where i can slice the data in such a manner, only high level roll-ups. The ability to see the VM details -> host details > Datacenter -> cluster linking would be awesome. The ability to run /export a report that slices the data to align to the table above (or similar, not saying my way is perfect, just what i have found that works) would save allot of spreadsheet time.
Would this be possible?
Thoughts or comments greatly appreciated.
Please sign in to leave a comment.