DevOps & Technology
It is here where we finally start focusing on IT automation and the famous CI / CD processes . What many call DevOps is just one small piece of the DevOps puzzle . Running systems in the cloud requires new tooling and methods . Many of the legacy tools we have used in the past require state and physical infrastructure . We recommend born-in-the-cloud solutions in the areas of security , monitoring , logging , code repositories , etc . Providing visibility into system health and application state is crucial in providing high SLAs in the new world where deployments happen frequently . Much thought needs to go into to building a robust security and monitoring framework that feeds into a central logging solution and can be accessed through a single pane of glass .
The build process should perform security and coding standards scans . Testing should be automated and part of the build process . The build process should produce a score for security , programming standards , and quality . The build should fail if any one of those scores are not at an acceptable level . The
Maturity Model Score : 1.74
Maturity Level
People Process Technology
Level 1 Ad-Hoc |
• Silo based
• Blame , finger texting
• Dependent experts
• Lack of accountability
|
• Manual process
• Tribal knowledge is the norm
• Unpredictably reactive
|
• Manual builds and deployments
• Manual testing
• Environment inconsistencies
|
Level 2 Repeatable
Level 3 Defined
Level 4 Measured
Level 5 Optimized
• Processes established within
• Managed communications silos
• Limited knowledge Continuous sharing Integration
• No standards
• Can repeat what is known , but can ' t react to unknowns
• Collaboration exists
• Processes are automated
• Shared decision making across SDLC
Continuous
• Shared accountability
• Delivery Standards across organization
• Collaboration backed on
• Proactive monitoring shared metricks with a focus
• Metrics collected and analyzed against business goals
Continuous Deployment on removing bottlenecks
• Visibility & predictability
• A culture of continuous • Self service automation improvement
• Risk & cost optimization permeates through Continuous the Operations
• High degree of organization experimentation
• Automated builds
• Automated tests written as part of story development
• Painful but repeatable releases
• Automated build & test cycle for every commit
• Push button deployments
• Automated user & acceptance testing
• Build metrics visible and acted on
• Orchestrated deployments with auto rollbacks
• Non functional requirements defined and measured
• Zero downtime deployments
• Immutable infrastructure
• Actively enforce resiliency by forcing failures
Figure 2 : CTP ' s Maturity Model Matrix *
70 | THE DOPPLER | FALL 2017