Child Welfare Digital Services

Sprint Review Presentation

Sprint Dates: 09/29/17 to 10/11/17

Sprint Review of PI 4.3

DevOps Engineering

Agenda

Review the Sprint Goal

Demo #1: Environment Status Automation (Arpit)

Demo #2: Environment Dashboard 1.0 (Chad)

Demo #3: New Production Design (Sree)

Demo #4: Cloudformation – New Prod Design (Vinod)

Team Metrics

Impediments

Risks

What’s Next

2

Sprint Goal

Keep the lights on (maintain existing environments)

Deliver & Maintain new and existing environment in the CD pipeline: Preview

& Performance

Management Plans

POC for automated smoke test for deployments – In-progress

DevOps Metrics & Dashboard - In-progress

Operational Plan & Buildout of Sandbox/Production

Access to logs via Web Browser for Env

Operations Support (Deployments, IDs, Bugs) - Support Dev Teams

3

Demo of Functionality: Environment Status Automation (Arpit)> This is an Ansible script that automates a lot of manual tasks the On-Call engineer had to perform to get the precise status of all our environments every single day.

> Considering we now have close to 200 AWS instances running, it is very easy to miss out on a critical task that needs to be performed if we go the manual way.

> The plan was to automate all the manual steps required to be performed in order to get the correct status of all our environments. This script runs in just under 2 minutes and returns a complete log report that shows the status of all app containers, services, hosts and URL HTTP status codes. Going forward, we want to use this data and create a dashboard which will be more readable for everyone on the project.

4

Demo of Functionality: Environment Dashboard 1.0 (Chad)

5

Demo of Functionality: New Production Design (Sree)

6

Demo of Functionality: Cloudformation – New Prod Design (Vinod)

7

• Decoupled environments into stacks• Networking• Application stack• Database stack

• Ansible for Generating Cloud formation Templates• Ansible playbook that generates Cloud formation stacks based on the environment

variables mentioned• The generated stack are updated into the GIT repos based on the environment type

using Jenkins

• Advantages• Application stacks are deployed/updated when ever required without effecting the

databases

DevOps Engineering – BUILD METRICS

8

PI 4.3 Only

PI 4.1, 4.2, and 4.3 Combined

Environments Sum of # Successful Sum of # Failed Sum of # Total Builds

Infrastructure-Builds 115 26 141

preint02 54 29 85

preint 62 11 75

Integration Environment 26 4 30

preintegration 12 12 24

Preview 11 3 14

app01 3 4 7

integration02 6 1 7

Devops-Builds 3 3 6

performance environment 5 1 6

Acceptance tests 1 1 2

Grand Total 298 95 397

0

100

200

300

400

500

PI3.1 PI3.2 PI3.3 PI3.4 PI3.5 PI3.6 PI4.1 PI4.3

DevOps Build Metrics

# Success # Failed # Total Builds

Row Labels Sum of # Successful Sum of # Failed Sum of # Total Builds

preint 180 44 227

Infrastructure-Builds 115 26 141

preint02 54 29 85

Integration Environment 73 12 85

integration02 28 14 42

Preview 24 12 36

app01 14 14 28

preintegration 12 12 24

demo-integration 10 3 13

performance environment 8 3 11

Devops-Builds 3 3 6

Acceptance tests 1 1 2

Grand Total 522 173 700

DevOps Engineering – Sprint Metrics: PI 3.5

9

Team Influence Team Control Organizational / External

High Impact Medium Impact Low Impact

Impediments

10

Unplanned In-flow work stream

Start Finishing Stop Starting

CDT Direct Connection Availability

Risks & Issues

ITSM/Change Management Process/Tool

Configuration Management - Low

Off hour Production Support

Identity & Access Management Cost for DevOps

11

What’s Next?

Non-Prod POC Delivery

Automated smoke test for All Apps

Operations Support (Deployments, IDs, Bugs)

12