1. DevOps
CSCI 577b

2. Process Models Waterfall vs Agile vs DevOps
*notional timeline
Process Models Waterfall vs Agile vs DevOps
Waterfall
Req & Design
Code
Test
Deploy
Agile
Design
Code & Test D
Code & Test D
Code & Test D
Code & Test
Deploy
DevOps
Design
Code & Test, Integration & Test
DevOps with iterations
Design D ….
e.g. Daily build/ integration at CI-level; Sprint-level integration for subsystem; Release-level integration for system/segment

3. DevOps – The Value Stream and Process Visibility
Essentials
Break down silos
Be responsible for delivery
Be responsible for stability
Be responsible for mission success
DevOps Tactics
Maximize flow
Reduce waste
Minimize work in progress
Use smaller batches
Create repeatability
Systematize tribal knowledge
Automate repetitive tasks
Infrastructure as code
Readability, testing, refactoring
Improve reliability
Test infrastructure on local host
No surprises in Production
Don’t rely on humans
Organization
Deployment Frequency
Amazon
Every 11.6 seconds
NetFlix
100 times per day
Facebook
Twice a day
Google
Multiple times a week

4. DevOps Practices Continuous Integration Continuous Delivery
Continuous Deployment
Continuous Integration is for everyone, Continuous Delivery is for most, and Continuous Deployment is for the rare few
Continuous Delivery
Continuous Deployment
Automatically

5. DevOps Enablers Tools and Infrastructure Infrastructure as Code (IaC)
Continuous integration, orchestration, monitoring, deployment, and testing
Cloud technologies, Microservices
Infrastructure as Code (IaC)
Use Code (machine-readable definition files) to manage configurations and to provision and deploy servers and applications (dynamic infrastructure)
faster, consistency, easier to change, avoid human errors
Able to execute in repeatable fashion
Skilled engineers who understand architecture
Think of software and network configuration and infrastructure
Infrastructure Automation and Deployment
Zhu L., et.al “DevOps and Its Practices”, IEEE Software, May/June 2016

6. DevOps Bottlenecks Inconsistent environments
Create standard infrastructure
Manual intervention - human error and non-repeatable processes
Automate the build and deployment processes, use TDD
SDLC Maturity, legacy change management processes, lack of operational maturity
Invest in training, remove bureaucracy steps, increase agility and transparency
Outdated testing practices
Integrated QA & test teams, test automation, remove silos
Automating waste (unbalanced design)
Refactor, continuous improvement
Governance as an Afterthought
Pick right metrics, incentivize the quality, reliability, agility, resiliency
Limited to No Executive Sponsorship
TDD = Test Driven Development
SDLC = Software Development Life Cycle

7. DevOps - Pitfalls
Little/No collaboration between teams/groups; including oversight team
Program-level mind set; use collaboration tools
Rigid architecture (not easily extensible)
Need encapsulation, abstraction, and decoupling
Cannot replicate on-demand
Need automated build and configuration process
 virtual machines, containers
Expecting immediate change & expectation mismatch
Providing room for change & new processes & mistake
Use appropriate metrics

8. DevOps Challenges Team Skills DevTest environment Test
Collaboration, personnel skills
DevTest environment
Consistency between environments
Tools and Software Version Control
Test
Functional, acceptance, integration, performance, sustainability tests
(c) USC CSSE

9. DevOps – Available Tools

10. DevOps phases Build Deployment
Implement, manage dependencies, document, test
Continuous Integration
Integrate, test
Deployment
Continuous Delivery
Need homogenous infrastructure
Operations (Test as proxy for operation)
Log and Monitor
Aka integration and tester for