Shulou(Shulou.com)06/03 Report--

I. playbook cycle

# vi / etc/ansible/while.yml / / add the following-hosts: yw02 user: root tasks:-name: change mode for files file: path=/tmp/ {{item}} mode=600 with_items:-1.txt-2.txt-3.txt

Note: here is a file module, followed by a path, if it is a file, you can write / tmp/1.txt, multiple files, you can use a loop, with_items for the loop object

Execute: ansible-playbook while.yml

Error report: the other machine does not have these three files, add state=touch before mode and create one.

Execute again: ansible-playbook while.yml

If the execution is successful, create it first, and then define its permissions.

II. Condition judgment in playbook

# vi / etc/ansible/when.yml / / add the following-hosts: testhost user: root gather_facts: True tasks:-name: use when shell: touch / tmp/when.txt when: ansible_ens33.ipv4.address = = "192.168.149.131"

Description:

Here hosts writes testhost, but writing a machine is meaningless.

The facts is collected here, and this line can also be deleted. The default is the collection, which will be used next.

Ansible yw02-m setup can view all the facter information.

When is a conditional judgment, and only when this condition is true will the shell be executed.

Find out from the information collected by facts whether the address of the ipv4 under ansible_ens33 is the IP. If the condition is true, shell is executed. If there is no such condition, it will be executed directly.

When there is grading, those below each level should be dotted, and if there is no grading, the equal sign will be written directly.

When is not only for facts, but also for other situations, such as determining the existence of files and directories.

"ansible_facts": / / the most general level of "ansible_all_ipv4_addresses": [/ / the judgment condition starts at this level. Here is an array listing all the ipv4, but there are still two ipv6 under it. To judge, you need to judge two, so this is not what you want. "192.168.98.134", "192.168.149.132"],... "ansible_ens33": {"active": true, "device": "ens33",. "hw_timestamp_filters": [], "ipv4": {"address": "192.168.149.132", "broadcast": "192.168.149.255", "netmask": "255.255.255.0", "network": "192.168.149.0"} ... [root@fuxi01 ansible] # ansible-playbook when.ymlPLAY [testhost] * * TASK [Gathering Facts] * * fatal: [yw02]: UNREACHABLE! = > {"changed": false "msg": "Failed to connect to the host via ssh: ssh: connect to host yw02 port 22: No route to host" "unreachable": true} ok: [yw03] ok: [127.0.0.1] TASK [use when] * * * skipping: [127.0.0.1] [WARNING]: Consider using the file module with state=touch rather than running 'touch'. If you need to use command because file isinsufficient you can add 'warn: false' to this command task or set' command_warnings=False' in ansible.cfg to get rid of thismessage.changed: [yw03] PLAY RECAP * * * 127.0.0.1: ok=1 changed=0 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 yw02: ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0 yw03: Ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0

3. Handlers in playbook

After task, some actions to be performed after the server changes, for example, after we modify the configuration file, we need to restart the service.

# vi / etc/ansible/handlers.yml// add the following-name: handlers test hosts: yw02 user: root tasks:-name: copy file copy: src=/etc/passwd dest=/tmp/aaa.txt notify: test handlers handlers:-name: test handlers shell: echo "111111" > > / tmp/aaa.txt

Note: the following handlers-related operations will not be called until the copy module is really successful. In other words, if the content of 1.txt and 2.txt are the same, the shell-related commands in handlers will not be executed. This is more suitable for the operation of restarting the service after the configuration file changes. Similar to command1 & & command2 (handlers), the handler is not executed until the previous command is executed successfully, which needs to be associated with notify.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.