Ad-Hoc Ansible Commands 10 Questions

Most Updated & Latest Questions Question #:1 Create a file calledadhoc.sh in/home/sandy/ansible which will use adhoc commands to set up a new repository. The name of the repo will be 'EPEL' thedescription 'RHEL8' the baseurl is'https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp'there is no gpgcheck, but you should enable the repo. * You should be able to use an bash script using adhoc commands to enable repos. Depending on your lab setup, you may need to make this repo "state=absent" after you pass this task. See the Explanation for complete Solution below. Explanation chmod0777adhoc.sh vim adhoc.sh #I/bin/bash ansible all -m yum_repository -a 'name=EPEL description=RHEL8 baseurl=https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp gpgcheck=no enabled=yes' Question #:2 Create a jinja template in /home/sandy/ansible/ and name it hosts.j2. Edit this file so it looks like the one below. The order of the nodes doesn't matter. Then create a playbook in/home/sandy/ansible calledhosts.yml and install the template on dev node at/root/myhosts See the Explanation for complete Solution below. Explanation Solution as: Question #:3 Install and configure ansible Userbob has been created on your control node. Give him the appropriate permissions on thecontrol node. Install the necessary packages to run ansible on the control node. Create a configuration file /home/bob/ansible/ansible.cfg to meet the following requirements: • The roles path should include /home/bob/ansible/roles, as well as any otherpath that may be required for the course of the sample exam. • The inventory file path is /home/bob/ansible/inventory. • Ansible should be able to manage 10 hosts at a single time. • Ansible should connect to all managed nodes using the bobuser. Create an inventory file for the following five nodes: nodel.example.com node2.example.com node3.example.com node4.example.com node5.example.com Configure these nodes to be in an inventory file where node1 is a member of groupdev. nodc2 is a member of group test, nodc3 is a member of groupproxy, nodc4 and node 5 are members of groupprod. Also,prod is a member of group webservers. See the Explanation for complete Solution below. Explanation In/home/sandy/ansible/ansible.cfg [defaults] inventory=/home/sandy/ansible/inventory roles_path=/home/sandy/ansible/roles remote_user= sandy host_key_checking=false [privilegeescalation] become=true become_user=root become_method=sudo become_ask_pass=false In /home/sandy/ansible/inventory [dev] node 1 .example.com [test] node2.example.com [proxy] node3 .example.com [prod] node4.example.com node5 .example.com [webservers:children] prod Question #:4 Create the users in the fileusersjist.yml file provided. Do this in a playbook called users.yml located at /home/sandy/ansible. The passwords for these users should be set using the lock.yml file from TASK7. When running the playbook, the lock.yml file should be unlocked withsecret.txt file from TASK 7. All users with the job of 'developer' should be created on thedev hosts, add them to the group devops, their password should be set using thepw_dev variable. Likewise create users with the job of 'manager' on theproxy host and add the users to the group 'managers', their password should be set using the pw_mgr variable. See the Explanation for complete Solution below. Explanation ansible-playbook users.yml –vault-password-file=secret.txt Question #:5 Create a file called specs.empty in home/bob/ansible on the local machine as follows: HOST= MEMORY= BIOS= VDA_DISK_SIZE= VDB_DISK_SIZE= Create the playbook /home/bob/ansible/specs.yml which copies specs.empty to all remote nodes' path/root/specs.txt. Using the specs.yml playbook then edit specs.txt on the remote machines to reflect the appropriate ansible facts. See the Explanation for complete Solution below. Explanation Solution as: Question #:6 Create a playbook /home/bob /ansible/motd.yml that runs on all inventory hosts and docs the following: The playbook should replaee any existing content of/etc/motd in the following text. Use ansible facts to display the FQDN of each host On hosts in the dev host group the line should be "Welcome to Dev Server FQDN". On hosts in the webserver host group the line should be "Welcome to Apache Server FQDN". On hosts in the database host group the line should be "Welcome to MySQL Server FQDN". See the Explanation for complete Solution below. Explanation /home/sandy/ansible/apache.yml /home/sandy/ansible/roles/sample-apache/tasks/main.yml Question #:7 Create an empty encrypted file calledmyvault.yml in /home/sandy/ansible and set the password to notsafepw. Rekey the passwordto iwejfj2221. See the Explanation for complete Solution below. Explanation ansible-vault create myvault.yml Create new password: notsafepw Confirm password: notsafepwansible-vault rekeymyvault.yml Current password: notsafepw New password: iwejfj2221 Confirm password: iwejfj2221 Question #:8 Create a playbook calledwebdev.yml in'home/sandy/ansible . The playbook will create a directory Avcbdev on dev host. The permission of the directory are 2755 and owner is webdev. Create a symbolic link from /Webdev to /var/www/html/webdev. Serve a file from Avebdev7index.html which displays the text "Development" Curlhttp://node1.example.com/webdev/index.htmlto test See the Explanation for complete Solution below. Explanation Solution as: Question #:9 Create a file in/home/sandy/ansible/ calledreport.yml. Using this playbook, get a filecalled report.txt (make it look exactly as below). Copy this file over to all remote hosts at/root/report.txt. Then edit the lines in the file to provide the real informationofthehosts. If a disk does not exist then write NONE. See the Explanation for complete Solution below. Explanation Solution as: Question #:10 In /home/sandy/ansible/create a playbook calledlogvol.yml. In the play create a logical volume calledIv0 and make it of size 1500MiB on volume groupvgO If there is not enough space in the volume groupprint a message "Not enough space for logical volume" and then make a 800MiB Iv0 instead. If the volume group still doesn't exist, create a message"Volume group doesn't exist" Create xfs an filesystem on Iv0 all logical volumes. Don't mount the logical volume. See the Explanation for complete Solution below. Explanation Solution as: