Session
From 20 to 5 Person-Days: Standardizing OpenStack + Ceph Deployment
Standardizing OpenStack + Ceph deployment took us from 20 person-days per cluster with two engineers to 5 with one. Deployment time was the smaller half of the payoff.
Environment: Viettel private cloud — 10 OpenStack clusters with Ceph, bare metal, each deployed for a separate tenant organization across different data centers. Standardization was non-optional: every difference tolerated at deployment became one we had to remember at incident time, for a cluster we might not touch again for months.
Where the 20 person-days went — five recurring sources:
— Non-standardized tooling
— Manual hardening: many-item checklist applied by hand
— Manual integration: OpenStack,Ceph, monitoring, logging
— Piecemeal validation: no end-to-end gate, defects surfaced at handover
— Environment drift: failures no runbook anticipated
Drift produces defects, piecemeal validation finds them too late, and hand-built clusters keep charging in incidents and support long after handover. The highest-leverage fix: gate the environment before deploying, not the deployment after.
Attendees leave with a five-category diagnostic framework and a pre-deployment validation checklist for bare-metal OpenStack + Ceph.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top