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. We’re now almost in December and I said there would likely be a beta version out by September. “What’s going on ?”, one might ask… A fair question. There’s definitely been progress and I could’ve been doing a better job at communicating updates other than the tweet from time to time.
More and more users requested other ways of reaching the ARA community and I’ve finally given in ! Until now, the only way of getting in touch was through IRC and I understand that, in 2017, IRC is not for everyone. Seamless communication across IRC, Slack and Discord That’s right, you can now reach us through Slack and Discord. Both are linked to IRC so messages sent to one will be relayed automatically to the others.
Not long ago, I wrote that ARA: Ansible Run Analysis had it’s first birthday. It was an important milestone and it was a great opportunity to reflect back on where the project was coming from and think about what we needed to do in the future. Just for fun, let’s look at what I had written back in May to summarize what was probably coming: Python 3 compatibility This is done and was shipped in ARA 0.
(Edit: See at the end) I can’t get enough of this Ansible thing, it’s great and makes my life easier. Sometimes there’s this little awesome feature that is in a pull request or has already landed in the development branch. You can’t wait to use but it won’t be shipped until the next release of Ansible.. and sometimes that takes a while. What do you do in the meantime ?
Ansible is known to be good at running things in the order you write them and that’s why it’s awesome for orchestration. However, I have a use case where I have several similar and long-running tasks to run that do not need to run sequentially. Ansible provides a way to run tasks asynchronously and later recover their result. The problem The problem is that Ansible doesn’t provide a way to limit the amount of concurrent tasks run asynchronously.