ansible configuration management example

Ansible @ an efficient configuration management tool-Ansible configure management-translation (5), ansible-ansibleDo not reprint advanced Playbook without written permission Extra variablesYou may have seen in our template

worksDelegation of tasksAnsible performs tasks on the configured machine by default and is useful when you have a lot of machines to configure or every device can reach.But. When you need to perform a task on another ansible control machine, you need to use task delegation.The ability to delegate tasks to other machines is performed using Delegate_tokeyword. The fact that is available at the same time will also use the value on the delegated machine.

| Success >> {"Changed": false, "ping": "Pong"}this indicates that's can connect and use Ansible on all the hosts fro M yourinventory. You can use the Same-i argument with Ansible-playbook to run Yourplaybooks with the same inventory.Same as the first chapter. The output looks like this:localhost | Success >> {"Changed": false,"Ping": "Pong"}Example | Success >>

means that it will not run more than once in the role. If it is "yes", it will run again after it has run once, if you do not set this keyword, the default value is no. The same is true for specifying dependencies in a role. You can pass variables, static values, and dynamic values to the current role. The second feature is that variables can have default values. if the yml file is placed under the defult directory, the variables will be passed to the role, but they will be/vars/main. yml file

, the behavior of the copy, the template, and the script modules isslightly altered. Instead of searching for files by looking from the directory in whichthe playbook file is located, Ansible will look for the files in the location of the role.For example, if you are using a role named common , these modules will change to thefollowing behavior:? The copy module will look for files in roles/common/files .?

parameters. In this way, you can use variables to load different configurations. For example, if you want to load different nrpe configurations based on different architectures, the Code is as follows: ----Name: Configure nrpe for the right architectureHosts: ansibletestUser: RootTasks:-Name: copy in the correct nrpe Config FileCopy: src = files/nrpe. {ansible_architecture}. confDeST =/etc/Nagios/nrpe. cfg In the copy and template modules,

/{{ ansible_hostname }} force=yesurl=http://{{ ansible_hostname }}/diagnostic/configdelegate_to: localhostIf you are delegating to the localhost , you can use a shortcut when defining theaction that automatically uses the local machine. If you define the key of the actionline as local_action , then the delegation to localhost is implied. If we were tohave used this in the previous example, it would be slightly shorter and look like this:---- name: Fet

Do not reprint advanced playbook without written permission Extra variablesYou may have seen in our template example in the previous chapter that we used avariable called group_names . This is one of the magic variables that are provided byAnsible itself. At the time of writing there are seven such variables, described in thefollowing sections. External variables You have seen in the previous template example