RH294 Ch 9: Content Collections and RHEL System Roles

Modules outside ansible-core come from collections. utility serves collection tarballs at `http://utility/collections/` (no internet needed). Install the ones you need into the project, then use them — and a RHEL system role — on node1 (`dev`) and node2 (`prod`).

Tasks

1. Write ~/ansible/collections/requirements.yml that installs ansible.posix and community.general from http://utility/collections/, and install them into ~/ansible/collections.
2. Set collectionspath in ~/ansible/ansible.cfg so it searches ./collections first and still finds the system collections in /usr/share/ansible/collections.
3. With community.general.inifile (FQCN in your playbook), set option port to 8080 in section [web] of /etc/webasha.ini on all nodes.
4. With ansible.posix.firewalld, allow the http service on the prod hosts, both permanently and in the running firewall.
5. Use the RHEL system role redhat.rhelsystemroles.timesync to make all nodes sync time from utility.lab.example.com with iburst.