action #44066
closedmerge the two osd salt git repos
0%
Description
Motivation¶
I think separating states and pillars is not very common. Probably https://gitlab.suse.de/OPS-Service/salt should be our reference. Also, maybe the repo should not really be about "salt" but more about the overall configuration so inviting for more, deployment CI job definitions, docu, etc.
Updated by nicksinger over 5 years ago
- Status changed from New to Workable
I'm in general not sure how to handle this.
I'd like to manage "the whole infrastructure" in one repo indeed but always symlinking stuff around in systems can also cause unexpected problems and more confusion…
If you like we can one day talk about this over a coffee.
Updated by coolo over 5 years ago
btw: the original motivation behind the split was to be able to have states published for all openqa instances to use and pillars to be osd specific. But I don't think that turned out to be true
Updated by okurz almost 5 years ago
- Related to coordination #43934: [epic] Manage o3 infrastructure with salt again added
Updated by okurz almost 5 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
According to https://gitlab.suse.de/OPS-Service/salt/blob/production/bin/prepare_test_env.sh#L69 this repo uses symlinks to create /srv/pillar and /srv/salt . It would be nice to have other instances, namely o3, covered by the same salt repo as well which IMHO is more important to get right then this ticket so let's block by that one
Updated by okurz over 4 years ago
- Status changed from Blocked to Rejected
We have more and more progress regarding #43934 so by now I think it's a good idea that the repos are separate.