I often get asked at events and in forums about sizing Azure Stack HCI, and if there is a standard tool for sizing. Often what is being asked is either: “How do I go about sizing the fabric” and/or “How do I size for a given set of virtual machines?” It is also important to include within your sizing calculations enough capacity in the cluster to handle failures and accommodate any maintenance operations.
Sizing for volume capacity is made easy when you leverage the Storage Spaces Direct Calculator developed by Microsoft. You can find the Calculator here https://s2dcalc.blob.core.windows.net/www/index.html
The Storage Spaces Direct Calculator has been in preview since its initial release, which was quite some time ago. The first step when using this tool is to specify the count, capacity and type of each storage devices that will exist in each node.
The second step is to then select the number of nodes that you initially plan to include in the Azure Stack HCI cluster. You can select between a minimum of two nodes and a maximum of sixteen nodes.
The third step is to specify the level of resiliency that you wish to have in place within the Azure Stack HCI cluster. This will have a direct impact on the amount of usable storage that will be available to you within the Azure Stack HCI cluster. The Storage Spaces Direct Calculator will guide you to which types of resiliency you can use based on the Azure Stack HCI cluster configuration.
The main benefit of the Storage Spaces Direct Calculator is that it allows you to experiment with your storage configuration and resiliency options before you move forward with your project.
The final step is to review the results. Here you can see how much usable space is available within the Azure Stack HCI cluster and how much space is being used for resiliency and reserve.
As you can see, the Storage Spaces Direct Calculator only really addresses your available storage needs. There is no single tool to help address your overall sizing requirements around compute and so I will give you some guard rails to help with this aspect of sizing.
However, you might strategically use Dynamic Memory. In that case, you will need to decide what metric you size against e.g. maximum memory.
HPE offers an extensive range of solutions to assist customers like you, from simply installing the Windows operating system in the factory too much more complex solutions around Azure Stack HCI with public Azure integration. Our worldwide team of Hybrid IT Specialists and Solution Architects can help customers scope and size the right solutions to meet your requirements, and then accelerate the implementation of that solution with our on-site and remote support services.
Follow us on the WOLFE SYSTEMS socials for up to date tech trends, information and cool facts