Some thoughts on operating containers | R.I.Pienaar
On one hand I can go the route of a private PaaS where you push an image or Dockerfile into it and forget about it. And hope you never have to debug anything or dive deep into finding out why something is not performant as those tend to be very much closed systems. Some like deis are just Docker underneath but some others like the recently hyped lattice.cf unpacks the Docker container and transforms it into something else entirely that is much harder to interact with from a debug perspective. As a bit of an old school sysadmin this fire-and-hope-for-the-best approach leaves me a bit uninterested. I’m going to want to not loose the ability to carefully observe my running containers using traditional tools if I have to. It’s great to strive for never having to do that, never having to touch a running app using any thing but your monitoring SaaS or that you can just always scale out horizontally but personally I feel I need a bit more closer to the bits interaction at times. Aim for that goal and get a much better overall system, but while you’ve not yet reached this narvana like state you’re going to want to get at your running apps using strace if it has to.
cloudfoundry-incubator/lattice at v0.2.1
Lattice is an open source project for running containerized workloads on a cluster. Lattice bundles up http load-balancing, a cluster scheduler, log aggregation/streaming and health management into an easy-to-deploy and easy-to-use package.

List of feeds:

pinboard: last checked Tue 28 Apr 2015 12:00:02 AM EDT (1835 posts; 2 new)

flickr: last checked Tue 28 Apr 2015 12:00:05 AM EDT (48 posts)

youtube: last checked Tue 28 Apr 2015 12:00:04 AM EDT (10 posts)

libre.fm: last checked Tue 28 Apr 2015 12:00:04 AM EDT (0 posts)