A DevOps Pipeline - BuildStuff Ukraine 2016

@steveElsewhere PIPELINE A DEVOPS @steveElsewhere

@steveElsewhere ME

@steveElsewhere CONTEXT VALUE

@steveElsewhere WHY DO WE NEED A PIPELINE?

@steveElsewhere CREATING VALUE WHY WOULD WE SHIP 100 TIMES A
DAY?

@steveElsewhere ITERATION

@steveElsewhere PIPELINE SO, ABOUT THAT @steveElsewhere

@steveElsewhere ‣ NATURAL START AND END ‣ STARTS WITH SOURCE
CONTROL ‣ INITIATE WITH EACH CHANGE ‣ RUN IN PARALLEL AND/OR SEQUENTIALLY ‣ SUCCESS MEANS CODE IN PRODUCTION PIPELINE CHARACTERISTICS

@steveElsewhere CONTINUOUS DELIVERY CHANGE STABILIZE VALIDATE RELEASE

@steveElsewhere PROCESS CODE TEST BUILD DEPLOY RUN

@steveElsewhere STAGES OF MATURITY DEPLOY DIRECTLY/TEST CONTINUOUS INTEGRATION CONTINUOUS DELIVERY
CONTINUOUS DEPLOYMENT

@steveElsewhere IMPORTANT? WHY IS IT @steveElsewhere

@steveElsewhere THE WALL @steveElsewhere

@steveElsewhere DOCKER LETS TALK ABOUT

@steveElsewhere CAVEATS LETS TALK ABOUT

@steveElsewhere

@steveElsewhere ADVANTAGES LETS TALK ABOUT

@steveElsewhere LIGHT WEIGHT REUSE CONSISTENCY WHY DOCKER? PUSH/PULL VERSIONING PORTABILITY

@steveElsewhere 1. TRIGGER 2. RUN UNIT TESTS 3. BUILD THE
IMAGE THAT WE USE TO BUILD OUR APP 4. RUN THE BUILD CONTAINER AND COMPILING OUR APP 5. BUILD THE IMAGE THAT WE RUN AND DEPLOY 6. PUSH THE FINAL IMAGE TO A DOCKER REGISTRY 7. (TRIGGER) 8. PULL AND RUN OVERVIEW

@steveElsewhere SOME  PREREQUISITES

@steveElsewhere PROVISIONING AND CONFIG

@steveElsewhere LERN YOU SOME CONTAINER TYPES

@steveElsewhere BASE VOLUME BUILD RUN CONTAINER TYPES

@steveElsewhere OS SOURCE REPOS PACKAGES CLEANUP THE BASE CONTAINER

@steveElsewhere MINIMAL BARE OS FILE TOOLING FILES THE VOLUME CONTAINER

@steveElsewhere THE BUILD CONTAINER BASE CONTAINER CODE COPY COMPILE CLEANUP

@steveElsewhere BUILT CONTAINER RUN COMMAND THE RUN CONTAINER

@steveElsewhere CASCADE CHANGE CHANGE BASE REBUILD BUILD REBUILD BASE REBUILD
RUN RUN

@steveElsewhere QUALITY ASSURANCE

@steveElsewhere BEYOND BASICS

@steveElsewhere QUALITY ASSURANCE CODE COMMIT TEST ENV PRODUCTION

@steveElsewhere QUALITY ASSURANCE LOCAL Unit Mock COMMIT/CI Regression Cross-Device Functional
Static Analysis Integration TEST ENV Exploratory Acceptance Performance Smoke Security PROD Smoke A / B

@steveElsewhere QUALITY ASSURANCE

@steveElsewhere CI ONSITE ‣ JENKINS ‣ GITLAB CI ‣ GO.CD
‣ STRIDER ‣ TEAM FOUNDATION SERVER

@steveElsewhere CI ONLINE ‣ SHIPPABLE ‣ CODESHIP ‣ CIRCLE CI
‣ TRAVIS ‣ APPVEYOR

