Update docs for 13.1 - Salt #1653
Conversation
bochi
force-pushed
the
update_docs_for_13.1
branch
from
25a2a17
to
d806a36
Compare
plugins/foreman_salt/13.1/index.md
Outdated
| title: Foreman Salt 13.0 Manual | ||
| version: 13.0 |
There was a problem hiding this comment.
Shouldn't these say 13.1?
|
|
||
| ## 1.1 Release Notes | ||
|
|
||
| ### 1.1.1 Foreman plugin |
|
|
||
| If your Smart Proxy uses SSL, then the certs and key configured in the YAML should be the same ones it uses to talk to Foreman. If you're already using Puppet in Foreman, consult `/etc/puppet/foreman.yaml` or `/etc/puppet/node.rb` for those settings. | ||
|
|
||
| The :filecache: option makes foreman-node read the grains cache from files rather than using salt-run. | ||
|
|
||
| Please note this will only work if the master is not configured to use an external minion cache module. With salt's default configuration the filecache option works fine and should be used as it is much faster than getting the cache using salt-run. Please note that for this to work, the "msgpack" rubygem needs to be present. |
There was a problem hiding this comment.
Is that something one has to do manually or is it brought in as a dependency when installing the rpm?
There was a problem hiding this comment.
That I am not sure of. Currently, in our containerized foreman proxy we are installing it manually using gem install because there's no package available. @sbernhard commited something to foreman-packaging though adding the rubygem, but as of now, there's no dependency in the spec file yet.
plugins/foreman_salt/13.1/index.md
Outdated
|
|
||
| Please note this will only work if the master is not configured to use an external minion cache module. With salt's default configuration the filecache option works fine and should be used as it is much faster than getting the cache using salt-run. Please note that for this to work, the "msgpack" rubygem needs to be present. | ||
|
|
||
| If your salt-master is configured to use a different data directory for cache, you can also set the :cachedir: option to the same directory you configured in the salt master configuration. |
There was a problem hiding this comment.
you can also set the
can or have to?
plugins/foreman_salt/13.1/index.md
Outdated
| @@ -384,7 +384,26 @@ When running `state.highstate`, you can have Foreman process the results and sho | |||
|
|
|||
|  | |||
|
|
|||
| Uploading the salt reports is done by `/usr/sbin/upload-salt-reports` and is scheduled by a cron job running on the smart proxy. By default, reports are uploaded to Foreman once every 10 minutes from the Salt master's job cache. You may modify the smart_proxy_salt cron job to customize this by editing `/etc/cron.d/smart_proxy_salt`. | |||
| There are two ways to upload the highstate reports to foreman: | |||
There was a problem hiding this comment.
capital F in foreman I guess
plugins/foreman_salt/13.1/index.md
Outdated
| - /usr/share/foreman-salt/reactor/foreman_report_upload.sls | ||
| ``` | ||
|
|
||
| In case you decide to use the reactor/runner solution, please also remove the cronjob triggering `/usr/sbin/upload-salt-reports` from `/etc/cron.d/smart_proxy_salt`. |
There was a problem hiding this comment.
Why? To prevent reports being duplicated?
There was a problem hiding this comment.
Correct, I made it more clear. Thanks for your comments
|
What is the status here? |
|
Good question. I thought the "next" documentation system should be used. See https://docs.theforeman.org/3.1/Managing_Hosts/index-foreman-el.html#Using_Salt_for_Configuration_Management_managing-hosts |
Update docs for 13.1
This PR includes 3 commits: