With two days of AnsibleFest instead of one this time around, we had 100% more time to talk about Ansible things !
I was recently writing that ARA was open to limited development for the stable release in order to improve the performance for larger scale users.
This is part of a blog series highlighting awesome things in software engineering because not everything has to be depressing, about bugs, vulnerabilities, outages or deadlines. If you’d like to collaborate and write about awesome things in software engineering too, let’s chat: reach out on Twitter or LinkedIn.
So I got an idea recently… Let’s rebrand Ansible Run Analysis to ARA records Ansible.
Back in August, I posted about what was the roadmap for ARA 1.0 and why it was a very important milestone for the project.
More and more users requested other ways of reaching the ARA community and I’ve finally given in !
Not long ago, I wrote that ARA: Ansible Run Analysis had it’s first birthday.
(Edit: See at the end)
Ansible is known to be good at running things in the order you write them and that’s why it’s awesome for orchestration.