1. Install and configure Ansible on the control

• Install the required packages
• Default collection dir = /home/devops/ansible/mycollection
• Default roles dir = /home/devops/ansible/roles
• Host inventory = /home/devops/ansible/inventory
• Inventory groups (dev on node1, test on node2, prod node3 and node4, balancers node5, webservers on prod)
• Ansible Automation Platform 2.2 is utility.lab.example.com credentials are username: admin, password: 'redhat'
• Create ansible.cfg at /home/devops/ansible/

2. Create yum.yml playbook for repos

Repository 1

• Name= EX294_BASE
• Description = EX294 base software
• BaseURL = http://172.25.250.14/repo/BaseOS
• GPG signature enabled
• GPG key = RPM-GPG-KEY-redhat-release
• Repository enabled

Repository 2

• Name= EX294_STREAM
• Description = EX294 stream software
• BaseURL = http://172.25.250.14/repo/AppStream
• GPG signature enabled
• GPG key = RPM-GPG-KEY-redhat-release
• Repository enabled

3. Install packages (packages.yml)

• create a playbook called /home/devops/ansible/packages.yml and perform the following Tasks:
• Install php & mariadb on dev, test, prod
• Install RPM Development Tools on dev
• Update all packages on dev

4. Installing Ansible Content Collections installs the collection in the local collections directory. Download tar file url given on exam http://content.lab.example.com/collection

• ansible-posix-2.1.0.tar.gz
• redhat-rhel_system_roles-1.0.0.tar.gz
• community-general-11.2.1.tar.gz

5. RHEL System role - timesync.yml

• Run on all nodes
• Use timesync role
• Active NTP provider
• Time Server = 172.25.250.14 :
• Enable iburst

6. Install roles using Ansible Galaxy

• requirements.yml created
• Install to /home/devops/ansible/roles
• Role balancer from http://172.25.250.14/rhce/balancer.tgz
• Role phpinfo from http://172.25.250.14/rhce/phpinfo.tgz

7. Create and use a role (apache)

• Role apache created
• httpd installed, enabled, started
• Firewall installed enabled with web access rule
• a template file index.html.j2 exists and is used to create the file /var/www/html/index.html with the message: 'Welcome to HOSTNAME on IPADDRESS'
• Where HOSTNAME is fully qualified domain name.
• create a playbook name newrole.yml : runs on host in the webservers host group

8. Generate hosts file (hosts.yml)

• playbook /home/devops/ansible/hosts.yml
• Download an initial template file from http://172.25.250.14/hosts.j2 to /home/devops/ansible
• Download an initial template file from http://172.25.250.14/hosts.yml to /home/devops/ansible
• Complete hosts.j2 the template file so that it can be used to generate a file with a line for each host in the same Format as /etc/myhosts: 172.25.250.9 node1.lab.example.com node1
• Each host line like /etc/myhosts format

9. Cronjob (crontab.yml)

• Create a cronjob for user natasha in all nodes, the playbook Name crontab.yml and the Job Details are:
• User = natasha
• Every 2 min → logger "EX294 in progress"

10. SELinux (selinux.yml)

• Create a playbook named selinux.yml
• Use RHEL system role
• Set selinux mode as enforcing in all managed nodes

11. Rekey an Ansible Vault

• Download the Ansible vault file from http://172.25.250.14/salaries.yml to /home/devops/ansible/salaries.yml
• Current vault password = 1212
• New vault password = redhat
• File remains encrypted
• The vault file remains in an encrypted state with the new Password

12. Create & use a logical Volume Create a playbook called /home/devops/ansible/ansible/lv.yml that runs on devhost managed nodes that does the following:

• The logical Volume is Created in the data volume group
• Creates a Logical volume with these requirements: - The Logical volume is created in the devhost Group - The Logical volume name is 'lvdata' - The Logical volume size is 1500 MiB
• Format the Logical Volume with the ext4 file System
• if the requested Logical volume size cannot be created, the error message "could not create Logical volume of that size" should be displayed and size 800 MiB should be used instead
• if the volume data does not exist, the error message "volume Group does not exist" should be displayed * Does Not mount the Logical volume in any way
• should be displayed "Does NOT mount the logical volume in any way."

13.creat user accounts.

• Download a list of user to be created from http://172.25.250.14/user_list.yml
• Using the Password vault /home/devops/ansible/locker.yml created elsewhere in this exam, create a playbook called /home/admin/ansible/users.yml:
• User with Job description of developer should be:
• Create on managed node in the dev and test host group
• Assigned the Password from the pw_developer variable
• A member of supplementary Group devops
• * User with a Job description of Manager should be:
• Create on managed node in the prod host Group
• A member of supplementary Group opsmgr
• Password should use the SH512 has format
Assigned the Password from the pw_manager variable

14. Create a Password vault:

Create an ansible vault to store user Password as follows:

• The Name of the vault is /home/admin/ansible/locker.yml
• The vault contains two variables with names: - pw_developer with value Imadev: - pw_manager with value Imamgr
• The Password to encrypt and decrypt the vault is 'redhat'
• The password is stored in the file /home/admin/ansible/secret.txt

15. Modify the file Content

• Create a playbook called /home/devops/ansible/issue.yml
• The Playbook runs on all managed hosts
• The playbook replaces the Content of /etc/issue with a single line of text as follows:
• On hosts in the dev hostgroup, the line reads: Development
• On hosts in the test hostgroup, the line read: Test
• On hosts in the prod hostgroup, the line read: Production

16. use roles from Ansible Galaxy

17.Create a playbook webcontent.yml and it should run on dev group.

18.Create hwreport.yml on all groups.