Isvara
·visits
Tools/01 · SLA Builder

Define good, then write it down.

Set your service classes and the four indicators, and take away the agreement.

The agreement
3 classes · one benchmark
Private Cloud · IaaS
Gold1.00x
Availability
99.975%
10.8 min down
Performance
99.9%
43.2 min slow
CPU 1:1
Silver0.50x
Availability
99.95%
21.6 min down
Performance
99.8%
86.4 min slow
CPU 1:2
Bronze0.25x
Availability
99.9%
43.2 min down
Performance
99.6%
2.9 h slow
CPU 1:4
bars: failure window per 30-day monthvs Gold: down 1x · 2x · 4x slow 1x · 2x · 4x
One threshold, every class
per VM · 5-minute averages
CPU
≤ 2.5 %
Ready
Memory
≤ 1 %
Contention
Disk
≤ 10 ms
Latency
Network
≤ 0 %
Transmit dropped packets
Compliance 99.95% · every classRemedy · credit on the next billing cycle
Service classesprice · overcommit · nines

Under each SLA: the failure window it allows in a 30-day month, as downtime for availability and as slow time for performance.

The guide's model: the same threshold for every class (“2.5% will serve all classes. You just need to adjust the nines.”). Classes differ by price, overcommit and the promised percentage of time. Failure windows are deliberately spaced: Silver tolerates roughly twice Gold's window because it costs half as much. The guide explicitly rejects different thresholds per class: Silver could end up performing better than Gold, and the gaps are hard to explain.

The four indicatorsone benchmark, every class

One benchmark to rule them all: every class is measured against the same four thresholds, per VM, as 5-minute averages.

The guide's thresholds, shared by every class.
Every class is held to the same four numbers; what changes between the classes is the percentage of time promised.
Compliance SLA
all classes

Compliance is not tiered: it is in the provider's interest to secure every class equally.

The agreementlive preview
Service Level Agreement
per VM · per calendar month

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

ClassPriceCPUAvailabilityPerformance
Gold1.00x1:199.975%99.9%
Silver0.50x1:299.95%99.8%
Bronze0.25x1:499.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:

ResourceCounterThreshold
CPUReady2.5%
MemoryContention (latency)1%
DiskLatency (read & write avg)10ms
NetworkTransmit dropped packets0%

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)

ClassAvailabilityAllowed downtime
Gold99.975%10.8 min/month
Silver99.95%21.6 min/month
Bronze99.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
Take it to the meeting

Copy the agreement as Markdown, or print it as a PDF your tenants can hold you to.

In the guidePart 1 · SLA

Part 1's Service Level Agreement chapter sets the classes, their prices and their nines; the executive summary defines the Performance SLA's four indicators.