Recently at Config Management Camp I’ve had many discussions about Orchestration, Playbooks and Choria, I thought it’s time for another update on it’s status.
I am nearing version 1.0.0, there are a few things to deal with but it’s getting close. Foremost I wanted to get the project it’s own space on all the various locations like GitHub, Forge, etc.
Inevitably this means getting a logo, it’s been a bit of a slog but after working through loads of feedback on Twitter and offers for assistance from various companies I decided to go to a private designer called Isaac Durazo and the outcome can be seen below:
The process of getting the logo was quite interesting and I am really pleased with the outcome, I’ll blog about that separately.
There are various other places the logo show up like in the Slack notifications and so forth.
On the project front there’s a few improvements:
- There is now a registration plugin that records a bunch of internal stats on disk, the aim is for them to be read by Collectd and Sensu
- A new Auditing plugin that emits JSON structured data
- Several new Data Stores for Playbooks – files, environment.
- Bug fixes on Windows
- All the modules, plugins etc have moved to the Choria Forge and GitHub
- Quite extensive documentation site updates including branding with the logo and logo colors.
There is now very few things left to do to get 1.0.0 out but I guess another release or two will be done before then.
So from now to update to coming versions you need to use the choria/mcollective_choria module which will pull in all it’s dependencies from the Choria project rather than my own Forge.
Still no progress on moving the actual MCollective project forward but I’ve discussed a way to deal with forking the various projects in a way that seems to work for what I want to achieve. In reality I’ll only have time to do that in a couple of months so hopefully something positive will happen in the mean time.
Head over to Choria.io to take a look.