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.8k
はじめての BQ GAS
hakobera
10
3.6k
MQTT.IO
hakobera
9
1.7k
Logging Technique for HTML5 Single Page Application with Fluentd
hakobera
11
10k
Other Decks in Technology
See All in Technology
バイブコーディングと継続的デプロイメント
nwiizo
2
360
それでも私はContextに値を詰めたい | Go Conference 2025 / go conference 2025 fill context
budougumi0617
4
930
自作LLM Native GORM Pluginで実現する AI Agentバックテスト基盤構築
po3rin
2
210
DEFCON CHV CTF 2025 Write-up
bata_24
0
200
入門 FormObject / An Introduction to FormObject #kaigionrails
expajp
2
1.6k
Goのビルドシステムの変遷 / The history of Go's build system
ymotongpoo
12
3.5k
「技術負債にならない・間違えない」 権限管理の設計と実装
naro143
33
9.8k
KMP の Swift export
kokihirokawa
0
190
生成AIで「お客様の声」を ストーリーに変える 新潮流「Generative ETL」
ishikawa_satoru
1
240
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
9k
stupid jj tricks
indirect
0
7.6k
CData MCP ナイト!「CData × Oracleで実現する新しいデータ活用 ― 国産SaaS 連携から MCP Server for Oracle Database まで」
shisyu_gaku
0
190
Featured
See All Featured
Done Done
chrislema
185
16k
What's in a price? How to price your products and services
michaelherold
246
12k
Rails Girls Zürich Keynote
gr2m
95
14k
Writing Fast Ruby
sferik
629
62k
GraphQLの誤解/rethinking-graphql
sonatard
72
11k
The World Runs on Bad Software
bkeepers
PRO
71
11k
Building Adaptive Systems
keathley
43
2.8k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
140
34k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
114
20k
Java REST API Framework Comparison - PWX 2021
mraible
33
8.8k
Being A Developer After 40
akosma
90
590k
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