2024-11-25 18:24:56 +10:00
|
|
|
---
|
2026-03-24 15:27:46 -04:00
|
|
|
# You can use: --extra-vars="target=blah.fp.o" to skip the prompts.
|
|
|
|
|
#
|
|
|
|
|
# You _might_ decide that --limit looks cleaner and you use that a lot already,
|
|
|
|
|
# so you can "tweak" the playbooks to use it instead. You would be wrong.
|
|
|
|
|
# Then you might decide to ask AI how to do it, and it'll give you an answer
|
|
|
|
|
# but you'll still be wrong.
|
|
|
|
|
#
|
2025-08-05 15:21:04 -04:00
|
|
|
# Note that someone probably wants to run:
|
2026-03-24 15:27:46 -04:00
|
|
|
# ansible/scripts/dnf-update-y.sh
|
|
|
|
|
# ...before an outage.
|
|
|
|
|
# NOTE: that rebooting more than one vmhost at once isn't
|
2025-08-05 15:21:04 -04:00
|
|
|
# easily safe, because some vmhost will want another to be up while they reboot.
|
2026-03-24 15:27:46 -04:00
|
|
|
#
|
2025-08-05 15:21:04 -04:00
|
|
|
# Also:
|
2025-08-05 16:39:43 -04:00
|
|
|
# ansible ... 'staging:!copr*:!openqa*:!ocp*:!worker*'
|
2025-08-05 15:21:04 -04:00
|
|
|
# could be used for staging, but it's not that big.
|
|
|
|
|
|
2019-04-09 19:50:36 +00:00
|
|
|
- import_playbook: /srv/web/infra/ansible/playbooks/vhost_update.yml
|
|
|
|
|
- import_playbook: /srv/web/infra/ansible/playbooks/vhost_reboot.yml
|