Private cloud on OpenStackVMware to KVM migrationHybrid cloudPublic and multi-cloud landing zonesRunning the platform (Day 2)Private vs public cloud cost
Cloud guide
Running the platform after go-live
A cloud platform is only as good as the way it is run. Most private clouds that disappoint were built well and then left without monitoring, upgrades or capacity planning. We design the day-to-day operating model with you, hand it over to your team with runbooks, and can support it on agreed terms if you want.
CoversMonitoring, patching, upgrades, capacity, cost
Delivered asRunbooks your team owns
SupportOptional, on agreed terms
GoalNo upgrade you are afraid of
The Day-2 routine
| Activity | How often | What good looks like |
|---|---|---|
| Health and alert review | Daily | Alerts that matter reach a person. Noise is tuned out, not ignored. |
| Security patching | Monthly | Hosts patched in rolling order with no VM downtime, using live migration. |
| Capacity review | Monthly | A forecast of when compute, storage and IP ranges run out, with time to buy. |
| Backup restore test | Monthly | One real restore, timed and recorded. |
| Cost review (public cloud) | Monthly | Idle and oversized resources removed. Commitments matched to steady usage. |
| Platform upgrade | Once or twice a year | Tested in a staging environment first, then rolled out with a rollback plan. |
| DR test | Twice a year | See testing DR. |
What we hand over
- Monitoring and alerting already wired up, with dashboards for the platform and for each tenant.
- Runbooks for the common tasks: adding a compute node, replacing a failed disk, rotating certificates, patching, upgrading.
- An upgrade plan that keeps you within one or two releases of current.
- A capacity model your team can update with real numbers each month.
- Cost controls for public cloud: tags, budgets, alerts and a monthly report.
Tools we typically use
| Area | Common choices |
|---|---|
| Metrics and alerts | Prometheus, Alertmanager, Grafana |
| Logs | OpenSearch or Grafana Loki |
| Automation | Ansible, Terraform, GitLab CI or Jenkins |
| Public cloud cost | Native cost tools, tagging policies, budgets and commitment planning |
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.