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

Brief introduction

1. The process of ansible installation and deployment is very simple, and the learning curve is very flat.

2. There is no need to install the client separately, the knowledge can be made use of the existing SSHD service (protocol).

3. Based on Python development, it integrates the advantages of many operation and maintenance tools (puppet, chef, func, fabric), and realizes the functions of batch system configuration, batch program deployment, batch running commands and so on.

Characteristics of ansible

1. The deployment is simple. You only need to deploy the Ansible environment on the main control side, and the controlled side does not need to do anything.

2. The SSH protocol is used by default to manage the device.

3. There are a large number of routine operation and maintenance operation modules, which can realize most of the daily operations.

4. Simple configuration, powerful function and strong expansibility

5. Support API and custom modules, which can be easily extended through Python

6. Customize powerful configuration and state management through Playbooks

7. Lightweight, there is no need to install agent on the client side. When updating, you only need to make an update on the operator.

8. Provide a powerful and operational Web management interface and REST API interface-AWX platform.

Architecture diagram

Ansible:Ansible core program. HostInventory: records host information managed by Ansible, including port, password, ip, etc. Playbooks: "script" YAML format file, where multiple tasks are defined in one file, defining which modules the host needs to call to complete the function. CoreModules: core module, the main operation is to call the core module to complete the management task. CustomModules: custom module, complete the core module can not complete the function, support multiple languages. ConnectionPlugins: connection plug-in, Ansible and Host communication using ansible task execution mode Ansible system by the control host to the managed node operation can be divided into two categories, namely adhoc and playbook:

Ad-hoc mode (point-to-point mode)

Using a single module, batch execution of a single command is supported. The ad-hoc command is a command that can be entered quickly and does not need to be saved. It is equivalent to a word shell in bash.

Playbook mode (script mode)

It is not only the main management mode of Ansible, but also the key to the powerful function of Ansible. Playbook completes a class of functions through multiple task collections, such as the installation and deployment of Web services, batch backups of database servers, and so on. You can simply think of playbook as a configuration file by combining multiple ad-hoc operations.

Ansible execution process

The simple understanding is that when Ansible is running, it first reads the configuration in ansible.cfg, obtains the list of management hosts in Inventory according to the rules, executes the configuration tasks in these hosts in parallel, and finally waits for the returned results.

Real fuck

Environment

Management side: CentOS 7-2 192.168.18.147 managed side 1:CentOS 7-3 192.168.18.128 managed side 2:CentOS 7-4 192.168.18.148

Management side:

