This is a follow up to the previous commit -- now that there are no
longer any jobs that use these nodesets we can remove them here.
Change-Id: I84b5554184cfdbc006ed970559c4cb3e47a02768
They should have been removed in f4a40db53ec685d57947cca0cad0c891433c9b43
that also removed roles but I forgot about them.
Change-Id: Ic639156f6f2fc3e3ef7db9747dd32cc572e57c2e
These have been moved out to an Ansible collection:
https://github.com/ansible-community/ara-collection
Leaves a README.rst to tell users where to look for for a while.
Because the existing Zuul CI jobs relied on these roles, this also
changes the Zuul config to use the jobs that are used to test the
collection instead.
Related: https://github.com/ansible-community/ara/issues/71
Change-Id: I1c573d8677d36cfd431101f1f181253c1cce3bc1
The links provided by the UI when filtering or sorting by date/duration
didn't carry existing search arguments so if you sorted or filtered, you
lost existing search queries.
The sorting and filtering is now handled by the same django form which
takes care of keeping our arguments around.
Fixes: https://github.com/ansible-community/ara/issues/201
Change-Id: I03af5baaadd7fd731133db3ad83dee74ed4813ba
It's useful to filter status to failed/unreachable for failed playbooks
but filtering for changed results by default often leads to no results
being shown at all in the case of playbooks without changes.
I find myself clicking "clear filter" more times than the default filter
being useful so let's not do that anymore.
Change-Id: I7635a2282e1e12bbab4224960d36055a80be8f50
ara-web isn't currently in a state where we can demo it and it tends to
confuse users so remove it's mention for now.
Given that we no longer have a distinction between api and web, use
plain "demo.recordsansible.org" instead.
Change-Id: I788d5d457fc011364a7839172fbadc5c24de76d4
We were not including the pygments css file in the result details page
so despite the right css classes being set by the format_data filter, we
didn't have any highlighting.
Change-Id: Iae20c9ec82164bb24b69e4c056aec281b7ac40dc
Results for a task which involves a loop are typically stored in a
'results' list. This renders these results like normal ones inside the
'results' key instead of being raw json.
Change-Id: I3ec57d5f4fbe94809e7feef75b9f7f9e423a8a8b
The controller fqdn that ran the playbook is now recorded and can be
searched for both in the UI and the CLI.
Fixes: https://github.com/ansible-community/ara/issues/193
Change-Id: I53e8d158fc3b6ba7a16582234aaa2542eab5fcdc
- add debug logging and recover the log files
- discard database and settings file between container tests
Change-Id: Ifd8a8d544c4c550873a9eb586de038710a60ba05
Threading is prone to database lock exceptions when using the default
database backend (sqlite) and so disable it by default.
Users can enable threading when using mysql or postgresql by specifying
the ARA_CALLBACK_THREADS environment variable or callback_threads in
ansible.cfg.
Fixes: https://github.com/ansible-community/ara/issues/195
Change-Id: I80edfd6268684722c2783e01323355d791c19b9d
- Install which (because it's sometimes not installed by default)
- Fedora 33 images are out now, build and publish them
- Remove PyYAML workaround that is no longer necessary
Fixes: https://github.com/ansible-community/ara/issues/192
Change-Id: Ia64455655cd37299d84c657a3dc87e079f92f790
rather than a tz-naive stamp. ara drf should do the right thing with
timezones based on the now included iso tz.
Change-Id: I64e486e9c7d9ebe8ec48f9565ac42b3eecd9a788
Run benchmark with default settings:
tox -e benchmark
Run benchmark with specified number of hosts or tasks:
tox -e benchmark -- -e benchmark_host_count=50
Change-Id: I295967c6fb39ec5e02a80b863bde4c57fc6f2139
Variable precedence is higher in the playbook than from the job vars
which are provided through the inventory.
Use another variable and default properly instead.
Change-Id: I8c5cf72c78ea01ba1bc0a6fef2f9499837e9b262
With the coming rate limiting on docker hub, users might want to have an
alternative to pull from.
Change-Id: I35714fdd069165c9766371c83393aa431237ccec
When using >=2 threads with the offline client, the playbook execution
can sometimes, but not always, lock up.
The issue doesn't appear to reproduce when using a single thread so do
that for now.
Otherwise, default to 4 threads as a more conservative default to
prevent hitting urllib's connectionpool max.
Change-Id: I2b0c57f784be36685619d80549fa626c385b0e04
There are some parts of the callback that need to be synchronous because
they rely on an object that must be created before, for example.
However, for the parts that don't need to run synchronously, thread them
so we don't block Ansible from running.
This results in a dramatic performance increase.
Related: https://github.com/ansible-community/ara/issues/171
Change-Id: I4317d1d1175a5286704b04f57de9ef73fa911a3a
At some point the default was changed from ara-api to ara-report and so
it makes sense to use ara-report in the examples instead of ara-api.
Change-Id: I9962565c8466e9afad01b80e2922af1f154a5f8b
We had this data but we didn't include it for some reason.
It's at least as much relevant as the other numbers displayed so include
it.
Change-Id: I9b95a2cbe2bbee5bba1392e2d7d4afd6eebc6d03