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
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
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
クレジットカード決済基盤を支えるSRE - 厳格な監査とSRE運用の両立 (SRE Kaigi 2026)
capytan
6
2.7k
顧客の言葉を、そのまま信じない勇気
yamatai1212
1
350
SREチームをどう作り、どう育てるか ― Findy横断SREのマネジメント
rvirus0817
0
230
SREのプラクティスを用いた3領域同時 マネジメントへの挑戦 〜SRE・情シス・セキュリティを統合した チーム運営術〜
coconala_engineer
2
640
顧客との商談議事録をみんなで読んで顧客解像度を上げよう
shibayu36
0
230
仕様書駆動AI開発の実践: Issue→Skill→PRテンプレで 再現性を作る
knishioka
2
650
Context Engineeringが企業で不可欠になる理由
hirosatogamo
PRO
3
570
予期せぬコストの急増を障害のように扱う――「コスト版ポストモーテム」の導入とその後の改善
muziyoshiz
1
1.8k
Digitization部 紹介資料
sansan33
PRO
1
6.8k
Agile Leadership Summit Keynote 2026
m_seki
1
610
インフラエンジニア必見!Kubernetesを用いたクラウドネイティブ設計ポイント大全
daitak
1
360
AI駆動PjMの理想像 と現在地 -実践例を添えて-
masahiro_okamura
1
110
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
432
66k
How STYLIGHT went responsive
nonsquared
100
6k
Agile Actions for Facilitating Distributed Teams - ADO2019
mkilby
0
110
Neural Spatial Audio Processing for Sound Field Analysis and Control
skoyamalab
0
170
Why Our Code Smells
bkeepers
PRO
340
58k
The innovator’s Mindset - Leading Through an Era of Exponential Change - McGill University 2025
jdejongh
PRO
1
91
What Being in a Rock Band Can Teach Us About Real World SEO
427marketing
0
170
We Are The Robots
honzajavorek
0
160
Kristin Tynski - Automating Marketing Tasks With AI
techseoconnect
PRO
0
140
Accessibility Awareness
sabderemane
0
51
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
1
300
Done Done
chrislema
186
16k
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?