Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #16217: relayd admin guide #643

Merged

Conversation

amousset
Copy link
Member


Relay configuration is stored in `/opt/rudder/etc/relay`:

* `main.conf` contains general configuration. Its content is configured by the Rudder agent of the relay.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/configured/managed ?

Relay also reads the following data files:

* `/var/rudder/lib/relay/nodeslist.json`: contains information about the nodes behind a relay
* `/var/rudder/lib/ssl/allnodescerts.pem` (only on root server): contains the certificates of all nodes managed by the root server (only on root server)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

duplicate (only on root server)

Configuration reload uses the reload API endpoint, which allows `systemctl reload rudder-relayd`
to be synchronous (and ensure configuration is already applied when command returns).

Reloading relayd configuration reloads all data files and the `logging.conf` file,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I needed several pass to understand that sentence, I wasn't understanding the opposition introduced by the comma. Perhaps:

Reloading relayd configuration reloads all data files and update properties from
`logging.conf` but not the one from `main.conf`. Changing properties in `main.conf`
requires a restart to be taken into account. 

Relayd operates on different data directories:

* `/var/rudder/inventories` (on on simple relays): to forward inventories to upstream relay or root server. On root server, the webapp monitors this folder directly.
* `/var/rudder/reports`: to forward reports to upstream relay, or, on root server, to parse and insert reports into te database.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/te/the

@amousset
Copy link
Member Author

PR updated with a new commit

to be synchronous (and ensure configuration is already applied when command returns).

Reloading relayd configuration reloads all data files and update properties from
`logging.conf` but not the one from `main.conf`. Changing properties in `main.conf`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the ones

@amousset
Copy link
Member Author

PR updated with a new commit

1 similar comment
@amousset
Copy link
Member Author

PR updated with a new commit

@Normation-Quality-Assistant
Copy link
Contributor

This PR is not mergeable to upper versions.
Since it is "Ready for merge" you must merge it by yourself using the following command:
rudder-dev merge https://github.com/Normation/rudder-doc/pull/643
-- Your faithful QA
Kant merge: "It is beyond a doubt that all our knowledge begins with experience."
(https://ci.normation.com/jenkins/job/merge-accepted-pr/17661/console)

@amousset
Copy link
Member Author

OK, squash merging this PR

@amousset amousset merged commit 2712cd3 into Normation:branches/rudder/6.0 Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants