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
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
380
Production Backbone Monitoring Containerized Apps
philips
0
240
KubeCon EU 2017: Dancing on the Edge of a Volcano
philips
1
890
rkt - KubeCon EU keynote - 2017
philips
1
320
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
JSONataとAWS Step Functionsで目指すRuntimelessな世界
mu7889yoon
0
440
Mastering Agentic Development: Harness Engineering for Effective Coding Agents
konippi
1
130
事業課題から技術的負債に向き合う
sansantech
PRO
2
2.3k
【技術的負債conf】事業成長に伴う技術的負債の説明責任とAIによるモニタリング、認知的負債について
i35_267
3
2.1k
AIに賢く動いてもらうためのコンテキスト〜Snowflake女子会 vol.8
snowwmn0824
0
160
AIエージェントの自己改善をどう設計するか / How to Design Self-Improvement for AI Agents
22mi
25
17k
Railsのように考える: See through the Master
snoozer05
PRO
5
1.3k
C#未経験の僕がAIに読めるコードを書かせるまで
maguroalternative
0
250
バイブコーディング時代のWebアプリ開発入門~Cloud Runで学ぶセキュアなビルドとデプロイ
waiwai2111
1
140
Claude in Chrome 入門 / Introduction to Claude in Chrome
cielo1985
0
890
アプリログインとWeb認証基盤をつなぐ ASWebAuthenticationSession 作法
shimastripe
1
390
Goodbye ShellScript, Hello File-based App
shunsock
0
770
Featured
See All Featured
Redefining SEO in the New Era of Traffic Generation
szymonslowik
1
430
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
1
410
Conquering PDFs: document understanding beyond plain text
inesmontani
PRO
4
3.1k
Test your architecture with Archunit
thirion
2
2.4k
Design in an AI World
tapps
1
330
Speed Design
sergeychernyshev
33
2.1k
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
200
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
Exploring the relationship between traditional SERPs and Gen AI search
raygrieselhuber
PRO
3
4.3k
Practical Orchestrator
shlominoach
192
12k
Docker and Python
trallard
47
4.2k
Design of three-dimensional binary manipulators for pick-and-place task avoiding obstacles (IECON2024)
konakalab
0
600
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?