For a new project (will talk about it later), I needed to use Neo4J (graph database if you don’t know it yet). I tried to cover more features than the current existing Ansible roles available on Ansible Galaxy. More will come in the next weeks. I also tried to make it simple to install it and do not force dependencies at maximum. Here are parameters you can set: # Select neo4j version neo4j_package: neo4j # community version #neo4j_package: neo4j-advanced #neo4j_package: neo4j-enterprise # Neo4j spatial plugin neo4j_install_spatial: false neo4j_spatial_version: '0.
Since several weeks, I’m playing a lot with Debian Jessie as a server. I discovered some bugs, reported them to Debian, they’ve been fixed etc…good news! I also wanted to test the new version of LXC. So I decided to upgrade my 2 personal servers to Jessie. But that wasn’t so easy with Systemd. I still encounter non critical issues and going to prepare report bugs for Debian (cgroups issues with systemd).
Packer is a really great solution to make an image in several formats (VirtualBox, Docker…). I recently wanted to deploy it on a Jenkins server to automatically perform image build with the help of Packer. That’s why I’ve wrote a Packer role for Ansible really easy to use. You simply have to set (or let them by defaults) vars: # Packer version to install packer_version: '0.7.5' # Packer destination folder packer_destination: '/usr/bin' It will install the desired version :-)
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.
For my personal usages, I wanted do use DotDeb and MySQL playbooks. I first looked at the current ones on the Ansible Galaxy. However I did not find a good one for my needs. I first wanted to try to contribute to an existing one. But I needed to have them quickly and unfortunately didn’t have the time to do it. That’s why I made 2 new Ansible roles and added them to Ansible Galaxy.
If like me, you were using the Ansible Galaxy website to find and download your playbook for your favorite apps, you may missed a feature. It happened to me when I had to manage several playbook roles. I first wanted to use Git submodules to do it. However I preferred to search another way to do like like Puppet can do with R10K because I am working on a project with some unfamiliar Git users.