Scalability-wise, I rate this solution a nine out of ten. We have a team of nine engineers who are working on CloudStack infrastructure.

I rate the tool’s scalability an eight out of ten. It’s quite scalable. I used the solution on an hourly basis.

The scalability is good. We don't have any problems with CloudStack. The main limitation we face is our own infrastructure. We have a limited number of bare metal servers.

The solution is scalable.

My team is using the solution in my company and our clients.

Scaling CloudStack is really easy. You just need to add more servers to your CloudStack deployment and it will be available to the customer. There are also mechanisms for using Kubernetes with CloudStack, and other features to help the customer scale easier.

On the whole, you can see everything from small, medium, to large business using CloudStack, sometimes globally but also with local cloud providers. 

I rate it a seven out of ten. The globalization part makes it difficult for us to scale.

The solution is scalable. It's also easy to manage. However, if a company is not familiar with cloud technology, it would have trouble.

CS itself provides quite powerful options to scale: availability zones, clusters, etc. One main issue encountered: It's really hard to delete zones, clusters, datacenters. You need to follow strict rules, which were not properly documented, a couple of years ago.

I would say that the product scalability is good. It is very scalable, but it requires some additional effort from the user's side, or the administrator's side, to understand the product well before making changes to the environment. Research has to be done, and a POC may be required.

For example, it is possible to integrate this solution with Ceph Storage or load balancers, and it will handle it, but you have to do some research first. Similarly, if you want to integrate it with a public DNS or an internal DNS, you will have to test it well before integrating it.

We currently have fifteen users, but it is a system administration tool so there is not much customer-centric traffic. This is actually one of the major benefits that you have. Even with fifteen people, doing the same thing or otherwise, it allows you to have your own space without overriding the other person. It allows you to be multi-tenant.

They have zone features that allow you to keep your local environment, so if you want to deploy multiple cloud stacks, you do not need to. You can keep just one cloud stack and integrate with all of the servers at once. This is in contrast to OpenStack, where you have to deploy one OpenStack per region or per area so that all of your computers can be centrally managed.

Our usage will increase as we add more servers, or expand our services.

No, I did not face any issues scalability issues.

The platform has some problems, but this is due to restrictions of the hypervisor. For example, it's not possible to augment the disk core in VMware or reduce vCPU with the VM running.

No issues with scalability.

No issue with scalability.

With the scale that we operate, I have not encountered issues with scalability. CloudStack manages infrastructure with 2-4 thousands of hosts easily.

There were no scalability issues.

No issues. The platform is very simple to scale-out.

It’s hard to say because I have quite a small environment. But adding nodes to the cluster/POD was done without any problems.

There were no scalability issues.

No scalability issues. CloudStack has actually scaled quite well for our needs.  Even though it’s more monolithic in design compared to OpenStack, we have had no issues scaling, and it actually scales with far less complexity as a result.

No.