DevOps es un conjunto de prácticas que automatizan los procesos entre el desarrollo de software y los equipos de infraestructura, de manera que el software pueda ser construido, probado y puesto en producción más rápidamente y con la misma confiabilidad. El concepto de DevOps esta fundamentado en la construcción de una cultura de colaboración entre equipos que históricamente son silos. Los beneficios aparentes incluyen confianza mutua, más rápidos ciclos de puesta en producción, habilidad para resolución de incidentes más rápidamente y mejor adaptación a los cambios. En esta sesión revisamos conceptos clave de DevOps, el estado del arte y algunas de las tecnologías involucradas.

1. An evening with … DevOps
Arkho Innova Meetup series
August 2017

2. • Un espacio para compartir experiencias y
conocimiento
• Un espacio para hacer relaciones entre
personas y equipos con intereses afines
• Un espacio para pasarla bien
Gracias por su asistencia!!!

3. What’s up for today?

4. ¿DevOps?

5. • It comes from the need to keep up with software velocity
• Advances in agile culture and methods, exposed the need for a end-to-end
approach
• Extends agile development practices thru build, validate and deploy and
delivery
• It is a mindset: the combination of cultural philosophies, practices, and
tools that increases an organization’s ability to deliver applications and services
at high velocity
What is it?

6. Is it necessary?

7. Development
QA
Operations

8. Improve collaboration between all stakeholders, from planning through delivery and automation of
the delivery process in order to:
The Goal
✓ Improve deployment frequency
✓ Achieve faster time to market
(TTM)
✓ Lower failure rate of new
releases
✓ Shorten lead time between
fixes
✓ Improve mean time to recovery
(MTR)
✓ Improved collaboration

9. Wait a minute, How the big guys
do it?

10. Amazon Velocity Culture
• Since 2010, Amazon runs all traffic from EC2 containers (elastic web computing)
• Automatic scalability from a single host, to hundreds (up or down)
• Cultural change: Velocity Culture
• Amazon gains increased Business value from Continuos Deployment culture
Amazon Deployment Stats (production only)
Mean time between
deployments (weekday)
11.6 secs
Max deployments in
an hour
1,079
Mean # of hosts
receiving a
deployment in a day
10,000
Jon Jenkins, Director
Amazon Silk Amazon

11. Development at the speed and scale of Google
• More than 5K developers, More than 50K builds per day on average, More than 100M test cases
automated per day
• Build everything from source. Head of the tree should be stable and we test it with extensive
automated tests and enforcement of coding styles and guidelines (including coverage)
• Test Automation is built into development pipeline
• Focus is to accelerate Google: Source Control, Developer tools, Test Labs, Automation. We focus
on continuos improvement with Tools and strong focus on metrics
• We provide infrastructure for all the teams: centralize code review, run automated tests,
automate deployment, move all compute-intensive work to the cloud, etc.
• Key Goals are Speed of deployment, High Quality feedback, Simplicity
• Some of the technology behind: FUSE-based file system for code check out, Preforce as VCS (most
of the time we check in the HEAD), and others
• Build metadata is used to automate deployments. 66% of actions from automated builds
Ashish Kumar
Senior Engineering
Director

12. Facebook release process
• We put in practice two things: Tools & Culture
• You (the developer) will shepherd your changes out to the world. No QA group, but test
engineering group,You don’t test it? is not being pushed
• All of our frontend and backend systems follow the same procedure and guidelines
• Strong code management guidelines and changes quite small (800 developers and 14K
commits per month)
• Use a release cadence: Mon: Small daily, Tue: Larger Release, Wed: Larger Daily, Thu: Regular
daily, Fri: Careful daily
• IRC bots (automated rev response), obviously continuously automated testing (4K unit tests,
4K machines, 15 minutes), error logging and monitoring (aggregated, drilldown and timeline),
a GateKeeper (to control on/off features by various dimensions), PushKarma (size vs.
commits and developer karma), PerfLab (every single change has a full performance
regression), HipHop Virtual Machine for development and production
Chuck Rossi
Release Engineering
Facebook
“Tools will not save you.You need the right people”

13. And the mere mortals?

14. Let’s see RightScale State of Cloud

15. Let’s see StackOverflow

16. How often companies released code in 2014
versus 2015
Let’s see NewRelic

17. OK :), What are the key factors to
adoption?

18. 1. Transformational leaders share five common
characteristics that significantly shape an
organization's culture and practices
Critical factors

19. Transformational leadership
Gartner: By 2020, half of the CIOs who have not transformed their teams
capabilities will be displaced from their organizations digital leadership teams

20. It has to do with the culture
• Even with the best tools, DevOps is just another
buzzword if you don't have the right culture.
• Increased collaboration (DEV + QA + OPS)
• Attitude of shared responsibility (you developed it,
you ship it!)
• Involve development team on monitoring
• Deployment automation
• Building quality into development
• How to attend to emergencies
• Organizational shifts
• No silos between DEV and OPS
• Autonomous teams

