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

Configuration management remote commands

On master

# vi / srv/salt/shell_test.sls / / add the following content shell_test: # this is ID cmd.script: # module-source: salt://test/1.sh # what is defined here is the shell script to be executed-user: root # the user who executes it # vi / srv/salt/test/1.sh / / add the following content #! / bin/bashtouch / tmp/111.txt if [! -d / tmp/1233] then mkdir / tmp/1233fi change top.sls content # vi / srv/salt/top.slsbase:'*':-shell_test# salt 'yw02' state.highstate

Check for / tmp/111.txt and / tmp/1233

Configuration management task plan

On master

# vi / srv/salt/cron_test.sls / / add the following content cron_test: cron.present:-name: / bin/touch / tmp/111.txt # the name here is equivalent to the last paragraph in crontab-e-user: root # the user who executes it-minute:'*'# the following corresponds to the minutes, hours, days, months, and months in crontab. Zhou-hour: 20-daymonth:'*'- month:'*-dayweek:'*'

Note that * it needs to be enclosed in single quotation marks. Of course, we can also use the file.managed module to manage cron, because the cron of the system exists in the form of configuration files. To delete the cron, you need to add:

Cron.absent:-name: / bin/touch / tmp/111.txt

The two cannot coexist. If you want to delete a cron, you have to remove the previous present.

Change top.sls

# vi / srv/salt/top.slsbase:'*':-cron_test# salt 'yw02' state.highstate

Check cron:crontab-l on yw02 and you will see the prompt # Lines below here are managed by Salt, do not edit

We can't change it at will, otherwise we won't be able to delete or modify the cron.

# crontab-l # Lines below here are managed by Salt, do not edit # these two lines must not be moved. If you change them, you can no longer manage them. The line # SALT_CRON_IDENTIFIER:/bin/touch / tmp/111.txt* 20 * / bin/touch / tmp/111.txt # is defined by script. If you want to modify it, you can modify it from script.

III. Other orders

Cp.get_file copies files on master to the client

# salt'* 'cp.get_file salt://test/1.sh / tmp/123.shyw02: / tmp/123.shfuxi01: / tmp/123.sh

Cp.get_dir copy directory

# salt'* 'cp.get_dir salt://test/123 / tmp/

/ / will automatically create 123 directories on the client, so do not add 123s later. If written as / tmp/123/, it will create another 123directories under the / tmp/123/ directory.

# salt-run manage.up shows the surviving minion

Execute the shell script on master under the # salt'* 'cmd.script salt://test/1.sh command line and execute it in batches on the machine.

IV. Use of salt-ssh

Salt-ssh does not need to authenticate the client, and the client does not need to install salt-minion or start any services to operate on the other machine, as long as the public key of the local machine is placed on the other machine, which is similar to pssh/expect.

The installation is simple.

Install the yum source first

# yum install-y https://repo.saltstack.com/yum/redhat/salt-repo-latest-2.el7.noarch.rpm# yum install-y salt-ssh# vi / etc/salt/roster / / add the following fuxi01: host: 192.168.149.133 user: root passwd: 1346yw02: host: 192.168.149.131 user: root passwd: 134percent salt-ssh-- key-deploy'*-r 'w' / / this occurs because yes/no is asked when logging in for the first time Just reconnect the ssh. Yw02:-retcode: 254 stderr: stdout: The host key needs to be accepted, to auto accept run salt-ssh with the-I flag: The authenticity of host '192.168.149.131 (192.168.149.131)' can't be established. ECDSA key fingerprint is SHA256:Z7xp3qHrdUE3yl4C34LCIrYyaCTvwC/hhZsWu1iZfS4. ECDSA key fingerprint is MD5:ff:06:a8:bd:b0:d9:2f:72:df:64:07:b2:b0:36:c4:06. Are you sure you want to continue connecting (yes/no)? Fuxi01:-retcode: 254 stderr: stdout: The host key needs to be accepted, to auto accept run salt-ssh with the-I flag: The authenticity of host '192.168.149.133 (192.168.149.133)' can't be established. ECDSA key fingerprint is SHA256:PZXNkWqC/6h5hUQYkfOM9AMj82OTskLMIB4qLkgeajU. ECDSA key fingerprint is MD5:99:19:04:c5:11:8d:94:ad:9a:86:40:b9:ad:b9:d4:8f. Are you sure you want to continue connecting (yes/no)? # salt-ssh-- key-deploy'*'- r 'w'yw02:-retcode: 0 stderr: stdout: 17:01:40 up 3 days, 16:58, 2 users, load average: 0.00,0.01 0.05 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root tty1 1610 19 6 retcode 57m 0.24s 0.24s-bash root pts/0 192.168.149.1 10:05 6VR 55m 0.01s 0.01s-bashfuxi01:-retcode: 0 stderr: stdout : 17:01:44 up 3 days 20:23, 2 users, load average: 2.00, 1.43 0.64 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root tty1 1610 19 6virtual 56m 0.10s 0.10s-bash root pts/0 192.168.149.1 17:01 24.00s 12.36s 0.70s salt-ssh# ls-l / root/.ssh/authorized_keys / / View the public key on both machines The time is the same. -rw- 1 root root 393 October 26 16:59 / root/.ssh/authorized_keys

/ / the first execution will automatically put the public key of the local machine on the other machine, and then the password in the roster can be removed.

/ /-key-deploy, if you do not add this, it will not automatically push the public key to the other machine.

Now delete the password in / etc/salt/roster, and then execute salt-ssh-- key-deploy'*-r'wicked, which can also be executed successfully, because the public key has been pushed. The first time you need a password, the second time you don't need it.

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.