minion io

salt-ssh Batch automatic installation of the controlled end minion Salt-ssh is another way to manage saltstack, without the need to install the Minion end, can use all the functions of salt, management and use of basic and salt. However, Salt-ssh did not inherit the original ZEROMQ communication architecture. So, she's running slower. Supplements as salt are very useful in the initial batch installation of

Second, the source code installation ChapterUsing the SALT-SSH feature requires the client system Python version 2.6+1.salt-minion End Environment:System: SUSE SP3 64bitPython version: 2.6.6RPM Package: Pcre-devel #不安装, compile Swig error2. Configure/etc/salt/rosterCases:10.10.10.30: host:10.10.10.30 user:syspub #普通用户, with no password sudo permissions passwd:123456aa sudo:true Timeout:15When the number of clients, manual configuration/etc/salt/r

Not all of the options for the master and Minion end profiles are described here, but rather the usual ones.I. Description ofMaster Common configuration optionsCat/etc/salt/master Interface : Specify the address of bind (default is 0.0.0.0) Publish_port : Specify a publishing port (default is 4505) Ret_port : Specifies the result return port, corresponding to the Master_port in the Minion configurat

First, RPM installation ChapterUsing the SALT-SSH feature requires the client system Python version 2.6+1.salt-minion End Environment:System: CentOS 6.5 64bitPython version: 2.6.62. Configure/etc/salt/rosterCases:10.10.10.30: host:10.10.10.30 user:syspub #普通用户, with no password sudo permissions passwd:123456aa sudo:true Timeout:15When the number of clients, manual configuration/etc/salt/roster is cumbersome, here to write a simple script for refe

I. Cp.get_file implementing files from the master side to the Minion serverCp.get_file1. Modify/etc/salt/master to specify the root directory of the server's workFile-roots:-Base:/srv/salt (default path, can be specified)2. Create a DirectoryMkdir/srv/salt3. Copy the files that need to be copied to the working directoryCp-ra Souce_file/srv/salt4. Execute cp.get_file commandSalt ' * ' Cp.get_file salt://path/to/file/

Master Common configuration options :1Interface: Specifies the address of bind (default 0.0.0.0)2 Publish_port: Specify a publishing port (default 4505)3 Ret_port: Specifies the result return port, corresponding to the master--port of the Minion configuration file (default is root)4 User : Specifies the running users of the master process and, if adjusted, needs to adjust permissions for some directories (default root)5 Timeout: Specifies timeout time

When deploying Salt-minion, an error[[email protected] ~]#/etc/init.d/salt-minion startStarting Salt-minion Daemon:traceback (most recent):File "/usr/bin/salt-minion", line 6, From salt.scripts import salt_minionImporterror:no module named Salt.scriptsKnow a bit of Python, basically can confirm that Python module impor

Batch deployment, unattended deployment, salt master/minion deployment Preparation: Rhel-server-6.4-x86_64-dvd.iso Salt.tar.gz Step 1: Prepare a server to manage other servers System --- → rhel-server-6.4-x86_64-dvd.iso Ip --- → route 10.10.111 Hostname ---- → admin.black.com Configure the yum Source Mkdir/iso Mount/dev/cdrom/iso Create/etc/yum. repo. d/yum. repo Step 2: Use the admin Server as the DHCP server Requirements: 1: assign ip addresses to o

What is mine doing? Is that you define the collection module in mine, he will collect the data, where it is stored, do not know, but certainly the client Minino Local. Interested friends can check Saltstack code.Paste it down here first, official DOC usage: The code is as follows Copy Code Mine.delete: Remove specific function contents of minion. Returns True on success. CLI Example: Salt ' * ' mine.delete ' network.interfa

Install salt-minion ON RHEL5 This article applies to rhel5.4, 6.4, and. el5.4 is used as an example. 1 online installation is extremely simple: # Wget -- no-check-certificate-O install_salt.sh https://bootstrap.saltstack.com# Sh install_salt.sh-I The above applies to el5, el6, el7, and other versions. You can find a bunch of repo under/etc/yum. repos. d/and save the following: Epel. repoEpel-testing.repoSaltstack-salt-el5-epel-5.repo 2 The following d

Install salt-minion ON REHL5Install salt-minion ON REHL5 This article applies to rhel5.4, 6.4, and. el5.4 is used as an example.1 online installation is extremely simple: # wget --no-check-certificate -O install_salt.sh https://bootstrap.saltstack.com# sh install_salt.sh -I The above applies to el5, el6, el7, and other versions. You can find a bunch of repo under/etc/yum. repos. d/and save the following:

Install Salt-minion on REHL5This article applies to rhel5.4, 6.4, 7. Take el5.4 for example only.1 Online installation method is extremely simple:# wget--no-check-certificate-o install_salt.sh https://bootstrap.saltstack.com# sh install_salt.sh-iThe above applies to El5, El6, EL7 and other versions. You can find a bunch of repo under/etc/yum.repos.d/, save the following:Epel.repoepel-testing.reposaltstack-salt-el5-epel-5.repo2 The following main descr

IO Model Description:* Blocking IO blocking IO* nonblocking io non-blocking IO* IO multiplexing IO multiplexing* Signal driven IO signal dri

Issues in the previous section:Co-process: switch on IO operation.But when do you cut it back? How do I know I'm done with IO?first, the event-driven model introductionTypically, when we write a program that server processes a model, there are several models: (1) Each time a request is received, a new process is created to process the request;(2) Each time a request is received, a new thread is cre

processing.Network applications often have these characteristics, which makes them well suited to the event-driven programming model.The above event-driven model, as long as an IO to register an event, and then the main program can continue to do other things, only to the completion of IO processing, continue to restore the previously interrupted tasks, how is this essentially implemented?Logic diagram:Blo