Actions
action #159165
closedEnsure that rsyncd is properly covered in salt states size:S
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-04-17
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
We rely on rsyncd on both o3+osd for the worker cache, test syncing, but so far that does not seem to be covered in any documentation or salt states at all. Let's try to at least cover it in salt for osd.
Currently on OSD we have
openqa:/etc # ls -ltra rsyncd.*
-rw-r--r-- 1 root root 275 Mar 17 2017 rsyncd.conf
-rw------- 1 root root 14 Oct 25 2022 rsyncd.secrets
and the enabled systemd service I guess
Acceptance criteria¶
- AC1: rsyncd is setup by salt states
- AC2: non-trivial passwords are in https://gitlab.suse.de/openqa/salt-pillars-openqa/
Suggestions¶
- Probably just a simple file provides and service enable in https://gitlab.suse.de/openqa/salt-states-openqa like we often have (e.g. https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/kdump.sls?ref_type=heads or https://gitlab.suse.de/openqa/salt-states-openqa/-/tree/master/chrony?ref_type=heads)
- Check the rsyncd.secrets. If it has a non-trivial password then provide it from pillars
Updated by nicksinger 7 months ago
- Subject changed from Ensure that rsyncd is properly covered in salt states to Ensure that rsyncd is properly covered in salt states size:S
- Description updated (diff)
- Status changed from New to Workable
Updated by mkittler 7 months ago ยท Edited
- Status changed from In Progress to Feedback
MR: https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1157
It doesn't look like we use any secrets here so no MR for pillars is required.
Actions