Configuration RHCE

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)
Create ansible.cfg at /home/devops/ansible/

2. Create yum.yml playbook for repos

Repository 1

EX294_BASE repo
Description = EX294 base software
BaseURL = http://content/rhel9.0/x86_64/dvd/BaseOS
GPG signature enabled
GPG key = RPM-GPG-KEY-redhat-release
Repository enabled

Repository 2

EX294_STREAM repo
Description = EX294 stream software
BaseURL = http://content/rhel9.0/x86_64/dvd/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. Ansible Content Collections

http://172.25.250.14/collection/ansible-posix-2.0.0.tar.gz
Install system roles collection from http://content/Rhce/redhat-rhel_system_roles-1.0.0.tar.gz

5. RHEL System role - timesync.yml

Run on all nodes
Use timesync role
Active NTP provider
Time Server = 172.25.254.254 / classroom.example.com
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
create a playbook called /home/devops/ansible/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
Complete 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/admin/ansible/ansible/lv.yml that runs on all managed nodes that does the following:

The logical Volume is Created in the research volume group
Creates a Logical volume with these requirements: - The Logical volume is created in the datavolume 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 research 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/admin/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

Create a playbook called /home/admin/ansible/deploy-haproxy.yml
The playbook contains a Play that runs on balancer host Group and uses the balancer role.
This role to configure load balancer web Server request between hosts in the webserver host Group.
Browsing to host in the balancer host Group for http://servera.lab.example.com then it should give below Output: Welcome to serverb.lab.example.com on 172.25.250.11
Reloading the browser produces Output from the alternet webserver: Welcome to serverc.lab.example.com on 172.25.250.12
The playbook contains a Play that runs on webservers hostgroup and use the phpinfo role.
Browsing to host in the webservers host Group with the url URL/hello.php then it should give below Output: Hello PHP World from FQDN
For example Browsing to http://serverb.lab.example.com/hello.php produces the following Output: Hello PHP World from serverb.lab.example.com
Note: along with various Details of the PHP configuration include the Version of PHP that is installed. Similary, Browsing to http://serverc.lab.example.com/hello.php produces the following Output: Hello PHP World from serverc.lab.example.com Note: along with various Details of the PHP configuration include the Version of PHP that is installed.

Create a playbook called /home/admin/ansible/webconten.yml as follows:
one play runs managed node in the dev hostgroup
Create the Directory /webdev with the following requirement:
Membership in the webdev Group
it has regular permissions: owner=r+w+x, group=r+w+x, other=r+x
it has Special pemission: set Group GID
Symbolically link /var/www/html/webdev to /webdev
Create the file /webdev/index.html with a single line of text that reads: Development
Browsing this Directory on host in the dev host Group (for example http://serverd.lab.example.com/webdev/) produces following Output: Development

Note: - Need to check the webdev Group is exists or not if not create it. (some time question as about apache in place of webdev Group. in that case, we don't Need to create apache Group ist already there by Default.

another Play runs managed node in the test hostgroup>

Create the Directory /opsmgr with the following requirement:

- Membership in the 'opsmgr' Group

it has regular permissions: owner=r+w+x, group=r+w+x, other=r+x

it has Special pemission: set Group GID