[root@localhost ~] # systemctl stop firewalld.service [root@localhost ~] # setenforce 0 [root@localhost ~] # yum install epel-release-y [root@localhost ~] # yum install ansible-y [root@localhost ~] # ansible-- versionansible 2.9.2 [root@localhost ~] # yum install tree-y [root@localhost] # tree / etc/ansible//etc/ansible/ ├── ansible.cfg # configuration file ├── hosts ansible.cfg roles1 directory 2 Files` configure host list` [root@localhost ~] # vim / etc/ansible/hosts# insert the following under line 24 [webserver] 192.168.18.128 [MySQL] 192.168.18.148` generate key pair `[root@localhost ~] # ssh-keygen-t rsaGenerating public/private rsa key pair.Enter file in which to save the key (/ root/.ssh/id_rsa): # enter Created directory'/ root/.ssh'. Enter passphrase (empty for no passphrase): # enter password: abc123Enter same passphrase again: # enter password again: abc123Your identification has been saved in / root/.ssh/id_rsa.Your public key has been saved in / root/.ssh/id_rsa.pub.The key fingerprint is:SHA256:5RvIVqbI9hscNK1Y4YivNnnUEgQeNfNm/WJcBXr8jWc root@localhost.localdomainThe key's randomart image is:+--- [RSA 2048]-+ | oo=. . | |. + * + o. | | o o O B + | | o @ @ +. O | | OS *. O E | | = o + o | | =. +. | |. O o | |. | | +-[SHA256]-+ `Keypair location `[root@localhost ~] # ls-la total usage 56.drwxMurray. " 2 root root 38 January 22 17:34. Ssh. Omit multiple lines [root@localhost ~] # cd .ssh / [root@localhost .ssh] # lsid_rsa (private key) id_rsa.pub (public key) `push the key to the managed side 1` [root@localhost .ssh] # ssh-copy-id root@192.168.18.128/usr/bin/ssh-copy-id: INFO: Source of key (s) to be installed: "/ root/.ssh/id_rsa.pub" The authenticity of host '192.168 .18.128 (192.168.18.128) 'can't be established.ECDSA key fingerprint is SHA256:mTT+FEtzAu4X3D5srZlz93S3gye8MzbqVZFDzfJd4Gk.ECDSA key fingerprint is MD5:fa:5a:88:23:49:60:9b:b8:7e:4b:14:4b:3f:cd:96:a0.Are you sure you want to continue connecting (yes/no)? Yes # confirm the link / usr/bin/ssh-copy-id: INFO: attempting to log in with the new key (s), to filter out any that are already installed/usr/bin/ssh-copy-id: INFO: 1 key (s) remain to be installed-- if you are prompted now it is to install the new keysroot@192.168.18.128's password: # enter the root password Number of key (s) added: 1Now try logging into the machine corresponding to the managed end With: "ssh 'root@192.168.18.128'" and check to make sure that only the key (s) you wanted were added.` push the key to the managed end 2` [root@localhost .ssh] # ssh-copy-id root@192.168.18.148/usr/bin/ssh-copy-id: INFO: Source of key (s) to be installed: "/ root/.ssh/id_rsa.pub" The authenticity of host' 192.168.18.148 (192. 168.18.148) 'can't be established.ECDSA key fingerprint is SHA256:mTT+FEtzAu4X3D5srZlz93S3gye8MzbqVZFDzfJd4Gk.ECDSA key fingerprint is MD5:fa:5a:88:23:49:60:9b:b8:7e:4b:14:4b:3f:cd:96:a0.Are you sure you want to continue connecting (yes/no)? Yes # confirm the link / usr/bin/ssh-copy-id: INFO: attempting to log in with the new key (s), to filter out any that are already installed/usr/bin/ssh-copy-id: INFO: 1 key (s) remain to be installed-- if you are prompted now it is to install the new keysroot@192.168.18.148's password: # enter the root password Number of key (s) added: 1Now try logging into the machine corresponding to the managed end With: "ssh 'root@192.168.18.148'" and check to make sure that only the key (s) you wanted were added.

Verify that the key was pushed successfully:

Managed side 1: 192.168.18.128

[root@localhost ~] # systemctl stop firewalld.service [root@localhost ~] # setenforce 0 [root@localhost ~] # cd .ssh / [root@localhost .ssh] # lsauthorized_keys# the key is pushed successfully

Managed side 2:

[root@localhost ~] # systemctl stop firewalld.service [root@localhost ~] # setenforce 0 [root@localhost ~] # cd .ssh / [root@localhost .ssh] # lsauthorized_keys# the key is successfully managed by Ansible module at this time

1. Command module

`View the time of managed side 1 using IP address `[root@localhost .ssh] # ansible 192.168.18.128-m command-a 'date'Enter passphrase for key' / root/.ssh/id_rsa': # enter the key password abc123192.168.18.128 | CHANGED | rc=0 > > 15:53:20 on Sunday, February 2, 2020 CST` use alias to view the time of managed side 2` [root@localhost .ssh] # ansible mysql -m command-a 'date'Enter passphrase for key' / root/.ssh/id_rsa': # enter the key password abc123192.168.18.148 | CHANGED | rc=0 > > 15:55:13 on Sunday, February 2, 2020 to avoid the trouble of always entering the password We can execute the interaction-free agent `[root@localhost .ssh] # ssh-agent bash [root@localhost .ssh] # ssh-addEnter passphrase for / root/.ssh/id_rsa: # enter the key password abc123 Identity added: / root/.ssh/id_rsa (/ root/.ssh/id_rsa) [root@localhost .ssh] # ansible webserver-m command-a 'date'192.168.18.128 | CHANGED | rc=0 > February 2020 16:01:40 CST# on Sunday 02 can directly display the time at this time. All hosts hosts execute the date command `[root@localhost .ssh] # ansible all-a 'date'192.168.18.128 | CHANGED | rc=0 > > 16:21:08 CST192.168.18.148 on Sunday February 02, 2020 | CHANGED | rc=0 > > Sunday, February 2, 2020, 16:21:08 CST

2. Cron module [two states (state): present means added (can be omitted), and absent means removed]

[root@localhost .ssh] # ansible mysql-m cron-a 'minute= "* / 1" job= "/ usr/bin/echo hello" name= "test hello" '192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "envs": [] "jobs": ["test hello"]} [root@localhost .ssh] # ansible mysql-a 'crontab-lump 192.168.18.148 | CHANGED | rc=0 > > # Ansible: test hello*/1 * / usr/bin/echo hello

