continuous delivery seminars - cloudbees · • one of the first agile transformations ever...

Post on 09-Jun-2020

1 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

cdSummitContinuous Delivery Seminars

Automation & Continuous Delivery : Lessons from the front line24th June 2014

Agenda

• Looking back

• Goals

• Automation

• 5 C’s

• Putting it all together

• Where next ?

A bit about me…

• VP Marketing

• Worked in and around the software industry since 1988

• Worked for large enterprises and silicon valley startupsand ran a mobile / telecoms for many years

• It does appears Tech is cool ….was it ever not ?

• There was life….before DevOps

Can we ignore what’s going in Brazil...

34

3434

34

3

2 1

World Cup 2014Who should MidVision Support?

ARG

ENG

GER

ESP

USA

SKO

SWI

Spain

England

Argentina

Germany

Looking back…

Agile, Lean, Continuous

Integration….

I

9. IBM WAS ND 8.5.5.1 Liberty Profile(EGB Container & Extended Model)

10. IBM WAS ND 8.5.5.1 Liberty Profile(EGB Container)

11. IBM WAS ND 8.5.5.1 Liberty Profile(Extended Model)

12. IBM WMB 8.0.0.1

13. IBM WMQ 7.5.0.0

WAS Base

8.5.5.1 x64

WAS ND

8.5.5.1 x64

WAS NDLP

8.5.5.1 x64

WMB

8.5.5.1 x64

WMQ

7.5.0 x64

Barclays fears

tech firms could

replace banksby Tim Wallace

June 11, 2014, 2:48am

BANKS must continue to

invest in new technologies

and customer service if they

want to avoid being replaced

by firms such as PayPal and

Amazon, Barclays’ boss,

Antony Jenkins said

yesterday.

If you think compliance is expensive,

try non-complianceFormer US Deputy Attorney General, Paul McNulty

How to achieve your goalsWhat you must, should, could & won’t do to score high

II

Problem Statement

17

• IT has been automating business processes for years: ironically – it is yet to focus on

its own operations

• Pressure for faster innovation, SMAC and Agile initiatives, are driving increased pace

of IT change

• Through 2015, Gartner predict 80% of outages impacting mission-critical services will

be caused by people and process issues

• The Challenge: to increase the throughput of IT change; in a more reliable manor; at a

lower cost.

A Software Manufacturing Pipeline

Continuous Delivery

DEVELOPMENT QA STAGING PRODUCTION

DEVELOPMENT DEPLOYMENT TESTING

PR

OD

UC

T

DevOps, Continuous Delivery and Automation

DevOps

(Philosophy)

Continuous Delivery

(Practice)

Application Release Automation (ARA)(Tools)

Application Release Automationa.k.a. Deployment Automation

“The process of packaging and deploying an

application or update of an application from

development, across various environments,

and ultimately to production”

What is Continuous Delivery?

“Our highest priority is to satisfy the customer through

early and continuous delivery of valuable software.”

• The first principle of the agile manifesto.

• The logical extension of continuous integration.

• A holistic approach to development.

• Every commit creates a release candidate.

• Finished means released into production!

Why Continuous Delivery?

• Because software lifecycles are (typically) ....

– Slow

– Inflexible

– Expose risk late

– High cost

Lean Thinking

• Deliver Fast

• Build Quality in

• Optimise the Whole

• Eliminate Waste

• Amplify Learning

• Decide Late

• Empower the Team

Even SAP…Continuous Delivery?

Continuous Delivery ….Goals

• Reduce Cycle Time

• Reduce Inventory &

Obsolescence

• Reduce Risk & fear of change

• Fast Feedback

• Increase Agility

The Principles of Continuous Delivery

• Create a repeatable, reliable process for releasing software.

• Automate almost everything.

• Keep everything under version control.

• If it hurts, do it more often – bring the pain forward.

• Build quality in.

• Done means released.

• Everybody is responsible for the release process.

• Improve continuously….

Couple of questions….

• How long would it take your organisation today to deploy

a change that involved just one single line of code?

• Do you do this in a repeatable, reliable manner?

What’s the consensus….?

Minutes, Hours, Days, Weeks or Months

Must do’s ….

• Deployment Pipeline

• Repeatable and Reliable

• Small changes reduce risk

• Fast Feedback

• Reduces Inventory & Obsolescence

Continuous Delivery ….e2e Pipeline

• Continuous Integration

• Automated Unit Testing

• Artifact creation

• Automated Acceptance testing /

Approval

• Automated Deployment

Should do’s….

• Shift to SOA

• Have Build AND Deploy AND

Test Automation

• Create an Automated

dependancy chain

• Focus on your Technical Debt

