My biased advice would be to use the technology only after creating a proper design. This means doing thorough research and speaking with professionals with experience in implementing similar designs. It's important to have the design peer-reviewed by someone else before ordering any necessary hardware and attempting to deploy it. Additionally, consider seeking consultancy from a company like a UK-based company named ShapeBlue. Also, it is important to note that I don't work for ShapeBlue. Spending some money on professional help can get you up and running more smoothly.

Owing to the fact that when I consider the competition and available alternatives, CloudStack has proven to be an extremely reliable and durable piece of software in our company environment for over twelve years, and since I have no plans to switch to any other platform at this time, I rate this solution a ten out of ten.

I have used the solution more than once in the past twelve months. People might want to use payment for cost control if it is a private cloud. Even enterprises would use it for cost control. It's difficult to measure a return on investment. Overall, I rate the tool an eight out of ten.

I rate CloudStack eight out of 10. Make sure you have your on-premises solution for provisioning virtual machines. If you are going to do that, you must be sure that you need it because it's quite complicated. Although it works quite well, it's something really complicated.

If you are considering implementing CloudStack, there are a few questions that you should ask yourself. What are your requirements? Is it for your internal use or are you planning to offer services to end customers? The answers to these questions will depend on the size of your implementation. If you are planning to use CloudStack for your own internal environment with a small number of users, but want to manage those users within the CloudStack environment, then it could be a good fit. However, if you are planning for a larger-scale implementation with the potential to scale to a significant number of users over time, then it would be wise to consider other options as well.

I rate CloudStack a seen out of ten.

The primary advantage of using CloudStack is its open-source nature. Once you have a solid understanding of the underlying technologies and how the platform operates, it is relatively straightforward to deploy and maintain your own infrastructure, whether it is for your internal team or company. In most cases, you can handle maintenance on your own, unless you require significant changes to the solutions' functionality, which may necessitate dependence on the community or the involvement of Java developers to maintain your infrastructure.

I can recommend CloudStack because there are a lot of large companies using it in production for critical mission systems, and everything else. It's a very stable product, and compared to similar solutions it is also easier to deploy.

Then there's the fact that you don't need a license, so it's obviously cheaper than most alternatives. If you seek out a company such as a consultant service to help you build the infrastructure, service cloud, orchestrator, etc., then you will find that CloudStack doesn't take much time to implement. The other solutions are a different story, and they may take up to three or four times longer to deploy. CloudStack is very intentional about keeping things simple.

One final point is that with CloudStack, you don't have the vendor lock-in that you might have with OpenStack. If you're using CloudStack and you obtain support from one company and then decide to go with another company for support, it's all the same base code. Contrast this with OpenStack, where if you have Canonical OpenStack running in your infrastructure, you will have vendor lock-in because it's not that easy to move over to Red Hat OpenStack.

I would rate Apache CloudStack a ten out of ten.

Tagging is key if you want to manage more than a couple of resources.

I would rate Cloudstack an eight out of ten.

I'm an end-user.

I'd recommend the solution; however, it depends on the needs of the company as there are some limitations. 

I would rate the solution seven out of ten.

We rate Apache CloudStack a pure 10 out of 10 for its extremely versatile environment, rich feature set that can cover even the most complex customer requirements, and the ease of management.

We have been using CS for three years. I started a small PoC with a few VMware hosts. At the end, I had three production instances with VMware and XenServers.

I would rate CloudStack as a six out of 10. Main pros: You can manage infrastructure with a few people, since product is monolithic. We had three engineers (storage, virtual, Linux admins) only. Also, CS supports different flavours of hypervisors. Main concern: Environment is sensitive, so, unlike VMware, you can not afford middle-skilled engineers, they will ruin everything. 

It's very important to understand CS rules and baseline for them.

Make proper estimations for everything: networking, storage, performance (primary and  secondary) and then add 20% to your estimates. CS is good for private clouds, but I would never use it for public clouds.

My advice for anybody interested in implementing this product is to do the POC, and don't just go blindly with it. You need to see what the pitfalls are and whether your team can handle it, or not. If they cannot handle it then you should look at other cloud products, such as those that have more support in the community. 

On the other hand, if you are looking for something small, scalable, and easy to deploy, then this is a good solution.

I would rate this product a seven and a half out of ten.

I rate it at five out of 10. For a private cloud, CloudStack is good and fine, but for public cloud, it will not be that a great experience, in my opinion. CloudStack is good for private cloud, simple to install and set up.

If you are planning for a public cloud with microservices architecture, go for OpenStack. CloudStack is a monolithic architecutred solution to manage cloud  infra and sometimes it will be difficult to pick and fix a single component from CloudStack.

I recommend that you initially consider what solution or cloud product you require. Then, if you are looking for a stable product that is easy to install with a lot of documentation, a portal that is very easy to understand and manage and that can be modified, you should use CloudStack.

In general I would to say CS is a stable solution and, in my opinion, it will solve problems with administration of VMs.

I rate it a seven out of 10 because it is has most features you would expect from an orchestration tool, but less complexity.

I’ve used, managed, and integrated it for about seven years in three different mid-sized companies. I started using CloudStack before Citrix acquired Cloud.com.

I would rate Apache CloudStack at seven out of 10, compared with six out of 10 for OpenStack. 

If you are looking for a private cloud, just go for CloudStack.

Reduction in the time for the presentation of new improvements.

I would rate this an eight out of 10. It is a great solution for virtual hypervisor orchestration. It is purpose-built for our environment and does very well if you have the time to manage your environment.

We’ve been using some form of CloudStack in our environment since 2012. It has become an integral part of how we provide critical services to our customers.

Though the framework is best in its own way, a technology upgrade is lagging.

Every infrastructure is different, and company policies are also different. I can’t advise in a general way here. I can only say that KVM and Citrix, as a hypervisors, are very stable with CLoudStack. The rest is up to the architecting fantasy of the administrator.

This solution really works. That’s it.

I have used KVM or XenServer as hypervisors with CloudStack. These virtualization technologies are most supported on CloudStack.

I have used it for close to eight years, since Cloud.com, prior to the Citrix acquisition.

Get commercial assistance from an experienced consultant who has deployed it before. Choices made early on in a cloud deployment can lock you into a design that may be undesirable in the future, but near impossible to change if implemented incorrectly early on.

Attention to network design and secondary storage.