At this point, we can enter the managed terminal 2 for verification:

[root@localhost .ssh] # crontab-l#Ansible: test hello*/1 * / usr/bin/echo hello you have a new email in / var/spool/mail/root [root@localhost .ssh] # vim / var/spool/mail/rootFrom root@localhost.localdomain Sun Feb 2 16:40:02 2020Return-Path: X-Original-To: rootDelivered-To: root@localhost.localdomainReceived: by localhost.localdomain (Postfix, from userid 0) id 2255A319AE4E Sun, 2 Feb 2020 16:40:02 + 0800 (CST) From: "(Cron Daemon)" To: root@localhost.localdomainSubject: Cron / usr/bin/echo helloContent-Type: text/plain Charset=UTF-8Auto-Submitted: auto-generatedPrecedence: bulkX-Cron-Env: X-Cron-Env: Message-Id: Date: Sun, 2 Feb 2020 16:40:02 + 0800 (CST) hello# the following lines are omitted, generating one per minute

Remove the scheduled task at this point and use absent:

[root@localhost .ssh] # ansible mysql-m cron-a 'name= "test hello" state=absent'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "envs": [], "jobs": []} `[root@localhost ~] # crontab-l

3. User module [user module requests three instructions: useradd, userdel, usermod]

`Create user test01` [root@localhost ~] # ansible all-m user-a 'name=test01'192.168.18.128 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "comment": "", "create_home": true, "group": 1001, "home": "/ home/test01", "name": "test01" "shell": "/ bin/bash", "state": "present", "system": false, "uid": 1001} 192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "comment": "," create_home ": true," group ": 1001 "home": "/ home/test01", "name": "test01", "shell": "/ bin/bash", "state": "present", "system": false "uid": 1001} `go back to the managed side 1 to verify that the added user` [root@localhost ~] # id test01uid=1001 (test01) gid=1001 (test01) group = 1001 (test01) `then go back to the managed side 2 to verify that the added user` [root@localhost ~] # id test01uid=1001 (test01) gid=1001 (test01) group = 1001 (test01) # at this time both managed test01 users have successfully added the test01 user `[root@localhost] from the webserver side ~] # ansible webserver-m user-a 'name=test01 state=absent'192.168.18.128 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"} "changed": true, "force": false, "name": "test01", "remove": false, "state": "absent"} ``[root@localhost ~] # id test01id: test01: no such user# shows that the user cannot be found at this time. Indicates that it has been deleted

Group module [group module requests groupadd, groupdel, groupmod three instructions]

`Create mysql group` [root@localhost ~] # ansible mysql-m group-a 'name=mysql gid=306 system=yes'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "gid": 306, "name": "mysql", "state": "present" "system": true} `remotely check whether there is a mysql group in the managed end 2:mysql` [root@localhost ~] # ansible mysql-a 'tail / etc/group'192.168.18.148 | CHANGED | rc=0 > > postfix:x:89:stapusr:x:156:stapsys:x:157:stapdev:x:158:tcpdump:x:72:zhou:x:1000:dhcpd:x:177:named:x:25:test01:x:1001:mysql:x:306: # there is a mysql group at this time At the same time, create a new user test02 with GID number 306` and add it to the mysql group `[root@localhost ~] # ansible mysql-m user-a 'name=test02 uid=306 group=mysql system=yes'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "comment": "", "create_home": true, "group": 306 "home": "/ home/test02", "name": "test02", "shell": "/ bin/bash", "state": "present", "system": true "uid": 306} `remotely check whether there is a newly created user test02` [root@localhost ~] # ansible mysql-a'id test02'192.168.18.148 in the managed 2:mysql group | CHANGED | rc=0 > > uid=306 (test02) gid=306 (mysql) group = 306 (mysql)

Copy module

