I often receive questions about Ansible Inventories (far more often than any other Ansible component). My guess is that Inventories are effectively among the most complex things in Ansible.
Ansible Inventories are complex in the following ways:
After you have decided an Inventory model is hard to change it, in fact you would probably be required to touch all your Playbooks to make everything working again There is not a single way of doing Inventories Often Inventories are the glue to make a generic Playbook run properly on your specific architecture.
FOSDEM is a must for all open source enthusiast in Europe and close by. I think that the reasons to go to FOSDEM are different from the reasons of many other conferences, but equally valid. The comparison with DevConf is obvious, due to the temporal closeness of the two events.
I think that DevConf is more about enterprise grade software (or close to be), while FOSDEM is more about experimentations and community.
I think this is a special moment of the year, where in less than two weeks is possible to meet a huge amount of Open Source contributors in person. Obviously you will need to take few flights, but it’s definitely worth.
DevConf this year was great. I’ve been able to assist to a huge amount of talks (more than 20) and the majority of which were very interesting.
As always in conferences, there are themes heavily discussed and other completely absent.
When I speak with people that are starting with Ansible from Puppet, the first thing they want to experiment is Ansible Galaxy.
This leaves me very sceptical, since I think the default mode in Ansible should be DIY. Since I’ve found myself in this situation far to many times, I decided to write down all the reasons why you should avoid Ansible Galaxy in the majority of situations.
Using Ansible Galaxy often violates the Ansible way.
The single most frequent complain I hear about Ansible is about it’s slowness. This is very common, but even more common among people that used to use Puppet. There are many reasons why Ansible is slower than Puppet. The three main reasons are:
Linear execution: Ansible will execute each operation in order and will not run many steps at the same time as Puppet does. SSH Connection: all Ansible commands will be issued from the control system to the controlled system via SSH.
Posted on November 1, 2016 - Villanova di Bernareggio, IT
In Italy every year, during the last weekend of October, there is the Linux Day, an “open day” for the LUGs where they create events to publicize GNU/Linux and the Free Software. As usual (for the last 7 years now), the ViGLug organized this event and this time has been in Bernareggio (MB), a city less than half hour drive north-east from Milan. This year, for the first time in the ViGLug life, we have partnered up with other two organizations BrigX (the Bernareggio LUG) and the Coderdojo Brianza.
From the 25th to the 27th of this month I’ve been at the SMAU in Milan (Italy).
The SMAU (Salone Macchine e Attrezzature per l’Ufficio, that would be Exposition of Machinery and Equipment for the Office) is an historical fair started in 1964 and that has had many changes over the years, for instance some years it has been opened to the general public, other times it was only for business visitors.
IMPORTANT NOTICE: This article deals with Ansible Tower <= 3.0. If you are looking for information around Ansible Tower >= 3.1, please look my newer article on the topic.
In the last few months I’ve setted up multiple times Ansible Tower, but I’ve noticed that there is not much documentation on how to perform basic maintenance on Ansible Tower High Availability setup, so I decided to write an article about it.
This year, I have been able to go to Flock :). Flock location this year was Krakov (Poland). Since my flight arrival time was very close to Mailga’s one, I waited him at the airport and then we went together to the Flock location. This has proven to be a good idea, since we had the time to speak about some important topics around the Italian Community. We then arrived to the Flock location, were we discovered a problem with the rooms booking, but that got resolved in a quick way by Bexelbie.
After more than 12 years as a freelance consultant, today I start a new adventure within Red Hat. I’ve always admired Red Hat capability to run a multi billion dollars business selling services (subscriptions, training, and consultancy) on top of free software, so when I got the opportunity to join Red Hat I gladly accepted.
Joining Red Hat I’ll not change completely what I do, since I’ll go forward being a Consultant and I’ll work on similar products to the ones I work with today.