This document provides an overview of Spinnaker, an open source tool for continuous delivery. It discusses the traditional software delivery lifecycle and issues with manual processes. Continuous delivery is presented as a better approach using automation to deliver software frequently with automated testing and feedback. Spinnaker is introduced as a tool that provides features like pipelines, cloud drivers, and image deployments to help enable continuous delivery. The document demonstrates Spinnaker's capabilities through a multi-cloud deployment demo.

1. MAKE NEXT POSSIBLE Ⓡ
Making Continuous Delivery Easy with Spinnaker
Nicholas Eden-Walker, Kenzan

2. ● Delivering Software
(old way)
● Continuous Delivery
● Spinnaker
● Spinnaker Demo
OVERVIEW
What We’ll
Cover

3. ● Developers produce
builds
● Pitching over walls
starts
DELIVERING SOFTWARE
Traditional
Lifecycle

4. Pitching over walls
4

5. 5

6. 6

7. ● Environments maintained
manually
● Manual testing / weak feedback
● High effort for deployments
● Long lead times
● Big breakage
● Lack the strength
● Do it less often
DELIVERING SOFTWARE
Troubles with
manual delivery

8. ● Continuous Integration
○ Test integrations
● Continuous Delivery
○ Deliver to a higher env
● Continuous Deployment
○ Deliver through all envs to prod
DELIVERING SOFTWARE
Continuous *

9. ● Simple rule: Always
be ready for prod
● Business decides
when to push
CONTINUOUS DELIVERY
Finding a
Better Way

10. 10

11. ● Automate all the things!
(Build, Test, Deploy)
● Do less more frequently
● Increase feedback
● Reduce defects
CONTINUOUS DELIVERY
Goals for CD

12. CONTINUOUS DELIVERY - Continuous Feedback
12

13. CONTINUOUS DELIVERY
Seems like DevOps?
● A tool for DevOps
● DevOps is much more (culture vs
tech)

14. CONTINUOUS DELIVERY
GETTING TO CD
Doing that
automation
is tough
Tools can
seem a
lot like
duct tape
Little
integration
with cloud

15. Cloud Native
Continuous
Delivery

16. ● Asgard - Kitchen sink
AWS console with
deployments
● Mimir - scripting and
workflow system
● Spinnaker - Continuous
delivery for cloud - Full
OSS project
Origins of
Spinnaker

17. OSS &
COMMUNITY
● Netflix set out to work with partners
○ Google
○ Microsoft
○ Pivotal
○ Kenzan
● Community engagement
○ Slack
○ Github, spinnaker.io, stackoverflow

18. FEATURES
● Pipelines
● Event Driven
● Cloud Drivers
● Image Deployments
● API First
● HTML5 UI

19. STRUCTURE
● Microservices system
● Orchestration / Workflow
● Gate security proxy

20. Sorry about this, some say this is hard
to unsee...
20

21. 21

22. Spinnaker Structure - Microservices
22

23. ● Multi-stage Pipelines
● Many types of stages
● Use Jenkins for arbitrary
actions
● Spring expression language
● Event driven
● Chat integration
Spinnaker Features
Pipeline
Events

24. ● Bakery service for
building images
(packer as a service)
● Low configuration drift
Spinnaker Features
Image
Deployments

25. ● Several providers across
public, hybrid, container
● Abstraction where
appropriate
● Many deployment
strategies
Spinnaker Features
Cloud
Drivers

26. 26

27. That’s from the movie Highlander if you
didn’t know… and isn’t it “There can be
only one”?
27

28. ● UI is modern HTML5
client
● Rest APIs ease
automation &
integration
Spinnaker Features
HTML 5
& API
First

29. Spinnaker Features
How does
all this
help?
PIPELINES
○ Capture repeatable processes
○ Provide place for automated testing
○ Allow tighter feedback loops
IMAGE DEPLOYMENTS
○ Automate environments
○ Treat infrastructure as cattle
VISIBILITY

30. ● Professional Services
● Cloud consulting
● Front & Back-end
development
● Joined Spinnaker project
2015
● Contributed installation tools,
docs
● Created spinnaker-terraform
project
Spinnaker & Kenzan
Who is
Kenzan?

31. github.com/kenzanlabs/spinnak
er-terraform
● Everything you need for
Spinnaker CD
● Jenkins, artifact repo
● Spinnaker
● App
● Jobs + pipelines
Getting Started
Using
Terraform to
Bootstrap

32. ● Advanced CD Pipeline with
● Dev -> QA -> Prod
● Multi-cloud
○ Dev on Kubernetes
○ QA & Prod on AWS
● Automated testing stages
Demo Time
Multi-cloud
Deployments

33. @JinpaLhawang
@kenzanmedia
www.kenzan.com
techblog.kenzan.com
github.com/kenzanlabs
Thank you!