stable diffusion, img2img with controlnet:
low poly, paper craft origami parrot, illustration, studio lighting
# Install ansible and ara in a virtualenv
python3 -m venv ~/.ara/venv
pip install ansible ara[server]
# Run a playbook with ara enabled
export ANSIBLE_CALLBACK_PLUGINS=$(python3 -m ara.setup.callback_plugins)
# Check it out in your terminal
ara playbook list
# or in your browser: http://127.0.0.1:8000
This new version features a refresh of the built-in web interface including an update of Bootstrap from 4.6.0 to 5.3.0.
It lifts the supported version of Django up to the latest LTS, 4.2, and raises the minimum version of Python to >=3.8 as a result.
There’s also bug fixes and new features.
This blog post will highlight some of the changes since ara 1.6.1 but for the full list, see:
You can also catch up on the changelog and release notes for every version until now in the documentation.
A refresh for the UI
A pull request almost two years in the making (ok, with breaks in-between): a long overdue refresh including an update of the bootstrap CSS framework.
Just about every page needed to be fixed and it was a good opportunity to take what was there, clean it up a bit and make it more consistent.
No more bootswatch and jquery
In 1.7.0, ara switches to the default light theme from Bootstrap 5 along their newly included dark theme. This avoids the need to load an extra CSS file and makes it easier to eventually implement a setting in case users want different themes:
(Tested just by replacing bootstrap.min.css)
New light and dark themes
In both cases, the blue header is gone, there’s less green and links are blue like in the 1990’s.
Here’s a short video comparing the light themes:
Another short video, this time comparing the dark themes:
The text, links and buttons are generally bigger – they should be easier to read and click:
Thanks to helmo we now have coloured diffs when recording with
A mobile UI in a pinch
Leveraging Bootstrap means we get some amount of mobile responsiveness out of the box.
It has improvements over the previous version, though it’s certainly not perfect, it’s there and it works:
New recording settings
We have three new settings for ara’s Ansible callback plugin thanks to new contributors to the project.
By default, ara automatically detects the controller hostname and the user who is running a playbook in order to record them.
phemmer added two settings,
ARA_RECORD_USER_NAME, in order to override and customize their values.
ara also records the content of every task result but in some cases it’s either not necessary or desireable in order to decrease risks of leaking secrets.
tomsiewert added the setting
ARA_RECORD_TASK_CONTENT which can be set to false in order to prevent ara from recording task content.
That’s it for now, what’s next ?
There is no shortage of improvement opportunities but some bigger items in the not-too-distant future…
We’ve also been trying to write a Prometheus exporter for alerting and putting Ansible metrics in pretty graphs because why not:
Want to contribute, chat or need help ?
The prometheus exporter kind of works but we would welcome the help of anyone interested to look into that with us, please reach out !
The web interface has a lot of untapped potential and we would certainly appreciate contributors to improve the UI and UX.
We could use your help and we can help you get started.
The project community hangs out on IRC, Slack and Matrix.