Should and Could do’s….

• Focus on Culture, Small Product teams

• Move Dev teams closer to “customer”

• Actively combat “blame” culture,

encourage self-improvement

• Promote retrospectives across company

• Visualise all tasks, radiate and amplify

metrics

Won’t do’s….

• Don’t give up

• The journey is hard but the

payback is huge

• Think it will be done in a few

weeks

Where are you now?....Quicksand ?

• Monolithic App ?

• Shared and Interconnected Dependancies ?

• Spend all your time fixing bugs

• You need to “slow down” …. Assess the situation

Outcomes….and benefits

• Focused Apps AND Teams

• Single Button deployments

• Rollback procedures

• Blue/Green Deployments

• Delivery certainty increases

• For example…we see….rules develop

– No releases after 4pm and on a Friday

AutomationAutomate your tool chainempower your team

III

What are your needs and wants

Faster(Acceleration)

We automate processes carried out by IT

Faster deployments through whole lifecycle

Bring products to market quicker

Safer (Lower Operational Risk)

Eliminate outages

Workflow-scheduling

Audit & compliance controls

Cheaper(Reduce TCO)

More resource time for value-creation

Why outsource when you can automate

How do you release more, more often, for less ?

Automated Deployment Principles

• Version control and build configuration

• Release versions of configuration change in the

same way as code

• Allows linking of configuration releases and

application releases – together comprising a

business application

• “Build Once, Deploy Anywhere”

37

Model Driven Deployment

• Leverage templates created that define

infrastructure and/or application configuration

• Leverage templates that are environment neutral

and usually stored in the target platform format (i.e.

py, ddl, mqsc, etc.)

• Always contain the complete configuration for a

target technology

• Deltas become part of the template – so

configuration changes are not made in isolation

UK Bank with 25 million customers

• Achieved a 533% productivity improvement when deploying

their IBM WebSphere estate (one of the largest in Europe)

• Reduced application build time from 4 hours to 14 minutes

• Saved 100 man days in a 4 week project

Global Life Sciences

• Achieved a 40% reduction in manual tasks through move to Automation

• Enabled the transition to a next generation architecture and way of processing all financial, supply chain transactions (inc SAP and Non SAP applications) in a

$Multi-Billion operating business

• Steps in the process were absolutely transformed e.g. 4 hours to less than 15 minutes (including verification)

• Velocity of change is now 200-300% faster – Automation was key

North American Healthcare

• Enabled a Service Catalog for PAAS on demand.

• Lead time moved from 12 weeks to 1.5 hours maximum

• Consistent, reliable process managing over 20,000 Servers.

• Provisioning Environments ANDApplications is now a reality

UK Government

• One of the first Agile transformations ever delivered in Public Sector

• Release Lifecycle was taken from 6 days to 6 hours !!!

• Programme Manager said he had NEVERexperienced a project which had delivered 50% of budget, ahead of time and more scope than originally envisaged

• It worked out at being an 829% improvement in their Release Cycle time

What could be your story with Automation?

Faster(Acceleration)

We automate processes carried out by IT

Faster deployments through whole lifecycle

Bring products to market quicker

Safer (Lower Operational Risk)

Eliminate outages

Workflow-scheduling

Audit & compliance controls

Cheaper(Reduce TCO)

More resource time for value-creation

Why outsource when you can automate

Continuous Delivery through the 5 C’s

Delivery is the goal enabled by good foundations

IV

Do we agree ?

Much more

important ?

5 C’s…we believe that

• Continuous Delivery is underpinned by

– Continuous Integration

– Continuous Deployment

– Continuous Testing

– Continuous Approval or Rollback

– Continuous Monitoring

Putting it all together

V

Key Takeaways• Take a bird’s eye view of your e2e process – Value Stream Map

• Identify your “quick wins” to build stakeholder confidence

• Look for Automation opportunities – retire manual dependancies

• Analyse, review and decide on the “right tools to do the job”

Where next ?To achieve your Automation, Continuous Delivery and DevOps Goals ?

VI

Gartner think’s we’re cool

• Born in a Bank – regulation, risk and compliance

• Application Release Automation Platform, RapidDeploy deploy

environments AND applications at scale

• Cross industry customer success – proven in large complex

regulated enterprises

• Core Platform – with ability to integrate to Open Source and

Commercial tool chains

• Gartner DevOps Cool Vendor

Successes

A DevOps Engineer?

A DevOps Team?

A DevOps Solution?

But if in doubt...

Or you could…

But whatever you do…make sure you…

All I can say now is….

cdSummitContinuous Delivery Seminars

Automation & Continuous Delivery : Lessons from the front line24th June 2014

top related