Private Cloud · IaaS Service Level Agreement
Drafted with the Isvara SLA Builder, following the Isvara private-cloud guide: define good, measure per VM, differentiate the classes by price and nines, never by threshold.
01Service classes
| Class | Price | CPU | Availability | Performance |
|---|---|---|---|---|
| Gold | 1.00x | 1:1 | 99.975% | 99.9% |
| Silver | 0.50x | 1:2 | 99.95% | 99.8% |
| Bronze | 0.25x | 1:4 | 99.9% | 99.6% |
All classes are measured against the same service-level indicators below. The classes differ in price, overcommit and the percentage of time promised, not in the threshold itself.
02Performance SLA (slow time)
Each VM is scored every 5 minutes against four service-level indicators, measured at VM level as 300-second averages:
| Resource | Counter | Threshold |
|---|---|---|
| CPU | Ready | 2.5% |
| Memory | Contention (latency) | 1% |
| Disk | Latency (read & write avg) | 10ms |
| Network | Transmit dropped packets | 0% |
A 5-minute interval passes when the VM is at or under all four thresholds. The monthly Performance SLA is the percentage of intervals that pass, per VM, per calendar month. Crossing any one indicator fails the interval; failures are binary, with no partial or severe failure.
03Availability SLA (downtime)
| Class | Availability | Allowed downtime |
|---|---|---|
| Gold | 99.975% | 10.8 min/month |
| Silver | 99.95% | 21.6 min/month |
| Bronze | 99.9% | 43.2 min/month |
Availability is measured per VM by Guest OS response (a running but isolated VM fails the test). Operational availability, actual availability minus the agreed exclusions, is the number used in this SLA.
Exclusions: customer-initiated reboots; downtime caused by the guest or application; scheduled maintenance executed within the agreed window. There is no scheduled window for performance: slow time has no maintenance window.
04Compliance SLA
All classes: 99.95%. Compliance is not tiered: it is in the provider's interest to secure every class equally.
05Remedy
A breach in a calendar month is remedied as a credit on the next billing cycle.
06Also part of this agreement
- VM resource size and hardware capabilities per class
- Backup and disaster recovery arrangements
- Patching schedule and maintenance windows (availability only)
- Support response times per class