Open Hour 2022-JULY-14

July 14, 2022 - Alyssa Rock

Agenda

  • General updates and announcements
  • VMware Explore
  • From the community forums
  • Salt Project SRE updates
  • Test clinic report
  • Q&A plus discussion

Open Hour YouTube playlist | Contact us! saltproject@vmware.com

General updates and announcements

  • Open Hours are usually held every 1st and 3rd Thursday from 10a.m. to 11a.m. Pacific.
  • Our next Salt Community Open Hour will be July 28.
  • Join a Salt Project working group! https://saltproject.io/home/working-groups/

Events

VMware Explore

  • VMware Explore will be held August 29th – September 1st​ in San Francisco, CA.
  • Go to VMware.com/vmwareexpolore to register​.
  • The conference will feature:
    • An open source track.
    • Breakout sessions for Salt & Idem​.
    • “Getting To Know Salt” with Thomas Hatch and Wayne Werner..
    • “Solving the SRE Crisis with Idem” with Thomas Hatch and Dave Boucha.

From the community forums

  • Today’s issue: the rendering engines and what the state system expected. One of the things about the render engine is that it renders everything into a Python dictionary that Salt is expecting. That’s all it does: it import YAMLs, then outputs the expected highstate in the Python dictionary. It doesn’t actually try to call states or anything like that directly. You can call modules directly.

Salt Project SRE updates

  • The outside collaborators notices have been resolved now. Let us know if you require any further action.
  • Salt Issue #61929 (503 timeout access errors to resources on archive.repo.saltproject.io) is now resolved. If you’ve been previously having issues with this error, you shouldn’t experience that error now.

Test clinic report

  • Wayne has been making progress on the returner API tests. It’s mostly done but still needs tuning. That’s where we’re at with the Cassandra CQL returner right now as well. At this point, it’s a matter of implementing tests for all the returners. Reach out to Wayne if you’d like to help with these efforts.

Q&A plus discussion

  • Q: Any updates on the release?
    • A: We just finished up fixing some things and we internally tagged so that we can do testing. We’re re-running some tests and need to fix some additional things. Once that’s done, we’ll be able to release the RC. We’re still working on the Mac packages, which will be released later than the RC.
  • Q: We have a new contributor who opened a new PR: https://github.com/saltstack/salt/pull/62314 and I’d love it if someone could take a look at it.
  • Q: I wasn’t expecting this PR to make it in: https://github.com/saltstack/salt/pull/62227 but it did. The documentation puts it in 3006, but it should be in 3005.
    • A: We’ll work on fixing that.
  • Q: I opened https://github.com/saltstack/salt/pull/62295 to fix a loader issue, but I found that the Salt logging class has a fair amount of overhead. I’d love some additional eyes on it if anyone has some bandwidth to make sure it’s not just overall slowness.
    • A: We also tagged C.R. to look at that, since he authored the original. Gareth can also take a look.
  • Q: I opened https://github.com/saltstack/salt/issues/62318 and I don’t have a lot of great solutions to this problem. Perhaps someone who was involved in the syndic master can take a look and offer some insights.
    • A: One possible good solution would be to examine your HTTPS cert chain and certificate authorities. As long as your chain is intact, it should be fine. Perhaps we could adopt that same kind of functionality or architecture in Salt.
  • Q: The issue https://github.com/saltstack/salt/issues/62223 shows some errors that might be relevant to Tiamat.
    • A: Possibly look at how the native minions handle binaries for inspiration. The last error might have a fix in for that now. We’ll check and post that on the issue.
  • Q: The issue https://github.com/saltstack/salt/issues/62185 is having the warn-until function is having its deprecation warnings suppressed. Suppressing warnings could lead people to be unpleasantly surprised and confused.
    • A: Suppressing warnings does seem like a bad idea and we should default to showing them rather than suppressing them.
  • Q: I’m going to open an issue for a bug we’re experiencing with masters when we have at least temporarily disabled long-running minion services.
    • A: Rather than create a workaround for one specific event, consider developing a feature that can turn certain events one and off besides just this one.
  • Q: Is it safe to assume that SaltConf won’t happen? We’re asking because we’re passing the early bird pricing for VMExplore.
    • A lot is still changing and there is a lot we still don’t know at this point. We’re no longer allowed to host SaltConf per VMware’s corporate policy for all open source communities, but we’re trying to get that decision modified to allow us to have a one day virtual event. Probably there will not be any in-person conferences this year. If you want an in-person event, we recommend attending VMExplore.