1,576
edits
Changes
m
Protected "OPS635-lab-ansible": OER transfer ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
[[Category:OPS635]][[Category:OPS635-Labs]][[Category:peter.callaghan]]
=OPS635 Lab 3: System Configuration Management using Ansible=
==Overview==
In an enterprise environment, the existence of different hardware and operating systems running on production servers is very common. You may find the same software running on different OSes and even different hardware platforms. To manage the software configuration on different platforms by using a script, your script would have to be aware of and account for their differences. Your scripts would need to be written in way that they know how to query the operating environment and execute the appropriate installation and configuration actions based on the operating environment it is running on.
*Install Ansible on one of your VMs (we will refer to that as the server).
**Current installation instructions can be found [[OPS635_installation_ansible|here]].
*If you have not already done so, create an SSH key-pair for the a '''non-root user on your server''' and transfer the public portion of it to another VM (we will refer to it as the client). Ensure that you can use it to ssh to a non-root account on the client without by entering a passwordpassphrase.
*Modify the inventory file on your server to include the fully qualified domain names of client VM.
*Use the '''setup module''' to verify that your Ansible server can run plays on your client VM.
**The firewall-cmd service is running and enabled.
**Firewalld is not allowing the mdns or cockpit services. Remember to also make this permanent.
*Use the terminal on the client to confirm these changes worked.
*While these changes are not important to the service you will configure using a playbook in the next investigation, they give you some experience using one-off commands in ansible.