30
1 Automation & Release in Federal Julian Fish, Director of Products April 5 th , 2016

Automation and Release in Federal

Embed Size (px)

Citation preview

Page 1: Automation and Release in Federal

1

Automation & Release in Federal

Julian Fish, Director of Products

April 5th, 2016

Page 2: Automation and Release in Federal

2

The Market

DevOps value

Serena added value

Market direction / trends

Agenda

Page 3: Automation and Release in Federal

3

The Hype

http://www.zdnet.com/article/why-2016-is-going-to-be-the-year-of-devops/

http://devops.com/2015/12/22/devops-2016-year-implementation/

Page 4: Automation and Release in Federal

4

What the Analysts Say “ ”

“By 2016, DevOps Will Evolve From a Niche to a Mainstream

Strategy Employed by 25 Percent of Global 2000 Organizations”

“…with the total for DevOps tools reaching $2.3B in 2015 (up

21% yoy)”

“DevOps-ready tools have seen and will continue to see the

largest growth potential”

“Cultural resistance and low levels of process discipline will

create significant failure rates for DevOps initiatives..”http://www.gartner.com/document/2987231.

Page 5: Automation and Release in Federal

5

DevOps – NOT just Release Management

Image: IT Revolution

Page 6: Automation and Release in Federal

6

Purist DevOps

Continuous Delivery

Source Code

ManagementBUILD / CI Deployment / Test Automation

Cloud / Physical/ Virtual /

Container Infrastructure

Dev Ops

Analytics

Infrastructure as Code

Page 7: Automation and Release in Federal

7

Enterprise DevOps

Enterprise Change Management

Source Code

Management

Automation & Provisioning

Containerization Virtual Infrastructure Physical Infrastructure Cloud Infrastructure

Development Test UAT PROD

Agile

Planning &

Dev Task

Planning, Dashboard, Visibility, Integration, Analytics, KPI’s, Measurement

Business Application Development IT Operations

Definition

Business Value

Str

ate

gic

Functio

nal

Technic

al

Feature Validation

Build / CI Deployment Automation / Pipeline Management

Feature Acceptance

Develop, Test, Deploy Release & Deploy

Page 8: Automation and Release in Federal

8

Remember…

DevOps Not = Release Management

DevOps Not = Continuous Delivery

Page 9: Automation and Release in Federal

9

Value to Customers

SPEED

QUALITY

FAILURE

RISK

Page 10: Automation and Release in Federal

10

Value to Customers

Dr. Nicole Forsgren, PhD; Director, Organizational Performance & Analytics

Page 11: Automation and Release in Federal

11

Technology Leadership

Containers

Dimensions

SDA

Automation

Dimensions

SDA

People &

Process

SDA

RLC

SBM

Page 12: Automation and Release in Federal

12

Thought Leadership

Page 13: Automation and Release in Federal

13

Serena and DevOps

Function Description Serena?

Code Code Development and Review, continuous integration tools✅

Build Version control tools, code merging, Build status✅

Test Test and results determine performance

Package Artifact repository, Application pre-deployment staging✅

Release Change management, Release approvals, release automation✅

Configure Infrastructure configuration and management, Infrastructure as Code tools

Monitor Applications performance monitoring, End user experience

Page 14: Automation and Release in Federal

14

DevOps Trends

NOW Feature

✅ Application Automation

✅ Continuous Integration

✅ Continuous Delivery

✅ Full Stack Automation

NEXT Feature

✅ DevOps Pipelines

✅ Containerization & Support

Application Performance Monitoring

✅ Database Automation

Data Center Operating System (DCOS)

Analytics / Big Data

Page 15: Automation and Release in Federal

15

• Shift Left / Shift Right

• Test early in Production representative environments (Service Virtualization)

• Cloud

• Amazon EC2, Azure etc.

• Infrastructure as Code

• Chef, Puppet etc (Infrastructure Configuration Management)

• Continuous Delivery

• Containerization

• Software Defined Data Center (SDDC)

• BiModal IT

DevOps / Release Management BUZZ WORDS

Page 16: Automation and Release in Federal

16

High Level View: Above the Line vs. Below the Line

Release Control

Release Train

Release Package

Tasks

SDA DIM CM ZMF EROOTHER

RELEASE

PROCESS

ARTIFACT

MANAGEMENT

Integration Framework / Service Layer / Widgets

Page 17: Automation and Release in Federal

17

• WHAT

– Manage Release as a business process across

the organization

• WHY

– A platform for Release Innovation not a fixed

point product like competition

– Best in class visualization traceability, metrics

and reporting

– Integrates with Serena and third party Artefact

Repository, Deployment tools and Overall SLC

Ecosystem

• WHO

– Used by Release Managers, Release

Engineers, Environment Managers, QA