Remotely mount the fstab files in the etc directory in the 2:mysql of the managed end, copy them to the opt directory and name them fstab.bk, and the group is root. Permission is 644` [root@localhost ~] # ansible mysql-m copy-a 'src=/etc/fstab dest=/opt/fstab.bk owner=root mode=644'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "checksum": "100f3bbf6644926857bbec2a40ab2f70bf1c060b", "dest": "/ opt/fstab.bk", "gid": 0 "group": "root", "md5sum": "f57167de0e8f6f2963771a72af8a2840", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:usr_t:s0", "size": 595, "src": "/ root/.ansible/tmp/ansible-tmp-1580693038.81-171191249824445/source", "state": "file" "uid": 0} `remotely check whether there is a fstab.bk file in the mysql group under the opt directory of the 2:mysql under management` [root@localhost ~] # ansible mysql-a'ls-l / opt'192.168.18.148 | CHANGED | rc=0 > > the total usage is 4Murray. 1 root root 595 February 3 09:24 fstab.bkdrwxr-xr-x. 2 root root 6 March 26 2015 RH` specify content this is test Redirect to generate a new file test.txt under the opt directory `[ root@localhost ~] # ansible mysql-m copy-a 'content= "this is test" dest=/opt/test.txt'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "checksum": "b6794b2000d94d348203d0279c2e7322b922cb16", "dest": "/ opt/test.txt" "gid": 0, "group": "root", "md5sum": "8c6d115258631625b625486f81b09532", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:usr_t:s0", "size": 12, "src": "/ root/.ansible/tmp/ansible-tmp-1580693472.89-123279558248268/source", "state": "file" "uid": 0} `remotely check whether the content in the test.txt file under the opt directory of the 2:mysql under management is this is test` [root@localhost ~] # ansible mysql-a 'cat / opt/test.txt'192.168.18.148 | CHANGED | rc=0 > > this is test

File module

File test.txt under `path opt. The user is test02 and the group is specified as mysql. Permission is 666` [root@localhost ~] # ansible mysql-m file-a 'path=/opt/test.txt owner=test02 group=mysql mode=666'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "gid": 306, "group": "mysql", "mode": "0666", "owner": "test02" "path": "/ opt/test.txt", "secontext": "system_u:object_r:usr_t:s0", "size": 12, "state": "file", "uid": 306} `go back to the details of the test.txt file under the opt directory in the 2:mysql under management` [root@localhost ~] # cd / opt/ [root@localhost opt] # ls-l Total usage 8murrwmurr. 1 root root 595 February 3 09:24 fstab.bkdrwxr-xr-x. 2 root root 6 March 26 2015 rh-rw-rw-rw-. 1 test02 mysql 12 February 3 09:31 test.txt# at this time the owner of the test.txt file is test02 and the group is mysql Link file with 666` permission / opt/test.txt.link / opt/test.txt `[root@localhost ~] # ansible mysql-m file-a 'src=/opt/test.txt path=/opt/test.txt.link state=link'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "dest": "/ opt/test.txt.link" "gid": 0, "group": "root", "mode": "0777", "owner": "root", "secontext": "unconfined_u:object_r:usr_t:s0", "size": 13, "src": "/ opt/test.txt", "state": "link" "uid": 0} `at this time, go back to the opt directory in the managed 2:mysql to view the link file` [root@localhost opt] # ls-l. 1 root root 595 February 3 09:24 fstab.bkdrwxr-xr-x. 2 root root 6 March 26 2015 rh-rw-rw-rw-. 1 test02 mysql 12 February 3 09:31 test.txtlrwxrwxrwx. 1 root root 13 February 3 09:59 test.txt.link-> / opt/test.txt # linked file `create an empty file `[root@localhost ~] # ansible mysql-m file-a 'path=/opt/abc.txt state=touch'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true "dest": "/ opt/abc.txt", "gid": 0, "group": "root", "mode": "0644", "owner": "root", "secontext": "unconfined_u:object_r:usr_t:s0", "size": 0, "state": "file" "uid": 0} `go back to the details of the abc.txt file under the opt directory in the managed 2:mysql` [root@localhost opt] # ls # there is an abc.txt file abc.txt fstab.bk rh test.txt test.txt.link [root@localhost opt] # cat abc.txt # because it is empty Therefore, there is no content `Delete the created empty abc.txt file` [root@localhost ~] # ansible mysql-m file-a 'path=/opt/abc.txt state=absent'192.168.18.148 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "path": "/ opt/abc.txt" "state": "absent"} `return to the managed 2:mysql at this time to see if there is an abc.txt file` [root@localhost opt] # lsfstab.bk rh test.txt test.txt.link in the opt directory

Ping module

`Test whether the two managed servers are online `[root@localhost ~] # ansible all-m ping192.168.18.148 | SUCCESS = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": false "ping": "pong"} 192.168.18.128 | SUCCESS = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": false, "ping": "pong"}

Yum module

`install the httpd service in the managed 1:webserver `[root@localhost ~] # ansible webserver-m yum-a 'name=httpd'192.168.18.128 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "changes": {"installed": ["httpd"]} "msg": "," rc ": 0," results ": [" Loaded plugins: fastestmirror " Langpacks\ nLoading mirror speeds from cached hostfile\ n * base: mirrors.huaweicloud.com\ n * extras: mirror.bit.edu.cn\ n * updates: mirror.bit.edu.cn\ nResolving Dependencies\ nMurray-> Running transaction check\ nMurray-> Package httpd.x86_64 0vir 2.4.6-90.el7.centos will be installed\ nMurray-> Processing Dependency: httpd-tools = 2.4.6-90.el7.centos for package: httpd-2.4.6-90.el7.centos .x86q64\ nMel-> Processing Dependency: / etc/mime.types for package: httpd-2.4.6-90.el7.centos.x86_64\ nMel-> Processing Dependency: libaprutil-1.so.0 () (64bit) for package: httpd-2.4.6-90.el7.centos.x86_64\ nMel-> Processing Dependency: libapr-1.so.0 () (64bit) for package: httpd-2.4.6-90.el7.centos.x86_64\ Package apr-util.x86_64-> Running transaction check\ nMurray-> Package apr.x86_64 0vir 1.4.8-5.el7 will be installed\ nMerry-> Package apr-util.x86_64 0vir 1.5.2-6.el7 will be installed\ nMurray-> Package httpd-tools.x86_64 0vir 2.4.6-90.el7.centos will be installed\ nMube-> Package mailcap.noarch 0vir 2.1.41-2.el7 will be installed\ nMurray-> Finished Dependency Resolution\ n\ nDependencies Resolved\ n\ nhttpd x8634 / 64 2.4.6-90.el7.centos base 2.7m\ nInstalling for dependencies:\ n apr x86 / 64 1.4.8-5.el7 Base 103k\ n apr-util x86'64 1.5.2-6.el7 base 92 k\ n httpd-tools x86'64 2.4.6-90.el7.centos base 91 k\ n mailcap noarch 2.1.41-2.el7 base 31 k\ n\ NTransaction Summary\ nAfter painting =\ nInstall 1 Package (+ 4 Dependent packages)\ n\ nTotal download size: 3.0m\ nInstalled size: 10m\ nDownloading packages:\ n Murray -\ nTotal 1.0 MB/s | 3.0 MB 00:03\ nRunning transaction check\ nRunning transaction test\ nTransaction test succeeded\ nRunning transaction\ nInstalling: apr-1.4.8-5.el7.x86_64 1Accord 5\ nInstalling: apr-util-1.5.2-6.el7.x86_64 2 Installing: httpd-tools-2.4.6-90.el7.centos.x86_64 3 Installing 5\ n Installing: mailcap-2.1.41-2.el7.noarch 4 httpd-2.4.6 5\ n Installing: httpd-2.4.6-90.el7.centos.x86_64 5 Verifying: apr-1.4.8-5.el7.x86_64 1 Verifying 5\ n Verifying: mailcap-2.1.41-2.el7.noarch 2 httpd-tools-2.4.6 5 Verifying: httpd-tools-2.4.6-90.el7.centos.x86_64 3 debase 5 \ n Verifying: apr-util-1.5.2-6.el7.x86_64 4 Verifying 5\ n Verifying: httpd-2.4.6-90.el7.centos.x86_64 5 Accord 5\ n\ nInstalled:\ n httpd.x86_64 0VO Vera 2.4.6-90.el7.centos \ n\ nDependency Installed:\ n apr.x86_64 05.el7 apr-util.x86_64 1.4.8-5.el7 apr-util.x86_64 0nDependency Installed 1.5.2-6.el7\ n httpd-tools.x86_64 0v 2.4.6-90.el7.centos mailcap.noarch 0v 2.1.41-2.el7\ n\ nComplete!\ n "]} # after installation is complete At this point, you can go back to the managed 1:webserver to check whether the httpd service has been installed successfully `[root@localhost ~] # rpm-Q httpdhttpd-2.4.6-90.el7.centos.x86_64 # when the service installation is completed` you can remove the service` [root@localhost ~] # ansible webserver-m yum-a 'name=httpd state=absent' with the following command

