Design Patterns for Efficient DevOps Processes

Transcript

1. Design Patterns for Efficient DevOps Processes
2. Rebecca Fitzhugh •  @rebeccafitzhugh •  technicloud.com •  github.com/rfitzhugh •  vBrownBag •  vSphere Virtual Machine Management •  Learning VMware vSphere •  VCDX #243
3. Byron Schaller •  @byronschaller •  metalworker.io •  github.com/byronschaller •  Cut The Noise •  VCDX #231
4. Pattern vs Anti-Pattern Pattern “best practice” Anti-Pattern ”please don’t do this”
5. Value Stream Mapping
6. Process versus Service • Proc-ess, noun: a series of actions or steps taken in order to achieve a particular end. • Serv-ice, noun: a System supplying a [business] need.
7. The Process is not the Service
8. What is Value Stream Mapping? Planning tool to optimize results of eliminating waste
9. Lead Time vs Time on Task
10. Who should be part of a VSM? • Service Stakeholders and Customers • Executors of a Process Tasks • Management ...but not all at the same time.
11. Current State
12. Future State
13. Test Automation
14. Functional / Unit Testing •  Test each part thoroughly •  Unit •  Test how it all comes together •  Functional
15. Integration Testing •  Test ways of working together •  Component integration
16. Regression Testing •  Confirms that a code change has not adversely affected existing features
17. Browser/ Device Support Parallel execution Scalable Reports & Metrics Maintainable Run locally & remotely Easy to use OS & DB support Language / tool restrictions Different Environments Support features of product under test Tool support Test Automation Framework Design Criteria
18. Test full stack and automate it!
19. Flight Search Search Results Flight Details Passenger Info Payment Confirmation Application Server Database
20. Test Pyramid UI Web Service View Integration Component Unit Business facing tests Technolog y facing tests Manual/ Exploratory
21. UI Web Service View Integration Component Unit Security Accessibility Performance Recoverability Availability Manual/ Exploratory
22. Sample Test Framework
23. Release Engineering
24. Goal: Accelerate the path from dev to ops
25. Release Process Steps
26. More realistic…
27. OK...fine…the real process
28. Cynefin Framework Every release engineering strategy must: •  Be complexity-informed •  Account for the entirety of the system (systems thinking) •  Address human factors
29. Complexity is the enemy of reliability. Whatever you do, Whatever you buy, Simplify your architecture.
30. Design Pattern for Release Engineering •  Simplicity in process -> automate as much as possible, ensure oversight, gates •  Setting proper expectations -> day 2 ops, feedback loop, ITIL service transition •  Time to release -> canary, blue/green, feature flags and hiding
31. Anti-Patterns for Release Engineering •  If your team is not involved in some sort of continuous integration, be worried. •  If your team is not working on a continuous delivery pipeline, be worried.
33. Blue-Green Deployment
34. Feature Toggle
35. Change Management
36. STEP 1: Ensure change management board is staffed with appropriate personnel.
37. DevOps Difference Change management tends to be a barrier. Change and release management become federated and integrated processes. •  Make everything a standard change (trust but verify), automated gates
38. Check out code and build Unit testing Quality control Deploy to test environment Fetch latest builds Integration testing Package and archiving Fetch release ready builds Deploy to pre- prod Acceptance testing Deploy to production Change Advisory Board (CAB) Pipeline with CAB Feedback Loop
39. More Efficient Change Management Make Change Management a priority Establish different modes of change to balance speed, quality, and risk Integrate change into DevOps pipeline Automate capture of change records with artifacts Improve collaboration and build auditable history Streamline process ITIL, DevOps, business, etc. Speed change processing and increase adoption Single source of truth for ALL changes Increase visibility for risk and compliance management
40. Thank you. Byron Schaller | @ByronSchaller Rebecca Fitzhugh | @RebeccaFitzhugh