Serena Release Control

Page 18: Automation and Release in Federal

18

• WHAT

• Automate deployments to increase release

frequencies, eliminate bottlenecks and/or failure

and reduce cost of deployments

• WHY

• Vendor/technology/platform neutral

• Most secure deployment automation solution

• Best in class visualization, traceability and usability

• WHO

• Operations (deploying apps from dev)

• Developers (deploying apps through to test)

Serena Deployment Automation

Page 19: Automation and Release in Federal

19

Serena Artifact Repository (aka Dimensions Release Vault)

• WHAT

• Single source of truth

• WHY

• Secure, Scalable

• Distributed, Containerized and Mainframe artefacts

• Integrated deployment (SDA)

• WHO

• Operations (Assembling and deploying apps from

Dev)

• Outsourced development

Page 20: Automation and Release in Federal

20

Database Component

Dow nload

Files

Which

Environment?

Load Updates

Delete

Schema

Create

Schema

Load Test

Data

START

FINISH

Web Component

START

FINISH

Dow nload

Files

Which

Environment?

Stop

Application

Deploy

Application

Start

Application

Hot Deploy

Verify URL

SDA: Model Driven Application Deployment

Graphical modelling of activities to automatically install, update, activate and configure an every aspect of an

application reliably and repeatedly throughout all of its environment stages.

Otherw ise

DEV, INTOtherw iseDEV, INT, UAT

Container Component

Pull Container

Configuration

Needed?

Update Prod

Dataset

Update

Container

Deploy

Application

Push

Container

START

FINISH

Otherw iseDEV, INT, UAT

Page 21: Automation and Release in Federal

21

Development

Database Component

Download Fi les

Whic h Env i ronme

nt

Load Updates

Delete Sc hem a

Create Sc hem a

Load Test Data

STA

RT

FIN

ISH

Web ComponentSTA

RT

FINIS

H

Download Fi les

Whic h Env ironmen

t

Stop Appl ic ation

Deploy Appl ic ation

Start Appl ic ation

Hot Deploy

Veri fy URL

Environment Properties

WEB/DB

Resource

Environment Properties

Resource Properties

Test

Database Component

Download Fi les

Whic h Env i ronme

nt

Load Updates

Delete Sc hem a

Create Sc hem a

Load Test Data

STA

RT

FIN

ISH

Web ComponentSTA

RT

FINIS

H

Download Fi les

Whic h Env ironmen

t

Stop Appl ic ation

Deploy Appl ic ation

Start Appl ic ation

Hot Dep loy

Veri fy URL

WEB

Resource

DB

Resource

Environment Properties

Environment Properties

Resource Properties

Resource Properties

Production

Database Component

Download Fi les

Whic h Env i ronme

nt

Load Updates

Delete Sc hem a

Create Sc hem a

Load Test Data

STA

RT

FIN

ISH

Web ComponentSTA

RT

FINIS

H

Download Fi les

Whic h Env ironmen

t

Stop Appl ic ation

Deploy Appl ic ation

Start Appl ic ation

Hot Deploy

Veri fy URL

WEB

Resource

DB

Resource

WEB

Resource

Environment Properties

Environment Properties

Resource Properties

Resource Properties

Resource Properties

Model Driven Application Deployment Example

Docker Container

Page 22: Automation and Release in Federal

22

App ServerContainers

Trusted

Registry

Configuration

List, search,

push, pull

images

Apply system

configuration

Deployment Automation Server uses plugin to interact with Docker System (http / JMS via agent)

Docker used to container

management. External data

persistency required

SDA – Containers and Automation

Page 23: Automation and Release in Federal

23

SDA / Docker Integration Steps

Page 24: Automation and Release in Federal

24

How Containers work

• Containers are isolated environments that

are created from docker images.

• All the layers in an image are read-only

except the topmost layer which is called a

container.

• You can commit the changes made to a

container and make a new image out of it.

• If specific images are not present in the

host, docker will download it from the

docker hub

Image Taken from docs.docker.com

Page 25: Automation and Release in Federal

25

How Microservices Work

http://martinfowler.com/articles/microservices.html

Page 26: Automation and Release in Federal

26

Containers – not just docker!

Page 27: Automation and Release in Federal

27

Do they work?

Google, deals with more than two billion containers per

week. That’s a lot of containers to manage. Popular

Google services such as Gmail, Search, Apps and Maps

run inside containers.

Page 28: Automation and Release in Federal

28

Why would customers use containers

++ ENVIRONMENTS

CONSISTENCY

SIMPLICITY

SECURITY

ARCHITECTURE

EXISTING INVESTMENT

“Containers are faster, more efficient and easier to manage than Virtual Environments.”

Page 29: Automation and Release in Federal

29

Page 30: Automation and Release in Federal

30

Thank You!