21. 1. Transformational leaders share five common characteristics
that significantly shape an organization's culture and
practices
2. Automation is a huge boom to organizations, and
applies to all industries
Critical factors

22. Automation
• Medium performers have discovered a mountain of
technical debt — and that technical debt is holding
them back
• Once the stage of burning down technical debt has
passed, further automation becomes much more
achievable
“ability to develop and deliver software
efficiently and accurately, is a key
differentiator and value driver for all
organizations — for-profit, not-for-profit,
educational and government
organizations alike”

23. Automation

24. 1. Transformational leaders share five common characteristics
that significantly shape an organization's culture and
practices
2. Automation is a huge boom to organizations, and applies to
all industries
3. Loosely coupled architectures and coupled
teams, are the strongest predictor of continuous
delivery
Critical factors

25. Technical practices
• Creating architectures and teams that are loosely
coupled, drives the practice to continuous delivery
• Architectural approaches that enable this strategy
include the use of bounded contexts, and APIs
• The architecture should also enable the use of test
doubles and virtualization to test services, or
components in isolation
• High performers have the shortest integration times
and branch lifetimes (hours)
• Low performers have the longest integration times
and branch lifetimes (days to months)
Architecture
Code management

26. Test automation patterns

27. Agile testing

28. Is it cloud native?
• Containerized. Each part
(applications, processes, etc) is
packaged in its own container. This
facilitates reproducibility,
transparency, and resource isolation.
• Dynamically orchestrated.
Containers are actively scheduled
and managed to optimize resource
utilization.
• Microservices oriented.
Applications are segmented into
microservices. This significantly
increases the overall agility and
maintainability of applications.
Aims to ensure, applications can be ported between different public and private clouds. Free from vendor-lock in,
companies are able to transport whole web-scale applications from one cloud to another.

29. 1. Transformational leaders share five common characteristics
that significantly shape an organization's culture and
practices
2. Automation is a huge boom to organizations, and applies to
all industries
3. Loosely coupled architectures and coupled teams, are the
strongest predictor of continuous delivery
4. Lean product management drives higher
performance
Critical factors

30. Lean product management
• Decomposing work into small batches
• Creating prototypes or minimum viable
products (MVPs)
• Find the skateboard (eairlist testable
product)
• Avoid Big Bang
• Avoid “MVP” (As an example Earliest
testable/usable/lovable)
• Actively seeking customer feedback as an
input for product design (using techniques
such as A/B Testing)
• Increases the probability to drive value

31. Finally, a look on the path

33. • Quickly integrating newly developed
code with the main body of code that is
to be released

34. • Automation and testing to get the code
nearly ready to deploy with almost no
human intervention
• Quickly integrating newly developed
code with the main body of code that is
to be released

35. • Deploying all the way into production
without any human intervention
• Automation and testing to get the code
nearly ready to deploy with almost no
human intervention
• Quickly integrating newly developed
code with the main body of code that is
to be released

36. 1. http://joshuaseiden.com/blog/2013/12/amazon-deploys-to-production-every-11-6-seconds/
2. http://www.allthingsdistributed.com/2014/11/apollo-amazon-deployment-engine.html
3. https://thenewstack.io/devops-walmart-way-newly-released-oneops-cloud-platform/
4. https://www.infoq.com/presentations/Development-at-Google
5. https://www.infoq.com/presentations/Facebook-Release-Process
6. https://puppet.com/resources/whitepaper/state-of-devops-report
7. http://www.gartner.com/binaries/content/assets/events/keywords/infrastructure-operations-management/iome5/gartner-predicts-for-it-infrastructure-and-operations.pdf
8. https://www.thoughtworks.com/insights/blog/architecting-continuous-delivery
9. https://martinfowler.com/bliki/MicroservicePrerequisites.html
10. http://www.oreilly.com/webops-perf/free/microservices-for-modern-commerce.csp
11. https://www.thoughtworks.com/insights/blog/case-continuous-delivery
12. Forrester. Continuous Delivery Maturity Model (CDMM). http://info.thoughtworks.com/rs/thoughtworks2/images/continuous_delivery_a_maturity_assessment_modelfinal.pdf
13. https://explore.versionone.com/state-of-agile/versionone-11th-annual-state-of-agile-report-2
14. https://newrelic.com/resource/data-culture-survey-2016
15. https://www.versionone.com/devops-101/what-is-devops/
16. https://aws.amazon.com/devops/what-is-devops/
17. https://insights.stackoverflow.com/survey/2017#diversity
18. www.rightscale.com/lp/2017-state-of-the-cloud-report
19. http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
20. https://martinfowler.com/bliki/UtilityVsStrategicDichotomy.html
21. https://aws.amazon.com/devops/#versioncontrol
22. https://martinfowler.com/bliki/DevOpsCulture.html
23. https://xebialabs.com/periodic-table-of-devops-tools/
24. https://www.atlassian.com/devops
Referencias

37. An evening with … DevOps
Arkho Innova Meetup series
August 2017