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

In SaltStack's default working mode, the minion side returns the data directly to the mysql database, and master is not required to participate in this process. Because of the more flexible management, the execution result (job cache) of the minion side can also be saved on the master side. The default save address on the master side is: / var/cache/salt/master/jobs.

Job cache has the corresponding configuration parameters in the configuration file on the master side:

# cachedir: / path saved by var/cache/salt/master

# keep_jobs: 24 save time 24 hours

Configure Job cache to write directly to the database

The cache on the master side can be written directly to the database through configuration.

The default table structure of job cache is the same as that of the salt database, but if you want to interact with the database, you need to install MySQL-python on the master side:

Yum install MySQL-python-y

Modify the configuration file of master and add the configuration of mysql directly at the end:

# vim / etc/salt/mastermaster_job_cache: mysqlmysql.host: '172.16.10.60'mysql.user:' salt'mysql.pass: 'saltpw'mysql.db:' salt'mysql.port: 3306

Create data Table: https://docs.saltstack.com/en/latest/ref/returners/all/salt.returners.mysql.html

CREATE DATABASE `salt` DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;USE `salt`;-Table structure for table `jids`-- DROP TABLE IF EXISTS `jids`; CREATE TABLE `jids` (`jid` varchar (255) NOT NULL, `load`mediumtext NOT NULL, UNIQUE KEY `jid` (`jid`) ENGINE=InnoDB DEFAULT CHARSET=utf8;CREATE INDEX jid ON jids (jid) USING BTREE;---- Table structure for table `salt_ Secretns`-DROP TABLE IF EXISTS `jidns` CREATE TABLE `salt_ Secretns` (`fun` varchar (50) NOT NULL, `jid` varchar (25551) NOT NULL, `funn` mediumtext NOT NULL, `id`varchar (2555i) NOT NULL, `room`varchar (10) NOT NULL, `full_ ret` mediumtext NOT NULL, `alter_ time`TIMESTAMP DEFAULT CURRENT_TIMESTAMP, KEY `id` (`id`), KEY `jid` (`jid`), KEY `fun`( `fun`) ENGINE=InnoDB DEFAULT CHARSET=utf8;---- Table structure for table `salt_ events`-DROP TABLE IF EXISTS `salt_ events` CREATE TABLE `salt_ events` (`id` BIGINT NOT NULL AUTO_INCREMENT, `tag` varchar (255) NOT NULL, `data` mediumtext NOT NULL, `alter_ time` TIMESTAMP DEFAULT CURRENT_TIMESTAMP, `master_ id` varchar (255) NOT NULL,PRIMARY KEY (`id`), KEY `tag` (`tag`) ENGINE=InnoDB DEFAULT CHARSET=utf8

Create an authorized user in the database:

Grant all on salt.* to salt@172.16.10.60 identified by 'saltpw'

Restart salt-master:

# systemctl restart salt-master

Execute on the masterside:

# salt'* 'test.ping

If no error is reported, the execution is successful. You can check whether the data is written in mysql:

MariaDB [salt] > use salt;select * from salt_returns\ G

Each time it is executed, two records (two minion) are generated.

In this way, the job cache executed each time is returned to the database.

Common management commands for salt:

# salt-run jobs.list_jobs looks at the salt job-cache tasks performed by history, querying from the directory, not from the database.

# salt-run jobs.lookup_jid 20161124144637116519 View the execution result of a task

View the status of the current minion:

# salt-run manage.status

View the minion in the down state:

# salt-run manage-down

View the minion in the up state:

# salt-run manage-up

View version information:

# salt-run manage.versions

Return JID on execution, plus the-v parameter:

# salt'* 'test.run-v

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.