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.
I’ve been emailed for the first time less than 2 months ago by Kevin, a newcomer in HashiCorp which is taking care about marketing, community etc…
What I can say is I’m impressed by how they are taking care about their community :-). In my mailbox, I received a T-Shirt, 3 stickers and a letter.
Thanks a lot HashiCorp !
Following the deployment blog post I made on ES/Kibana/Fluentd, I released new version of Fluentd and Kibana playbooks to support the latests versions of themselves and ElasticSearch.
ElasticSearch 1.4 version is ,out which doesn’t changed anything for the deployment. However Kibana requires to enable an ElasticSearch configuration option now, to work properly. I updated the Kibana playbook for it.
On its side, Fluentd has the major release 2.0 out and I updated Ansible playbook for the best integration with Debian Wheezy.
A lot of time, I had to modify the text of my commit since I’m using a versionning system. Modifying the last commit comment is something common:
git commit --amend However, modifying the date is not so common. You may want to do it for several reasons (stats or similar), here is how to:
GIT_COMMITTER_DATE="`date`" git commit --amend --date "`date`" This will change the last commit with the current date.
I recently had the case, where I lost connexion of my NFS client connexion because NFS server crashed. The problem I had is simple, some of clients couldn’t recover their connexion because the old one was still shown as already connected.
And when I tried to remount NFS clients connexions, I got:
mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'udp,sec=sys,rsize=8192,wsize=8192,intr,hard,addr=10.0.0.1' mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: trying 10.