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.
Packer is one of the tools I’ve used in the past to build VirtualBox boxes. You can find what I’ve done on my GitHub account. For Smash project, I wanted to make a packer configuration to manage Docker and VirtualBox. I also wanted to call Ansible to build specific images for each needs. The goal is to be able to build cloud image ready to start, without any special dependencies. This because I need different usages:
In the last post, I talked about how to manage Docker and VirtualBox with Vagrant. This post follows the last one, with the integration of Ansible as a provisioner. Once again, I’m using it for the Smash project. With Ansible, I made several “group_vars” files containing custom and common information related to the used environment (dev, uat, staging…). This helps to setup different kind of environment easily. Vagrant will help to build images with Ansible deployed inside.
As you may know, I’m using Vagrant for more than a year now with VirtualBox. Docker is a faster alternative that needs to be taken into consideration. Having the possibility to manage both of them with the same tool can be very interesting. For information, I mainly use it with VirtualBox because it’s any platform compatible and Docker because it’s perfect for a CI like Jenkins. I recently talked about my implication into the Smash project.
Fig is a fast, isolated development environments using Docker. For some features, it can be compared to Vagrant where the Dockerfike is not enough powerful to build multiple instances. For example, let’s say you want to test a new product version of a software like MediaWiki and you want to build the complete stack. So you may need to have several tools categories (depending of the usage): Web: Nginx, PHP-FPM, Varnish App Cahing: Redis Search: ElasticSearch In Vagrant you can natively build 3 VM and interconnect them without the need of additional tool.
I really like this kind of news, new versions of docker and RedHat: Docker 1.0: this is the first stable version after more than one year of development. This version is production ready and I will start using it asap. RedHat 7: this is a good news as the version 6 started to be a little bit old now. What’s new? MariaDB replace MySQL \o/ Docker integrated systemd XFS by default Kernel 3.
Luc (@lstep) informed me about an interesting software that looks like Juju at first and I wanted to share it with you. It’s called Gaudi. If you already use Docker to setup your dev box for large applications, don’t you suffer to maintain complex Dockerfiles? Splitting a service Oriented Architecture into several Docker containers is the solution, except managing links and mounts between them is a pain. gaudi solves that by offering a way to describe a system of Docker containers using a simple DSL.
- OLDER POSTS
- page 1 of 2