For another personal project (that I can’t talk about for the moment ;-)), I wanted to have a Changelog file to get a better following of the infrastructure evolution (configuration management, scripts…all under git). Of course the documentation is very important, but when you do not write it at the same time you’re building the infrastructure, it may be complex to remember each little things you’ve done. That’s why a Changelog can help to understand how the infrastructure has been built step by step.
A few months ago, I already talked about offloading SSL with Nginx. I also wanted to try it with HAProxy which can be more interesting in some cases. The good On HAProxy, the good thing is the simplicity to do it. First of all you need to have at least the version 1.5 of HAProxy so to get SSL support. Then you only need those lines to offload SSL:
For my company, I recently had to find a good solution to make Snapshots from Instance IDs or from tags on AWS. I made several searches but unfortunately didn’t find what I was searching for. That’s why I started to make a tool to do this kind of job. It’s written in Python and requires the Boto library. Here is what you can do with Simple EC2 snapshots: Hot snapshots (by default) and Cold snapshots Multiple instances snapshot in one line Detection of doubles Filters by tags (allowing wildcards) or by instance IDs Credentials file multiple with profiles Limit the number of snapshots Restrict snapshots to data disks only The tool is open source and can be downloaded on GitHub :-).
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:
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.
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.
Jessie is now frozen!!! Here is the news. That mean only limited updates can be done: targeted fixes for release critical bugs (i.e., bugs of severity critical, grave, and serious) in all packages (applies during the entire freeze (ok for TPU)); fixes for severity: important bugs in packages of priority: optional or extra, only when this can be done via unstable (until the 5th of December 2014);