+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ In this module we will be talking about ansible module called "setup" which is used to gather information about modules, The file module for a variety of different file based operations. We will look at the color notation used at the ansible execution . And how it relates to the key feature of Ansible called "Idempotency" We will be using the We will be using the copy module and the command module, Ansible.doc to quickly understand the options available while using ansible modules . Used for gathering facts about playbooks. $ ansible centos1 -m setup $ ansible centos1 -m setup | more We can see information about devices . loads of information that get gathered here as facts , Using the file module using the combination of paths and states , path to the file being managed...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ YAML +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ We can take the power of Ansible to the next level by the use of its scripting functionality known as playbooks. A playbook allows us to perform many actions across a multitude of systems Ansible playbooks can be written in both YAML and JSON. Ansible is a python program It is interesting to how Ansible will interpret YAML as Python . There is an excellent tool that uses the same python module that ansible uses pyaml . And it will dynamically convert from python to YAML. Not to be found now : http://yaml-online-parser.appsppot.com You can use this command line utility that I am using or you can chose the online tool by pull jar as above. Lets take a look at revision 1
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Ansible Architecture and Design Ansible Inventory How can we provide connectivity to our Ansible hosts via root There is a directory for each of these sections As you can see there is a directory for each of these sections essentially we can move to each directory and run ansible from each directory . Currently our setup is quite simple we are connected as pact user connect to controller machine and using ansible as pack user connected to the end points. We are going to configure Ansible so that we can have *root* connectivity for all of our end points. The centos systems are pretty simpler . we have "ansible_user" variable set for centos hosts stating the user we will use for connectivity is root. $ ansible all -m ping the variable ansible_user hosts fails as we havent s...
Comments
Post a Comment