su - postgres
psql -U postgres
drop database raas_43cab1f4de604ab185b51d883c5c5d09

create database raas_43cab1f4de604ab185b51d883c5c5d09
\du – should display users for postgres and salteapi

su – raas
raas -l debug upgrade

sudo sseapi-config --all > /etc/salt/master.d/raas.conf

Configure the master plugin engines:
The master plugin
eventqueue
and
rpcqueue
engines offload some communications with
Automation Config
from performance-critical code paths to dedicated processes. While the engines are waiting to communicate with
Automation Config
, payloads are stored in the Salt master’s local filesystem so the data can persist across restarts of the Salt master. The
tgtmatch
engine moves the calculation of minion target group matches from the RaaS server to the salt-masters.
To enable the engines, ensure that the following settings are present in the Salt Master Plugin configuration file (raas.conf):
engines: 
     - sseapi: {} 
     - eventqueue: {} 
     - rpcqueue: {} 
     - jobcompletion: {}      
     - tgtmatch: {}
To configure the
eventqueue
engine, verify that the following settings are present:
sseapi_event_queue: 
  name: sseapi-events 
  strategy: always 
  push_interval: 5 
  batch_limit: 2000 
  age_limit: 86400 
  size_limit: 35000000 
  vacuum_interval: 86400 
  vacuum_limit: 350000 
The queue parameters can be adjusted with consideration to how they work together. For example, assuming an average of 400 events per second on the Salt event bus, the settings shown above allow for about 24 hours of queued event traffic to collect on the Salt master before the oldest events are discarded due to size or age limits.
To configure the
rpcqueue
engine, verify the following settings in raas.conf:
sseapi_rpc_queue: 
  name: sseapi-rpc 
  strategy: always 
  push_interval: 5 
  batch_limit: 500 
  age_limit: 3600 
  size_limit: 360000 
  vacuum_interval: 86400 
  vacuum_limit: 100000 
要配置 tgtmatch 引擎，请确保主节点插件配置文件 (/etc/salt/master.d/raas.conf) 中存在以下设置：
engines: 
    - sseapi: {} 
    - eventqueue: {} 
    - rpcqueue: {} 
    - jobcompletion: {}    
    - tgtmatch: {} 

sseapi_local_cache:     
    load: 3600 
    tgt: 86400 
    pillar: 3600 
    exprmatch: 86400 
    tgtmatch: 86400 

sseapi_tgt_match: 
    poll_interval: 60     
    workers: 0 
    nice: 19
To make use of target matching on the salt-masters, the following config setting must also be present in the RaaS configuration:
target_groups_from_master_only: true
.
Limit minion grains payload sizes:
sseapi_max_minion_grains_payload: 2000
Enable skipping jobs that are older than a defined time (in seconds). For example, use
86400
to set it to skip jobs older than a day. When set to
0
, this feature is disabled:
sseapi_command_age_limit:0
During system upgrades, enabling this setting is useful to prevent old commands stored in the database from running unexpectedly.

sudo systemctl restart salt-master

salt -v '*' test.ping

systemctl restart salt-minion

salt-key
salt-key -A

# Orchestration to move Minions from one master to another
# file: /srv/salt/switch_masters/init.sls
{% import_yaml 'switch_masters/map.yaml' as mm %}
{% set minions = mm['minionids'] %}

{% if minions %}
{% for minion in minions %}
move_minions_{{ minion }}:
  salt.state:
    - tgt: {{ minion }}
    - sls:
      - switch_masters.move_minions_map

{% endfor %}    
{% else %}
no_minions:
  test.configurable_test_state:
    - name: No minions to move
    - result: True 
    - changes: False 
    - comment: No minions to move
{% endif %}

remove_minions:
  salt.runner:
    - name: manage.down
    - removekeys: True 

# map file for moving minions
# file: /srv/salt/switch_masters/map.yaml
newsaltmaster: <new_ip_address>
oldsaltmaster: <old_ip_address>
minionids:
  - minion01
  - minion02
  - minion03
state to switch minions from one master to another
# file: /srv/salt/swith_masters/move_minions_map.sls
{% set minion = salt['grains.get']('os') %}
# name old master and set new master ip address
{% import_yaml 'switch_masters/map.yaml' as mm %}
{% set oldmaster = mm['oldsaltmaster'] %}
{% set newmaster = mm['newsaltmaster'] %}

# remove minion_master.pub key
{% if minion == 'Windows' %}
remove_master_key:
  file.absent:
    - name: c:\ProgramData\Salt Project\Salt\conf\pki\minion\minion_master.pub

change_master_assignment:
  file.replace:
    - name: c:\ProgramData\Salt Project\Salt\conf\minion.d\minion.conf 
    - pattern: 'master: {{oldmaster}}'
    - repl: 'master: {{newmaster}}'
    - require:
      - remove_master_key
{% else %}
remove_master_key:
  file.absent:
    - name: /etc/salt/pki/minion/minion_master.pub

# modify minion config file
change_master_assignment:
  file.replace:
    - name: /etc/salt/minion.d/minion.conf 
    - pattern: 'master: {{oldmaster}}'
    - repl: 'master: {{newmaster}}'
    - require:
      - remove_master_key
{% endif %}
# restart salt-minion
restart_salt_minion:
  service.running:
    - name: salt-minion 
    - require:
      - change_master_assignment
    - watch:
      - change_master_assignment

<旧的 salt 主节点> IP 地址/FQDN
<新的 salt 主节点> IP 地址/FQDN
要移动的 Salt 工作节点 ID 的列表。