Open Hour 2022-SEPT-15

September 15, 2022 - Alyssa Rock

Agenda

  • General updates and announcements
  • Salt v3003 extended life support
  • From the community forums
  • Salt docs update
  • Tiamat and onedir switch deep dive
  • 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 October 6.
  • Join a Salt Project working group! https://saltproject.io/home/working-groups/

Events

Salt v3003 extended life support

  • Salt version 3003 is entering extended life support at the end of September 2022. See Salt version support lifecycle for more information.
  • That means Salt v3003 users won’t receive any more updates once this month ends.

From the community forums

  • Today’s issue: methodologies on helping the community. How to give an answer and how to walk through the debugging and tools used to debug. How to find the issues on your own vs. always coming to us for answers.
  • If you can get them to see deeper into the tools they’re using, it will prevent more problems down the line.
  • Salt has a very rich suite of debugging tools that people might not be aware of.

Salt docs update

  • After a brief summer break, the Salt Docs Working group is back again. We meet Tuesdays at 4 p.m. MDT.
  • We’re open to creating a second Salt Docs Working Group meeting at an EMEA-friendly meeting time.
  • Alyssa’s next documentation epic has been decided: Salt case studies!
  • At this point, the epic has only been decided, not yet started. She’ll have more details about how the community can be involved later.

Tiamat and onedir switch deep dive

  • Due to unforeseen circumstances, we will delay this segment for the next Open Hour on October 6.
  • We will do our best to answer all your questions at that session.

Q&A plus discussion

  • Q: Are there any plans to fix the Slack engine?
    • A: Yes, we are planning to focus on this extensively in the
    • Slack made some major changes to their API that will require us to rewrite the code.
  • Q: Is there a cadence for when you prefer releases to occur?
    • A: We do not currently have an officially designated cadence. We’re moving in the right direction with onedir, that will likely make our release schedule or much more flexible. These new packages will make it so much easier and faster to release. We hope to get it out by the end of the year, if not sooner.
  • Q: Is there an estimate for the 3005.1 release?
    • A: We were targeting the end of September, but it doesn’t seem like we’ll meet that goal. Probably the beginning of October.
  • Q: Can anyone take a look at https://github.com/saltstack/salt/pull/62655 ? Many of my other PRs are dependent on this and it will create merge conflicts if it doesn’t get in soon. Can you also tell me why it was made this way?
    • A: Yes, we can take a look at that. In this case, you might want to do some Git archaeology to see if there was a good reason that was documented. If there’s no good reasons, it can certainly be changed.
    • The team discussed possible technical approaches. Check the meeting recording for details.
  • Q: Could I get some attention for https://github.com/saltstack/salt/issues/62523 ? There is a global variable that salt-check uses that sets it, but when it does a callout to the renderer, it does some loader magic. When it does the loader call, it reinitializes that variable and sets it to none.
    • A: The team discussed possible technical approaches. Check the meeting recording for details.
  • Q: Any plans to address bugs and lack of concurrency in Deltaproxy?
    • A: Assuming you’re talking about parallel startup for Deltaproxy, that’s slated for possible inclusion in the 3006 release cycle. It probably will not make it in for 3005.1. Pull requests are always welcome.
    • I wonder if there would be enough interest to form a deltaproxy working group/coworking time just to work through documentation and any other issues.
  • Q: I would love to see a bit more documentation for deltaproxy. Specifically, if people add and remove assignments to a deltaproxy, will deltaproxys stop, are there any checks to make sure a deltaminion isn’t started / running in two places? I need to spin up about 4000 minions and I’d love deltaproxy to be usable so I don’t have to buy $10k worth of hardware just to run them.
    • A: I wonder if there would be enough interest to form a deltaproxy working group/coworking time just to work through documentation and any other issues.
    • A: That currently isn’t something you can easily do with deltaproxy. Since it’s the Salt proxy that is running all the proxy devices, there is a single process that is handling all of them and just sending the commands to the appropriate device when a Salt command comes in.