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
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Thom May
April 16, 2014
Technology
540
1
Share
Implementing Continuous Delivery with Chef
my #chefconf 2014 presentation
Thom May
April 16, 2014
More Decks by Thom May
See All by Thom May
Abusing Databags for Fun and Profit
thommay
1
180
Other Decks in Technology
See All in Technology
ブラックボックス化したMLシステムのVertex AI移行 / mlops_community_62
visional_engineering_and_design
1
270
15年メンテしてきたdotfilesから開発トレンドを振り返る 2011 - 2026
giginet
PRO
2
270
OPENLOGI Company Profile for engineer
hr01
1
62k
CloudFrontのHost Header転送設定でパケットの中身はどう変わるのか?
nagisa53
1
250
バックオフィスPJのPjMをコーポレートITが担うとうまくいく3つの理由
yueda256
1
230
最大のアウトプット術は問題を作ること
ryoaccount
0
280
やさしいとこから始めるGitHubリポジトリのセキュリティ
tsubakimoto_s
3
2.1k
The essence of decision-making lies in primary data
kaminashi
0
240
不確実性と戦いながら見積もりを作成するプロセス/mitsumori-process
hirodragon112
1
180
Microsoft Fabricで考える非構造データのAI活用
ryomaru0825
0
630
Cursor Subagentsはいいぞ
yug1224
2
140
自分をひらくと次のチャレンジの敷居が下がる
sudoakiy
5
1.7k
Featured
See All Featured
Build your cross-platform service in a week with App Engine
jlugia
234
18k
B2B Lead Gen: Tactics, Traps & Triumph
marketingsoph
0
95
Side Projects
sachag
455
43k
Stop Working from a Prison Cell
hatefulcrawdad
274
21k
Git: the NoSQL Database
bkeepers
PRO
432
67k
Raft: Consensus for Rubyists
vanstee
141
7.4k
Marketing to machines
jonoalderson
1
5.1k
Leadership Guide Workshop - DevTernity 2021
reverentgeek
1
260
Automating Front-end Workflow
addyosmani
1370
200k
Scaling GitHub
holman
464
140k
GitHub's CSS Performance
jonrohan
1032
470k
Design in an AI World
tapps
0
190
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