why ara is key to devops

15
www.ranger4.co m DevOpstasti c Why ARA is a Key to DevOps Webcast: Helen Beal Mark Roberts

Upload: ranger4-limited

Post on 20-Aug-2015

340 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Why ARA is a Key to DevOps

Webcast:Helen Beal

Mark Roberts

Page 2: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Agenda

1 Why Application Release Automation

2 Demonstration

3 The Ranger4 DevOps Readiness Assessment

Page 3: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

41%experience development

delays

34%experience deployment

delays

45%experience production

delays

4-6weeks

to delivercode

changes

A lack of continuous delivery impacts the entire business

Operations/Production

Development/TestCustomers

BusinessOwners

Costly, error prone manual processes and efforts

to deliver software across an enterprise

CHALLENGES

Upgrade risk due to managing multiple application configurations

and versions across servers

Slow deployment to development and test environments leave teams

waiting and unproductive

Page 4: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Agile Dev

Customers

Desire for fast and continuous innovation

Line of Business

Requirements

Dev & Test Teams

Code & Tests

Operations Team

Business Services

1st Gap

2nd Gap

Addressing BusDev gaps

1. Iterative and Incremental Process2. Traceability

Addressed by...

Page 5: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Customers

Desire for fast and continuous innovation

Line of Business

Requirements

Dev & Test Teams

Code & Tests

Operations Team

Business Services

2nd Gap

DevOps

Addressing Application Lifecycle Management gaps

Page 6: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

With only Agile Development improvements…

Agile Dev

CI builds are piling up

Functional TestingFunctional Testing

Acceptance TestingAcceptance Testing

ProductionProduction

Operator

Setup (weeks)

Install

Test and Ops teams have increased pressures to keep up with increased loads but continue to use waterfall approaches and traditional tools.

Page 7: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Continuous Delivery Adoption Maturity

Common Source Control

Automated Builds (Build Definitions)

Continuous Integration (CI)

Automated Delivery

Continuous Delivery to Test

Continuous Delivery to Production-like Systems

Continuous Delivery through to Production

Page 8: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

IBM UrbanCode Deploy Deployment Automation

Deployment of Applications through Environments

Rapidly deliver to multiple environments for testing

Visibility into deployment status via dashboards

Easily roll back applications due to errors or changes

Compliance via audit trails and security Integrated with existing investments

(Open Source, Tivoli, Cloud, Microsoft, Commerce, Portal)

Versioned Artifacts

QAEnvironment

Production Environment

Development Environment

Artifacts Artifacts Artifacts

Execute Against Execute Against Execute Against

Deploy orRollback

Deploy orRollback

Deploy orRollback

Application Blueprint

Page 9: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

IBM UrbanCode Release Release planning and orchestration

Collaborative release management solution : Replaces error-prone manual

spreadsheets and streamlines release activities

Orchestrate release of multiple applications across multiple environments

Centralized release processes control desk with real-time status

Environments-to-releases allocation

Page 10: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

demonstration

Page 11: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

the ranger4 devops readiness

assessment

Page 12: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

The Goal of the DevOps Readiness Assessment

Aligning business strategy with investment in

software

Through IT process analysis and improvement

• Increase visibility• Monitor and improve

performance• Report on actual

business outcomes

• Assess current state and readiness

• Identify and articulate business impact

• Quantify results

Measurement

Page 13: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

The Assessment Process

1• Identify business drivers and outcomes

2• Assess current state

3• Visualize future desired state

4• Identify potential inhibitors and roadblocks

5• Establish roadmap to adoption

6• Identify trackable metrics

7• Execute and measure

Page 14: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Establish Roadmap to Adoption

GO LIVE

Visi

on o

f Des

ired

Futu

re S

tate

Continuous Delivery

Fit Assessment

Organizational Initiatives

Approved Project Plan

Cultural Initiatives

Base

line

Asse

ssm

ent &

Met

rics

Architectural Imperatives

Process Initiatives

Technology Initiatives

Prio

ritiza

tion

Qua

ntifie

d Va

lue

DevOps Reorganization

Cultural Change Program

Deployment Process Automation

ARA Tools Implementation

Test Process Review

APM Rollout

Service Virtualization

Page 15: Why ARA is Key to DevOps

www.ranger4.com

DevOpstastic

Want to get started on your DevOps journey?Go to:

www.ranger4.com