Assessments - The Practice of Cloud System Administration - page 438

• Idle capacity that is not currently used by any service is monitored.
• The desired amount of headroom is defined.
• The roles and responsibilities for keeping the inventory up-to-date are defined.
• Systems for tracking the devices that are connected to the network and their hard-
ware configurations are in place.
Level 4: Managed
• Dashboards track performance, utilization, and resource efficiency.
• Minimum, maximum, and 90th percentile headroom are tracked and compared to
the desired headroom and are visible on a dashboard.
• Goals for performance and efficiency are set and tracked.
• There are periodic reviews of performance and efficiency goals and status for each
service.
• KPIs are used to set performance, utilization, and resource efficiency goals that
drive optimal behavior.
• Automated systems track the devices that are on the network and their configura-
tions and compare them with the inventory system, flagging problems when they
are found.
Level 5: Optimizing
• Bottlenecks are identified using the performance dashboard. Changes are made as
a result.
• Services that use large amounts of resources are identified and changes are made.
• Changes are reverted if the changes do not have a positive effect.
• Computer hardware models are regularly evaluated to find models where utiliza-
tion of the different resources is better balanced.
• Other sources of hardware and other hardware models are regularly evaluated to
determine if cost efficiency can improved.
A.9 Service Delivery: The Build Phase
Service delivery is the technical process of how a service is created. It starts with source
code created by developers and ends with a service running in production.