@steveElsewhere BUILD ‣ DOCKER (LOCAL) ‣ PACKER (LOCAL) ‣ DOCKER
HUB ‣ QUAY.IO ‣ ANY CI TOOL

@steveElsewhere DEPLOYMENT PULL FROM HUB CONFIG MANAGEMENT RUN

@steveElsewhere THE #! CODE CHANGE PUSH TRIGGER TEST PULL TRIGGER

@steveElsewhere THE #! PULL TRIGGER CODE CHANGE PUSH TRIGGER TEST

@steveElsewhere WHERE WE GO FROM HERE

@steveElsewhere MEASUREMENT ‣ CYCLE TIME (MTTR) ‣ ITS OK TO
ADD TESTS ‣ FAILURE RATE ‣ TEST TYPE COVERAGE ‣ CONFIG COVERAGE ‣ MANUAL EDGES

@steveElsewhere VALUE STREAM MAP

@steveElsewhere AUTOMATION

@steveElsewhere THE BOTS AGE OF

@steveElsewhere COLLABO- TOMATION CHATOPS

@steveElsewhere VISIBILITY CHATOPS

@steveElsewhere MY ADVICE

@steveElsewhere THE EDGES THINK ABOUT

@steveElsewhere SCHEDULING STORAGE SERVICE - DISCOVERY OTHER CONSIDERATIONS: LOGGING MONITORING
NETWORKING

@steveElsewhere HEALTHCHECK ROLLBACK GRACEFUL FAILURE OTHER CONSIDERATIONS: SECRETS SCALING CRON

@steveElsewhere CHANGE AS LITTLE AS POSSIBLE GO CRAZY.

@steveElsewhere SPECIFICS AIM FOR

@steveElsewhere THINK ABOUT SECURITY

@steveElsewhere START NOW

@steveElsewhere THE STACK STATFLO.COM CONVOX

@steveElsewhere CIRCLE

@steveElsewhere --- MACHINE: SERVICES: - DOCKER DEPENDENCIES: PRE: - DOCKER
PULL FEBUILD - PIP INSTALL --UPGRADE AWSCLI TEST: OVERRIDE: - 'MAKE VERIFICATION-ISOLATION' DEPLOYMENT: PRODUCTION: BRANCH: MASTER COMMANDS: - $(AWS ECR GET-LOGIN) - MAKE JS CSS BUNDLE-LEGACY - MAKE META - ./CONVOX LOGIN CONSOLE.CONVOX.COM - ./CONVOX SWITCH STATFLO/PROD - ./CONVOX DEPLOY --WAIT CIRCLE.YML

@steveElsewhere 1. TRIGGER 2. RUN UNIT TESTS 3. BUILD THE
IMAGE THAT WE USE TO BUILD OUR APP 4. RUN THE BUILD CONTAINER AND COMPILING OUR APP 5. BUILD THE IMAGE THAT WE RUN AND DEPLOY 6. PUSH THE FINAL IMAGE TO A DOCKER REGISTRY 7. (TRIGGER) 8. PULL AND RUN OVERVIEW AS CI PIPELINE

@steveElsewhere PIPELINE: STATFLO.COM - REUSABLE CONTAINERS - AUTOMATED TESTS -
CONSTANT DEPLOYMENT [email protected]

@steveElsewhere CONTINUOUS AWESOME STATFLO.COM [email protected]

@steveElsewhere WE’RE HIRING! STATFLO.COM [email protected]

@steveElsewhere WE’RE HIRING! STATFLO.COM - DATA - PYTHON - AWS
[email protected]

@steveElsewhere ДЯКУЮ J.MP/TALKRESOURCES

A DevOps Pipeline - BuildStuff Ukraine 2016

A DevOps Pipeline - BuildStuff Ukraine 2016

More Decks by Steve Pereira

Other Decks in Technology

Featured

Transcript