Over the years, we have valued CloudStack for its stability. When we talk about stability, we're referring to technical stability and the fact that CloudStack is an Apache project with a clear and stable path that the project follows.

The tool has good stability.

CloudStack is highly stable.

While working with CloudStack, we have encountered several bugs, which we are addressing through collaboration and finding workarounds. However, we have observed that each new release is an improvement over the previous versions, even though it may not be considered entirely stable. Since new releases are made every six months, new bugs are likely to be discovered. While the platform is continuously improving, it may still be prone to instability due to ongoing development and changes.

I rate the stability of CloudStack a six out of ten.

CloudStack is a production-rated product and it is very stable. As for maintenance, the LTS version from the community requires periodic updates that sometimes require a company with expertise to help in order to reduce your risks. 

There is also support from the community, although you are not always guaranteed a timely response. That's mainly where my company steps in to help, as we are able to help customers update, improve, and expand their cloud infrastructure as necessary.

There were a couple of times when we had to restart the management servers as it was unable to bring up the virtual machines. There were challenges with the nested virtualization.

The solution is stable. We haven't faced any issues with the solution. The performance is very good. 

We did encounter issues with stability, and the main issue was secondary storage. When it is not available, XenServers and hypervisors are affected. And CS doesn’t do anything to reboot, or fix. Come to think of it, maybe it shouldn’t, considering their approach – CS just orchestrates everything else on the hypervisor and storage level. But considering so many points of failure and dependencies on infrastructure, they could figure out something. This was another reason why we planned migration to SOA.

The stability is problematic, in part, because there is no support. It is an open source product, so similar to OpenStack there is community involvement. One challenge, however, is that it is a small community of users compared to OpenStack. There are professional services available by multiple vendors, so you can leverage that if you wish to.

It becomes an issue when there are new problems and you do not have support for them to be fixed. Otherwise, the product is good. If it is working fine then it will continue to work until something changes.

If you are stuck with a problem then it may take between a couple of days and a couple of months to solve it. It may require research, but it is challenging because you do not have a major community of people.

I encountered some stability issues. When I tried to remove high-capacity virtual machines it took a long time to update, and sometimes the VM status failed to update properly in the cloud database. This occurred multiple times, even though I had sufficient resources. Other than that everything was fine.

No problem, the platform is very stable.

Only once, an instance with VM on Windows Server was rebooted without any action from my side.

Yes, we encountered stability issues. We were using an older version on which, when we restarted the CloudStack management service, the connection would break between CloudStack and KVM hosts. This resulted in VM deployment failure. The issue was resolved after updating to the new version.

The product is stable. There were times where longer running operation could run into issues. Some of these stability related problems have been fixed in newer releases.

There were no stability issues.

We had only one problem with the hypervisors, but not with the ACS.

The system is stable, I haven't faced any problems with it. The organization of management is simple and clear.

There were no stability issues.

We had some issues with XenServer an OVS, but that wasn’t really a CloudStack problem.

No.