All posts by hansamann

Sven is a maker at heart and loves to connect things. In his role as IoT architect at Samson Pilotentwicklung GmbH, he’s researching end-to-end IoT architectures. He believes in a playful approach for learning, loves flashy projects and is happy to share his insights at conferences around the globe. To learn more, check out his twitter timeline at https://twitter.com/hansamann.

Creating a Multi-Arch Kubernetes Cluster

During the last days and weeks, we focused on Kubernetes. It sounds like the most logical next step for evolving our CI/CD pipeline. And we knew before that Kubernetes is a different beast. It takes a while to get used to the concepts of Kubernetes, but that’s not even the hardest part. We figured out ...

Code to Container v4: the evolution of GitLab

As already introduced in the last Code to Container post, we’re moving to GitLab. We’ve started evaluating the Gitlab CI system first and now begin to move other parts such as the deployments to GitLab, too. This blog post is a bit shorter and mainly describes how we setup deployments using a manual build step ...

Code to Container v3: the discovery of GitLab

When I take another look at Code to Container v2 (our last sprint results), I get goose bumps 🙂 But that’s OK. In v2 we’ve created an pretty complex system of MQTT messaging and systems involving Continuous Integration (Circle CI, namely) and Continuous Deployment (self-made mqtt-triggered Docker deployers). When I look back and also taking ...

Code to Container v2: creating an MQTT based CI/CD backbone and adding Docker Swarm

In our first post about our research architecture for automated Docker deployments, we’ve explained a simple mechanism to automatically update a Docker container based on a push to a code repo. That mechanism, frankly, was not quite sophisticated. Yet we’ve learnt a lot and that’s the main reason we’re doing this. We iterate quickly to ...

Code to Container v1: automatically deploying a Docker container on RPI

This blog post will describe the output of our first sprint. Our goal (which me met, somehow) was to be able to push code to a repo of our choice, compile, (test?) and build a docker image for Raspberry PI and finally automatically deploy this image, e.g. run it on a Raspberry PI. So, just ...