Open Hour 2020-MAY-28

January 23, 2021 - slangadmin


  • Salt news and updates
  • SEP #28: Move unsupported releases to a separate URL
  • SEP #18: Release label improvements
  • Feedback Item of the Week: POP build and Salt Bin discussion
  • Open discussion and questions

Salt News and Updates

Cassandra Faris

  • New event schedule for Meetups and other events coming to
  • First German language meetup on May 27 went well. It included a formal talk and open conversation. Additional Meetups in other languages are coming.
  • Watch for the weekly “What’s Happening at SaltStack This Week?” post on the Community Wiki and in Slack. It details the event schedule, SEPs, release updates, and the week’s Core Team focus in one place.
  • Weekly communication schedule
    • Monday: “What’s Happening?” post
    • Tuesday: Publish Open Hour Agenda
    • Thursday: Community Open Hour

SEP #28: Move unsupported releases to a separate URL

Cassandra Faris

SEP #18: Release Label Improvements

Wayne Werner

  • This SEP is a process improvement. Currently, labels are sometimes confusing because they have both a priority and a visibility that don’t always align. This simplifies labels to make it more clear to tell what is a priority.
  • Proposed priorities in order of highest to lowest:
    • Critical: Issues that are severe enough to block a release. They’ll impact most or all users in a specific area and cause problems like data loss and crashes.
    • High: Serious issues that aren’t serious enough to block a release. They’ll likely affect most people but will also have a workaround.
    • Medium: Issues that affect about half the people in a particular area. These produce incorrect or bad functionality or confusing user experience
    • Low: Cosmetic issues or those with simple/reasonable workarounds
  • Priority labels will help contributors know how quickly various issues will be fixed

Feedback Item of the Week: POP Build and Salt Bin Discussion

Tyler Johnson

  • POP Build, being renamed Tiamat to remove confusion with POP
  • Makes building Salt easier to develop and deploy by packaging it into a single binary
  • POP build and Salt Bin have been used the last few months for Arista native minions at IBM, Juniper native minion, and Cisco being built. Being used at limited sites.
  • POP build will make it so that the version of Python doesn’t matter since it will be able to be packaged as a single binary
  • Additional POP Build information: Watch Tom Hatch’s Maryland Python Virtual Meetup presentation at

Open Discussion and Questions

Community and Team Core

  • Question: Can you please clarify Py2 support? There’s concern that not everyone knows that Py2 will no longer be supported.
    • We’ve been sharing this news for a year through an open SEP, blog posts, Open Hours, mailing lists, and announcements. Core Team is open to other suggestions for communication outlets and plans to make more effort to keep Salt’s Twitter, Stack Overflow, and Reddit communities updated.
    • POP Build will help address this issue because Salt will be packaged with Python into a single binary
    • Python 2 is being end-of-lifed. The industry is moving forward with Python 3. It won’t be removed from Salt all at once, but over time as releases progress
  • Question: There are people using modules in Jinja that use Py2 features that don’t work without modification in Py3. Salt itself will work, but installations might not. How to resolve this?
    • Start by creating GitHub issues for those specific issues so we can fix them
  • Question: How would POP Build solve external states library dependency like Elastic Search?
    • User can still do a pip install into the POP Build environment to install extra dependencies
  • Question: Is it possible to add dependencies into the POP Build process? By the time Salt from POP Build starts can it have its dependencies installed? How does this apply to both third party dependencies and the underlying libraries?
    • With the pip install, hard dependencies are there and available right away. Optional dependencies will still need installed into POP Build.
    • Documentation about this is being updated. If you want to help with documentation, check out the Documentation Working Group. They’ll be aware of this.
  • Question: Can users create their own installation packages to include those extra dependencies rather than needing to install them to each after Salt has been installed?
    • Yes. Users can create their own POP (Tiamat) Build of Salt and choose the dependencies they want rather than the standard dependencies. People can fork it and build their own self-contained versions.
  • Will users be able to use Tiamat to build on Windows as well as Linux platforms?
    • Yes. It’s not in place for Windows yet, but it will be.
  • What’s the status of PyTest deployment?
    • As of today, the Master branch has one test failure under PyTest which doesn’t happen under run tests. This is because we weren’t actually testing that test case using run tests. There’s a PR to fix that. It may get into Sodium.
    • We haven’t switched because it’s getting so close to the release. We want them to run for a couple weeks to ensure that results are the same when we run tests.
    • After code freeze, we should be ready to make the full switch. The ground work to run PyTest and have it pass is done.