5. Clearly pointed out that IT should be strategic and transformational
And that we need to become more agile in our way of working.
2016 - New Managing Director
Clear direction and new organization
6. Disclaimer
The opinions expressed in this presentation
and on the following slides are solely those of
the presenter and not necessarily those of
Scania as a whole.
10. We at infra need to be an enabler for
developers. Enable automatic deployments
and roll-backs.
Creating tools/dashboards with relevant
KPI’s so that the developer can fast and
easily see the consequences of a deployment.
- Mattias Järnhäll, Infrastructure manager
2014.03.03 on Scania social network
11. in the early days…
DevOps movement
More features
quicker Stability
21. Version Control
Pull & Push several
times a day
Continuous
Integration
Server Target Servers
(Dev, Staging, Prod)
Version Everything
- Code
- Tests
- Configuration
- Database
- Infrastructure
10 minutes
Automation – Deployment Pipeline
Deploy
Server
27. All Infra
needs
User Interface
Service
1
Service
2 Service
5
Service
7
Service
8
Service
10
Service
12
Service
14
Service
3
Service
4
Service
6
Service
9
Service
11
Service
15
Service
13
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
GUI
Database
Infra
Business
Logic
Why Microservices?
1. Autonomous teams
2. Build, Test, Deploy SPEED
Microservices
42. Level 1
Level 2+3
Infrastructure As A Service
Infra/
Operations
Feature
Team
Feature
Team
Feature
Team
Feature
Team
GUI
Business
Logic
Database
Virtual Machine ESB Network Change Management Database Monitoring
Today
43. Infrastructure As A Service
Infra/
Operations
Feature
Team
Feature
Team
Feature
Team
Feature
Team
GUI
Business
Logic
Database
Virtual Machine Web server Load Balancer Change Management Monitoring
You build it You
run it!
Infrastructure
as code
Cultural Technical
53. Use your technical skills
Poor little me.
I’m just a Dev.
What can I do?
Zero Downtime
Feature Toggles
Deploy becomes a part
of your daily job
Deploy is decoupled
from Release
The power of rapid software development makes our hardware products even better.
Code review is your security gate. Not a QA or an ISec department.
Code review is your security gate. Not a QA or an ISec department.
Code review is your security gate. Not a QA or an ISec department.
Ops1: “Wait until Tuesdays CAB!”
Dev1: “You must start to code and version your stuff”
Dev2: “Use my repo. I’ll be contributing”
Ops1: “Wait until Tuesdays CAB!”
Dev1: “You must start to code and version your stuff”
Dev2: “Use my repo. I’ll be contributing”
On a startup it is quite obvious that one single person is capable to iterate fast depending on customer needs. But also to monitor and finding interest in monitoring performance an income of cash.
We try to keep the good parts of this environment and delegate control to the feature teams. Within the teams all individuals have equal responsibility for quality and income.
Short iterations gives more quality: http://whatgivesquality.devops.vision
High focus on Continuous Integration:
Versioning all assets
Trunk-based development
Automated Tests
Claim > Blaim
…but we were unable to effectively scale and do CI + CD
Code review is your security gate. Not a QA or an ISec department.
This is a developer from the eyes of an operations guy. Obviously, since he is not responsible for quality and stability.
QA is not Quality Assurance. It is Quality Assistance.
”It’s a trade from code complexity to operational complexity”
Martin Fowler:
https://www.youtube.com/watch?v=wgdBVIX9ifA
http://martinfowler.com/articles/microservices.html
Adrian Cockcroft:
https://www.youtube.com/watch?v=nMTaS07i3jk&feature=youtu.be
Gene Keen, Randy Shoup
http://youtu.be/MRa21icSIQk 43:00
Randy Shoup:
http://gotocon.com/dl/goto-cph-sept-2014/slides/DeanWampler_and_EvaAndreasson_and_KevlinHenney_and_RandyShoup_WheresCaptainKirkChartingACourseThroughEnterpriseArchitecturePartI.pdf
With zero downtime deployments engineers can push code to Prod on a daily basis. We have overcome our biggest challenges which have been relational database deployments and automation of our on-prem load balancer.
A huge advantage is the fact that developers pushes the code themselves and will thereby be present when the code goes live.
Visibility is key to make everyone think of what happens and what could be improved.
About 4 times more check-ins with the microservice architecture.
IaaT = Infrastructure as a Ticket
Don’t automate in silos! Learn Ops the art of code reviews and mob programming.
At Scania today we colocate Dev and Ops!
The wide diversity of skills required to build today’s applications means collaborative teamwork, not dysfunctional silos.
These autonomous teams speaks with http status codes (via APIs).
#NoRoles
Visibility is key to make everyone think of what happens and what could be improved.
The scope of what you as a developer is responsible for has grown.