What is our primary use case?
We use KVM virtualization on which Red Hat works very actively. We run Windows servers from it and some of our other machines as well. We also use it as a container in the way others may use Docker.
How has it helped my organization?
We can use the solution the same way we use Red Hat, even though we don't use Red Hat itself.
What is most valuable?
It offers a high-availability environment. We like the way everything is distributed. If one node dies, another resource is automatically enabled.
It offers good virtualization.
The solution, generally, is very familiar to VMware. The difference it is free to use. It has all of the main features you would find on VMware.
It works 24/7 without fail.
The setup is very simple.
It is stable.
The solution can scale.
We have found the solution to have good forums for troubleshooting.
What needs improvement?
If it would work a little faster, that would be ideal. It's run on a 10GB network, so it is relatively slow.
Some things are pretty basic, and they could be more robust with more detail.
For how long have I used the solution?
I've been using the solution for ten years or more.
What do I think about the stability of the solution?
It is a completely stable solution. While there may be a few bugs, in general, we didn't face any special issues.
What do I think about the scalability of the solution?
The solution is scalable. You can have as many servers as you want to run as a deployment. I'd rate the scalability nine out of ten. We use CEPH storage that is extremely scalable and can go up to petabytes, although we don't have a use case for that sizing.
We likely do not have plans to increase usage. Our basic needs are covered.
How are customer service and support?
I've never used technical support. There are forums, however, that are available if people need assistance. Typically, if something comes up, you aren't the first person dealing with it.
Which solution did I use previously and why did I switch?
We have used VMware and Microsoft Hyper V, among others, and then changed to KVM. I was not happy with Hyper V at all as we didn't want to use any Microsoft domain, and Hyper V needed us to use it. KVM allows us to avoid Microsoft.
How was the initial setup?
The initial setup process is pretty simple and straightforward. Even in high availability mode, the setup is simple.
If you have, for example, three servers and all of them can run the restore machines, and one dies, and everything moves to the others, for that step, you do need some sort of storage.
The deployment takes two or three days, at least if you need to start from scratch.
If you are doing the implementation in combination with setting up separate networks and everything, you need to program the hardware and so on, and that takes a little bit.
I'd rate the ease of setup an eight out of ten. Sometimes it doesn't work as you expect at the outset. We just need one person to handle the setup as we are a small company.
What's my experience with pricing, setup cost, and licensing?
The solution is free to use and open-source. You may have to pay for support, however. There is an enterprise option that can be accessed as well.
What other advice do I have?
I am an end-user.
I'm not sure which version number of the solution we're using.
I'd warn users that if they do not have experience with systems, then it may not be suitable. You need a bit of knowledge. Most companies use system integrators, and it is hard to sell free software. You can sell your services, yet not the solution. It's easier to sell VMware. I wouldn't necessarily recommend it to customers who don't have technical skills.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
Private Cloud