The ease or difficulty of setting up CloudStack depends on one's level of knowledge. I would say that the setup is easy. However, one should possess some knowledge of what they are doing. So, it's not as simple as picking someone off the street and asking them to install the software. However, if you are a bit into technology, it's not a particularly difficult task to install.

When rating the solution's setup process, on a scale from one to ten, where one is difficult, and ten is easy, I would rate it as a seven.

Regarding the initial deployment of CloudStack, approximately twelve years ago, it took us about one to two days to get it up and running for the first time. Right now, we can complete the setup process in a couple of hours because we have automated many things on our end. Additionally, we also have the experience of doing it so many times.

The solution is cloud-based. The solution can be deployed on public, private, and hybrid clouds. If we get the right documentation, the initial setup is quite quick. There's a lot on the internet, which sometimes would take people on the wrong route. The very first time I set it up, it took me about eight hours to find the right process. Once I found the right documentation, the deployment took 30 minutes.

Deploying CloudStack is quite complex. It took a few months for us to spread it throughout the company and put it into production. We first implemented it in a development environment. 

The setup of CloudStack is difficult. The time required for deploying CloudStack depends on the scale of the environment. For small-scale deployments, it may take a day at most to deploy the applications, assuming prior experience in deploying such applications. If you are an experienced person, you may be able to do it even faster. If the environment is well-prepared, with physical servers, networking setup, and other necessary equipment already in place, the deployment time for CloudStack services can be reduced to half a day. Mr. Arun suggests that the deployment time can vary depending on the level of expertise and the readiness of the environment.

The setup for CloudStack is a really easy process, compared with other solutions. For example, in only one day you can have an operational cloud running in your infrastructure. This is where you see a big difference when you compare CloudStack with OpenStack. With OpenStack, you have a lot of models to contend with, making it complex to deploy and configure, whereas with CloudStack it's easy because you only require one package that provides everything you need.

There were different ways to set up: scalable and non-scalable way.

We had the whole thing running on top of Amazon Web Services, which added another layer of complexity because it had nested virtualization at that point. You are running VMs on a VM. It did not seem trivial to set up; it was definitely a challenge for us.

The initial setup is difficult. You need to set up the cloud and the networking. We have to manage the VPC (the Virtual Private Cloud), meaning we have to manage the cloud directly. That's fine. However, the technology itself needs to be improved. We need to manage the policies and set everything up. There is a lot of time needed to deploy the product.

It was complex for three reasons:

1. I had to match business logic, so initial testing came in.
2. To make it work properly, I had to figure out how it exactly interacts with hypervisors, and rules for that. It was not clearly described at that time.
3. Sensitive environment, so if you make a mistake during the initial configuration, get ready to start from the beginning.

It is simple to perform the initial setup. Compared to OpenStack, it is really straightforward and simple. The deployment will take a couple of hours.

You will need at least two or three people to maintain the solution. It is a complex environment, even though it has a very simple GUI. The back-end system, such as the database or the application itself, definitely requires at least four to five good people who are able to handle issues in the CloudStack environment.

This is less maintenance than is required for other solutions, but expertise is still needed.

Straightforward, a very simple process.

The initial setup was easy with the support of a partner.

Regarding the first creation of an instance in CloudStack, I would say that it is rather straightforward. I was faced with a non-activated network within a VM and it took a little time to find and fix it.

The initial setup was simple compared to competitive products.

The initial setup is actually pretty easy because CloudStack has a monolithic, all-in-one architecture.

It is not complex, but has some little tricks.

It was easy and took no more than an hour (including HA configuration).

The setup was straightforward. The installation guide is easy to follow. The concepts are easy to understand and are based on the standard mechanisms.

Complex, but all clouds are complex so that is to be expected. I and one other community member actually write a bunch of documentation for first-timers to help them through the process, because the networking always threw everybody.

It was simple, taking into consideration that any private cloud deployment is intrinsically complex. We could manage to decrease the network complexity representing the physical network with VLANs mapping to guest, isolated and VPC networks.