Linux demo updates bblasco pt1 (#45)

* Improved description of Ansible group to address issue #29

* Ensured "at" package is present rather than latest for Issue #31

* Added timesync as a second example role to run (Issue #37)

Co-authored-by: Benjamin Blasco <bblasco@redhat.com>

linux/README.md

@@ -51,7 +51,7 @@ Navigate to the Credentials section and update the `Insights Inventory` credenti
 Edit the `Linux / System Roles` job to include the list of roles that you wish to apply and the variables applicable for each role. See documentation [here](https://console.redhat.com/ansible/automation-hub/repo/published/redhat/rhel_system_roles) for configuring System Roles.
 
 ## Suggested Usage
-**Linux / Register** - Use this job to register systems to Red Hat Insights for showing Advisor recommendations and dynamic inventory.
+**Linux / Register** - Use this job to register systems to Red Hat Insights for showing Advisor recommendations and dynamic inventory.  Note that the "Ansible Group" will create an AAP inventory group, as well as tag hosts with that group name in Insights.
 
 **Linux / Troubleshoot** - Use this job to show incident response troubleshooting and basic running of commands with an Ansible Playbook.
 
@@ -65,11 +65,24 @@ Edit the `Linux / System Roles` job to include the list of roles that you wish t
 
 **Linux / Podman Webserver** - Use this job show managing individual containers with Podman via an Ansible Playbook.
 
-**Linux / System Roles** - This job demonstrates running [RHEL System Roles with AAP. See the documentation [here](https://console.redhat.com/ansible/automation-hub/repo/published/redhat/rhel_system_roles) for how to configure system roles with variables by editing the extra_vars on the job template. Example:
+**Linux / System Roles** - This job demonstrates running [RHEL System Roles with AAP. See the documentation [here](https://console.redhat.com/ansible/automation-hub/repo/published/redhat/rhel_system_roles) for how to configure system roles with variables by editing the extra_vars on the job template.
+
+Example 1:
 ```
 system_roles:
   - selinux
 
 selinux_state: enforcing
 ```
+
+Example 2 (less invasive, and runs faster):
+```
+system_roles:
+  - timesync
+
+timesync_ntp_servers:
+  - hostname: pool.ntp.org
+    pool: yes
+    iburst: yes
+```
 **Linux / Compliance** - Apply compliance profile hardening configuration from [here](https://galaxy.ansible.com/RedHatOfficial). BE AWARE: this could have unintended results based on the current state of your machine. Always test on a single machine before distributing at scale. For example, AWS instances have NOPASSWD allowed for sudo. Running STIG compliance without adding `sudo_remove_nopasswd: false` to extra_vars on the job template will lock you out of the machine. This variable is configured on the job template by default for this reason.

linux/setup.yml

@@ -81,7 +81,7 @@ controller_templates:
             - QA
             - Prod
           required: true
-        - question_name: Ansible Group
+        - question_name: Ansible Inventory Group (and Insights tag) to be created
           type: text
           variable: ansible_group
           required: true

linux/temp_sudo.yml

@@ -18,7 +18,7 @@
     - name: Check Cleanup package
       yum:
         name: at
-        state: latest
+        state: present
 
     - name: Check Cleanup Service
       service: