Manual steps (documented in SLES Enterprise Storage Guide) that could be automated?
- manage policy.cfg file (roles)
The /srv/pillar/ceph/proposals/policy.cfg configuration file is used to determine roles of individual cluster nodes. For example, which node acts as an OSD or which as a monitor node. Edit policy.cfg in order to reflect your desired cluster setup. The order of the sections is arbitrary, but the content of included lines overwrites matching keys from the content of previous lines.
- manage master_minion.sls file (salt-master)
Check that the file /srv/pillar/ceph/master_minion.sls on the Salt master points to your Salt master. If your Salt master is reachable via more host names, use the one suitable for the storage cluster. If you used the default host name for your Salt master—salt—in the ses domain, then the file looks as follows:
master_minion: salt.ses
Ensure salt-master/salt-minion services get reloaded afterwards
- open firewall ports
Check that the Salt master node has ports 4505 and 4506 open to all Salt minion nodes on the firewall. If not, you can open them using the yast2 firewall command and allowing the SaltStack service.
- mange deepsea_minions file
Setting the deepsea_minions option's target is a requirement for DeepSea deployments. DeepSea uses it to instruct minions during stages execution (refer to DeepSea Stages Description for details.
To set or change the deepsea_minions option, edit the /srv/pillar/ceph/deepsea_minions.sls file on the Salt master and add or replace the following line:
deepsea_minions: target
Tip: deepsea_minions Target
As the target for the deepsea_minions option, you can use any targeting method: both Matching the Minion Name and Targeting with a 'deepsea' Grain.
Match all Salt minions in the cluster:
deepsea_minions: '*'
Match all minions with the 'deepsea' grain:
deepsea_minions: 'G@deepsea:*'
Manual steps (documented in SLES Enterprise Storage Guide) that could be automated?
Ensure salt-master/salt-minion services get reloaded afterwards