SaltStack and openSUSE
If you haven't been living under a rock, you've certainly noticed that SaltStack is one of the hot topics within openSUSE and SUSE. It is used in many of the major openSUSE projects like [DeepSea][gh-deepsea] for managing and automating Ceph deployments, in [Kubic][web-kubic] to provision Kubernetes cluster or the newly announced Spacewalk fork [Uyuni project][web-uyuni] to manage your whole IT infrastructure. Therefore I think it's time to take a closer look at how SaltStack itself is being packaged and shipped and how you might collaborate.
Let's talk about the RPM packages itself for a moment. Usually when you install SaltStack (`zypper in salt`), you don't have to care from which repository the packages are coming. They are either in the Leap or Tumbleweed repos. But before they end up there, they are first in [saltstack:testing/salt][obs-saltstack:testing/salt] (which is for testing the new changes) and then in [saltstack/salt][obs-saltstack/salt]. After the patches where accepted to `saltstack/salt`, the state is pushed to [openSUSE:Factory/salt][obs-openSUSE:Factory/salt]. This is only true for now, because we've got the rare condition that Leap 42.3, Leap 15, Tumbleweed and SLE15 are shipping SaltStack 2018.3.0. But this will change in the future, because Tumbleweed will move on. Leap 15 and SLE 15 will both stick to the same version, which is 2018.3.0. I know that this was different in the past. But this caused confusion and there is no good reason for having a different version in Leap and SLE.
But don't let the version numbers fool you. We are still pulling in bugfixes and even backport important features if we need them.
## How to get changes in?
This is the easy part. Just do it [upstream][saltstack/salt]. And if the changes got merged upstream, create a pull request in the [openSUSE/salt GitHub repository][openSUSE/salt]. Just [cherry pick][docs - git cherry pick] your change from upstream and squash all commits into one.
You can also do this for upstream changes you think should be in the openSUSE package. I can't guarantee that everything will be accepted. But just try it!
## What is already in?
Previously I've mentioned that even though we are shipping version 2018.3.0 of SaltStack, we don't just stick to the dot-release. The SaltStack dot-release is just the base the openSUSE SaltStack package is build on. That's why there are already 25 patches coming with that package. In the [spec file][saltstack/salt/salt.spec] you can even find the links to the upstream pull requests. This is an easy way to keep track of what got fixed and what you might want to cherry pick from upstream. ;)
Currently the patch list looks like this:
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46006
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/45972
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46416
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46575
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46643
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46413
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46684
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46635
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/46890
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47149
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47155
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47270
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47232
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47497
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47504
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47471
# PATCH-FIX_OPENSUSE bsc#1091371
# PATCH-FIX_UPSTREAM https://github.com/saltstack/salt/pull/47211
I hope you enjoyed this little overview. Just ping me on freenode#suse if you've got questions or suggestions. My nick is `brejoc`.
Have fun and happy hacking!
[docs - git cherry pick]: https://git-scm.com/docs/git-cherry-pick