Apresentação sobre DevOps realizada no evento DevChamps na Microsoft Brasil em agosto/14 por Márcio Sete da especificacoes.com

1. DevOps for Large Enterprises
Márcio Sete, Principal Consultant
Visual Studio ALM MVP
marcio.sete@especificacoes.com http://especificacoes.com/cases
@marciosete

2. “It’s not my machines,
it’s your code!”

3. “It’s not my code,
it’s your machines!”

4. Traditional thinking
Dev’s job is to add new features
Ops’ job is to keep the site stable and fast

5. Opportunity Cost Of
Wasted IT Spending?
$2,600,000,000,000.00
($2.6 Trillion US)
Source: Gene Kim - Why Everyone Needs DevOps Now: My Fifteen Year Journey Studying High Performing IT Organizations

6. Ops’ job is NOT to keep
the site stable and fast

7. Ops’ job is to enable
the business
(this is dev’s job too)

8. The business requires change

9. But change is the root cause
of most outages!

10. Discourage change in the interests of stability
OR
Allow change to happen as often as it needs to

11. Lowering risk of change
through tools and culture

12. DEV and OPS

13. The IT Core Chronic Conflict
Every IT organization is pressured to simultaneously:
 Respond more quickly to urgent business needs
 Provide stable, secure and predictable IT service
Source: The authors acknowledge Dr. Eliyahu Goldratt, creator of the Theory of Constraints and
author of The Goal, has written extensively on the theory and practice of identifying and
resolving core, chronic conflicts.

14. “Every company is an IT company regardless of
what business they think they’re in.” - Christopher Little
 95% of all capital projects have an IT component…
 50% of all capital spending is technology-related
We are here…
Where we need
to be…
IT is always in the way

15. Ops who think like devs
Devs who think like ops

16. DevOps
Which problems are we trying to solve?

17. Fear of change

18. Risky Deployment

19. It works on my machine!

20. Siloisation

21. Focus
Amanda Novais, ProductOwner
Code Enviroments
Bringing value to business

22. DevOps
The (real) movement

23. Upstream Agile Process vs. Downstream Agile Practices
Agile Downstream
Agile UpStream
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report

24. DEVOPS
Culture
Automation
Metrics
Feedback

25. Culture
• People and process first. If you don’t have
culture, all automation attempts will be
fruitless.

26. Automation
• Automate
– Provisioning
– Testing
– Releasing
– Monitoring

27. Automate Provisioning
• Are the configuration files in place?
• Do they contain the right settings?
• Is this port open?
• Is that port closed?
• Are we patched sufficiently?
• Are we using the correct version of this
package?

28. Automate Provisioning
• More ways to deploy infrastructure and code:
– Windows PowerShell
– Windows PowerShell Desired State Configuration (DSC)
– Puppet
– Chef (for servers that are not running a Windows operating system)

29. Automate Provisioning
• Practical applications:
– Enabling or disabling server roles and features
– Managing registry settings
– Managing files and directories
– Starting, stopping, and managing processes and services
– Managing groups and user accounts
– Deploying new softwares
– Managing environment variables
– Running Windows PowerShell scripts
– Fixing a configuration that has drifted away from the desired state
– Discovering the actual configuration state on a given node

30. Automate Testing
• Unit
• UI (Functional and Integration)
• Load
• Database
• Provisioning (already solved, yea?)

31. Automate Releasing

32. Automate Monitoring
• Availability
• Performance Metrics
• User expirience
Server monitoring
Application Performance Monitoring

33. Metrics
• Deploy frequency
• Lead Time for Changes
• Mean time to Recover (MTTR)

34. “Culture eats strategy for breakfast”
- Peter Drucker

35. http://especificacoes.com/cases