Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
CoreOS Overview @ LinuxCon US 2014
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Brandon Philips
August 28, 2014
Technology
700
7
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
CoreOS Overview @ LinuxCon US 2014
Brandon Philips
August 28, 2014
More Decks by Brandon Philips
See All by Brandon Philips
Node.js Workflow with Minikube and Skaffold
philips
0
300
Manage the App on Kubernetes
philips
0
390
Production Backbone Monitoring Containerized Apps
philips
0
250
KubeCon EU 2017: Dancing on the Edge of a Volcano
philips
1
890
rkt - KubeCon EU keynote - 2017
philips
1
330
FOSDEM_Keynote_2017-_.pdf
philips
0
180
Tectonic Summit Day 2 Keynote
philips
0
430
Kubernetes: Simple to Manage Anywhere (self-hosted, Tectonic upgrade demo)
philips
0
460
KubeCon Keynote 2016- Distributed Systems Simplified on Kubernetes
philips
2
600
Other Decks in Technology
See All in Technology
Persisting Massive Data with Rails ~Designing for 60 billion rows, and fighting the bottlenecks~ Railsで挑む大量データ永続化 〜600億件を永続化するための設計とボトルネックとの戦い〜
occhi
0
480
WasmをRustにする
sansantech
PRO
0
220
事業成長とデータ活用を止めないためのマネジメントへ挑戦
hiracky16
0
330
FOSS4Gを活用した自治体業務DXの試み
470715
0
150
実践!Cloud Run ハンズオン!! / Cloud Run handson
y0hgi
1
260
脆弱性診断って、何をしているの? 〜弱点を見つけて、会社の改善につなげるまで〜
keeg
0
890
Benchmarking Disaggregated Serving on vLLM + Dynamo with a Real Coding-Agent Workload
nttcom
0
120
[AWS 秋のクラウドオペレーション祭り 2026]AWS DevOps Agentで変わるリリースと運用対応 ~リリース管理機能と Directed actions のご紹介~
furuton
4
1.2k
PagerDuty Tech Hub-鳴らすけれど、人は動かない
ezaki
0
120
子育てエンジニアの可処分時間が減っても成長を諦めない戦い方
sudoakiy
6
4.5k
自分で立ててみるLLMサービス
y_sera15
0
160
分析の民主化を支えるメタデータ整備の実践
kakehashi
PRO
4
1.3k
Featured
See All Featured
BBQ
matthewcrist
90
10k
Lessons Learnt from Crawling 1000+ Websites
charlesmeaden
PRO
1
1.6k
Statistics for Hackers
jakevdp
799
230k
Producing Creativity
orderedlist
PRO
348
41k
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
450
Fireside Chat
paigeccino
43
4.1k
Building Adaptive Systems
keathley
44
3.2k
エンジニアに許された特別な時間の終わり
watany
109
250k
Automating Front-end Workflow
addyosmani
1369
210k
Kristin Tynski - Automating Marketing Tasks With AI
techseoconnect
PRO
0
550
DevOps and Value Stream Thinking: Enabling flow, efficiency and business value
helenjbeal
2
410
Ethics towards AI in product and experience design
skipperchong
2
430
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?