Repository navigation
Consolidate Operations category duplicate patterns #434
Description
What: Action the five Operations consolidation pairs identified in #385 (Optimise storage utilization, Optimize CPU utilization, Right-size compute resources, Scale down applications when not in use, Dynamic scaling based on demand), each as its own PR showing the original patterns and the proposed replacement, with cost impact added as part of the same pass.
Patterns Analysis ‐ August 2026 ‐ Operations
Why: Operations is the most duplication-heavy category in the catalogue. Clearing this out is the main blocker to adding cost impact sections across the category, agreed as the next priority after consolidation.
Success: All five consolidated patterns merged, each reviewed by at least one SME before merging (per Liya's standing requirement), cost impact section present in each.
SoW:
- @russelltrow to send Franzi a specific brief/prompt for one pilot pattern pair
- @russelltrow and @franziska-warncke to verify quality of the pilot consolidation together
- @russelltrow : VM rightsizing (near-identical) Consolidate VM rightsizing patterns into 'Rightsize compute to match utilization' #436
- @russelltrow : CPU utilization (near-identical) Consolidate CPU utilization patterns into 'Match CPU capacity to average and peak utilization' #437
- @russelltrow : Storage cleanup (near-identical) Consolidate storage cleanup patterns into 'Delete or auto-expire unused storage' #438
- @franziska-warncke : Storage rightsizing (mirrors VM cluster)
- @franziska-warncke : Scale-to-zero (general vs. K8s-specific)
- @franziska-warncke : Broader scale-down umbrella
- @franziska-warncke : Carbon-intensity time-shifting (partial overlap)
Activity