Service module

`start the httpd service in managed terminal 2 `[root@localhost ~] # ansible webserver-m service-a 'enabled=true name=httpd state=started'192.168.18.128 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "enabled": true, "name": "httpd", "state": "started",. Omit multiple lines here. At this time, go to the managed end 1:webserver to view the status of the httpd service `[root@localhost ~] # systemctl status httpd.service ● httpd.service-The Apache HTTP Server Loaded: loaded (/ usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: active (running) since-2020-02-03 10:24:28 CST; 2min 25s ago# at this time the status is displayed as running running

Shell module

`Create a user Generate an interaction-free password for the user `[root@localhost ~] # ansible webserver-m user-a 'name=jarry' # create a new user jarry192.168.18.128 | CHANGED = > {"ansible_facts": {"discovered_interpreter_python": "/ usr/bin/python"}, "changed": true, "comment": "", "create_home": true, "group": 1001 "home": "/ home/jarry", "name": "jarry", "shell": "/ bin/bash", "state": "present", "system": false, "uid": 1001} [root@localhost ~] # ansible webserver-m shell-a 'echo abc123 | passwd-- stdin jarry'192.168.18.128 | CHANGED | rc=0 > > change the password of user jarry. Passwd: all authentication tokens have been successfully updated. # generate the login password of jarry users as abc123

