Ignite talk at Devopdays Barcelona 2013 about Poka yoke and how it's inspire and can be implemented in a Devops culture

1. Poka­yoke and DevOps
Ulf Månsson ­ @ulfmansson ­ Recorded Future AB

2. Poka­yoke ­ failure proof
Poka­Yoke is a system that, after
being implemented, makes the
creation of a defect in the
manufacturing process impossible
to happen.

3. ポカヨケ
Quality term developed in Japan
Helps an equipment operator avoid (yokeru) mistakes (poka)
Origin in lean manufacturing system

4. Example of Poka­yoke

5. Type of poka­yoke
Control poka­yoke
Warning poka­yoke

6. Poka­yoke ­ failure proof
Poka­Yoke is a system that, after
being implemented, makes the
creation of a defect in the
manufacturing process impossible
to happen.

7. DevOps
About culture
Involving everyone
Deliver

8. Devops + Poka­yoke = true
Make processes fail proofs
Safer for everyone to do tasks by them self
Everyone should be able to do simple tasks as a deploy

9. Automation
One of the build blocks in DevOps
Reduce human errors

10. Deployment
Easy to deploy for everyone – developers are deploying
At Recorded Future, just set the revision number of the component
Component depending are automatically restarted

11. Continuous delivery
Continuous delivery treats the commonplace notion of a deployment
pipeline as a lean Poka­Yoke: a set of validations through which a piece
of software must pass on its way to release
Source Wikipedia

12. Continous delivery safeguard
Image from Wikipedia

13. Test everything
Application code
Infra code
Use tools like test kitchen
Test full deployment

14. Simple to use tools
rfknife_upload apache
Logstash
Graphite
Sensu

15. Auto scaling
Problem with a server, just shut it down, you will get a new for free
Think about your servers as cattle not individual cows

16. Same language for all infra code
Standardized all infra codes in one common language, eq Ruby
Bash, Perl, Python etc is banned
Easy for developers to understand and change
Easy for operation people to understand and maintain

17. Code
All code is code
Keep the code in the same repository
Treat all code in the same way, it doesn’t
matter if it’s application code, infra code,
test code or whatever

18. Same processes, same tools
We all use JIRA
Use the same name for components etc
We run the same sprints

19. Internal tools
Web based to prefer
Few tools
Should warn if there is a major impact of the command
­­help should always work
Should be error prone, take care of the user

20. DevOps and Poka­yoke
Makes everyday life easier
Share
Automation