Cloud questions, answered
Short answers to the questions IT heads ask us most often about private cloud, public cloud and leaving VMware.
Is OpenStack too complex for a mid-sized organisation?
It can be. OpenStack makes sense when you need multi-tenancy, self-service and an API that teams build on. If you mainly need to run VMs reliably, Proxmox VE or a smaller KVM platform is simpler to operate. We recommend the smallest platform that meets the need.
How long does a VMware to KVM migration take?
For a few hundred VMs, typically three to six months: a few weeks for inventory and design, a few weeks to build and test the target, then waves every week or two. The pace is usually set by application owners' testing time, not by conversion speed.
Can we keep some VMs on VMware?
Yes. Some appliances and vendor applications are only supported on VMware. A small remaining vSphere cluster, or moving those few systems to public cloud, is often cheaper than forcing them onto KVM.
Will moving to public cloud save us money?
Sometimes. It usually saves money for spiky, short-lived or fast-growing workloads, and costs more for large, steady ones running 24x7. Use the cost calculator with your own numbers.
Can our data stay in India?
Yes. Major public clouds have Indian regions, and a private cloud can sit in any data centre you choose. Check what your regulator or contracts require: some need data in India, some need it on infrastructure you control.
How do we avoid lock-in?
Build with open tools where you can (KVM, Ceph, Kubernetes, Terraform), keep infrastructure as code, and be deliberate about which managed services you depend on. Some lock-in is a fair price for a service you would not want to run yourself.
What skills does our team need to run a private cloud?
Linux, networking and automation (Ansible or similar) are the foundation. OpenStack and Ceph skills can be built over the first months with good runbooks and some support. We plan this handover as part of the project.
What do you need from us to start?
An export of your VM inventory (RVTools is ideal), a short list of your most important applications and their owners, and what is driving the change: cost, a renewal date, compliance or growth.
Planning a cloud move or a VMware exit?
Send us a VM inventory export (RVTools is fine) and a line on what is driving the change. We will come back with a plain first view: what could move where, in what order, and roughly what it would cost to run.