There are a lot of areas for improvement. Since I've been working very closely with this product, there are many areas, especially in software-defined networking. We had to improve multiple areas because we depended on the service fabric cluster to manage the software-defined network. That means we're already running a hypervisor inside a VM, and we're managing the control plane of the software-defined network. That's another cluster. So, multiple layers make the complexity more complex. So, from an operational perspective, it's very difficult to manage. So whoever is actually managing it should find it easier. Therefore, I would like to improve the operational aspect by making it easier for users. The deployment process can also be improved. It's purely based on PowerShell settings. So, there's a bit of optimization and tuning that can be done in the process settings as well because the current deployment process takes approximately one hour. But again, it's a one-time process. We can always counter the challenge by saying that we don't want to improve it because it's a one-time process. But one hour is a bit long. So there's some tuning happening, especially a service fabric cluster thing, which has been taken care of now in the next version of HCI. The service fabric service is completely removed, and they are integrating the control plane process of software-defined networking into the HCI node itself, not running it inside a VM. So that's a good thing. Azure Stack HCI is already being used by many customers in the market. The only complexity and challenge is with Software Defined Networking (SDN) alerts. So, I haven't seen many customers using it yet because I'm the only person here who's good at Software Defined Networking and HCI right now. That's a challenge because a lot of people depend on me since I'm the only one working on this. So I want to improve that area as well. I need more people to be accustomed to this product so we can help our customers more efficiently in different time zones. At the same time, support is challenging for Azure Stack HCI with Software Defined Networking (SDN). We are trying to create a new team and train them to make sure we have more people available in this region to work on this product and help customers in a better way.
Hyper-Converged Infrastructure refers to a system where numerous integrated technologies can be managed within a single system, through one main channel. Typically software-centric, the architecture tightly integrates storage, networking, and virtual machines.
We faced multiple problems with the product’s stability. The product must provide more versions and bug fixes.
There are a lot of areas for improvement. Since I've been working very closely with this product, there are many areas, especially in software-defined networking. We had to improve multiple areas because we depended on the service fabric cluster to manage the software-defined network. That means we're already running a hypervisor inside a VM, and we're managing the control plane of the software-defined network. That's another cluster. So, multiple layers make the complexity more complex. So, from an operational perspective, it's very difficult to manage. So whoever is actually managing it should find it easier. Therefore, I would like to improve the operational aspect by making it easier for users. The deployment process can also be improved. It's purely based on PowerShell settings. So, there's a bit of optimization and tuning that can be done in the process settings as well because the current deployment process takes approximately one hour. But again, it's a one-time process. We can always counter the challenge by saying that we don't want to improve it because it's a one-time process. But one hour is a bit long. So there's some tuning happening, especially a service fabric cluster thing, which has been taken care of now in the next version of HCI. The service fabric service is completely removed, and they are integrating the control plane process of software-defined networking into the HCI node itself, not running it inside a VM. So that's a good thing. Azure Stack HCI is already being used by many customers in the market. The only complexity and challenge is with Software Defined Networking (SDN) alerts. So, I haven't seen many customers using it yet because I'm the only person here who's good at Software Defined Networking and HCI right now. That's a challenge because a lot of people depend on me since I'm the only one working on this. So I want to improve that area as well. I need more people to be accustomed to this product so we can help our customers more efficiently in different time zones. At the same time, support is challenging for Azure Stack HCI with Software Defined Networking (SDN). We are trying to create a new team and train them to make sure we have more people available in this region to work on this product and help customers in a better way.