Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Implementing Continuous Delivery with Chef
Search
Thom May
April 16, 2014
Technology
1
510
Implementing Continuous Delivery with Chef
my #chefconf 2014 presentation
Thom May
April 16, 2014
Tweet
Share
More Decks by Thom May
See All by Thom May
Abusing Databags for Fun and Profit
thommay
1
170
Other Decks in Technology
See All in Technology
BDD(Cucumber)コミュニティが無料提供しているコンテンツの紹介と現在起きている危機
nihonbuson
4
750
技術広報として2023年度に頑張ったこと / What we did well in FY2023 as a DevRel
pauli
5
490
イチから学ぶdbt / Learn dbt from scratch
shinyaa31
0
160
業務で使えるかもしれない…!?GitHub Actions の Tips 集 / CI/CD Test Night #7
ponkio_o
PRO
24
7.3k
10 Years of Kubernetes Patterns Evolution
bibryam
1
100
サービス成長と共に肥大化するモノレポ、長くなるCI時間 / As services grow, monorepos get bigger and CI time gets longer
kohbis
5
2.1k
「XX試験の環境作ってよ」と言われた時によく使うAWSのソリューションについて
bun913
0
120
KubeCon EU 2024 : Knative Maintainers Session
salaboy
0
380
AMLD 2024 - Build Your Own GPT
donlelef
1
260
これまでのキャリアとこれからMLエンジニアとしてどう動くか
masatakashiwagi
1
790
複数の LLM モデルを扱う上で直面した辛みまとめ
kazuyaseki
1
260
Autify Company Deck
autifyhq
1
30k
Featured
See All Featured
jQuery: Nuts, Bolts and Bling
dougneiner
57
7.1k
Agile that works and the tools we love
rasmusluckow
323
20k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
6
950
It's Worth the Effort
3n
180
27k
Designing the Hi-DPI Web
ddemaree
275
33k
Documentation Writing (for coders)
carmenintech
59
3.8k
GitHub's CSS Performance
jonrohan
1023
450k
Designing with Data
zakiwarfel
94
4.8k
Bash Introduction
62gerente
604
210k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
8
8.2k
A Modern Web Designer's Workflow
chriscoyier
689
190k
Navigating Team Friction
lara
177
13k
Transcript
Implementing Continuous Delivery in Chef
Why am I here?
Opinionated
and yet…
Options
@thommay
None
Why Continuous Delivery?
Continuous is a side effect
Consistency
Correctness
Reproducibility
Repeatability
Why Chef?
Availability
Has all the bits we need
Let’s get started
Out of the box
Production quality?
The deploy resource
git clone …
Callbacks
Duplicates work
Reproducible?
Application cookbooks
:(
Assumptions galore
More duplicate work
Slow
Recap
Pipelining
CD can’t work in isolation
Continuous Integration
build once
test what you deploy
Packages
(I don’t care about Windows)
leverage your OS
easy to get a repo up
fpm
but…
atomic
config files
Something Custom
“artiballs”
package-lite
tarball
chef-solo
pretty similar to omnibus
“deployable”
a manifest file
some number of: artifacts
some number of: config file templates
generate resources
Honourable mentions
docker/lmctfy chef-metal decker Flynn ProjectAtomic Mesos/Marathon
Recap
None
baton
https://github.com/digital-science/baton
amqp messaging
not mcollective
build agents trivially
Chef Push Jobs
require on-premise enterprise chef
I don’t have one
looks nifty though
AutoScaling Groups
“a/b” deploys
add new ASG
grow new one
shrink old one
Bamboo
deploy tasks
Recap
Conclusions
Any Questions? Images: Paula Marina - Pipeline! https://flic.kr/p/4V3wLC Kihong Kim
- Orchestra Miniature https://flic.kr/p/dM32mX