Blog

Yesterdays (ok, late post - at the last) MeetUp was first and foremost about the Container Manifesto, which aims to foster understanding about how to build and run a Container.

Afterwards we figured that I missed 'Containers should start fast (thx Lukasz)' as an additional point - next time. :)

For today I will just put the video in here, a separat blog post might follow - even though I feel it is not that necessary, as no code was executed.

During the latest MeetUp we talked about the rise of virtualization techniques and how software changed from clunky big services to state-less functions.

Last week-end I was hacking on my metrics collector to be able to fetch docker-engine and docker-container stats.

But as my MeetUp in Berlin is called M.E.L.I.G. (Metrics,Events,Logs,Inventory and Glue), there is much more to it then metrics.

This week-end I hacked on a new tool: qwatch

Docker 1.13 is on it's way and I like what comes to light.

The highlights from where I stand are:

• service port publishing now as mode host or ingress, which allows for service ports to be outside of the IPVS load-balancer and just exposed on the SWARM node.
• the load-balancer seems to honour established connections
• experimental has an end-point /metrics, which exposes Prometheus formatted metrics.

And this last bit got me interested. So much, though, that I hacked a Prometheus collector into qcollect. :)

I won't apologise for the log delay between posts again, busy times...

But that should discourage you from checking in every once in a while - I got something nice today, at least I think so. :)

A while back I stumbled upon Fullerite, a GOLANG metrics collector, which can reuses the collectors of the python Diamond collector.

One of the issues I had was, that it is not using the event time, but the process time of collected metrics. Thus, if you want to bulk update collected metrics, they will all have the same timestamp of the time they are push to the metrics backend.

Running Docker services on single nodes is quite boring, so let's boot up three boxes with the latest version of docker.

This is a blog post to accompany the talk I gave a the Berlin Docker Meetup:

After a couple of month being busy, it's time for a blog post about Docker Services.

As I stated often - I became a big fan of Consul for service orchestration, service discovery and as a K/V store in my docker stacks.

Since Docker Engine 1.11 the necessary DNS feature to be able to use a 127.0.0.1 address was somewhat kicked, so I had a hard nut to crack. My workaround was to not care about local resolution and use the consul servers as DNS resource. Anyway...

This years 'Linux Container' workshop at the ISC 2016 is called: Docker: Linux Containers to Optimise IT Infrastructure for HPC & BigData.

It was held after the International Supercomputing Conference in Frankfurt on June 23rd at the Marriott hotel.

• Official agenda page: http://www.isc-hpc.com/isc16_ap/

Unlike last year the focus was to provide actionable knowledge about the world of Linux Containers, discuss problems and possible solutions.

After a quick Proof of Concept I pushed it to my little HPC setup with physical nodes and InfiniBand.

Next I aimed to run HPCG within containers instead of a bare-metal run.