Skip to content

Update layers-in-the-stack.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
robwdux wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update layers-in-the-stack.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/post/layers-in-the-stack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ I was chatting on an Xoogler message board the other day and Dennis Ordanov ([@d
So, with that, here is a brain dump of the parts that make up a "modern" stack:

* **Production Host OS**. This is a simplified and manageable Linux distribution. Usually it is just enough to get a container engine up and running.
* Examples include [CoreOS](https://coreos.com/using-coreos/), [Red Hat Project Atomic](http://www.projectatomic.io/), [Ubuntu Snappy](https://developer.ubuntu.com/en/snappy/), and [Rancher OS](http://rancher.com/rancher-os/).
* Examples include [CoreOS](https://coreos.com/using-coreos/), [Red Hat Project Atomic](http://www.projectatomic.io/), [Ubuntu Snappy](https://developer.ubuntu.com/en/snappy/), [Rancher OS](http://rancher.com/rancher-os/) and [CargOS](https://cargos.io/).
* **Bootstrapping system**. Assuming you are starting with a generic VM image or bare metal hardware, something has to be able to bootstrap those machines and get them running as productive members of the cluster. This becomes very important as you are dealing with lots machines that come and go as hardware fails.
* [Cloud Foundry BOSH](https://bosh.io/docs) was created to do this for Cloud Foundry but is seeing new life as an independent product.
* The standard config tools ([Puppet](https://puppetlabs.com/), [Chef](https://www.chef.io/), [Ansible](http://www.ansible.com/home), [Salt](http://saltstack.com/)) can serve this role.
Expand Down Expand Up @@ -94,4 +94,4 @@ Next on the list would be to talk about continuous integration/continuous deploy
* I've listed example projects/products/companies/systems at different levels but this isn't meant to be exhaustive.
* The fact that I've listed a system here doesn't mean that I've run it in production and it has my stamp of approval.

[^flume]: Don't confuse Apache Flume with [Google FlumeJava](http://research.google.com/pubs/pub35650.html). I guess once you start processing logs some names are just obvious. Also see [Google Sawzall](http://research.google.com/archive/sawzall.html) and [Google Dremel](http://research.google.com/pubs/pub36632.html).
[^flume]: Don't confuse Apache Flume with [Google FlumeJava](http://research.google.com/pubs/pub35650.html). I guess once you start processing logs some names are just obvious. Also see [Google Sawzall](http://research.google.com/archive/sawzall.html) and [Google Dremel](http://research.google.com/pubs/pub36632.html).