Script module

`First of all, write a script on the management side `[root@localhost ~] # cd / opt/ [root@localhost opt] # vim test.shend.shrunkamp / opt/script.txtchmod 666 / opt/script.txt [root@localhost opt] # lsrh test.sh [root@localhost opt] # chmod + x test.sh# to execute the test.sh script` [root@localhost opt] # ansible all-m for all managed clients Script-a 'test.sh'192.168.18.128 | CHANGED = > {"changed": true "rc": 0, "stderr": "Shared connection to 192.168.18.128 closed.\ r\ n", "stderr_lines": ["Shared connection to 192.168.18.128 closed."], "stdout": "," stdout_lines ": []} 192.168.18.148 | CHANGED = > {" changed ": true," rc ": 0 "stderr": "Shared connection to 192.168.18.148 closed.\ r\ n", "stderr_lines": ["Shared connection to 192.168.18.148 closed."], "stdout": "" "stdout_lines": []} `verify whether there are script.txt files in the opt directory of the two managed clients` # managed side 1: [root@localhost ~] # cd / opt/ [root@localhost opt] # lsrh script.txt [root@localhost opt] # cat script.txtthis is test script# managed side 2: [root@localhost opt] # lsfstab.bk rh script.txt test.txt test.txt.link [root@localhost opt] # cat script.txtthis is test script

Setup module

`List all the host information of the managed 2:mysql `[root@localhost opt] # ansible mysql-m setup192.168.18.148 | SUCCESS = > {"ansible_facts": {"ansible_all_ipv4_addresses": ["192.168.122.1", "192.168.18.148"] "ansible_all_ipv6_addresses": ["fe80::1cb1:b734:7f72:576f", "fe80::578f:4368:6a2c:80d7", "fe80::6a0c:e6a0:7978:3543"], "ansible_apparmor": {"status": "disabled"}, "ansible_architecture": "x86x64" "ansible_bios_date": "07auto 29gamma 2019", "ansible_bios_version": "6.00", "ansible_cmdline": {"BOOT_IMAGE": "/ vmlinuz-3.10.0-693.el7.x86_64", "LANG": "zh_CN.UTF-8", "crashkernel": "auto", "quiet": true "rhgb": true, "ro": true, "root": "UUID=32c169ff-9bf7-4d89-a2f1-a99a7e59d4f2"}, "ansible_date_time": {"date": "2020-02-03", "day": "03", "epoch": "1580698171", "hour": "10" "iso8601": "2020-02-03T02:49:31Z", "iso8601_basic": "20200203T104931948449", "iso8601_basic_short": "20200203T104931", "iso8601_micro": "2020-02-03T02:49:31.948682Z", "minute": "49", "month": "02", "second": "31" "time": "10:49:31", "tz": "CST", "tz_offset": "+ 0800", "weekday": "Monday", "weekday_number": "1", "weeknumber": "05", "year": "2020"} "ansible_default_ipv4": {"address": "192.168.18.148", "alias": "ens33", "broadcast": "192.168.18.255", "gateway": "192.168.18.2", "interface": "ens33", "macaddress": "00:0c:29:79:45:8e" "mtu": 1500, "netmask": "255.255.255.0", "network": "192.168.18.0", "type": "ether"}

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.