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
Quipper on Containers
Search
Kazuyuki Honda
September 21, 2016
Technology
0
1.2k
Quipper on Containers
2016/09/21 JAWS UG コンテナ支部 #6
Kazuyuki Honda
September 21, 2016
Tweet
Share
More Decks by Kazuyuki Honda
See All by Kazuyuki Honda
How to Write Complex Data Pipeline in Ruby
hakobera
2
4.6k
はじめての BQ GAS
hakobera
10
3.5k
MQTT.IO
hakobera
9
1.6k
Logging Technique for HTML5 Single Page Application with Fluentd
hakobera
11
10k
Other Decks in Technology
See All in Technology
コンピュータビジョンの社会実装について考えていたらゲームを作っていた話
takmin
1
600
JavaにおけるNull非許容性
skrb
2
2.6k
あなたが人生で成功するための5つの普遍的法則 #jawsug #jawsdays2025 / 20250301 HEROZ
yoshidashingo
2
290
技術スタックだけじゃない、業務ドメイン知識のオンボーディングも同じくらいの量が必要な話
niftycorp
PRO
0
100
生成AI×財務経理:PoCで挑むSlack AI Bot開発と現場巻き込みのリアル
pohdccoe
1
720
Potential EM 制度を始めた理由、そして2年後にやめた理由 - EMConf JP 2025
hoyo
2
2.6k
OCI Success Journey OCIの何が評価されてる?疑問に答える事例セミナー(2025年2月実施)
oracle4engineer
PRO
2
150
偏光画像処理ライブラリを作った話
elerac
1
170
AWSを活用したIoTにおけるセキュリティ対策のご紹介
kwskyk
0
350
NFV基盤のOpenStack更新 ~9世代バージョンアップへの挑戦~
vtj
0
350
ディスプレイ広告(Yahoo!広告・LINE広告)におけるバックエンド開発
lycorptech_jp
PRO
0
360
エンジニアリング価値を黒字化する バリューベース戦略を用いた 技術戦略策定の道のり
kzkmaeda
6
2.7k
Featured
See All Featured
BBQ
matthewcrist
87
9.5k
The Language of Interfaces
destraynor
156
24k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
129
19k
Reflections from 52 weeks, 52 projects
jeffersonlam
348
20k
Raft: Consensus for Rubyists
vanstee
137
6.8k
How to Ace a Technical Interview
jacobian
276
23k
Designing Experiences People Love
moore
140
23k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Being A Developer After 40
akosma
89
590k
For a Future-Friendly Web
brad_frost
176
9.6k
Testing 201, or: Great Expectations
jmmastey
42
7.2k
Designing for Performance
lara
604
68k
Transcript
on Containers )
@hakobera DevOps Engineer
None
Mexico City London Tokyo Manila Jakarta Sales team only Sales
and dev team International Offices No one here (yet).
Products
Container != Docker
Docker is one of the container impls. Ubuntu LXD Microsoft®
Windows® Server Container Hyper-V® Container
When do you use container on your system?
Now!
Why do you use container?
Portability and Beyond Your Cloud Limits
Docker on Elastic Beanstalk • For short batch using worker
tier • Avoid darkness of .ebextension • Avoid Amazon Linux ◦ We want to use Ubuntu
Load Test on Elastic Container Service • Easy to setup
locust cluster ◦ Consists of 2 Tasks ▪ 1 master ▪ Multiple slave ◦ Manage instances using Spot Fleet ▪ Cheap but scalable
nginx-build on CircleCI • Easy to build custom nginx build
◦ Bundle custom modules such as ngx_mruby ◦ Patch for security issue ▪ Update only openssl but not nginx
Ansible playbook test on CircleCI • Run playbook to clean
environment • Run playboot test in parallel
Do you also use container for Web application?
Yes! But it’s not so easy
History of Quipper and Container
Quipper is Container Native Company
Quipper use container from beginning
Back to 2012 First Product First Container is ...
None
It’s too early
No source repository Only CTO only knows
From 2013 Second Container Choice is ...
None
Heroku is great!
Awesome features of Heroku • Deploy via git • Buildpack
• Multiple Dyno Size • One-off dyno • Review Apps
At April, 2015 We are acquired by Recruit Co. Ltd
What problem do we have to resolve? • Performance ◦
Latency from Japan and USA (400ms/req) ◦ Needed more powerful dyno • Security ◦ At least we need fixed outbound IP address • Cost
We want to keep awesome features • Deploy using git
from CircleCI • Buildpack • Multiple Dyno Size • One-off dyno • CLI compatibility
None
Your PaaS, Your Rules Open Source Application Platform
Similarity to Heroku • Deploy via git • Buildpack •
CLI sub command ◦ Ex: heroku conifg:set <-> deis config:set • Interactive console not yet supported ◦ Create own tool using Docker API
Similarity to Heroku is important Because we’re deploying one source
Source: http://docs.deis.io/en/latest/understanding_deis/architecture/
None
None
None
Components of PaaS for Web app • Router • Controller
• Slug Builder • Container Registry • Object Storage • Scheduler • Key Value Store • Database • Git Repository • Logger
Where is the best place to deploy each component?
Late 2015
Elastic Load Balancing Router Controller Builder Applications etcd AZ #1
AZ #2 Production Cluster 1st Gen. PosggreSQL On Amazon RDS Docker Registry On Amazon S3
Hard to Scale Out
April 2016
Elastic Load Balancing Router/Applications AZ #1 AZ #2 Controller /Builder
etcd Production Cluster 2nd Gen. PosggreSQL On Amazon RDS Docker Registry On Amazon S3
Noisy Neighbor AND Cost Increase
Fleet is too simple • Fleet is not resource aware
scheduler • Fleet deploy new container in instance which has the least containers • Sometimes make it unbalanced workload of clusters
Bad scheduling of fleet High High Normal Low Low Low
Instance 1 Instance 2 Instance 3
We hope resource aware scheduling High High Normal Low Low
Instance 1 Instance 2 Instance 3 Low
Aug 2016 〜
Elastic Load Balancing Router/Apps (Shared) AZ #1 AZ #2 Controller
/Builder High-Load Apps (Dedicated) etcd Production Cluster 3rd Gen PosggreSQL On Amazon RDS Docker Registry On Amazon S3
Tag based Deployment High HighI Normal Low Low Low high=false
high=true
Tag based Deployment • Tag = Fleet metadata • Set
fleet metadata by cloud-init #cloud-config Coreos: ... fleet: public-ip: $private_ipv4 metadata: dataPlane=true,high=true #cloud-config Coreos: ... fleet: public-ip: $private_ipv4 metadata: dataPlane=true,routerMesh=true,high=false For dedicated For shared
Elastic Load Balancing Router AZ #1 AZ #2 Controller /Builder
Applications etcd Staging Cluster PosggreSQL On Amazon RDS Docker Registry On Amazon S3
Other Awesome Features
Blue Green Deployment 1. Start new containers 2. Notify to
etcd 3. Update nginx.conf by confd 4. Reload router (nginx) 5. Update routing 6. Destroy old containers
Use nginx as reverse proxy for PaaS • Easy to
handle naked domain • Resolve slow client issue • Can support HTTP/2 • Flexible routing ◦ A/B test, 10% release, etc ...
Problem as of now
Fleet is too simple (again) • Fleet is not resource
aware scheduler • Fleet deploy new container in instance which has the least containers • Sometimes make it unbalanced workload of clusters
etcd stability • etcd sometimes get high CPU load
In the future ...
Deis Workflow (Deis v2) • https://github.com/deis/workflow • Based on Kubernates
End
We’re hiring! https://www.quipper.com/career/Japan/ https://www.wantedly.com/companies/quipper