part 3: enabling continuous delivery (pivotal cloud platform roadshow)

1 © Copyright 2013 Pivotal. All rights reserved. 1 © Copyright 2014 Pivotal. All rights reserved.

Pivotal Cloud Platform Deep Dive

Part 3: Enabling Continuous Delivery

Pivotal CF Team

© Copyright 2014 Pivotal. All rights reserved.

Before we get started…

2


Setup Prerequisites•CloudBees Account (Jenkins)

http://grandcentral.cloudbees.com

• JFrog Artifactory Online Accounthttps://www.jfrog.com/registration/registration.html

3


CloudBees

4


Artifactory Online

11


Enabling Continuous Delivery• Setup Prerequisites

• Continuous Delivery Overview

• How Cloud Foundry Enables Continuous Delivery

• Lab: Setup a CD Pipeline with Jenkins, Artifactory, CF Client, and PWS

19

Meet Henry (Our Business Owner)

20

Meet Henry

He needs an app built in the next 8 weeks He knows what the app should do

He expects competitors to try to beat us to market

21

Meet Jane (Our App Architect)

22

Meet Jane

Jane is a little worried: Not everyone understands agile here Environment setup takes a long time

8 Weeks isn’t much time to get a release to production (!)

23

Continuous Delivery To The Rescue!

24

Continuous Deployment

25

Github: On August 23, 2012 – 563 builds and 175 deploys

github.com/blog/1241-deploying-at-github

Continuous Delivery != Continuous Deployment

26

Continuous Delivery != Continuous Deployment

27 twitter.com/ccaum/statuses/372620989257232384

The Difference: !

Who Presses The Button For A Production Deployment?

28

What Could Get In Jane’s Way?

29

Cycle Time

www.flickr.com/photos/nnova/339990495330

How Long Does It Take To Deploy One Line Of Code To Production?

Silos

www.flickr.com/photos/denimdave/633422442831

… But We Have A DevOps Team!

Process

www.flickr.com/photos/kevgilmour/484305133132

You Need To Open A Ticket For That!

Feedback Loop

www.flickr.com/photos/tenspeedphotography/545045678333

Are We Building The Right Thing?

34

ChangeProduction Breaks When Changes Are Made (!)

… Right?

Jane Needs Some Help (This Seems Insurmountable)

35

Strategies For Success

36


Do Implement Continuous Integration

37


Do Not Create Environment Specific Packages

38


Do Externalize Environment Specific Configuration

39

|


Do Automate Everything

40


Do Not Assume Existing Processes Are Right (Engage In Continuous Improvement)

41


Do Not Use A Different Process For Different Environments

42


Do Recreate App Environments Frequently (Also Known As: Servers Are Not Puppies)

43


Do Ensure Database Changes Are Automated

44


Do Deploy Less More Frequently !

45

v2.1

v2.1

v2.3

v2.2


Do Automate All Testing Where Test Failures Would Prevent A Production Release From

Occurring !

46

|


Do Try To Use Tools That Support The Process (But Don’t Get Stuck In Tool Selection Hell!)

47

g






48

Cloud Foundry Helps Jane…

49


Get A New App Environment In Seconds

50

in a


Have Complete Consistency Between Environments

51


Have A Consistent API To Automate Deployments

52


Inject Environment Specific Configuration

53


Inject External Dependencies

54

55

Promote Apps Through Environments With The Same Process

!



By Providing New Options: + Canary Deployment

+ Zero Downtime Deployment + A/B Testing

+ Scale Apps On-Demand

56

App Developers Can Be More Successful When They Are Supported

By Agile Infrastructure

57






58


Lab• Follow the instructions found at https://github.com/cf-

platform-eng/cf-workshop-cd-module using your:

• Pivotal Web Services Account

•CloudBees Account

•Artifactory Online Account

59






60


Coming Up•Break (4:00 - 4:15)

• Part Four (4:15 - 5:30)

• Learn CF Extension Points

•Customize a Buildpack -OR-

•Write and Deploy a Service Broker

61

A NEW PLATFORM FOR A NEW ERA

part 3: enabling continuous delivery (pivotal cloud platform roadshow)

Software

pws copyright

cloud foundry

continuous delivery

started copyright

continuous improvement41

continuous integration37

continuous deployment26

continuous deployment25github