Skip to content

Conversation

vzhestkov
Copy link
Contributor

@vzhestkov vzhestkov commented May 30, 2025

@vzhestkov vzhestkov force-pushed the split-salt-master-and-salt-api branch from d3c83ae to a114bb1 Compare May 30, 2025 10:12
Copy link
Member

@rjmateus rjmateus left a comment

Choose a reason for hiding this comment

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

Other then taht comment, looks good to me

Make `salt-master` service abailable for the minions with ports `4505` and `4506` by publishing these ports from `uyuni-salt-master` container.
The following storage volumes need to be mapped to the `uyuni-salt-master` container:

| Volume | Comment |
Copy link
Member

Choose a reason for hiding this comment

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

We will need to research and document which volumes need to be shared with the big container. Tomcat writes the configuration channels to disk in the salt folder. We need to share those locations as writable in the big container, and probably read only on salt-master

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, seems srv-susemanager:/srv/susemanager is missing in the list, but about this one I'm wondering why do we have a separate sls files per system, maybe it will be better to refactor it slightly to use common states, but using jinja to fill corresponding sections with pillar data? That way we can avoid one extra common issue when the file is missing due to faulty registration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants