VM fleet design
Map workload groups, isolation, sizing, storage and network before capacity commitment.
Private cloud and VM fleets
Predictable infrastructure for defined VM fleets.
Qualified dedicated capacity converted into operated virtual infrastructure for workloads that need control, isolation or a predictable monthly footprint.
- Since 2009
- 99.9% uptime SLA
- P1 under 15 min
Infrastructure
Private cloud is an operating model, not a label.
The design starts with VM density, storage, network, failure reserve, backup, licences, customer term and who owns the hypervisor and guest operating systems.
Platform operations
Operate the virtualisation layer, monitoring, maintenance and agreed recovery path.
Guest operations
Add managed guest operating systems and workload ownership only where scoped.
Operating boundary 01 02 03 04
Separate platform, guest and application ownership.
A private VM fleet has several operating layers.
Physical capacity
Server, storage, network, maintenance and upstream replacement boundary.
Virtualisation
Cluster or node configuration, resource allocation, updates and platform monitoring.
Guest systems
Operating-system access, patching, backups and incident response.
Applications
Application releases, product decisions and business ownership.
Commercial model
Monthly matched commitment.
Customer term and payment must cover the committed infrastructure and agreed operating scope.
- Qualified design before quote
- Monthly infrastructure plus operations
- No speculative capacity commitment
Start with the workload