DriveTime's DevOps
Roadmap 2017
A look into some of the upcoming
DevOps initiatives
of 2017
Assistance and feedback from: Nick, Ken, Shiloh & Jason
A quick look at some principals
- Know why you're working on something
- Know how to measure what you're working on
- Work on small slices / small scope
- Work on things that add value now
- Try to be as antifragile as possible
- Create documentation whenever appropriate
- Use source control whenever possible
sources of work
Currently
- Larger business needs (Ally)
- Team needs that come in via requests or engagements
- DevOps team needs
Managing the work
- Trello board
- Feedback from dev leadership metings
- Measuring metrics
Ongoing projects
- Cross training within the team
- Dashboarding on and off the team
- Quality of service improvements and measurements
- Documentation (Wiki / Playbook / Recipes)
DevOps Projects in 2017
Short-term
- Ally
- SQL CI/CD
- Blue/Green Deployments
- Jenkins as code
- Hosting platform as code (IIS & Azure)
- Server split (chef)
- Automated deployments
DevOps Projects in 2017
Mid-term
- Build health aggregation (SonarQube)
- Additional build enhancements (Whitehat)
- Bringing consistency to builds
DevOps Projects in 2017
Long-term
- Automated gating of builds
- Orchestration
Devops Engagements
Information gathering & training
- Set expectations
- Information gathering and documenting
- Inject ourselves in the process to help and lead by example
- Train on what they don't know
- Help with what they can't do
- Measure the whole time
Measurements for engagements
On and Off the team measurements
- Capabilities of the team
- Improved execution
- Time spent on support
- Response time
- More reported metrics
