Keep CALM And Architect On: An Architect's Role In DevOps

SATURN 2017 Keep CALM and Architect On: An Architect’s Role in DevOps Terri Potts (@terri potts) and Eric Ort Raytheon IIS Unrestricted Content Unrestricted Content Keep Calm Keep andCalm Architect and Architect On: An Architect’s On: An Architect’s Role in DevOps Role in DevOps 2017 Raytheon 2017 Raytheon 1

SATURN 2017 What is Raytheon? Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 2

SATURN 2017 Helping a DevOps team stay CALM Culture Lean Continual learning & experimentation High-trust & scientific approach Kata Value stream mapping Provide fast feedback right-to-left Automation Automate deployment pipeline Move fast left-to-right Measurement Provide visibility Photo of Graham Fitter surfing on the Colorado River, 2017 Brian Doss Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 3

SATURN 2017 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: 20688/ Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 4

SATURN 2017 Architects Role in Automation Application modernization Deployment pipeline architecture Infrastructure architecture Photo: httpwebrequest-readwritetimeout-set-to-5-minutes Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 5

SATURN 2017 Infrastructure as Code and Versioned Environments Quality Attributes: Maintainability / Deployability / Self-Service Tactics: IaC and versioned environments Result: Eliminates environment snowflakes Instantiate Environment 1.2.3 Instantiate Automation Scripts Security Policy Files COTS / FOSS Containers Dev Environment @ v1.2.3 Incremental DB Schema Configuration Instantiate Instantiate OS Kickstart Images Integration Environment @ v1.2.3 System Test Environment @ v1.2.3 Ops Environment @ v1.2.3 Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 6

SATURN 2017 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 } Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 7

SATURN 2017 Semantic Versioning Pattern Quality Attribute: Deployability and Availability Tactics: Semantic versioning, versioned interfaces Results: Live deploys Live switch to semantically compatible version Node RHEL VM Microservice V1.0.1 Consumer Consumer Node RHEL VM Microservice V1.0.3 X Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 8

SATURN 2017 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 Change DB Change Total SW Changes SW v.1.2.3 Upgrade Database V1.2.3 Apply DB Changes SW v.1.3.5 Database V1.3.5 Total DB Changes Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 9

SATURN 2017 Forward / Backward Compatibility Quality Attributes: Deployability, Upgradability Tactics: Forward/backward DB compatibility Results: Painless rollback / fallback and no-risk upgrades Full Name Full Name First Name Last Name First Name Last Name Eric Ort Eric Ort Eric Ort Eric Ort Terri Potts Terri Potts Terri Potts Terri Potts Microservice v1 Database V1 Microservice v2 Add First Name & Last Name columns Database V2 Microservice v3 Remove Full Name column Database V3 Lines indicate compatibility Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 10

SATURN 2017 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 Business Logic GUI Disk Access Layer / Code Disk SaleTerminal . void notifyServer() Test Code production WebService Consumer test SoapUI Mock SaleTerminal void notifyServer() SaleTerminal Subclass (at seam) . void notifyServer() Jmockit no-op version of notifyServer() Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 11

SATURN 2017 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 OpenShift / Kubernetes Cluster Consumer Consumer Consumer Node RHEL VM Node RHEL VM Node RHEL VM POD Container Container APP APP POD Container Container APP APP POD Container Container APP APP POD Container Container APP APP POD Container Container APP APP POD Container Container APP APP OpenShift / Kubernetes Router Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 12

SATURN 2017 Architects Helping the Organization Get Lean Representative schedules Value stream mapping Reduce work in progress Feature driven development Kata Photo courtesy of Pixaby.com Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 13

SATURN 2017 THE FOUR STEPS OF THE IMPROVEMENT KATA MODEL A systematic, scientific pattern of working 1 2 3 4 Understand the Direction or Challenge 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” Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 14

SATURN 2017 TERMINOLOGY Threshold of Knowledge Obstacles Next Target Condition (dated) Experiments Current Condition By Mike Rother Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 15

SATURN 2017 WHAT IT REALLY LOOKS LIKE Challenge Next Target Condition (date) Threshold of Knowledge Experiments Current Condition At the Current Knowledge Threshold By Mike Rother Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 16

SATURN 2017 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 http://www.some example.com:8081/healthcheck * deadlocks: OK * database: OK to-customize-hat-sizes.html Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 17

SATURN 2017 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 Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 18

SATURN 2017 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 Keep Calm and Architect On: An Architect’s Role in DevOps 2017 Raytheon Unrestricted Content 19

Keep Calm and Architect On: An Architect's Role in DevOps 2017 Raytheon 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 .