I’m managing applications inside Kubernetes for more than 2 years for MySocialApp a social news feed solution and recently Referlab, an impressive referral marketing solution. If you follow me, you certainly know that I’ve made multiple Helm charts on distributed technologies like: Cassandra Helm chart Elasticsearch Helm chart Traefik Helm chart After several years of experience on it, you can trust me when I say managing statefulset on Kubernetes is not the easiest thing to do.
Since several years, I’m hosting a lot of things: blog, wiki, emails etc… I’ve played with Vserver, OpenVZ, KVM and finaly LXC. For years, I’ve learned how to use all of them but the most known solution during the last years is Docker. I even can remeber the first Meetup I’ve attended in Paris talking about Docker 5 years ago. Now containers are eveverywhere. I recently changed the server I’m running for my own usage and this was the good timing to switch from LXC to Docker.
I’m using Kubernetes on an on premise cluster for MySocialApp. Today, I’m storing MySocialApp public images at Quay.io and I also wanted to store private images. I didn’t want to bootstrap a private registry for it to avoid maintaining it, having a distributed storage to maintain for it etc…but wanted a solution at a lower cost. I started to look at DockerHub and Quay.io. As far aas I saw, DockerHub do not provide private registry while Quay does.
The Jeedom software is open source; you have complete access to the software that manages your home automation. Jeedom is compatible with various protocols, like Z-Wave, RFXCOM, RTS SOMFY, EnOcean, xPL, etc. Installing Jeedom on Synology with Docker it not a complex task. However for those who are not familiar with those technologies, I summarized here the installation process for a Z-wave network. First of all, let’s look at the requirements:
Some of you may not be familiar with the terms “Rolling upgrade” or “Rolling restart”. This is the action of upgrading or restarting a cluster without service interruption (alias zero downtime). In most cases, this is done node by node, but in fact it depends of the technology you’re managing and the number of active nodes in your cluster. At Nousmotards we have several Java Spring Boot applications running. Restarting one application can take up to 1 min.
This title can sounds like a troll, but this is not the case! I’m writing this post as a feedback. When I spoke during an Ansible meetup presenting Nousmotards infrastructure, I had several questions regarding why I chose monit as the init system instead of supervisord. That’s what encouraged me to write this post and that’s why I wanted to clarify here the things. Introduction Docker is made to run a process in a confined area.
The Ansible meetup ended ! That was really nice for my first one. I had really great feedbacks and liked the questions when ended. More than that I met nice people after the meetup and could have interresting discussions :-). I’m really happy about it. For those who would like to review the slides, you can find them here: http://nousmotards.github.io/ansible-meetup-0915/ If you want to watch the video: http://www.infoq.com/fr/presentations/reseau-social-motard or view the PDF version here:
- OLDER POSTS
- page 1 of 3