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
CoreOS Overview @ LinuxCon US 2014
Search
Brandon Philips
August 28, 2014
Technology
7
650
CoreOS Overview @ LinuxCon US 2014
Brandon Philips
August 28, 2014
Tweet
Share
More Decks by Brandon Philips
See All by Brandon Philips
Node.js Workflow with Minikube and Skaffold
philips
0
280
Manage the App on Kubernetes
philips
0
360
Production Backbone Monitoring Containerized Apps
philips
0
210
KubeCon EU 2017: Dancing on the Edge of a Volcano
philips
1
810
rkt - KubeCon EU keynote - 2017
philips
1
290
FOSDEM_Keynote_2017-_.pdf
philips
0
150
Tectonic Summit Day 2 Keynote
philips
0
380
Kubernetes: Simple to Manage Anywhere (self-hosted, Tectonic upgrade demo)
philips
0
420
KubeCon Keynote 2016- Distributed Systems Simplified on Kubernetes
philips
2
570
Other Decks in Technology
See All in Technology
Bill One急成長の舞台裏 開発組織が直面した失敗と教訓
sansantech
PRO
1
170
MCPでつなぐElasticsearchとLLM - 深夜の障害対応を楽にしたい / Bridging Elasticsearch and LLMs with MCP
sashimimochi
0
120
システムのアラート調査をサポートするAI Agentの紹介/Introduction to an AI Agent for System Alert Investigation
taddy_919
2
1.5k
Deno・Bunの標準機能やElysiaJSを使ったWebSocketサーバー実装 / ラーメン屋を貸し切ってLT会! IoTLT 2026新年会
you
PRO
0
230
プロダクト成長を支える開発基盤とスケールに伴う課題
yuu26
3
1.1k
変化するコーディングエージェントとの現実的な付き合い方 〜Cursor安定択説と、ツールに依存しない「資産」〜
empitsu
4
1.3k
Webhook best practices for rock solid and resilient deployments
glaforge
1
210
What happened to RubyGems and what can we learn?
mikemcquaid
0
220
Data Hubグループ 紹介資料
sansan33
PRO
0
2.7k
2026年、サーバーレスの現在地 -「制約と戦う技術」から「当たり前の実行基盤」へ- /serverless2026
slsops
2
190
SREのプラクティスを用いた3領域同時 マネジメントへの挑戦 〜SRE・情シス・セキュリティを統合した チーム運営術〜
coconala_engineer
2
540
Amazon S3 Vectorsを使って資格勉強用AIエージェントを構築してみた
usanchuu
3
420
Featured
See All Featured
Speed Design
sergeychernyshev
33
1.5k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Paper Plane
katiecoart
PRO
0
46k
sira's awesome portfolio website redesign presentation
elsirapls
0
140
WCS-LA-2024
lcolladotor
0
440
The untapped power of vector embeddings
frankvandijk
1
1.6k
A Tale of Four Properties
chriscoyier
162
24k
Applied NLP in the Age of Generative AI
inesmontani
PRO
4
2k
Building Adaptive Systems
keathley
44
2.9k
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
310
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.3k
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
9.5k
Transcript
None
About Me CTO/CO-FOUNDER systems engineer @brandonphilips github.com/philips
What is CoreOS?
What is CoreOS?
None
None
Why build CoreOS?
reduce API contracts minimal
kernel systemd etcd ssh docker python java nginx mysql openssl
app distro distro distro distro distro distro distr
python java nginx mysql openssl app distro distro distro distro
distro distro distr kernel systemd etcd ssh docker
python openssl-A app1 distro distro distro distro distro distro distr
java openssl-B app2 java openssl-B app3 kernel systemd etcd ssh docker
CoreOS python openssl-A app1 distro distro distro distro distro distro
distr java openssl-B app2 java openssl-B app3
CoreOS container distro distro distro distro distro distro distr container
container
manual updates
automatic updates
automatic updates
atomic with rollback auto updates
None
None
None
run and isolate apps containers
pid ns isolated pid 1
user ns isolated uid 0
network ns isolated netdev
mount ns isolated /
cgroups manage resources
cgroups count resources
None
cgroups limit resources
docker engine
None
machines and clusters configuration
get into the cluster machine conf
#cloud-config users: - name: core coreos-ssh-import-github: philips coreos: etcd: discovery:
https://discovery.etcd.io/ba09c units: - name: etcd.service command: start - name: fleet.service command: start
#cloud-config users: - name: core coreos-ssh-import-github: philips coreos: etcd: discovery:
https://discovery.etcd.io/ba09c units: - name: etcd.service command: start - name: fleet.service command: start
#cloud-config users: - name: core coreos-ssh-import-github: philips coreos: etcd: discovery:
https://discovery.etcd.io/ba09c units: - name: etcd.service command: start - name: fleet.service command: start
#cloud-config users: - name: core coreos-ssh-import-github: philips coreos: etcd: discovery:
https://discovery.etcd.io/ba09c units: - name: etcd.service command: start - name: fleet.service command: start
what is running cluster conf
skydns, discoverd, confd services
what should run cluster conf
locksmith coordination
fleet, kubernetes scheduling
etcd
/etc distributed
open source software highly available and reliable sequentially consistent watchable
exposed via HTTP runtime reconfigurable
-X GET Get Wait -X PUT Put Create CAS -X
DELETE Delete CAD
Available
Available
Available
Unavailable
Available Leader Follower
Leader Follower Available
Leader Follower Temporarily Unavailable
Leader Follower Available
Sequential Consistency Index Time
1 1 1 2 GET A @ index 2 ->
blocking GET A @ index 2 -> 2 2
1 1 1 2 GET A @ index 2 ->
2 2 2
etcd guarantees that a get at index X will always
return the same result. Avoid thinking in terms of real time because with network latency the result is always out-of-date.
Watchable Changes HTTP Long-poll
1 2 3 > GET asdf?waitIndex=4&wait=true HTTP/1.1 > Accept: */*
> < HTTP/1.1 200 OK < Content-Type: application/json < X-Etcd-Index: 3 < X-Raft-Index: 97 < X-Raft-Term: 0 < BLOCK
1 2 3 4 > GET asdf?waitIndex=4&wait=true HTTP/1.1 > Accept:
*/* > < HTTP/1.1 200 OK < Content-Type: application/json < X-Etcd-Index: 3 < X-Raft-Index: 97 < X-Raft-Term: 0 < {"action":"set","node":{"key":"/asdf","value":"foobar"," modifiedIndex":4,"createdIndex":4}}
1 2 3 4 > GET asdf?waitIndex=4&wait=true HTTP/1.1 > Accept:
*/* > < HTTP/1.1 200 OK < Content-Type: application/json < X-Etcd-Index: 4 < X-Raft-Index: 516 < X-Raft-Term: 0 < {"action":"set","node":{"key":"/asdf","value":"foobar"," modifiedIndex":4,"createdIndex":4}}
getting work to servers scheduling
You Scheduler API Scheduler Machine(s)
$ cat foo.service [Service] ExecStart=/usr/bin/sleep 500 $ fleetctl start foo.service
Job foo.service launched on e1cd2bcd.../172.17.8.101
while true { todo = diff(desState, curState) schedule(todo) }
while true { todo = diff(desState, curState) schedule(todo) }
while true { todo = diff(desState, curState) schedule(todo) }
while true { todo = diff(desState, curState) schedule(todo) }
Talk tomorrow! fleet: systemd for clusters 2:30pm Mississippi
Why use CoreOS?
is it ready? stable released
lots of work todo the future
None
DEMO?