Keep CALM and Architect On: An Architect s Role in DevOps

Transcription

1 Keep CALM and Architect On: An Architect s Role in DevOps Terri Potts (@terri_potts) and Eric Ort Raytheon IIS Keep Calm Keep and Calm Architect and Architect On: An Architect s On: An Architect s Role in DevOps Role in DevOps 1

2 What is Raytheon? 2

3 Helping a DevOps team stay CALM Culture Continual learning & experimentation High-trust & scientific approach Automation Automate deployment pipeline Move fast left-to-right Lean Kata Value stream mapping Provide fast feedback right-to-left Measurement Provide visibility Photo of Graham Fitter surfing on the Colorado River, 2017 Brian Doss 3

4 Architects & Culture Embrace change! Define capabilities & features Become part of the team Lead and guide experimentation Change impact analysis for legacy software baselines Test architecture Photo: 4

5 Architects Role in Automation Application modernization Deployment pipeline architecture Infrastructure architecture Photo: httpwebrequest-readwritetimeout-set-to-5-minutes 5

6 Infrastructure as Code and Versioned Environments Quality Attributes: Maintainability / Deployability / Self-Service Tactics: IaC and versioned environments Result: Eliminates environment snowflakes Security Policy Files Environment Automation Scripts COTS / FOSS Containers OS Kickstart Images Incremental DB Schema Configuration Instantiate Instantiate Instantiate Instantiate Dev v1.2.3 Integration v1.2.3 System Test v1.2.3 Ops v

7 Feature Flags for Dark Launch Quality Attributes: Deployability, Testability Tactics: Feature flags and dark launching Results: Quick / easy rollback of features Dark launching Avoids branching hell Less risk to production If (configparams.feature) { <new feature code> } 7

8 Semantic Versioning Pattern Quality Attribute: Deployability and Availability Tactics: Semantic versioning, versioned interfaces Results: Live deploys Live switch to semantically compatible version Consumer Consumer X Node RHEL VM Microservice V1.0.1 Node RHEL VM Microservice V

9 Incremental Database Upgrades Quality Attributes: Maintainability, Modifiability, Upgradability Tactics: Incremental database upgrades Results: Fully automated upgrade of an existing database to match a new software version SW Change DB Change SW v Upgrade SW v SW Change DB Change Database V1.2.3 Apply DB Changes Database V1.3.5 Total SW Changes Total DB Changes 9

10 Forward / Backward Compatibility Quality Attributes: Deployability, Upgradability Tactics: Forward/backward DB compatibility Results: Painless rollback / fallback and no-risk upgrades Full Name Eric Ort Terri Potts Full Name First Name Last Name Eric Ort Eric Ort Terri Potts Terri Potts First Name Eric Terri Last Name Ort Potts Microservice v1 Microservice v2 Microservice v3 Database V1 Add First Name & Last Name columns Database V2 Remove Full Name column Database V3 Lines indicate compatibility 10

11 Patterns that support Test Automation Quality Attributes: Testability Tactics: Mocking, seams, service isolation, separation of business logic Results: Defect localization for lower MTTR, easier to automate tests, automated test suite performance GUI Business Logic Disk Access Layer / Code Disk Consumer production test WebService SoapUI Mock Test Code SaleTerminal void notifyserver() Jmockit no-op version of notifyserver() SaleTerminal. void notifyserver() SaleTerminal Subclass (at seam). void notifyserver() 11

12 Dynamic Infrastructure Patterns for Automation Quality Attributes: Performance, Elasticity, Resiliency Tactics: Immutable microservices, containers, container management / scaling software, SW that is ready to live, die and multiply Results: Seamless user experience and results with just the right amount of resource usage Consumer Consumer Consumer Node RHEL VM POD Container APP APP POD Container APP APP OpenShift / Kubernetes Cluster Node RHEL VM POD Container APP APP POD Container APP APP OpenShift / Kubernetes Router Node RHEL VM POD Container APP APP POD Container APP APP 12

13 Architects Helping the Organization Get Lean Representative schedules Value stream mapping Reduce work in progress Feature driven development Kata Photo courtesy of Pixaby.com 13

14 Understand the Direction or Challenge THE FOUR STEPS OF THE IMPROVEMENT KATA MODEL A systematic, scientific pattern of working Grasp the Current Condition Establish the Next Target Condition Iterate Toward the Target Condition TC CC By Mike Rother Planning Executing Phase Phase The Improvement Kata model comes from six years of research into how Toyota manages people, which is summarized in the book Toyota Kata 14

15 TERMINOLOGY Threshold of Knowledge Obstacles Next Target Condition (dated) Experiments Current Condition By Mike Rother 15

16 WHAT IT REALLY LOOKS LIKE Challenge Threshold of Knowledge Next Target Condition (date) Current Condition Experiments At the Current Knowledge Threshold By Mike Rother 16

17 Measurement that Support Measurement Microservice built-in metric support at the endpoints Health checks and metrics - Application of circuit breaker pattern - SW based resiliency Proactively determine if software, VMs or HW are getting sick and automatically respond $ curl * deadlocks: OK * database: OK 17

18 Measurement (Cont)that Support Measurement Monitoring and Response at scale Intelligent analysis of metrics Intelligent correlation of metrics Intelligent collation and routing of alerts Automated response orchestration 18

19 Conclusion Architects must still understand the whole system up front Architects have a different, but ongoing role Stay current on the latest patterns that support automation, cloud, etc. New architectural roles are needed for Infrastructure and Test Photo courtesy of Pixaby.com 19