ContainerDays Boston 2015: "CoreOS: Building the Layers of the Scalable Cluster for Containers" (Barak Michener)
•
2 likes•805 views
Slides from Barak Michener's talk "CoreOS: Building the Layers of the Scalable Cluster for Containers" at ContainerDays Boston 2015: http://dynamicinfradays.org/events/2015-boston/programme.html#layers
Recommended
More Related Content
What's hot
What's hot (20)
Similar to ContainerDays Boston 2015: "CoreOS: Building the Layers of the Scalable Cluster for Containers" (Barak Michener)
Similar to ContainerDays Boston 2015: "CoreOS: Building the Layers of the Scalable Cluster for Containers" (Barak Michener) (20)
More from DynamicInfraDays
More from DynamicInfraDays (17)
Recently uploaded
Recently uploaded (20)
ContainerDays Boston 2015: "CoreOS: Building the Layers of the Scalable Cluster for Containers" (Barak Michener)
- 1. Building the Layers of the Scalable Cluster for Containers by Barak Michener
- 7. kernel systemd lvm ssh python java nginx mysql openssl app distrodistrodistrodistrodistrodistrodistr
- 8. python java nginx mysql openssl app distrodistrodistrodistrodistrodistrodistr kernel systemd lvm ssh
- 10. super-powers OS
- 11. Opportunity for automatic updates. Consistent set of software across hosts. Base OS independent from app.
- 13. design for host failure clustering
- 14. etcd
- 16. open source software sequentially consistent exposed via HTTP runtime reconfigurable
- 17. Available
- 18. Available
- 19. Available
- 20. Unavailable
- 25. 1 2 3 4 {Log
- 26. 1 2 3 4 Entries
- 27. 1 2 3 4 Indexes
- 28. Sequential Consistency Operations* are atomically executed in the same sequential order on all machines.
- 29. 1 1 1 2 Pet=dog Pet=cat Pet=cat 1 2 PUT Pet = cat PUT Pet = dog
- 30. 1 1 1 2 2 1 2 PUT Pet = cat PUT Pet = dog Pet=dog Pet=dog Pet=cat
- 31. 1 1 1 2 2 2 1 2 PUT Pet = cat PUT Pet = dog Pet=dog Pet=dog Pet=dog
- 33. 1 1 1 2 GET Pet @ 10:00.0 -> 1[cat]!? GET Pet @ 10:00.0 -> 2[dog] 2
- 34. 1 1 1 2 2 2 GET Pet @ 10:00.1 -> 1[dog]
- 36. 1 1 1 2 GET Pet @ 2 -> blocking GET Pet @ 2 -> 2[dog] 2
- 37. 1 1 1 2 GET Pet @ 2 -> 2[dog] 2 2
- 38. 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.
- 39. Quorum GETs GET via Raft
- 40. 1 1 1 2 2
- 41. 1 1 1 2 QGET A 2
- 42. 1 1 1 2 QGET A -> 2[dog] 2 2
- 43. 1 1 1 2 QGET A -> 2[dog] 2 2 3 3
- 46. Share configuration data across hosts. Resilient to host failures. Designed for consistency across hosts.
- 48. what can we build together? cluster resources
- 49. We have some important primitives now What cluster-wide services can we provide? Network, Disk, Compute (kublets) Personal opinion: ls /dev
- 52. Partition a IP range -- hand out an IP to each container (consistently) Speed! (Avoiding userspace is good)
- 54. getting work to servers orchestration
- 55. You Orchestrator API Scheduler, Network, NS Machine(s)
- 56. while true { todo = diff(desState, curState) schedule(todo) }
- 57. while true { todo = diff(desState, curState) schedule(todo) }
- 58. while true { todo = diff(desState, curState) schedule(todo) }
- 59. while true { todo = diff(desState, curState) schedule(todo) }
- 63. Think about app capacity first. Take advantage of compute/memory/disk/network resources. Build on etcd resilience to host failure.
- 65. run and isolate apps containers
- 66. what is it exactly? containers
- 68. libc python django app.py example.com/myapp "Lifts" myapp from the OS into Layer 6
- 69. $ container fetch example.com/myapp $ container run example.com/myapp Pull from layer 6 Invoke in layer 2
- 70. pid ns isolated pid 1
- 71. user ns isolated uid 0
- 77. how are they created? containers
- 80. Application (you, MySQL, ElasticSearch)Layer 3 Linux Distro (Ubuntu, Red Hat, CentOS)Layer 2 Physical (Bare Metal, OpenStack, AWS, DO)Layer 1 revisiting today’s Model
- 83. a Cluster
- 84. a Cluster
- 85. a Cluster
- 86. a Cluster
- 87. @coreoslinux