Azure Stack HCI, like many other HCI systems, needs multiple servers to create a cluster architecture. This new architecture presented to us with HCI OS, which is built on top of physical servers that we call nodes, is a very sufficient product for many workloads. Since each workload has different needs, you can set up the HCI cluster architecture by purchasing the infrastructure hardware suitable for these workloads.
So you’ve decided on the workloads, but where does that workload work best? It is a recommended method to work wherever the workload is most suitable (cost, latency, performance, regulation, etc.). So we love the cloud, our apps are on the cloud, edge is cheaper for us, let’s put our apps in edge locations. Or I always want to work in my own data center, everything is onprem, unfortunately it is far from meeting today’s business needs. For this reason, for many modern business needs, some systems may be on the cloud, some systems may be on-prem due to the topics I mentioned above, and some systems may be in edge locations. For example, in the scenario where edge is deployed for the workload, a single node compute will actually be sufficient. For such a scenario, single node Azure Stack HCI support has arrived and is integrated and managed in the central system. But of course it won’t offer fault tolerance in case there is a physical problem for the node. However, the lodge will continue to offer tolerance against disk failure. In summary, it is a really good solution that does not need very high compute power like these EDGE locations, but does not lose management, maintenance, workloads and other features offered by Azure Stack HCI.
When we look at the basics, Azure Stack HCI provides us with many advantages. When we consider the topics we shared in our previous articles, such as extending certain and most widely used services on Azure to onprem servers, running popular services such as VDI or AKS, and the ability to manage, backup and monitor through central management consoles, keep in mind that all of these will apply to single node Azure Stack HCI. Please.
An important issue here is that the operating system for single node Azure Stack HCI should be Azure Stack HCI.
As you will see here, you can install Azure Stack HCI infrastructures with either Windows Server 2022 or Azure Stack HCI OS. If a single node is to be installed, you need to install Azure Stack HCI OS as the OS.
I also share the following links that I think will be useful;
Azure Stack HCI server catalog:
S2D Storage scaling tool:
Workload based scaling tool: (“size” link)
AKS (Kubernetes) on Azure Stack HCI: