DevOps Porto #39 ONLINE: Let's talk about automation 26 October 2020 https://www.meetup.com/devopsporto/events/274098255/

1. Automate from the start
Giulio Vian
26 October 2020

2. Feed for thought

3. Hardware spec:
1 KB RAM
(16KB after upgrade)
4 KB ROM
(8KB after upgrade)
First computer Past Companies Communities
Giulio Vian Senior DevOps Engineer

4. Common Sense
https://xkcd.com/1205

5. But…
there’s more

6. What about?
Acquired knowledge
Outdated documentation
Fear of change
Happiness through accomplishment
Ability to plan, design and test

7. So you setup an
automated CI / CD
pipeline

8. Let’s check we are on the
same page
Continuous Integration
Software development practice where members of a team
integrate their work frequently […] verified by an automated
build (including test) to detect integration errors as quickly
as possible — Martin Fowler
Continuous Delivery
The ability to get changes of all types […] into production, or
into the hands of users, safely and quickly in a sustainable
way — Jez Humble

9. What if I lose my
build
infrastructure?

10. Value/Recycle scale
Production
data & keys
Source
code
Comm
keys
Config
data
Testing
data
Build
data
Build
infrastructure
P r e c i o u s D i s p o s a b l e

11. What’s the Value? 𝑉𝑎𝑙𝑢𝑒 = 𝐿 𝑏𝑢𝑠𝑖𝑛𝑒𝑠𝑠 + 𝐿ℎ𝑜𝑡𝑓𝑖𝑥 ×
𝐻 𝑑𝑒𝑙𝑎𝑦 − 𝐻 𝑎𝑢𝑡𝑜𝑚𝑎𝑡𝑒𝑑
L = hourly Loss
H = Hours
Averaged over year
Business impact of
feature delay
Hotfix deployment
delay
Hours for manual
rebuild

12. Return On Investment
𝑅𝑜𝐼 =
𝐺𝑎𝑖𝑛 − 𝐶𝑜𝑠𝑡 𝑜𝑓 𝐼𝑛𝑣𝑒𝑠𝑡𝑚𝑒𝑛𝑡
𝐶𝑜𝑠𝑡 𝑜𝑓 𝐼𝑛𝑣𝑒𝑠𝑡𝑚𝑒𝑛𝑡

13. There are no
development
environments

14. Only
environments you
can rebuild

15. bricks

16. Fault
line

17. Changes
CrenellationPointed arc &
canopy
Windows, door &
stairway

18. Brown-field

19. Company
Heritage

20. Explore the unknown

21. What’s the Value? 𝑉 = 𝑁𝑎 × 𝐺 − 𝐶 𝑎 − 𝑅 𝑎 × 𝐸 𝑎
− 𝑁𝑏 × 𝐺 − 𝐶 𝑏 − 𝑅 𝑏 × 𝐸 𝑏
G = Gain per change
C = impl. Cost per change
N = changes per year
R = error Ratio
E = Error cost
Cost of change before
and after
Rate of change before
and after
Business advantage of
new technology
Reduced errors

22. Improvement

23. Psychological
and Social
effects

24. Less chores

25. Sense of
accomplishment

26. Learn new
technology

27. Remove fear of
change

28. Ripple Effect

29. https://xkcd.com/1319

30. Automate
everything

31. “Automate ALL the things”
— Chris Jones et al.

32. The more you
automate, the
more everything
becomes
production

33. References
https://www.thoughtworks.com/insights/blog/wh
en-to-automate-and-why
https://ma.ttias.be/why-do-we-automate/
https://www.thoughtworks.com/insights/blog/fun
ctional-tests-how-decide-what-automate
Niall Murphy et al., Site Reliability Engineering,
O′Reilly 2016
or https://landing.google.com/sre/book/index.html

34. Address
giulio.dev@casavian.eu
@giulio_vian
https://www.slideshare.net/giulio
v
http://blog.casavian.eu
https://medium.com/@giuliovdev
https://github.com/giuliov

35. thIS is…
…ALL