IT memoirs

As part of my home infra renovations I've been transferring more and more functions to run in containers on top of Rasperry Pis. Even though specifics are extremely hacky and home use only, there's been quite a few lessons learned which link into enterprise grade ways of working also. This journey mainly started off with Hypriot , which provides great automation to setup docker basics on Pi. So getting to the initial state of delivering everything in one infrastructure as a code model was straight forward.  Version 1.0 Hypriot provides support for cloud-init, which makes automating deployment very easy. Essential flow was / is like this: Deployment image = Hypriot (GIT) Deployment configuration = cloud-init user-data Persistent storage = NFS (Re-)Deployment model = flash SD card with image & config Whole magic is in the cloud-init user-data, which has a lot of failures actually in this model but we'll get to that later. Activities that I placed...

Starting point The title can and will mean very different things to different people, to some people it means building a toolshed to begin with. Anyhow, we're in IT context now in my personal context this renovation means actions to get rid of a traditional server park running on Dell VRTX and moving more actions into both containers and public cloud. These activities themselves can be understood many ways, but hopefully the story will clarify as we go along. This activity has been actually ongoing already for a while and now as I had a otherwise free weekend I got things a bit more forward, to a let's say midway state from the actual goal. Midway physical architecture Since pictures are always nice, here's physical architecture of my home infra. This is now almost current state, currently the clusterfw is actually behind worksw as there's a bit open actions going on with the devices. As one might guess, worksw is in my office and backendsw is then in my cl...