├── .gitignore ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── communication.md ├── community-membership.md ├── doc ├── AL Milestones March Release delay.jpg ├── AL Release Milestones 2021-JAN update.jpg ├── AL Release Milestones.png ├── Community-Message.pdf ├── Mg Release Milestones OP.png ├── Mg Release Milestones UPDATED.pdf ├── Mg Release Milestones UPDATED.png ├── Open Hour 2020-DEC-03.pdf ├── Open Hour 2020-DEC-10.pdf ├── Open Hour 2020-NOV-05 .pdf ├── Open Hour 2020-NOV-12.pdf ├── Open Hour 2020-NOV-19 (1).pdf ├── Open Hour 2020-OCT-22.pdf ├── Open Hour 2021-JAN-07.pdf ├── Open Hour 2021-JAN-14.pdf ├── README.md ├── Release timeline Sodium 2020-05-19.png ├── Release timeline Sodium 2020-05.pdf ├── Release timeline Sodium UPDATED.png ├── Sodium Release Timeline.png ├── diagrams │ └── Working-group-timelines.svg ├── doc_make.py ├── generate_docs.sls ├── group_template.sls ├── home_page_template.sls └── working_groups_raw_data.yaml └── working_groups ├── community-temp-proj-chrtr.md ├── wg-Cloud ├── README.md └── meeting-notes │ ├── 2019-06-14.md │ ├── 2019-07-12.md │ └── 2019-08-09.md ├── wg-Documentation ├── wg-MacOS └── README.md ├── wg-Networking └── README.md ├── wg-Release ├── README.md └── meeting-notes │ ├── 2021-06-09.md │ ├── 2021-07-14.md │ └── salt_release_debian_presentation_2021-09-08_final.pdf ├── wg-SSH ├── README.md └── meeting-notes │ ├── 2019-06-20.md │ ├── 2019-08-08.md │ ├── 2019-09-12.md │ ├── 2019-10-10.md │ ├── 2019-12-12.md │ ├── 2020-01-09.md │ ├── 2020-02-13.md │ ├── 2020-03-12.md │ └── 2020-04-09.md ├── wg-Security ├── README.md └── meeting-notes │ ├── 2021-AUG-09-SecurityWG.md │ ├── 2021-JUN-14-SecurityWG.md │ ├── 2022-APR-13-SecurityWG.md │ ├── 2022-JUL-13-SecurityWG.md │ ├── 2022-SEP-14-SecurityWG.md │ ├── 2023-FEB-08-SecurityWG.md │ ├── 2023-JAN-11-SecurityWG.md │ ├── 2023-MAY-10.md │ └── 2025-04-09-SecurityWG.md ├── wg-Testing └── README.md └── wg-Windows ├── README.md └── meeting-notes ├── 2019-06-18.md ├── 2019-12-17.md ├── 2020-01-21.md ├── 2020-02-18.md ├── 2020-03-17.md ├── 2020-04-21.md ├── 2020-05-19.md ├── 2020-06-16.md ├── 2020-07-21.md ├── 2020-08-18.md ├── 2020-09-15.md ├── 2020-10-20.md ├── 2020-11-17.md ├── 2020-12-15.md ├── 2021-01-19.md ├── 2021-02-16.md ├── 2021-03-16.md ├── 2021-04-20.md ├── 2021-05-18.md ├── 2021-09-21.md ├── 2022-01-18.md ├── 2022-02-15.md ├── 2022-03-15.md ├── 2022-04-19.md ├── 2022-05-17.md ├── 2022-06-21.md ├── 2022-07-19.md ├── 2022-08-16.md ├── 2022-09-22.md ├── 2022-10-20.md ├── 2022-11-17.md ├── 2022-12-15.md ├── 2023-01-19.md ├── 2023-02-16.md ├── 2023-03-16.md ├── 2023-04-20.md ├── 2023-05-18.md ├── 2023-06-22.md ├── 2023-08-17.md ├── 2023-09-21.md ├── 2023-10-19.md ├── 2023-11-16.md ├── 2023-12-21.md ├── 2024-01-18.md ├── 2024-02-15.md ├── 2024-03-21.md ├── 2024-04-18.md ├── 2024-05-16.md ├── 2024-06-27.md ├── 2024-07-18.md ├── 2024-08-15.md ├── 2024-09-19.md ├── 2024-10-17.md ├── 2024-12-19.md ├── 2025-01-16.md ├── 2025-02-20.md ├── 2025-03-20.md ├── 2025-04-17.md └── 2025-05-15.md /.gitignore: -------------------------------------------------------------------------------- 1 | # Byte-compiled / optimized / DLL files 2 | __pycache__/ 3 | *.py[cod] 4 | *$py.class 5 | 6 | # C extensions 7 | *.so 8 | 9 | # Distribution / packaging 10 | .Python 11 | env/ 12 | build/ 13 | develop-eggs/ 14 | dist/ 15 | downloads/ 16 | eggs/ 17 | .eggs/ 18 | lib/ 19 | lib64/ 20 | parts/ 21 | sdist/ 22 | var/ 23 | wheels/ 24 | *.egg-info/ 25 | .installed.cfg 26 | *.egg 27 | 28 | # PyInstaller 29 | # Usually these files are written by a python script from a template 30 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 31 | *.manifest 32 | *.spec 33 | 34 | # Installer logs 35 | pip-log.txt 36 | pip-delete-this-directory.txt 37 | 38 | # Unit test / coverage reports 39 | htmlcov/ 40 | .tox/ 41 | .coverage 42 | .coverage.* 43 | .cache 44 | nosetests.xml 45 | coverage.xml 46 | *.cover 47 | .hypothesis/ 48 | 49 | # Translations 50 | *.mo 51 | *.pot 52 | 53 | # Django stuff: 54 | *.log 55 | local_settings.py 56 | 57 | # Flask stuff: 58 | instance/ 59 | .webassets-cache 60 | 61 | # Scrapy stuff: 62 | .scrapy 63 | 64 | # Sphinx documentation 65 | docs/_build/ 66 | 67 | # PyBuilder 68 | target/ 69 | 70 | # Jupyter Notebook 71 | .ipynb_checkpoints 72 | 73 | # pyenv 74 | .python-version 75 | 76 | # celery beat schedule file 77 | celerybeat-schedule 78 | 79 | # SageMath parsed files 80 | *.sage.py 81 | 82 | # dotenv 83 | .env 84 | 85 | # virtualenv 86 | .venv 87 | venv/ 88 | ENV/ 89 | 90 | # Spyder project settings 91 | .spyderproject 92 | .spyproject 93 | 94 | # Rope project settings 95 | .ropeproject 96 | 97 | # mkdocs documentation 98 | /site 99 | 100 | # mypy 101 | .mypy_cache/ 102 | 103 | # IDE files 104 | /.idea 105 | 106 | # VIM files 107 | *.un~ 108 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at conduct@saltstack.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright {yyyy} {name of copyright owner} 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # SaltStack Community 2 | 3 | ## Working Groups 4 | 5 | A Working Group is a small group of individuals who come together with a common goal and work towards achieving that goal within a predetermined amount of time. It’s an opportunity for the Salt community to lead Salt projects and be part of the process in its entirety. 6 | 7 | ### Here's the list of active working groups and their respective Captains. 8 | * [Cloud](https://github.com/saltstack/community/tree/master/working_groups/wg-Cloud): [Nick Hughes](https://github.com/nicholasmhughes) 9 | * [MacOS](https://github.com/saltstack/community/tree/master/working_groups/wg-MacOS): [Wesley Whetstone](https://github.com/weswhet) 10 | * [Windows](https://github.com/saltstack/community/tree/master/working_groups/wg-Windows): [Markus](https://github.com/markuskramerIgitt) 11 | * [Testing](https://github.com/saltstack/community/tree/master/working_groups/wg-Testing): Needed 12 | 13 | 14 | ## Eligibility to participate 15 | 16 | Salt community members are eligible to be part of a working group if they have exhibited interest in working on the Salt project by raising either 1 or more PR(s), issue(s) or SEP(s) (Salt Enhancement Proposal). 17 | 18 | In addition, a working group applicant is a Subject Matter Expert (SME) in areas impacting the group. 19 | 20 | If you want to lead or be part of a different working group then the ones mentioned above, Salt would be happy to include that as part of initial working groups, provided Salt receives enough interest from others to participate. 21 | 22 | ## Application Process 23 | 24 | Salt community members indicate their interest to be part of one or more working group(s) by filling out an application consisting of simple 4-5 question survey; Applicants indicate their preference for the type of working group(s) they want to join and the role they want to play: Captain or facilitator. If an application is received past the due date then the applicant will automatically be considered for the next term of the working groups. 25 | 26 | ## Election 27 | 28 | Salt will conduct an election to choose the working group members in the following scenarios: 29 | - When the number of applicants interested in joining the working groups exceeds the number that is ideal for a working group (3 to 9 members) 30 | - 2 or more community members indicate their interest in being captain 31 | - If Salt doesn’t receive any eligible applicants for captain role, a member of the Salt open/core will be elected to be captain of that working group. 32 | 33 | The rules for the election process are: 34 | - Election for the first working group captain will be internal and voting will be done by the Salt core team. 35 | - Elections for all subsequent working group captains and members will be voted on by the outgoing members of the current working group and Salt core team. 36 | - In the event of a tie, [Thomas Hatch](https://github.com/thatch45), Salt project creator, will make the final decision. 37 | 38 | ## Timelines 39 | 40 | Based on the applications submitted, Salt chooses the final working group members 41 | 42 | Below is the approximate timeline for how long each working group term will last. The actual timeline may differ. For example, the Testing and Release Working Group might decide to convene immediately after a major release and dissolve after the next major release. 43 | 44 | ![Working Group Timelines](./doc/diagrams/Working-group-timelines.svg) 45 | 46 | 47 | 48 | *T0 is feature freeze date of current major release 49 | T1 is feature freeze date of next major release 50 | 51 | 52 | ## Collaboration 53 | Working Groups will meet not less than once a month for 60 mins. The monthly meetings which are set by SaltStack will be recorded and uploaded on Youtube. Meetings are not just restricted to the Working group members and can be attended by any Salt community members. Details of the meeting will be published in the individual working group github page; For example, for Testing working group meeting [check here](https://github.com/saltstack/community/tree/master/working_groups/wg-Testing) 54 | 55 | Below are some guidelines for working group participants, although each of these groups may operate a little differently depending on their needs and workflow. 56 | 57 | ## Working Group Structure 58 | 59 | Each member of a working group will fill one of 3 roles: captain, participant or facilitator. 60 | 61 | ### Captain 62 | 63 | Each working group captain will help lead their respective working group. 64 | 65 | #### Role of Captains 66 | - The captain helps shepherd a subset of features/critical fixes for a given release 67 | - The captain will help coordinate other contributors' work in their area 68 | - The captain will attend monthly working group meetings for their respective working group. SaltStack will set these up, but SaltStack will hold no restriction on any additional meetings the captain may deem necessary 69 | 70 | #### Captain Guidelines 71 | 72 | - The captain will have merge rights to Salt repository 73 | - A captain of one working group cannot be captain of any other Salt working groups. But the captain can be a participant of other Salt working groups 74 | - The captain can nominate the captain and/or participants of next term working group 75 | - Captains are limited to 3 successive terms. Captains must take a break after their 3rd successive term. Following the break, they may come back to fill the role of captain again. 76 | - Starting from 2nd term working groups, the captains chosen need to have been a participant in at least one working group 77 | - Once a captain’s term ends and they are no longer captaining the next term, their merge rights will be rescinded and transferred to the new captain of the working group 78 | - Single review completed by the captain on the PR will be considered as criteria met to merge the PR (No additional reviews required) 79 | - The captain must follow the [Merge Guidelines](https://github.com/saltstack/salt-enhancement-proposals/); This is to ensure the Salt project grows responsibly. 80 | - In rare occasions and in consultation with the Salt Core team, the captain can nominate a vice-captain for the working group, to help assist during a leave of absence or to share responsibilities. The captain can also give merge access to said vice-captain of their working group while ensuring they follow the Merging Guidelines. 81 | 82 | 83 | ### Participant 84 | 85 | Participants form the core of each of the working groups. 86 | 87 | #### Role of Participant 88 | - Participants will attend monthly working group meetings for their respective working group 89 | - Participants will get to work on exciting Salt projects: enhancements or issues that impacts thousands of Salt users 90 | 91 | #### Participant Guidelines 92 | - No restriction on the number of working groups a participant can be part of 93 | - Once their term ends, a participant can move to a different working group or continue in the same working group 94 | - No term limits on how many times a Salt community member can be a participant of a working group 95 | - Participants don’t have merge rights. However in rare circumstances, the captain can recommend that a participant be granted merge rights. 96 | 97 | 98 | ### Facilitator 99 | 100 | Until the working groups mature, Saltstack will facilitate the working group meetings and there will be at least 1 SaltStack facilitator in every working group meeting 101 | 102 | #### Role of Facilitator 103 | - The facilitator will work with the Salt core team to identify the list of participants, communicate/invite them to the working groups 104 | - The facilitator will ensure everyone gets a chance to voice their opinions 105 | - The facilitator will ensure members adhere to the goals of the meeting and that the meeting doesn't devolve into tangential conversations 106 | - The facilitator sets up the monthly working group meetings and invites the appropriate participants 107 | - The facilitator makes the agenda clear before every meeting 108 | - The facilitator takes notes and shares the action items after every meeting 109 | - The facilitator ensures the working group members needs/interests are met 110 | 111 | 112 | ## Benefits of Working Group 113 | 114 | - Active voice and participation in Salt projects 115 | - SaltStack will publish the efforts of working groups to the broader Salt community 116 | - SaltStack will recognize working groups members in various public platforms. 117 | - Participants and Captains will receive dedicated working group swag 118 | -------------------------------------------------------------------------------- /communication.md: -------------------------------------------------------------------------------- 1 | # Communication 2 | 3 | The SaltStack community has a [Code of Conduct]. All community members must abide by 4 | this code. 5 | 6 | ## Working Groups 7 | 8 | The SaltStack project is vast and is organized around areas of interest called "Working Groups". 9 | 10 | For example, people interested in Salt's networking capability might join the "Networking" working 11 | group. These groups meet often and are considered the primary maintainers of their respective areas 12 | of the Salt project. For more information, please see the [Working Groups] page. 13 | 14 | ## Getting Help 15 | 16 | **IRC Chat** - Join the vibrant, helpful and positive SaltStack chat room in 17 | Freenode at #salt. There is no need to introduce yourself, or ask permission to 18 | join in, just help and be helped! Make sure to wait for an answer, sometimes it 19 | may take a few moments for someone to reply. 20 | 21 | ``_ 22 | 23 | **SaltStack Slack** - Alongside IRC is our SaltStack Community Slack for the 24 | SaltStack Working groups. Use the following link to request an invitation. 25 | 26 | ``_ 27 | 28 | **Mailing List** - The SaltStack community users mailing list is hosted by 29 | Google groups. Anyone can post to ask questions about SaltStack products and 30 | anyone can help answer. Join the conversation! 31 | 32 | ``_ 33 | 34 | You may subscribe to the list without a Google account by emailing 35 | salt-users+subscribe@googlegroups.com and you may post to the list by emailing 36 | salt-users@googlegroups.com 37 | 38 | **Reporting Issues** - To report an issue with Salt, please follow the 39 | guidelines for filing bug reports: 40 | ``_ 41 | 42 | 43 | [Code of Conduct]: https://github.com/saltstack/salt/blob/develop/CODE_OF_CONDUCT.md 44 | [Working Groups] TODO 45 | -------------------------------------------------------------------------------- /community-membership.md: -------------------------------------------------------------------------------- 1 | # Community membership 2 | 3 | 4 | | Role | Responsibilities | Requirements | Defined by | 5 | | -----| ---------------- | ------------ | -------| 6 | | member | Active contributor in the community | Sponsored by 2 reviewers. Multiple contributions to the project. | SaltStack GitHub org member. | 7 | | reviewer | review contribution from other members | History of review and authorship in an area | OWNERS file reviewer entry. | 8 | | approver | approve accepting contributions | Highly experienced and active reviewer + contributor to an area | OWNERS file approver entry| 9 | | owner | set priorities and approve proposals | Demonstrated responsibility and good judgement for entire area | OWNERS file approver entries for entire area. "# owner" comment next to entry. | 10 | | maintainer | Cross-area ownership of project health | Highly experienced contributor active in multiple areas and roles. | GitHub repo write access | 11 | 12 | # Proposing a Working Group 13 | 14 | To propose a working group, the following are required: 15 | 16 | * A leader, who is willing to run the group. This leader should be willing to dedicate 2-3 hours a week to the group, including 17 | scheduling meetings and leading group discussions. 18 | 19 | * A secondary leader, willing to dedicate 1-2 hours a week to the group. 20 | 21 | The primary leader and the secondary leader should get together and come up with a brief paragraph describing the purpose 22 | of the group along with the proposed leadership committee and email it to `core@saltstack.com`. 23 | -------------------------------------------------------------------------------- /doc/AL Milestones March Release delay.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/AL Milestones March Release delay.jpg -------------------------------------------------------------------------------- /doc/AL Release Milestones 2021-JAN update.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/AL Release Milestones 2021-JAN update.jpg -------------------------------------------------------------------------------- /doc/AL Release Milestones.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/AL Release Milestones.png -------------------------------------------------------------------------------- /doc/Community-Message.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Community-Message.pdf -------------------------------------------------------------------------------- /doc/Mg Release Milestones OP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Mg Release Milestones OP.png -------------------------------------------------------------------------------- /doc/Mg Release Milestones UPDATED.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Mg Release Milestones UPDATED.pdf -------------------------------------------------------------------------------- /doc/Mg Release Milestones UPDATED.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Mg Release Milestones UPDATED.png -------------------------------------------------------------------------------- /doc/Open Hour 2020-DEC-03.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-DEC-03.pdf -------------------------------------------------------------------------------- /doc/Open Hour 2020-DEC-10.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-DEC-10.pdf -------------------------------------------------------------------------------- /doc/Open Hour 2020-NOV-05 .pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-NOV-05 .pdf -------------------------------------------------------------------------------- /doc/Open Hour 2020-NOV-12.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-NOV-12.pdf -------------------------------------------------------------------------------- /doc/Open Hour 2020-NOV-19 (1).pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-NOV-19 (1).pdf -------------------------------------------------------------------------------- /doc/Open Hour 2020-OCT-22.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2020-OCT-22.pdf -------------------------------------------------------------------------------- /doc/Open Hour 2021-JAN-07.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2021-JAN-07.pdf -------------------------------------------------------------------------------- /doc/Open Hour 2021-JAN-14.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Open Hour 2021-JAN-14.pdf -------------------------------------------------------------------------------- /doc/README.md: -------------------------------------------------------------------------------- 1 | # Doc Generation 2 | 3 | > **NOTE**: _This README can be ignored, as `salt` is no longer a prereq tool to_ 4 | > _contribute to this repo._ 5 | 6 | ## How to Generate Docs 7 | * Install Salt. 8 | * Open a terminal with admin privileges. 9 | * Run `python doc_make.py` in doc directory. 10 | 11 | ## How to Edit README.md 12 | All of the working groups `"README.md"` data is kept in `"working_groups_raw_data.yaml"`. 13 | Don't directly modify the Working groups or Homepage `"README.md"`. 14 | Modify the `".yaml"` and then generate the docs. 15 | If the generation of the docs was successfully then push them to the repo. 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /doc/Release timeline Sodium 2020-05-19.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Release timeline Sodium 2020-05-19.png -------------------------------------------------------------------------------- /doc/Release timeline Sodium 2020-05.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Release timeline Sodium 2020-05.pdf -------------------------------------------------------------------------------- /doc/Release timeline Sodium UPDATED.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Release timeline Sodium UPDATED.png -------------------------------------------------------------------------------- /doc/Sodium Release Timeline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/doc/Sodium Release Timeline.png -------------------------------------------------------------------------------- /doc/doc_make.py: -------------------------------------------------------------------------------- 1 | import os 2 | 3 | 4 | def generate_docs(): 5 | """ 6 | info: generates_docs for salt community 7 | :return: 8 | """ 9 | path = '/'.join(os.path.dirname(os.path.realpath(__file__)).split('\\')) 10 | os.system('salt-call --local --file-root={0} state.sls generate_docs'.format(path)) 11 | 12 | 13 | if __name__ == "__main__": 14 | generate_docs() 15 | -------------------------------------------------------------------------------- /doc/generate_docs.sls: -------------------------------------------------------------------------------- 1 | {%- import_yaml "working_groups_raw_data.yaml" as wg %} 2 | 3 | {%- set community_repo = '/'.join(opts['file_root'].split('/')[:-1]) %} 4 | 5 | {% for group, info in wg.workgroups.items() %} 6 | add_{{ group }}_README: 7 | file.managed: 8 | - name: {{ community_repo }}/working_groups/wg-{{ group }}/README.md 9 | - source: salt://group_template.sls 10 | - makedirs: True 11 | - template: jinja 12 | - context: 13 | group: {{ group }} 14 | info: {{ info }} 15 | contributors: {{ wg.contributors }} 16 | {%- endfor %} 17 | 18 | add_home_page_README: 19 | file.managed: 20 | - name: {{ community_repo }}/README.md 21 | - source: salt://home_page_template.sls 22 | - makedirs: True 23 | - template: jinja 24 | - context: 25 | contributors: {{ wg.contributors}} 26 | homepage: {{ wg.homepage}} 27 | workgroups: {{ wg.workgroups }} 28 | -------------------------------------------------------------------------------- /doc/group_template.sls: -------------------------------------------------------------------------------- 1 | # {{ group }} Working Group 2 | 3 | ## Captain 4 | [{{ info.captain }}]({{ contributors[info.captain]['git_link'] }}) 5 | 6 | ## Participants 7 | {%- for name in info.contributors %} 8 | * [{{ name }}]({{ contributors[name]['git_link'] }}) 9 | {%- endfor %} 10 | 11 | ## Project Board 12 | [Github Project]({{ info.project_board }}) 13 | 14 | ## Contact 15 | {%- for link_name in info.contacts %} 16 | * [{{ link_name }}]({{ info.contacts[link_name] }}) 17 | {%- endfor %} 18 | 19 | ## Meeting Details 20 | {%- for detail in info.meeting_details %} 21 | * {{ detail }} 22 | {%- endfor %} 23 | 24 | ## Notes 25 | {%- for note in info.notes %} 26 | * {{ note }} 27 | {%- endfor %} 28 | -------------------------------------------------------------------------------- /doc/home_page_template.sls: -------------------------------------------------------------------------------- 1 | # SaltStack Community 2 | 3 | Don't update the Readme files directly. Check the doc folder to see instructions on how to update 4 | 5 | ## Working Groups 6 | 7 | A Working Group is a small group of individuals who come together with a common goal and work towards achieving that goal within a predetermined amount of time. It’s an opportunity for the Salt community to lead Salt projects and be part of the process in its entirety. 8 | 9 | ### Here's the list of active working groups and their respective Captains. 10 | {%- for group, info in workgroups.items() %} 11 | {%- set group_link = '[' + group + '](https://github.com/saltstack/community/tree/master/working_groups/wg-' + group + ')' %} 12 | {%- set captain_link = '[' + info.captain + '](' + contributors[info.captain]['git_link'] + ')' %} 13 | * {{ group_link }}: {{ captain_link }} 14 | {%- endfor %} 15 | 16 | ## Term {{ homepage.term }} Timeline 17 | {%- for activity in homepage.timeline %} 18 | * {{ activity }} 19 | {%- endfor %} 20 | 21 | ## Eligibility to participate 22 | 23 | Salt community members are eligible to be part of a working group if they have exhibited interest in working on the Salt project by raising either 1 or more PR(s), issue(s) or SEP(s) (Salt Enhancement Proposal). 24 | 25 | In addition, a working group applicant is a Subject Matter Expert (SME) in areas such as Windows, Cloud, Networking or SSH 26 | 27 | If you want to lead or be part of a different working group then the ones mentioned above, Salt would be happy to include that as part of initial working groups, provided Salt receives enough interest from others to participate. 28 | 29 | ## Application Process 30 | 31 | Salt community members indicate their interest to be part of one or more working group(s) by filling out an application consisting of simple 4-5 question survey; Applicants indicate their preference for the type of working group(s) they want to join and the role they want to play: Captain or facilitator. If an application is received past the due date then the applicant will automatically be considered for the next term of the working groups. 32 | 33 | ## Election 34 | 35 | Salt will conduct an election to choose the working group members in the following scenarios: 36 | - When the number of applicants interested in joining the working groups exceeds the number that is ideal for a working group (3 to 9 members) 37 | - 2 or more community members indicate their interest in being captain 38 | - If Salt doesn’t receive any eligible applicants for captain role, a member of the Salt open/core will be elected to be captain of that working group. 39 | 40 | The rules for the election process are: 41 | - Election for the first working group captain will be internal and voting will be done by the Salt core team. 42 | - Elections for all subsequent working group captains and members will be voted on by the outgoing members of the current working group and Salt core team. 43 | - In the event of a tie, [Thomas Hatch](https://github.com/thatch45), Salt project creator, will make the final decision. 44 | 45 | ## Timelines 46 | 47 | Based on the applications submitted, Salt chooses the final working group members 48 | 49 | Below is the approximate timeline for how long each working group term will last. The actual timeline may differ. For example, the Testing and Release Working Group might decide to convene immediately after a major release and dissolve after the next major release. 50 | 51 | ![Working Group Timelines](./doc/diagrams/Working-group-timelines.svg) 52 | 53 | 54 | 55 | *T0 is feature freeze date of current major release 56 | T1 is feature freeze date of next major release 57 | 58 | 59 | ## Collaboration 60 | Working Groups will meet not less than once a month for 60 mins. The monthly meetings which are set by SaltStack will be recorded and uploaded on Youtube. Meetings are not just restricted to the Working group members and can be attended by any Salt community members. Details of the meeting will be published in the individual working group github page; For example, for Testing working group meeting [check here](https://github.com/saltstack/community/tree/master/working_groups/wg-Testing) 61 | 62 | Below are some guidelines for working group participants, although each of these groups may operate a little differently depending on their needs and workflow. 63 | 64 | ## Working Group Structure 65 | 66 | Each member of a working group will fill one of 3 roles: captain, participant or facilitator. 67 | 68 | ### Captain 69 | 70 | Each working group captain will help lead their respective working group. 71 | 72 | #### Role of Captains 73 | - The captain helps shepherd a subset of features/critical fixes for a given release 74 | - The captain will help coordinate other contributors' work in their area 75 | - The captain will attend monthly working group meetings for their respective working group. SaltStack will set these up, but SaltStack will hold no restriction on any additional meetings the captain may deem necessary 76 | 77 | #### Captain Guidelines 78 | 79 | - The captain will have merge rights to Salt repository 80 | - A captain of one working group cannot be captain of any other Salt working groups. But the captain can be a participant of other Salt working groups 81 | - The captain can nominate the captain and/or participants of next term working group 82 | - Captains are limited to 3 successive terms. Captains must take a break after their 3rd successive term. Following the break, they may come back to fill the role of captain again. 83 | - Starting from 2nd term working groups, the captains chosen need to have been a participant in at least one working group 84 | - Once a captain’s term ends and they are no longer captaining the next term, their merge rights will be rescinded and transferred to the new captain of the working group 85 | - Single review completed by the captain on the PR will be considered as criteria met to merge the PR (No additional reviews required) 86 | - The captain must follow the [Merge Guidelines](https://github.com/saltstack/salt-enhancement-proposals/); This is to ensure the Salt project grows responsibly. 87 | - In rare occasions and in consultation with the Salt Core team, the captain can nominate a vice-captain for the working group, to help assist during a leave of absence or to share responsibilities. The captain can also give merge access to said vice-captain of their working group while ensuring they follow the Merging Guidelines. 88 | 89 | 90 | ### Participant 91 | 92 | Participants form the core of each of the working groups. 93 | 94 | #### Role of Participant 95 | - Participants will attend monthly working group meetings for their respective working group 96 | - Participants will get to work on exciting Salt projects: enhancements or issues that impacts thousands of Salt users 97 | 98 | #### Participant Guidelines 99 | - No restriction on the number of working groups a participant can be part of 100 | - Once their term ends, a participant can move to a different working group or continue in the same working group 101 | - No term limits on how many times a Salt community member can be a participant of a working group 102 | - Participants don’t have merge rights. However in rare circumstances, the captain can recommend that a participant be granted merge rights. 103 | 104 | 105 | ### Facilitator 106 | 107 | Until the working groups mature, Saltstack will facilitate the working group meetings and there will be at least 1 SaltStack facilitator in every working group meeting 108 | 109 | #### Role of Facilitator 110 | - The facilitator will work with the Salt core team to identify the list of participants, communicate/invite them to the working groups 111 | - The facilitator will ensure everyone gets a chance to voice their opinions 112 | - The facilitator will ensure members adhere to the goals of the meeting and that the meeting doesn't devolve into tangential conversations 113 | - The facilitator sets up the monthly working group meetings and invites the appropriate participants 114 | - The facilitator makes the agenda clear before every meeting 115 | - The facilitator takes notes and shares the action items after every meeting 116 | - The facilitator ensures the working group members needs/interests are met 117 | 118 | 119 | ## Benefits of Working Group 120 | 121 | - Active voice and participation in Salt projects 122 | - SaltStack will publish the efforts of working groups to the broader Salt community 123 | - SaltStack will recognize working groups members in various public platforms. 124 | - Participants and Captains will receive dedicated working group swag 125 | -------------------------------------------------------------------------------- /doc/working_groups_raw_data.yaml: -------------------------------------------------------------------------------- 1 | homepage: 2 | term: 1 3 | timeline: 4 | - 'Working group announced **May 31st**' 5 | - 'Working group convenes **June 15th**' 6 | - 'Working group dissolves **Next major release (Sodium)**' 7 | 8 | workgroups: 9 | Cloud: 10 | captain: 'Nick Hughes' 11 | contributors: 12 | - 'Swaminathan' 13 | - 'Ben Gridley' 14 | - 'Cedric Bosdonnat' 15 | - 'Adam C. Greenfield' 16 | - 'Peter Norton' 17 | - 'Vernon Cole' 18 | - 'Prashanth Goud B' 19 | - 'Tyler Johnson' 20 | - 'Michael Verhulst' 21 | - 'Daniel Wallace' 22 | project_board: https://github.com/saltstack/community/projects/1 23 | contacts: 24 | Slack: https://saltstackcommunity.slack.com/messages/C7KKMMYDQ/ 25 | 'Google Group': https://groups.google.com/forum/#!forum/salt-cloud 26 | meeting_details: 27 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 28 | notes: [] 29 | 30 | MacOS: 31 | captain: 'Wesley Whetstone' 32 | contributors: 33 | - 'Joaquín' 34 | - 'Brian LaShomb' 35 | - 'Shea Craig' 36 | - 'Kris Anthony' 37 | project_board: https://github.com/saltstack/community/projects/2 38 | contacts: 39 | Slack: https://saltstackcommunity.slack.com/messages/C8VH92RJT 40 | 'Google Group': https://groups.google.com/a/saltstack.com/d/forum/salt-mac 41 | meeting_details: 42 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 43 | notes: [] 44 | 45 | Windows: 46 | captain: Shane 47 | contributors: 48 | - 'Prashant Goud B' 49 | - 'Rares POP' 50 | - 'rigel marcinik' 51 | - 'Markus' 52 | - 'Joseph Eacott' 53 | - 'Chad McMarrow' 54 | project_board: https://github.com/saltstack/community/projects/4 55 | contacts: 56 | Slack: https://saltstackcommunity.slack.com/messages/C7U9FLK8S 57 | 'Google Group': https://groups.google.com/a/saltstack.com/forum/#!forum/salt-windows 58 | meeting_details: 59 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 60 | notes: [] 61 | 62 | Testing: 63 | captain: 'Mihai Dinca' 64 | contributors: 65 | - 'Pablo Suárez Hernández' 66 | - 'Jochen Breuer' 67 | - 'Alberto Planas' 68 | - 'Swaminathan' 69 | project_board: https://github.com/saltstack/community/projects/6 70 | contacts: 71 | Slack: https://saltstackcommunity.slack.com/messages/C7KKN9P6W 72 | 'Google Group': https://groups.google.com/a/saltstack.com/forum/#!forum/salt-testing 73 | meeting_details: 74 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 75 | notes: [] 76 | 77 | Networking: 78 | captain: 'Mircea Ulinic' 79 | contributors: 80 | - 'Alberto Planas' 81 | - 'Andrew Dampf' 82 | - 'Jochen Breuer' 83 | - 'Pablo Suárez Hernández' 84 | - 'Mihai Dinca' 85 | - 'Yeshwanth Ambati' 86 | - 'Lawrence Bird' 87 | - 'Chad Geary' 88 | - 'Swaminathan' 89 | - 'Wayne Werner' 90 | - 'Zach Moody' 91 | project_board: https://github.com/saltstack/community/projects/7 92 | contacts: 93 | Slack: https://saltstackcommunity.slack.com/messages/C7KPR0ZDK 94 | 'Google Group': https://groups.google.com/forum/#!forum/salt-networks 95 | meeting_details: 96 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 97 | notes: [] 98 | 99 | SSH: 100 | captain: 'Megan Wilhite' 101 | contributors: 102 | - 'Chad Geary' 103 | - 'Swaminathan' 104 | - 'Jochen Breuer' 105 | - 'Pablo Suárez Hernández' 106 | - 'Mihai Dinca' 107 | - 'Balvinder Singh Rawat' 108 | project_board: https://github.com/saltstack/community/projects/8 109 | contacts: 110 | Slack: https://saltstackcommunity.slack.com/messages/CK7LFCW92 111 | 'Google Group': https://groups.google.com/a/saltstack.com/forum/#!forum/salt-ssh 112 | meeting_details: 113 | - '[Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)' 114 | notes: [] 115 | 116 | contributors: 117 | 'Daniel Wallace': 118 | git_link: https://github.com/gtmanfred 119 | 'Swaminathan': 120 | git_link: https://github.com/swamguru 121 | 'Nick Hughes': 122 | git_link: https://github.com/nicholasmhughes 123 | 'Ben Gridley': 124 | git_link: https://github.com/bgridley 125 | 'Cedric Bosdonnat': 126 | git_link: https://github.com/cbosdo 127 | 'Adam C. Greenfield': 128 | git_link: https://github.com/admgre 129 | 'Peter Norton': 130 | git_link: https://github.com/pcn 131 | 'Vernon Cole': 132 | git_link: https://github.com/vernondcole 133 | 'Prashanth Goud B': 134 | git_link: https://github.com/prashanthbgoud 135 | 'Tyler Johnson': 136 | git_link: https://github.com/Akm0d 137 | 'Michael Verhulst': 138 | git_link: https://github.com/verhulstm 139 | 140 | 'Wesley Whetstone': 141 | git_link: https://github.com/weswhet 142 | Joaquín: 143 | git_link: https://github.com/lctrkid 144 | 'Brian LaShomb': 145 | git_link: https://github.com/lashomb 146 | 'Shea Craig': 147 | git_link: https://github.com/sheagcraig 148 | 'Kris Anthony': 149 | git_link: https://github.com/Kris-anthony 150 | 151 | Shane: 152 | git_link: https://github.com/twangboy 153 | 'Prashant Goud B': 154 | git_link: https://github.com/prashanthbgoud 155 | 'Rares POP': 156 | git_link: https://github.com/rares-pop 157 | 'rigel marcinik': 158 | git_link: https://github.com/rmarcinik 159 | 'Markus': 160 | git_link: https://github.com/markuskramerIgitt 161 | 'Joseph Eacott': 162 | git_link: https://github.com/xeacott 163 | 'Chad McMarrow': 164 | git_link: https://github.com/cmcmarrow 165 | 166 | 'Mihai Dinca': 167 | git_link: https://github.com/dincamihai 168 | 'Pablo Suárez Hernández': 169 | git_link: https://github.com/meaksh 170 | 'Jochen Breuer': 171 | git_link: https://github.com/brejoc 172 | 'Alberto Planas': 173 | git_link: https://github.com/aplanas 174 | 175 | 'Mircea Ulinic': 176 | git_link: NULL 177 | 'Andrew Dampf': 178 | git_link: https://github.com/wasabi222 179 | 'Yeshwanth Ambati': 180 | git_link: https://github.com/Network 181 | 'Lawrence Bird': 182 | git_link: https://github.com/TheBirdsNest 183 | 'Chad Geary': 184 | git_link: https://github.com/chadgeary 185 | 'Wayne Werner': 186 | git_link: https://github.com/waynew 187 | 'Zach Moody': 188 | git_link: https://github.com/zachmoody 189 | 190 | 'Megan Wilhite': 191 | git_link: https://github.com/ch3ll 192 | 'Balvinder Singh Rawat': 193 | git_link: https://github.com/balrawat 194 | -------------------------------------------------------------------------------- /working_groups/community-temp-proj-chrtr.md: -------------------------------------------------------------------------------- 1 | - Salt Working Group Name: (fill with unique name i.e. Salt MacOS) 2 | - Description: (generally what the group does, why it formed, general purpose) 3 | - Current Captain: (name, gh handle and link or other means of contact) 4 | - Current Term: (leave this blank) 5 | 6 | # Purpose 7 | [purpose]: #purpose 8 | 9 | (why are we doing this?) 10 | 11 | # Objectives/Goals 12 | [objectives/goals]: #objectives/goals 13 | 14 | (what are we doing, exactly? list) 15 | 16 | # Risks 17 | [risks]: #risks 18 | 19 | (what trouble might we run into? tradeoffs? reasons to not do this?) 20 | 21 | # Milestones 22 | [milestones]: #milestones 23 | 24 | (what time frame do we expect to accomplish pieces of work? how will we break it up?) 25 | 26 | # Participants/R&R 27 | [participants/r&r]: #participants/r&r 28 | 29 | (list names and role/responsibility) 30 | 31 | # Returns/Measurement 32 | [returns/measurement]: #returns/measurement 33 | 34 | (what do we expect to accomplish or expected outcome? how we will know we are successful?) 35 | 36 | # Project Board/Meeting Notes 37 | [project board/meeting notes]: #project board/meeting notes 38 | 39 | (where do we keep track of the work?) 40 | -------------------------------------------------------------------------------- /working_groups/wg-Cloud/README.md: -------------------------------------------------------------------------------- 1 | # Cloud Working Group 2 | 3 | ## Captain 4 | [Nick Hughes](https://github.com/nicholasmhughes) 5 | 6 | ## Participants 7 | * [Swaminathan](https://github.com/swamguru) 8 | * [Ben Gridley](https://github.com/bgridley) 9 | * [Cedric Bosdonnat](https://github.com/cbosdo) 10 | * [Adam C. Greenfield](https://github.com/admgre) 11 | * [Peter Norton](https://github.com/pcn) 12 | * [Vernon Cole](https://github.com/vernondcole) 13 | * [Prashanth Goud B](https://github.com/prashanthbgoud) 14 | * [Tyler Johnson](https://github.com/Akm0d) 15 | * [Michael Verhulst](https://github.com/verhulstm) 16 | * [Daniel Wallace](https://github.com/gtmanfred) 17 | * [Nick Garber](https://github.com/nickgarber) 18 | 19 | 20 | ## Contact 21 | * [Slack](https://saltstackcommunity.slack.com/messages/C7KKMMYDQ/) 22 | * [Working-Groups](working-groups@saltstack.com) email contacts Sage Robins and Janae Andruss 23 | 24 | ## Meeting Details 25 | Currently, the group voted to meet on the 2nd Monday every month at 4 PM Moutain, but due to inactivity the group is on pause. 26 | 27 | * You can get the Outlook Shared Calendar [HTML link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.html) or the [ICS link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.ics) but these aren't great, there is also this new page with details of all [Working Groups](https://saltproject.io/home/working-groups/) 28 | 29 | -------------------------------------------------------------------------------- /working_groups/wg-Cloud/meeting-notes/2019-06-14.md: -------------------------------------------------------------------------------- 1 | # 2019-06-14 Meeting (Friday 1400 UTC) 2 | 3 | ## Attendees intro and interest 4 | 5 | * Daniel Wallace: leading the working group, has worked on salt-cloud in the past. 6 | * Ben Gridley: interested in using salt-cloud to interact with AWS 7 | * Peter Norton: interested in improving the usability of salt-cloud 8 | * Tyler Johnson: working for saltstack on core 9 | * Swaminathan: certs in aws and salt and works with vmware too. Exp. with chef and interested in helping improve salt-cloud. 10 | * Cedric Bosdonnat: Works for SUSE and contributes to libvirt. Improve salt's libvirt support. 11 | * Nick Garber: using Salt for VMware with interest in AWS and Azure 12 | 13 | ## Scope and goals for this incarnation of the working group 14 | 15 | Daniel: 16 | 17 | The working group has a 6 month remit. The primary for this cycle is 18 | to document what needs to be in a salt cloud provider. 19 | 20 | Goals: 21 | * Standardize and document that salt-cloud drivers as being 22 | specifically for launching servers. 23 | 24 | * Document the above primary use case as being primary, and 25 | secondary use cases (e.g. DO networking actions) as being 26 | secondary/optional, so future implementors of cloud drivers know 27 | what needs to be present to provide as "complete" an 28 | implementation as any other. 29 | 30 | * The most complete drivers are currently AWS and DO. Use those as 31 | our baseline to document our standard. 32 | 33 | * For drivers that don't meet our standards, document that they 34 | are incomplete, and document why they are 35 | incomplete/broken/etc. and what needs to be done to fix it. 36 | 37 | * Specify tests that should be runnable for drivers. 38 | 39 | * Move salt-cloud to using the sls renderer instead of maps. 40 | 41 | * Map files are plain yaml that needs to be rendered out, and 42 | which aren't used in any other part of salt, so by leveraging 43 | the state/sls renderer, maps and potentially profiles etc. could 44 | be made easier to manage. 45 | 46 | * Move salt-cloud out of salt via fractus 47 | 48 | * Cloud providers release features on a cadence that is faster 49 | than salt releases. Salt-cloud or fractus are just runners, so 50 | could be added to the runner path to be loaded. 51 | 52 | * AWS specifically provides botocore and boto3 which is in-sync 53 | with their API. To add new features, it should be as simple as 54 | installing the appropriate version of boto3 with the new 55 | feature, and writing an action that passes arguments to the 56 | API. This should make it possible to add more features to 57 | cloud/fractus quickly - much faster than the salt release cycle. 58 | 59 | 60 | The community github will be used to create and track issues. 61 | 62 | ### Actions from this meeting 63 | 64 | * Document requirements for a cloud driver 65 | * Tickets created for the group for going through the cloud 66 | drivers and determining what needs to be done to meet the 67 | requirements. Due Date: 2019-06-21 68 | 69 | * Blog post by 2019-07-12 by Daniel describing the use of SLS for 70 | replacing maps in cloud. 71 | 72 | ### Other notes/topics 73 | * Observation from Cedric re: libvirt, there may be an opportunity to 74 | distinguish cloud providers that have a complete 75 | implementation/API/support in cloud, from lower-level cloudish APIs 76 | like libvirt that e.g. don't handle OS images, etc. Also, libvirt 77 | code is distributed in 2 places in the code. It's desirable to 78 | consolidate this. 79 | 80 | * Type annotations and type checking was discussued. Salt isn't going 81 | to be completely past python 2.7 and python 3.4 until the magnesium 82 | (atomic weight 12) or aluminum (13) release, so they're a desirable 83 | goal but will be brought in for work when they don't introduce 84 | incompatibility with the test suite (using in-line syntax). 85 | 86 | * There was an idea presented by Daniel about using possible future 87 | features in slots in order to make cloud actions idempotent. 88 | 89 | * Kubernetes was discussed, not clear how it would/could fit in with 90 | the cloud at this point. 91 | -------------------------------------------------------------------------------- /working_groups/wg-Cloud/meeting-notes/2019-07-12.md: -------------------------------------------------------------------------------- 1 | # 2019-07-12 Meeting (Friday 1400 UTC) 2 | 3 | ## Attendees 4 | 5 | * Daniel Wallace 6 | * Tyler Johnson 7 | * Swaminathan 8 | * Cedric Bosdonnat 9 | * Adam Greenfield 10 | * Michael Verhulst 11 | * Tom Chong 12 | * Max Arnold 13 | * Vernon Cole 14 | 15 | ## Notes 16 | 17 | * Daniel over estimated the amount of time he had. Planned on deligating more. 18 | * Max, Adam, Swami and Michael are all going to work on documenting what we currently have in the salt cloud providers. 19 | * We request the ability to be able to see the output from Cloud integration tests. 20 | * Daniel is going to commit 5 hours before next month to triaging open salt-cloud bugs, and figure out what is actually a bug and what is unimplemented. 21 | 22 | ### Actions from this meeting 23 | 24 | - [ ] Document functions in all cloud drivers (grouped by usage) 25 | * Max Arnold 26 | * Swami G 27 | * Michael Verhulst 28 | * Adam Greenfield 29 | - [ ] Spend 5 hours triaging and categorizing open cloud issues. 30 | * Daniel Wallace 31 | - [ ] Discuss with the Salt SRE team about how we can see the results of the output from the SaltCloud integration tests. 32 | * Tyler Johnson 33 | - [X] Submit a Talk for SaltConf 2019 about Fractus. 34 | * Daniel Wallace 35 | 36 | ## Links 37 | 38 | [Cloud Driver Functions](https://docs.google.com/spreadsheets/d/1IAjslY9ZDR1u8F4C0_t-0WFUBTi-j4ZGcndjqaJfgfA/) - Google Doc 39 | 40 | [Cloud Test Results](https://jenkinsci.saltstack.com/job/2017.7.9/view/Cloud/) - They 403, we would like them not to. 41 | -------------------------------------------------------------------------------- /working_groups/wg-Cloud/meeting-notes/2019-08-09.md: -------------------------------------------------------------------------------- 1 | # 2019-07-12 Meeting (Friday 1400 UTC) 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Nick Garber 7 | * Tyler Johnson 8 | * Swaminathan G 9 | * Cedric Bosdonnat 10 | * Adam Greenfield 11 | * Michael Verhulst 12 | * Tom Chong 13 | * Max Arnold 14 | * Vernon Cole 15 | 16 | ## Notes 17 | 18 | * Megan (@ch3ll) stepping up while Dan (@gtmanfred) is temporarily unable to attend. 19 | * Dan requested (in advance) we discuss progress on: 20 | - what we found from catagorizing the cloud drivers 21 | - make sure we know which ones are fully supported from the writing a cloud driver doc 22 | - which ones do not have everything required from there 23 | - where we are with getting access to the testing results 24 | * Swami shared link to Google Doc with [Cloud Driver Functions] audit progress. 25 | 26 | ### Actions from this meeting 27 | 28 | - [ ] Document functions in all cloud drivers (grouped by usage) 29 | * Max Arnold 30 | * Swami G 31 | * Michael Verhulst 32 | * Adam Greenfield 33 | - [ ] Spend 5 hours triaging and categorizing open cloud issues. 34 | * Daniel Wallace 35 | - [ ] Discuss with the Salt SRE team about how we can see the results of the output from the SaltCloud integration tests. 36 | * Tyler Johnson 37 | - [ ] Check for cloud drivers that have 0 tests 38 | * Nick Garber (with assistance from Megan Wilhite) 39 | 40 | 41 | ## Links 42 | 43 | [Cloud Driver Functions](https://docs.google.com/spreadsheets/d/1IAjslY9ZDR1u8F4C0_t-0WFUBTi-j4ZGcndjqaJfgfA/) - Google Doc 44 | 45 | [Cloud Test Results](https://jenkinsci.saltstack.com/job/2017.7.9/view/Cloud/) - They 403, we would like them not to. 46 | 47 | [Triage Process](https://docs.google.com/document/d/1SHCtwommGgTVArb_YnPN09B4y-tG30pPMXXkh2qBujU/) 48 | 49 | -------------------------------------------------------------------------------- /working_groups/wg-Documentation: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /working_groups/wg-MacOS/README.md: -------------------------------------------------------------------------------- 1 | # MacOS Working Group 2 | 3 | ## Captain 4 | [Wesley Whetstone](https://github.com/weswhet) 5 | 6 | ## Participants 7 | * [Joaquín](https://github.com/lctrkid) 8 | * [Brian LaShomb](https://github.com/lashomb) 9 | * [Shea Craig](https://github.com/sheagcraig) 10 | * [Kris Anthony](https://github.com/Kris-anthony) 11 | 12 | ## Project Board 13 | [Github Project](https://github.com/saltstack/salt/projects/18) 14 | 15 | ## Contact 16 | * [Slack](https://saltstackcommunity.slack.com/messages/C8VH92RJT) 17 | * [Salt-Mac](mailto:salt-mac@saltstack.com) this email goes to Sage Robins and Gareth Greenaway 18 | 19 | ## Meeting Details 20 | Group meetings the 3rd Tuesday monthly at 11:30 AM Mountain 21 | 22 | * Outlook Shared Calendar links: 23 | [HTML link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.html) or the [ICS link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.ics) 24 | * See our [Working Groups](https://saltproject.io/home/working-groups/) page for more details 25 | 26 | 27 | -------------------------------------------------------------------------------- /working_groups/wg-Networking/README.md: -------------------------------------------------------------------------------- 1 | # Networking Working Group 2 | 3 | ## Captain 4 | * TBD - currently this group is not meeting 5 | 6 | ## Participants 7 | * [Alberto Planas](https://github.com/aplanas) 8 | * [Andrew Dampf](https://github.com/wasabi222) 9 | * [Jochen Breuer](https://github.com/brejoc) 10 | * [Pablo Suárez Hernández](https://github.com/meaksh) 11 | * [Mihai Dinca](https://github.com/dincamihai) 12 | * [Yeshwanth Ambati](https://github.com/Network) 13 | * [Lawrence Bird](https://github.com/TheBirdsNest) 14 | * [Chad Geary](https://github.com/chadgeary) 15 | * [Swaminathan](https://github.com/swamguru) 16 | * [Wayne Werner](https://github.com/waynew) 17 | * [Zach Moody](https://github.com/zachmoody) 18 | 19 | ## Project Board 20 | [Github Project]() 21 | 22 | ## Contact 23 | * [Slack](https://saltstackcommunity.slack.com/messages/C7KPR0ZDK) 24 | * [Google Group](https://groups.google.com/forum/#!forum/salt-networks) 25 | 26 | ## Meeting Details 27 | * Outlook Shared Calendar links: 28 | [HTML link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.html) or the [ICS link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.ics) 29 | * See our [Working Groups](https://saltproject.io/home/working-groups/) page for more details 30 | 31 | 32 | ## Notes 33 | * Currently paused 34 | -------------------------------------------------------------------------------- /working_groups/wg-Release/README.md: -------------------------------------------------------------------------------- 1 | - Salt Working Group Name: Release 2 | - Description: Improving the Salt release process. 3 | - Current Captain: [Pablo Suárez Hernández](https://github.com/meaksh) 4 | - Current Term: (leave this blank) 5 | 6 | 7 | # Purpose 8 | [purpose]: #purpose 9 | 10 | * Make the Salt release process more transparent 11 | * Identify pain points in the release process 12 | * Improve the workflow of releasing Salt 13 | * Provide a place for different OS vendors to discuss about the Salt release process 14 | 15 | 16 | # Objectives/Goals 17 | [objectives/goals]: #objectives/goals 18 | 19 | * Learn about the current release process of Salt 20 | * Identify the pain points of the release process #119 21 | * Research on improving the points identified above #120 22 | * Create proposal for improvement #121 23 | * Document/improve documentation of the release process #93 24 | 25 | 26 | # Risks 27 | [risks]: #risks 28 | TBD 29 | * ... 30 | 31 | # Milestones 32 | [milestones]: #milestones 33 | TBD 34 | * ... 35 | 36 | # Participants/R&R 37 | [participants/r&r]: #participants/r&r 38 | 39 | * [Pablo Suárez Hernández](https://github.com/meaksh) (Captain) 40 | * [Jochen Breuer](https://github.com/brejoc) 41 | * [Alexander Graul](https://github.com/agraul) 42 | * [Victor Zhestkov](https://github.com/vzhestkov) 43 | * ... 44 | 45 | 46 | # Returns/Measurement 47 | [returns/measurement]: #returns/measurement 48 | 49 | * Is the release process more transparent? 50 | 51 | * Have Salt release process improved any of the pain points? 52 | 53 | 54 | # Project Board/Meeting Notes 55 | [project board/meeting notes]: #project board/meeting notes 56 | 57 | * [Release Working Group Github Project](https://github.com/saltstack/community/projects/6) 58 | * [Slack](https://saltstackcommunity.slack.com/messages/C7KKN9P6W) 59 | * [Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) 60 | -------------------------------------------------------------------------------- /working_groups/wg-Release/meeting-notes/2021-06-09.md: -------------------------------------------------------------------------------- 1 | # 2021-06-09 WG Release Meeting 2 | 3 | topic: Salt Release Coordination Community Meeting 4 | date: 2021-06-09 5 | time: 17:00 CEST (UTC+2) 6 | where: zoom online meeting, hosted by VMware 7 | 8 | 9 | # Attendees (8x) 10 | 11 | * Bengamin Drung (Debian DD Salt packager) 12 | * Fede Grau (Debian community member Salt team) @donfede 13 | * Alexander Graul (SUSE) 14 | * Patrick McLean (Gentoo) 15 | * Sage Robins (VMware Salt) @sagetherage 16 | * Pablo Suárez Hernández (SUSE; led the meeting) @meaksh 17 | * Randy Thompson (GoDaddy; salt/Tiamat) 18 | * Victor Zhestkov @vzhestkov 19 | 20 | 21 | # Agenda 22 | - walkthrough of how doing releases of Salt at SUSE 23 | - goals to do the same with other distros, aiming to learn and improve 24 | - maybe Tiamat review 25 | 26 | 27 | # Notes 28 | - (PSH) reviewed agenda 29 | [see slide 02; 30 | https://github.com/saltstack/community/projects/60 31 | https://github.com/saltstack/community/issues/143 ] 32 | - (AG screenshare) walkthrough of SUSE Salt release process 33 | [see slide 03; 34 | https://github.com/openSUSE/salt/wiki#opensuse-salt-packaging ] 35 | - SUSE supports multiple distributions, including openSUSE and SUSE Linux Enterprise 36 | - use "OBS" (Open Build Service; [not Open Broadcast Software]) to build 37 | - new Salt releases amounts to creating new branch on openSUSE 38 | [see slide 04; 39 | https://github.com/openSUSE/salt-packaging/tree/3000/salt ] 40 | - helper tool generates patches, in a different repo (Git on github) 41 | - SUSE uses upstream tarball as is, with patches on top 42 | - Git commit messages, often a single line, are used to autogenerate Changelog 43 | - OBS can build containers and OS images 44 | [see slide 05: 45 | https://build.opensuse.org/project/show/systemsmanagement:saltstack:products ] 46 | - due to "political reasons", SUSE does not change the version number 47 | - RPM spec file quick review 48 | - "MU branches are complicated" [seem ok to ignore initially] 49 | - OBS follows a similar process to Git with "branches" 50 | - OBS uses a "service" file 51 | [see slide 06] 52 | - OBS also builds for different distributions, including CentOS, Fedora, Ubuntu 53 | - "nothing from pip is used directly; only SUSE's own validated RPMs" 54 | 55 | - Q/A for walkthrough of SUSE Salt release process 56 | - BD Q - "version number review" 57 | "upstream version-release.rebuild" 58 | 59 | - FG Q - "do you package full Salt or just minion client for other distros, 60 | and why? are Windows builds included?" 61 | [answered in part by OBS screenshare; full Salt is built if possible] 62 | "SUSE builds various Salt packages for another software product they 63 | support 'uyuni' (spacewalk successor) 64 | [ https://www.uyuni-project.org/ ] 65 | "no current support for Windows" 66 | 67 | - FG Q - "are repos accessed only by SUSE employees, or also community?" 68 | "SUSE uses open development model hosted on github, and are open to 69 | community contributions; though few are received" 70 | "in OBS members have 'submit' and 'review' process, much like Git and github" 71 | [see slide 07 72 | https://build.opensuse.org/package/requests/systemsmanagement:saltstack:products:testing/salt ] 73 | 74 | 75 | - (17:30) (Randy) impromptu review of "tiamat" 76 | [ ? https://gitlab.com/saltstack/pop/tiamat ] 77 | - overview "pop wrapper to pi-installer"; helps build any codebase 78 | - pulls in all deps via requriments, source package 79 | - also includes shared libraries (optional) 80 | - creates a dynamic binary, "staticx" 81 | [ ? https://pypi.org/project/staticx/ ] 82 | - still in beta; systemd bug starting 83 | - tiamat is used at GoDadddy 84 | - BD Q - purpose? 85 | "easier deployment of Salt, via a single binary for master, minion" 86 | "lower entry to deploy code" 87 | - unclear if a Salt Project priority, but GoDaddy is using it 88 | - shared library security patches can optionally be used 89 | - pip security updates, "pip install within binary" 90 | - RT has some ideas to support SUSE model of using RPMs instead of pip 91 | - regular tiamat contributors include "Pedro, RT, and ?'karl'" 92 | 93 | 94 | - (17:45) Open Table 95 | - BD "patches" and getting all patches upstream 96 | - Debian has ~15-20 currently; SUSE has hundreds 97 | - ideally upstream patches have open MR/PR 98 | - AG "SUSE tries to present patches upstream" "some patches are SUSE specific" 99 | - PSH "SUSE procedures require upstream PR with patches" 100 | - PSH review next meeting action items [see below] 101 | - check if there is interest in OBS quick intro? 102 | - next meeting in 1 month [FIXME: actual date] 103 | 104 | 105 | # Action Items 106 | - ?Debian (or Gentoo) prepare presentation of Salt release flow 107 | - (FG) could be open to drafting some slides for Debian Salt Team review 108 | 109 | - (17:56) close call 110 | 111 | 112 | -------------------------------------------------------------------------------- /working_groups/wg-Release/meeting-notes/2021-07-14.md: -------------------------------------------------------------------------------- 1 | # 2021-07-14 WG Release Meeting 2 | 3 | topic: Salt Release Working Group 4 | date: 2021-07-14 5 | time: 17:00 CEST (UTC+2) 6 | where: zoom online meeting, hosted by VMware 7 | 8 | 9 | ## Attendees (6x) 10 | 11 | * Enno Gotthold (SUSE) 12 | * Fede Grau (Debian community member Salt team) @donfede 13 | * Patrick McLean (Gentoo) 14 | * Sage Robins (VMware Salt) @sagetherage 15 | * Pablo Suárez Hernández (SUSE; led the meeting) @meaksh 16 | * Victor Zhestkov @vzhestkov 17 | 18 | 19 | ## Agenda 20 | * open 21 | * explore future Release process presenters 22 | 23 | 24 | ## Meeting Details 25 | 26 | - PSH recap last meeting's presentation 27 | - check for community volunteers to present their release process 28 | https://github.com/saltstack/community/issues/144 29 | - FG offer to try and prepare Debian release process presentation for next meeting 30 | https://github.com/saltstack/community/issues/147 31 | - PM inquired if a "micro release" of Salt was possible a few days before 32 | meeting; this would allow for a live demo of package update 33 | 34 | - reviewed Release Working Group github project board 35 | https://github.com/saltstack/community/projects/6 36 | - wg goal to review, improve, and document Release process 37 | - wg goal to improve CVE coordination 38 | - reviewed and updated attendee access on https://github.com/saltstack/community 39 | 40 | - open table 41 | - nothing 42 | 43 | - (17:30 CEST) close call 44 | 45 | - next meeting scheduled for 2021-Aug-11 17:00 CEST (UTC+2) 46 | 47 | 48 | ## Actions 49 | - [ ] 2021-08-11 https://github.com/saltstack/community/issues/147 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /working_groups/wg-Release/meeting-notes/salt_release_debian_presentation_2021-09-08_final.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/saltstack/community/ae0026dbc29024599c2377c2c0fc60a30d54440b/working_groups/wg-Release/meeting-notes/salt_release_debian_presentation_2021-09-08_final.pdf -------------------------------------------------------------------------------- /working_groups/wg-SSH/README.md: -------------------------------------------------------------------------------- 1 | # SSH Working Group 2 | 3 | ## Captain 4 | [Megan Wilhite](https://github.com/ch3ll) 5 | 6 | ## Participants 7 | * [Chad Geary](https://github.com/chadgeary) 8 | * [Swaminathan](https://github.com/swamguru) 9 | * [Jochen Breuer](https://github.com/brejoc) 10 | * [Pablo Suárez Hernández](https://github.com/meaksh) 11 | * [Mihai Dinca](https://github.com/dincamihai) 12 | * [Balvinder Singh Rawat](https://github.com/balrawat) 13 | 14 | ## Project Board 15 | [Github Project]() 16 | 17 | ## Contact 18 | * [Slack](https://saltstackcommunity.slack.com/messages/CK7LFCW92) 19 | * [Google Group](https://groups.google.com/a/saltstack.com/forum/#!forum/salt-ssh) 20 | 21 | ## Meeting Details 22 | * Outlook Shared Calendar links: 23 | [HTML link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.html) or the [ICS link](https://outlook.office365.com/owa/calendar/105f69bacd4541baa849529aed37eb2d@vmware.com/434ec2155b2b4cce90144c87f0dd03d56626754050155294962/calendar.ics) 24 | * See our [Working Groups](https://saltproject.io/home/working-groups/) page for more details 25 | 26 | 27 | ## Notes 28 | * Currently paused 29 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2019-06-20.md: -------------------------------------------------------------------------------- 1 | # 2019-06-20 Meeting (Friday 1600 UTC) 2 | 3 | 4 | ## Attendees 5 | 6 | * Megan Wilhite: @Ch3LL works for saltstack. helping lead the ssh working group 7 | * Chad Geary: @chadgeary linux admin full time, using salt 8 | * Balvinder: @balrwat: currently using salt and wants to help make it better 9 | * Tom Hatch: @thatch45 Architected Salt-SSH 10 | * Gareth Greenaway: @garethgreenaway works for saltstack, helping facilitate meeting 11 | * Wayne Warner: @waynew works for saltstack, helping facilitate meeting 12 | * Kayva Chandrashehar: @KChandrashekhar works for saltstack, project manager for open team 13 | 14 | ## Goals for Sodium Release 15 | 16 | Megan: 17 | - Python 2 to Python 3 Migration for Salt-SSH. There is currently a 18 | SEP here: https://github.com/saltstack/salt-enhancement-proposals/pull/11 19 | that outlines the work that will need to occur. 20 | - Want to tackle these bugs for the Sodium release: 21 | https://github.com/saltstack/salt/issues?q=is%3Aopen+is%3Aissue+label%3Ateam-ssh+label%3A%22High+Severity%22+label%3Atriage 22 | 23 | Tom: 24 | - Tom is working on a POC to demonstrate Salt-SSH as a standalone project pulled 25 | out from salt. This standalone project will include using the asncio library, 26 | increase the speeds of salt-ssh, use python 3.6 and interface with pop: 27 | https://github.com/saltstack/pop/ 28 | - If the POC is successful the ssh working group will need to create a SEP detailing 29 | the deprecation path to migrate to the new project in two releases after Sodium. 30 | 31 | ## Actions 32 | 33 | - Megan will follow up with the SEP to ensure it gets merged. 34 | - Once the SEP is merged, Megan will create issues surrounding the tasks to complete the 35 | Python2 to Python3 Migration for Salt. 36 | - Tom will create a POC to demonstrate salt-ssh as a seperate project pulled out from salt. 37 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2019-08-08.md: -------------------------------------------------------------------------------- 1 | # 2019-08-08 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Gareth Greenaway 8 | * Wayne Warner 9 | * Tommy Chong 10 | 11 | ## Meeting Details 12 | 13 | - Issues were created in the community repo to help tackle the Python3 Salt-SSH task for the sodium release. They can be seen here: 14 | https://github.com/saltstack/community/issues?q=is%3Aopen+is%3Aissue+label%3ASalt-SSH 15 | - If anyone wants to work on an issue from the community repo or the list of bugs we want to tackle here: https://github.com/saltstack/salt/issues?q=is%3Aopen+is%3Aissue+label%3Ateam-ssh+label%3A%22High+Severity%22+label%3Atriage please comment on the issue since github permissions do not allow assignment. 16 | - More demo and details on heis- the new ssh POC tom is working on. 17 | 18 | ## Actions 19 | - Tom will make the new heis product public. 20 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2019-09-12.md: -------------------------------------------------------------------------------- 1 | # 2019-09-12 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Gareth Greenaway 8 | * Frode Gundersen 9 | * Tommy Chong 10 | * Tyler Johnson 11 | 12 | ## Meeting Details 13 | 14 | - More demo and details on heis- the new ssh POC Tom is working on. 15 | - New project salt-bin https://github.com/saltstack/salt-bin helps build salt and python for heis. 16 | Uses pyinstaller and staticx. 17 | - heis can dynamically update salt versions 18 | - Unit test suite added to heis 19 | 20 | ## Actions 21 | - Tyler is working on adding integration tests to heis. 22 | - Tom is improving on some issues with the salt binary and querying multiple minions 23 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2019-10-10.md: -------------------------------------------------------------------------------- 1 | # 2019-10-10 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Gareth Greenaway 8 | * Daniel Wozniak 9 | * Tommy Chong 10 | 11 | ## Meeting Details 12 | 13 | Heist Update 14 | - The heis project was renamed to heist. 15 | - Auto download of artifacts. (the salt-bin binary) 16 | - Added the clustershell, scan and flat roster. 17 | - Sudo now works. 18 | - Bootstrap minions with heist to communicate with specific master. 19 | 20 | Salt-Bin Update 21 | - Tom demoed the salt-bin project to build salt into portable binaries. 22 | It currently builds a working mac and linux binary. Still working out 23 | some issues with the windows build. 24 | 25 | ## Actions 26 | - Current backlog for heist: https://github.com/saltstack/heist/issues 27 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2019-12-12.md: -------------------------------------------------------------------------------- 1 | # 2019-12-12 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Tommy Chong 8 | 9 | ## Meeting Details 10 | 11 | Heist Update 12 | - Heist was officially announced at SaltConf and there was a lot of excitment! 13 | - We had a sprint focused on heist and a couple of issues were logged that 14 | we will need to clean up. https://github.com/saltstack/heist/issues 15 | - Will need to do a new release with current fixes and fixes to resolve 16 | some of these issues. This will be done either this week or next. 17 | - Megan created a heist demo with docker, which makes it easy to see the power 18 | of docker just by running `docker-compose up`: 19 | https://github.com/Ch3LL/heist-docker-demo 20 | 21 | Salt-SSH Post Neon 22 | - We are ramping up to get a RC out for neon by the first part of January. 23 | Once neon is out, the ssh working group will need to shift a lot of focus 24 | to the work that needs to be done to deprecate python2 for salt-ssh. The 25 | issues to track this work are located here: 26 | https://github.com/saltstack/community/issues?q=is%3Aopen+is%3Aissue+label%3ASalt-SSH 27 | 28 | Pop EcoSystem Update from Tom 29 | - updates to rend to make it more asynchronous 30 | - currently working on a secrete store system refered to as takara 31 | - will also need to do a release of idem and rend soon. 32 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2020-01-09.md: -------------------------------------------------------------------------------- 1 | # 2020-01-09 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Tommy Chong 8 | 9 | ## Meeting Details 10 | 11 | Salt-Bin Update (pop-build) 12 | - The publish_port PR to ensure heist works has been merged into neon 13 | (https://github.com/saltstack/salt/pull/55730) This will ensure we 14 | don't need to point to a personal repo in the requirements.txt file 15 | in salt-bin. Once neon is released we can remove this line 16 | `git+https://github.com/Ch3LL/salt.git@v2019.2.2-1` 17 | from the requirements.txt file in salt-bin repo. 18 | - There is a new project pop-build (https://github.com/saltstack/pop-build) 19 | The idea behind this project was to combine both pop-seed and salt-bin. 20 | Using this issue https://github.com/saltstack/pop-build/issues/1 to track 21 | the work to add salt-bin to pop-build 22 | 23 | Review Issue: https://github.com/saltstack/salt/issues/49840 24 | - It was decided that we sould remove the line where it 25 | is resolving the dns as its not required and causes 26 | buggy behavior. 27 | 28 | ## Actions 29 | - add fix and test for https://github.com/saltstack/salt/issues/49840 30 | - remove the personal repo pointer in salt-bin once neon is released 31 | - https://github.com/saltstack/pop-build/issues/1 32 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2020-02-13.md: -------------------------------------------------------------------------------- 1 | # 2020-02-13 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tom Hatch 7 | * Tommy Chong 8 | * Gareth Greenaway 9 | 10 | ## Meeting Details 11 | 12 | Salt-Bin Update (pop-build) 13 | - The custom salt tag to install from in salt-bin has been removed: 14 | `git+https://github.com/Ch3LL/salt.git@v2019.2.2-1` 15 | has been updated to just `salt` with the release of neon. 16 | - The pop projects have been moved to gitlab. 17 | - The new project pop-build has now been updated to build salt. 18 | The salt-bin repo is still being used to store the configurations 19 | needed for pop-build to build the salt binary. 20 | 21 | Salt-SSH Sprint: 22 | - Megan will investigate the possibility of running a salt-ssh sprint 23 | for the next meeting to help tackle the issues in this list: 24 | https://github.com/saltstack/salt/issues?q=is%3Aopen+is%3Aissue+label%3Ateam-ssh+label%3A%22High+Severity%22+label%3Atriage 25 | 26 | ## Actions 27 | - Megan will reach out to community manager to help organize the sprint. 28 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2020-03-12.md: -------------------------------------------------------------------------------- 1 | # 2020-03-12 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tommy Chong 7 | * Cassandra Faris 8 | 9 | ## Meeting Details 10 | 11 | - Discussed in more detail the salt-ssh sprint we want to do to tackle the salt-ssh bug list 12 | Cassandra stated will need 3-4 weeks to properly communicate the sprint out to community. 13 | Megan will work directly with Cassandra to plan these details. 14 | 15 | - Discussed the python2 deprecation work that will need to be done for Sodium: 16 | -> need to write new python version support SEP 17 | -> add ability for salt-ssh to copy over salt-bin binary to run salt-call with 18 | if python versions differ. 19 | -> add ability for someone to run a custom script before salt-ssh runs in order 20 | to install python3. 21 | -> add documentation and communicate across all channels 22 | (many of these steps are outlined in the original salt-ssh python3 SEP 23 | https://github.com/saltstack/salt-enhancement-proposals/pull/11) 24 | 25 | ## Actions 26 | - Megan working on python versions SEP and rest of the work outlined above. 27 | - Megan and Cassandra will plan out a salt-ssh sprint 28 | -------------------------------------------------------------------------------- /working_groups/wg-SSH/meeting-notes/2020-04-09.md: -------------------------------------------------------------------------------- 1 | # 2020-04-09 Meeting 2 | 3 | ## Attendees 4 | 5 | * Megan Wilhite 6 | * Tommy Chong 7 | * Cassandra Faris 8 | * Gareth Greenaway 9 | 10 | ## Meeting Details 11 | 12 | - Discussed in more detail the salt-ssh sprint. We will have this setup post Sodium 13 | and after Megan returns from leave (around July/August) 14 | 15 | - Discussed the python2 deprecation work that will need to be done for Sodium: 16 | -> Demod new ssh_pre_flight feature: https://github.com/saltstack/salt/pull/56488 17 | 18 | ## Actions 19 | - Megan researching ssh_ext_alternatives to see if there are any improvements to be made. 20 | -------------------------------------------------------------------------------- /working_groups/wg-Security/README.md: -------------------------------------------------------------------------------- 1 | - Salt Working Group Name: Security 2 | - Description: 3 | - Current Captain: (name, gh handle and link or other means of contact) 4 | - Current Term: (leave this blank) 5 | 6 | # Purpose 7 | [purpose]: #purpose 8 | 9 | * Ensure that when user installs Salt, they get an installation that minimises risks but doesn't impact on their ability to use the full power of Salt 10 | 11 | * Provide documentation that helps users configure Salt to meet their needs with exposing themselves to security issues 12 | 13 | * Support the community to help them develop, deploy and operate Salt securely 14 | 15 | 16 | # Objectives/Goals 17 | [objectives/goals]: #objectives/goals 18 | 19 | * Update Salt packages to configure all components with least possible privilege 20 | 21 | * Update Salt packages to configure file system permissions, groups and Salt so that users can use Salt without being root 22 | 23 | * Develop AppArmour or SELinux profiles to include in Salt packages where distributions support those 24 | 25 | * Review and improve existing documentation for securing Salt 26 | 27 | * Produce and mantain guides for securing and hardening Salt components (eg API, ZeroMQ) 28 | 29 | * Review of remotely accessible components for design issues and relevance (??) 30 | 31 | * Review of modules for security issues (??) 32 | 33 | # Risks 34 | [risks]: #risks 35 | 36 | * Making default package installations function differently may cause issues with existing installations. This can be managed/mitigated 37 | 38 | * Making default package installations more secure may increase friction for new users. This can be managed/mitigated with some thought. 39 | 40 | * There are some known issues (especially around PAM authentication) and running masters as non-root that will cause some issues, but should be solvable. 41 | 42 | * There may be resistance from the community against siginificant changes to how default installations of Salt work. 43 | 44 | 45 | # Milestones 46 | [milestones]: #milestones 47 | 48 | * Updated packages 49 | * Salt master running as non root user with least possible privilege 50 | * Package managed groups to allow users to run salt tools as non root user 51 | * Filesystems permissions set to allow users in managed groups to use salt 52 | * Working publisher ACL configuration tied to groups 53 | 54 | * AppArmour and SELinux profiles included in packages 55 | 56 | * Documentation updated to reflect new package install defaults 57 | 58 | * Securing Salt documentation updated 59 | 60 | * Series of pragmatic hardening guides produced for various Salt components: 61 | * Salt API 62 | * ?? 63 | 64 | # Participants/R&R 65 | [participants/r&r]: #participants/r&r 66 | 67 | (list names and role/responsibility) 68 | 69 | # Returns/Measurement 70 | [returns/measurement]: #returns/measurement 71 | 72 | * Default package installs are reasonably secure but don't cause users to turn off or work round supplied configuration 73 | 74 | * Users are using and recommending the documentation we produce 75 | 76 | * Future CVEs are mitigated for users using the default package config 77 | 78 | * Users with more complex requirements are able to improve the security of their Salt infrastructure by using the using the hardening guides, even where they have to expose some of their infrastructure to untrusted networks 79 | 80 | # Project Board/Meeting Notes 81 | [project board/meeting notes]: #project board/meeting notes 82 | 83 | (where do we keep track of the work?) 84 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2021-AUG-09-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2021-AUG-09 Security Workin Group Monthly Meeting 2 | 3 | ## Project Boards and issues 4 | 5 | - [New board](https://github.com/saltstack/salt/projects/22) has been set up to replace the [org level board](https://github.com/orgs/saltstack/projects/35) we had been using 6 | - Barney to discuss getting access to new board and how it's expected to be used with Jeff Blair. 7 | - Not clear if opening issues as "Feature request" to track work for SEP19/PoC is the correct thing to do. Barney to raise with Jeff 8 | 9 | ## SEP19 update 10 | 11 | - [New PR for SEP19](https://github.com/saltstack/salt-enhancement-proposals/pull/55) 12 | - WG members to review and comment on changes and ensure it covers our previous discussions and comments in the [original PR](https://github.com/saltstack/salt-enhancement-proposals/pull/35) 13 | - Barney to open issues for the [unresolved questions](https://github.com/saltstack/salt-enhancement-proposals/blob/1142a50016dad80d41269efff264f4ed3525d15f/0019-master-non-root.md#unresolved-questions) 14 | - Alexander raised some issues around salt-ssh and required permissions for keys. He'll look into those and add a comment on the PR. 15 | 16 | ## Actions 17 | 18 | - Barney to discuss project boards and issues with Jeff 19 | - Barney to open issues for SEP19 unresolved questions 20 | - Alexander to add comments about salt-ssh and permissions 21 | 22 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2021-JUN-14-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2021-JUN-14 Security Working Group Monthly Meeting 2 | 3 | ## Agenda: Group Expectations and [SEP 19](https://github.com/saltstack/salt-enhancement-proposals/pull/35) 4 | 5 | ## Group Expectations 6 | 7 | - Working on some issues 8 | - Reduce risks 9 | - Please read the Group's [Project Charter](https://github.com/saltstack/community/tree/master/working_groups/wg-Security) 10 | - Work around the Salt Master and associated network exposed services ie Salt API, reduce privileges they run with 11 | - Harden the initial installation of Salt "standard setup" 12 | - How to also install differently from a standard setup and provide doumentation for that 13 | - Salt master easiest, may look at Salt Minion later 14 | 15 | ## Salt Minion: Not run from root (SEP 19) 16 | 17 | SEP 19 broken into 2 parts: 1) namely running Salt as non-root, and 2) changing the location of Salt files, (configuration, daemons, etc.) 18 | - Running master and and salt api etc as non root 19 | - Minion running not as root, would be good, but better focus is on master and salt-ssh and API. 20 | - Possiblity to run minion as non root but using sudo (https://docs.saltproject.io/en/latest/ref/configuration/minion.html# sudo-user) 21 | - allow users to easily use the CLI clients (w/out requiring the use of sudo or similar) we could 22 | - list the issues - deploy Salt via pip non-run; would like the examples and docs to be updated and better written, please write up some issues 23 | - PAM and external auth - problematic, add the user that the salt daemons run as the shadow group, packages could default to not doing that have it selected at install - not ideal daemon user can read /etc/shadow - but better than running as root, avoids issues like shell injection attacks as root. 24 | - POC for this? 25 | - Grains: Salt Master loads some grains, if not running as root this could be a bigger problem - SUSE knows this has come up in the past; salt-user as non-root - salt-master and salt grains / only one that did not gracefully fail, but may be fixed; 26 | - Standard minion should be set as root user, initially 27 | - salt-ssh low hanging fruit here as well - move it up a level 28 | - handle perms with sudo internally. it's somewhat more...manual, but we only allow salt access to paths/binaries/cmd's specified in a sudoers.d file we create for the salt user 29 | - how that is run in Windows and Mac will need those experts to weigh in, as well, as noted from Sage to get them into the conversation 30 | - config files are definitely related, eg for writing SSH keys - that is likely why comments started to go that direction in the SEP - deal with it on a case by case basis, instead of rebuilding or re-architecting the config files 31 | 32 | ## Other WG - Packagers is within the Release WG 33 | 34 | - salt-pkg is the Tiamat packaging of Salt 35 | - exclude files 36 | - FPM built and include whatever else you may need/want 37 | - libC version the package was built on 38 | - salt-pkg3 is the packaging of rpms of Salt as is today for repo.saltproject.io 39 | - downstream packagers are part of the Release WG 40 | - each distro has it's own pipeline config 41 | 42 | ## Same signing key forever 43 | 44 | - New keys with new versions example Ubuntu 21.04 has a new key, but keeps it for the life of the version 45 | - start a draft on the project board 46 | 47 | ## Actions Assigned today 48 | 49 | - Sage to update project board with expectations (more details) as such as how to work async, discussions on SEPs 50 | - Sage to ask David Murphy to draft another or work with Barney on another SEP for config location changes - changing the location of Salt files and will need Windows and MacOS Working Groups opinions 51 | - Barney to review and draft changes to SEP19 52 | - Bryce and Sage to write up a draft in issues on this WG project board for rotation of GPG signing keys prior to writing a full SEP 53 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2022-APR-13-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2022-APR-13 Security Workin Group Monthly Meeting 2 | 3 | ## Project Boards and issues 4 | 5 | - [Project board](https://github.com/orgs/saltstack/projects/35) is back and Barney now has access again 6 | - Tasks can be added to that board and existing tasks for work to look at running Salt aas non-root (SEP19) have been added 7 | - Looking for people to pick up tasks - @viq said they may be able to lookk at some of those 8 | 9 | ## Alternative transports and PKI 10 | 11 | - Discussion around alternative transports and PKI in relation to: 12 | 13 | - [SEP32 - keyrotation](https://github.com/saltstack/salt-enhancement-proposals/pull/48) 14 | - [Recent CVEs and Cloudflare's Blog](https://blog.cloudflare.com/future-proofing-saltstack/) 15 | - [Demo of ActiveMQ based Transport at Saltconf2021](https://youtu.be/CcZSdzTutw0?list=PL9svBjLDUl_8j1hNjel7kZL3Ql4LMPOAG&t=2393) 16 | 17 | Agreed we'd follow up with Core team regarding mTLS transport that Cloudflare mentioned that "We have shared our preliminary results with Salt, and we are working together to add an mTLS-based transport upstream." 18 | 19 | Discussed whether using traditional PKI would be a benefit in the case of [SEP32](https://github.com/saltstack/salt-enhancement-proposals/pull/48) but there was no consensus 20 | 21 | ## Actions 22 | 23 | - @viq to look at Salt as non-root tasks 24 | - Barney to follow up on mTLS 25 | 26 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2022-JUL-13-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2022-JUL-13 Security Working Group Monthly Meeting 2 | 3 | ## Agenda 4 | 5 | * CVE announcement and release process 6 | * Pre-announcement 7 | * Release 8 | * Issues raised by community 9 | * Questions to Core Team 10 | * Current process docs 11 | * Process to change (SEP?) 12 | * Feedback on this CVE 13 | * Changes to process 14 | * Template for announcements 15 | * Any other issues 16 | 17 | ## Present 18 | 19 | * @barneysowood 20 | * @nicholasmhughes 21 | * @jneel 22 | * @mstrong ? 23 | 24 | ## Notes 25 | 26 | * Appear to be two main conflicting positions in the community, those that think there shouldn't be a pre-annoucement and those that think there should be. 27 | * There's also some feeling that if there is a pre announcement it should have more information to allow people to understand if they are likely to be affected. 28 | * Both positions are understandable but depend on the context of the user or their organisation 29 | * Not having a clear and consistent process exacerbates the situation 30 | * Delays in releasing or last minute changes further erode confidence in the process 31 | 32 | * Including information about what components are affected without revealing details of issue can be tricky 33 | * It should be possible in many cases to at least indicate the major component or subsystem - this would go someway to helping people to understand if they are likely to affected. 34 | 35 | * Setting timelines and meeting those is important for confidence in the process and to allow users to have people in place to deploy updates 36 | * Meeting those for all deployment methods is also important - or it should be clear which deployments methods can expect that 37 | 38 | * Releasing information about the full timeline after the patch release would be good 39 | * More information about impact (on a sliding scale?) could be released 40 | 41 | * Current documentation on security/release process is out of date or incorrect 42 | 43 | ## Actions 44 | 45 | * Talk to core team about timelines for past CVEs - @barneysowood 46 | * Ask core team for documentation on current process 47 | * Update public docs to reflect current process 48 | * Draft or update standard pre-announcement 49 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2022-SEP-14-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2022-SEP-14 Security Working Group Monthly Meeting 2 | 3 | ## Agenda 4 | 5 | * Last meeting notes 6 | * CVE releases 7 | * Project board 8 | * Any other issues 9 | 10 | ## Present 11 | 12 | * @barneysowood 13 | * @jneel 14 | 15 | ## Notes 16 | 17 | ### Discussion on CVE releases and onedir 18 | 19 | * How is onedir going to affect releases? 20 | * 3005 will be supported until 2024-02-24 so normal releases will have to be supported until then 21 | * Will that have an impact on release process? 22 | * For onedir releases, CVE issues in bundled dependencies will require a release 23 | * Has that process been worked out? 24 | * Notes in [PR 34 for SEP 26](https://github.com/saltstack/salt-enhancement-proposals/pull/34#issuecomment-687292534) - "That's correct, and a .x release would be made whenever needed to address a dependency security issue. We are screening our dependencies for security advisory issues and we would release updates when needed, or, information on how to proceed to upgrade a dependency." 25 | * Is there an automated process in place for scanning/alerting on issues in dependencies? (does this use dependabot?) 26 | * Salt will not get pre-warning of issues in dependencies, so will have to produce a new build once issue is public - how quickly will that happen? 27 | 28 | ## Actions 29 | 30 | * @barneysowood to reach out core team to discuss release process. Possiblye invite to next month's call 31 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2023-FEB-08-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2023-FEB-08 Security Working Group MOnthly Meeting 2 | 3 | ## Agenda 4 | 5 | * CVE release process 6 | * LTS/STS release plan 7 | * Github Actions CI/CD work 8 | 9 | ## Present 10 | 11 | * @barneysowood 12 | * @hunter 13 | 14 | ## Notes 15 | 16 | ### CVE Release process 17 | 18 | * No further updates since last meeting 19 | 20 | ### LTS/STS release plan 21 | 22 | * Discussed LTS/STS release plan 23 | * Agreed it looks good from a CVE release point of view 24 | * @hunter suggested ensuring clear communication of when releases leave active support and CVE/critical support will be important 25 | 26 | ### Github Actions CI/CD work 27 | 28 | * Discussed Github Actions CI/CD work as demoed on Community call, agreed that it is very positive step towards ensuring that salt is always in a releasable state and should help with CVE releases. 29 | 30 | ### Surfacing dependency information 31 | 32 | * Continued discussion on surfacing dependency information 33 | * Discussed dependabot not surfacing issues in Python or C library deps 34 | 35 | ## Actions 36 | 37 | * @barneysowood to follow up with Megan on 38 | * outstanding CVE Release process questions 39 | * documentation of process for handling vulnerabilities in onedir dependencies 40 | * @barneysowood to ask about communication plan for release status changes 41 | * @hunter to look at dependabot support for non-python package deps 42 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2023-JAN-11-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2023-JAN-11 Security Working Group MOnthly Meeting 2 | 3 | ## Agenda 4 | 5 | * CVE release process 6 | * SEP19 7 | * PR 59622 – disable netapi clients 8 | 9 | ## Present 10 | 11 | * @barneysowood 12 | * @nicholasmhughes 13 | * @hunter 14 | 15 | ## Notes 16 | 17 | ### CVE Release process 18 | 19 | * Discussions with core team regarding CVE Release process and documentation is ongoing 20 | * Update to Security disclosure policy to document pre-announcement is on master 21 | * Policy doesn't cover vulnerabilities in dependencies for Onedir builds 22 | * Currently python deps are checked with dependabot 23 | * Issue of lower level dependencies unclear 24 | 25 | ## Actions 26 | 27 | * @barneysowood to follow up with Megan on 28 | * outstanding CVE Release process questions 29 | * documentation of process for handling vulnerabilities in onedir dependencies 30 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2023-MAY-10.md: -------------------------------------------------------------------------------- 1 | # 2023-MAY-10 Security Working Group MOnthly Meeting 2 | 3 | ## Agenda 4 | 5 | * Core team participation - moving meeting 6 | * Upstreaming security related changes 7 | * Cloudflare - mTLS 8 | * Linkedin - various 9 | * 3006.0 release - salt user for salt-master 10 | * Docs 11 | 12 | ## Present 13 | 14 | * @barneysowood 15 | * @jneel 16 | 17 | ## Notes 18 | 19 | ### Core team participation 20 | 21 | * @Ch3LL would like to attend 22 | * Current time clashes with a core team meeting 23 | * Will look to move time, 1hr earlier 24 | 25 | ### Upstreaming security related changes 26 | 27 | * Cloudflare published blog post on [Future-proofing SaltStack](https://blog.cloudflare.com/future-proofing-saltstack/) 28 | * Key part of this was an mTLS based transport that they indicated they wanted to upstream - "We have shared our preliminary results with Salt, and we are working together to add an mTLS-based transport upstream". 29 | * Haven't heard anything further from them 30 | * LinkedIn publish blog post "[Scaling Salt for Remote Execution to support LinkedIn Infra growth](https://engineering.linkedin.com/blog/2023/scaling-salt-for-remote-execution-to-support-linkedin-infra-grow)", which mentions a number of changes they have made, including 31 | * PKI auth module for salt-api 32 | * Auth token management 33 | * Engine for monitoring executions and Salt ACLs 34 | * Should follow up with Cloudflare and LinkedIn to try and work with them to upstream those changes 35 | 36 | ### 3006.0 release - salt user for salt-master 37 | 38 | * Unclear why change was added between last RC and .0 release 39 | * [SEP19](https://github.com/saltstack/salt-enhancement-proposals/blob/master/accepted/0019-master-non-root.md) was accepted some time ago and outlines design for this, but that wasn't used 40 | * Disruption caused by last minute change and problems from that ([#64174](https://github.com/saltstack/salt/pull/64174), [#64193](https://github.com/saltstack/salt/issues/64193), [#64219](https://github.com/saltstack/salt/issues/64219)) are likely to cause more friction and make implementing other changes from SEP19 more difficult. 41 | * Would be good to understand why change were made when they were and why the SEP wasn't followed. 42 | 43 | ### Docs 44 | 45 | * Docs on [running salt as unprivileged user](https://docs.saltproject.io/en/latest/ref/configuration/nonroot.html) are very outdated and not up to date with 3006.0 46 | * Security/hardening docs are not easy to find, in multiple places and outdated 47 | * @jneel has some time to help with this but will need some assistance on where to start 48 | 49 | 50 | ## Actions 51 | 52 | * @barneysowood to finalise new time, get calendar/website updated and announce on slack 53 | * @barneysowood to follow up with Cloudflare and LinkedIn 54 | * @barneysowood to discuss 3006.0/salt user with core team 55 | * @barneysowood to open tickets on required docs updates and co-ordinate with @jneel 56 | 57 | -------------------------------------------------------------------------------- /working_groups/wg-Security/meeting-notes/2025-04-09-SecurityWG.md: -------------------------------------------------------------------------------- 1 | # 2025-04-09 Security Working Group monthly meeting 2 | 3 | ## Agenda 4 | 5 | * Security disclosure policy 6 | * Github private vuln reporting 7 | 8 | * Dependabot/dependency issues 9 | * relenv – how are dependencies and their vulns being tracked 10 | 11 | * Salt extensions 12 | * Review copier template, Github Actions and discussion with Salt extensions WG 13 | 14 | * Github Actions security 15 | * Review of Actions in main repo 16 | * Scanning - [Zizmor](https://github.com/woodruffw/zizmor) 17 | * Supply chain security with GHA 18 | 19 | * Github Issues spam 20 | * Repo settings 21 | * Tooling 22 | 23 | * ACL support for netapi SSE/websocket endpoints 24 | 25 | ## Present 26 | 27 | * Barney Sowood (@barneysowood) 28 | * Shane Lee (@twangboy) 29 | * Derek Ardolf (@ScriptAutomate) 30 | * Jim 31 | 32 | ## Notes 33 | 34 | ### Github private vulnerability reporting 35 | 36 | * Raised as possible way to simplify management of vulnerability reporting 37 | * Been investigated before - at that point issues with functionality (esp around private forks) 38 | * @ScriptAutomate to find previous issues [done] 39 | * @barneysowood to investigate and see if it would still be beneficial even without using private forks 40 | 41 | ### relenv dependencies 42 | 43 | * Discussion of how dependencies are tracked for relenv 44 | * @ScriptAutomate would like to see SBOM for relenv and salt builds 45 | * @barneysowood to discuss further with @dwoz 46 | 47 | ### salt-extenions Github Actions 48 | 49 | * Some concerns over permission usage in copier template 50 | * @barneysowood to complete further testing and discuss with maintainers 51 | 52 | ### Github Actions security for Salt repo 53 | 54 | * Discusion of security in GHA for Salt repo 55 | * Scanning with [Zizmor](https://github.com/woodruffw/zizmor) hasn't revealed any serious issues 56 | * Some minor issues to look at 57 | * Longer term, looking at simplification and reduction in reliance on 3rd party Actions 58 | * @barneysowood to open PR with minor fixes 59 | 60 | ### Github Issues spam 61 | 62 | * Problem recently on [saltstack/pepper](https://github.com/saltstack/pepper) repo 63 | * Some modifications to settings have helped but mainly relying on Github to catch and cleanup 64 | * No good solutions currently 65 | 66 | ### ACL support for netapi SSE/websocket endpoints 67 | 68 | * No support for ACLs on netapi for SSE/websockets currently 69 | * @barneysowood working on possible feature - open PR and discussion when ready 70 | 71 | -------------------------------------------------------------------------------- /working_groups/wg-Testing/README.md: -------------------------------------------------------------------------------- 1 | # Testing Working Group 2 | 3 | ## Captain 4 | [Mihai Dinca](https://github.com/dincamihai) 5 | 6 | ## Participants 7 | * [Pablo Suárez Hernández](https://github.com/meaksh) 8 | * [Jochen Breuer](https://github.com/brejoc) 9 | * [Alberto Planas](https://github.com/aplanas) 10 | * [Swaminathan](https://github.com/swamguru) 11 | 12 | ## Project Board 13 | [Github Project](https://github.com/saltstack/community/projects/6) 14 | 15 | ## Contact 16 | * [Slack](https://saltstackcommunity.slack.com/messages/C7KKN9P6W) 17 | * [Google Group](https://groups.google.com/a/saltstack.com/forum/#!forum/salt-testing) 18 | 19 | ## Meeting Details 20 | * [Click to add the Salt Community Events Google calendar to see the meeting details](https://calendar.google.com/calendar?cid=c2FsdHN0YWNrLmNvbV9tZDczYzN1ZmNzMmVxYnNtbW5pa2U0ZW04MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) 21 | 22 | ## Notes 23 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/README.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group 2 | 3 | ## Captain 4 | [Shane](https://github.com/twangboy) 5 | 6 | ## Participants 7 | * [Prashant Goud B](https://github.com/prashanthbgoud) 8 | * [Rares POP](https://github.com/rares-pop) 9 | * [rigel marcinik](https://github.com/rmarcinik) 10 | * [Markus](https://github.com/markuskramerIgitt) 11 | * [Joseph Eacott](https://github.com/xeacott) 12 | * [Chad McMarrow](https://github.com/cmcmarrow) 13 | 14 | ## Project Board 15 | [Github Project](https://github.com/saltstack/community/projects/4) 16 | 17 | ## Contact 18 | * [Slack](https://saltstackcommunity.slack.com/messages/C7U9FLK8S) 19 | * [Salt-Windows](mailto:salt-windows@saltstack.com) 20 | 21 | ## Meeting Details 22 | * The group meets the 2nd Tuesday monthly 23 | * [Zoom Meeting Link](https://vmware.zoom.us/s/95732069361) 24 | * [Working Groups page](https://saltproject.io/?page_id=35255) 25 | 26 | 27 | ## Notes 28 | https://github.com/saltstack/community/tree/master/working_groups/wg-Windows/meeting-notes 29 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2019-06-18.md: -------------------------------------------------------------------------------- 1 | # 2019-06-18 Meeting (Tuesday 1530 UTC) 2 | 3 | ## Introductions 4 | - Shane Lee: Leading the working group. SaltStack 5 | - Chad Mcmorrow: SaltStack 6 | - Joe Eacott: SaltStack 7 | - Markus Kramer: Combined bitTorrent with Salt, has many Windows clients 8 | - Rigel Marcinik: Standard usage of Salt 9 | 10 | ## Purpose 11 | Shane: 12 | Come together as a community to make Salt awesome on Windows. Improve 13 | stability. Add features that people care about. 14 | 15 | ## Background 16 | Most recent effort for Salt on Windows have been directed towards stability. 17 | The test suite is running on Windows though there are still some issues that 18 | need to be worked out. PRs and Branch builds are now running tests on Windows. 19 | Additionally all PRs are required to have tests written and the tests must be 20 | passing before PRs can be merged. 21 | 22 | ## Pain Points 23 | - Missing functionality in the service execution module. 24 | - Missing `service.create` 25 | - Unicode issues on Windows 26 | - No supported MSI installer on Windows 27 | - No nightly builds for Windows for either .exe nor .msi 28 | - Ability to make some parts of the installation optional 29 | - pip 30 | - salt-cloud 31 | 32 | ## Should we support it 33 | - Active Directory 34 | - Read Only Access? 35 | - Ability to add/remove users 36 | - Not a lot of interest 37 | - IIS 38 | - Already have a modules for this 39 | - Add additional functionality 40 | - MSSQL 41 | - Maybe. Ability to configure it 42 | - Exchange Server: No Interest 43 | - Office 365 Foundations: No Interest 44 | - Sharepoint: No Interest 45 | - Windows Event Logging: 46 | - Have Salt log to application logs in Windows 47 | - Ability to query event logs 48 | - Ability to configure logging 49 | - Ability to install Salt anywhere 50 | - Use the registry to store the location of the config file 51 | - Lock that key down 52 | 53 | ## Action Items 54 | - Create a `service.create` state for Windows : Rigel 55 | - Migrate to Python 3.6 / 3.7 : Shane 56 | - Verify defaults on Windows : Markus 57 | - Windows Event Logs : Chad 58 | 59 | ## Followup Meetings 60 | We'll be having two followup meetings to further discuss how the MSI Salt repo 61 | works and to show how to setup a build environment, run tests, and write new 62 | tests. 63 | - Salt Testing Meeting (Shane): 0930 MDT (1530 UTC) on Wednesday, June 26 64 | - Setup a dev environment 65 | - Setup the test environment 66 | - Run a single test 67 | - Run a group of tests using a names-file 68 | - Create a unit test 69 | - Create an integration test 70 | - Attendees: (Rigel, Joe, Chad, Markus) 71 | - MSI Architecture Meeting (Markus): 0930 MDT (1530 UTC) on Tuesday, July 2 72 | - One of many meetings to better understand the MSI system 73 | - Mirror the functionality of the NullSoft installer 74 | - Discuss parts of Salt that can be installed optionally 75 | - Pip 76 | - Salt-Cloud 77 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2019-12-17.md: -------------------------------------------------------------------------------- 1 | # Notes from 2019-12-17 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus Kramer 6 | - Sage Robins 7 | - Cassandra Faris 8 | 9 | ## Issues Discussed 10 | 11 | ### PY2/PY3 Issues 12 | When is Salt going to stop building Py2 versions? 13 | - Neon will be the last release to support Py2 14 | 15 | Minion connection issues (5 min) in Py3 16 | - https://github.com/saltstack/salt/issues/54447 17 | - Makes it difficult to transition to PY3 with these issues 18 | - profiling/debugging the minion (yappi) to figure out why it takes 5 min 19 | 20 | code page issues (cp437) in languages other than English 21 | - Non latin characters cause errors 22 | - a possible solution: 23 | - set codepage to 65001 in batch files, service startup, etc 24 | - remove code in `_run` that sets it to 437 25 | - https://github.com/saltstack/salt/blob/master/salt/modules/cmdmod.py#L578 26 | 27 | ### MSI Issues 28 | 29 | MSI build to be included in the Salt build scripts 30 | - run the `build_env` script 31 | - then run the `build` script 32 | 33 | removing visual studio from msi to remove complexity 34 | - There's a lot of code in the msi repo that allows you to build from Vuisual 35 | Studio. This adds to the complexity of the code and could be removed. 36 | 37 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-01-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-01-21 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus Kramer 6 | - Peter Mudd 7 | - Tommy Chang 8 | - Joe Eecott 9 | - Gareth Greenaway 10 | 11 | ## Issues Discussed 12 | 13 | ### PY2/PY3 Issues 14 | Minion connection issues (5 min) in Py3 15 | - https://github.com/saltstack/salt/issues/54447 16 | - Makes it difficult to transition to PY3 with these issues 17 | - profiling/debugging the minion (yappi) to figure out why it takes 5 min 18 | 19 | code page issues (cp437) in languages other than English 20 | - Non latin characters cause errors 21 | - a possible solution: 22 | - set codepage to 65001 in batch files, service startup, etc 23 | - remove code in `_run` that sets it to 437 24 | - https://github.com/saltstack/salt/blob/master/salt/modules/cmdmod.py#L578 25 | 26 | ### MSI Issues 27 | 28 | Possible problem with the new versioning schema 29 | - 3000 is not going to work for the MSI 30 | - Will need to go with something like 30.00.00 31 | - Markus has been using 19.2.2 32 | 33 | MSI build to be included in the Salt build scripts 34 | - run the `build_env` script 35 | - then run the `build` script 36 | 37 | removing visual studio from msi to remove complexity 38 | - There's a lot of code in the msi repo that allows you to build from Vuisual 39 | Studio. This adds to the complexity of the code and could be removed. 40 | 41 | ## Action Items 42 | Shane: 43 | - Build master with Python 3.6.8 44 | - Fix issues 45 | - Add MSI to the build scripts 46 | - Send Markus any issues found during the build process 47 | - Try Markus' suggestions to fix the unicode issues 48 | - Merge pending PRs on the salt-windows-msi repo 49 | 50 | Markus: 51 | - Send Shane a method of testing the Unicode issue 52 | 53 | Peter: 54 | - Generate a formula for demonstrating salt usage in Windows 55 | - Show how to spin up different builds of Windows for testing 56 | - Possible demo next meeting 57 | - I think he said he was using Travis-CI 58 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-02-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-02-18 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Tommy Chong 6 | - Gareth Greenaway 7 | - Cassandra Faris 8 | 9 | ## Agenda 10 | - Welcome 11 | - 3000 Release 12 | - MSI on Windows 13 | - Python 3.7 14 | - Testing the Unicode 15 | - Possible demo from Peter Mudd 16 | - Windows Issues 17 | 18 | ### Windows Issues 19 | - Improved support for DSC:https://github.com/saltstack/salt/issues/43718 20 | - Non-admin Salt-Minion: https://github.com/saltstack/salt/issues/55161 21 | - cmd.run with powershell: https://github.com/saltstack/salt/issues/55213 22 | 23 | ## Action Items 24 | Joe: 25 | - https://github.com/saltstack/salt/issues/55213 26 | Shane: 27 | - Troubleshoot Unicode on Python 3.7 28 | - Work with Markus on the MSI installer 29 | - DSC 30 | - Running Salt-Minion as non Administrator 31 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-03-17.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-03-17 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Tommy Chong 6 | - Cassandra Faris 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3000.1 Release 11 | - MSI on Windows 12 | - Python 3.7 13 | - Testing the Unicode 14 | - WMI vs PythonNet 15 | - Windows Issues (skipped) 16 | 17 | ### Windows Issues 18 | - Improved support for DSC: https://github.com/saltstack/salt/issues/43718 19 | - Non-admin Salt-Minion: https://github.com/saltstack/salt/issues/55161 20 | - Minion fails to start: https://github.com/saltstack/salt/issues/56296 21 | - Pip issues: https://github.com/saltstack/salt/issues/56390 22 | - TLS Support: https://github.com/saltstack/salt/issues/56276 23 | - CPU Usage: https://github.com/saltstack/salt/issues/56250 24 | - Minion restart loop: https://github.com/saltstack/salt/issues/56216 25 | 26 | ### Python 3 Issues 27 | - https://github.com/saltstack/salt/issues/36031 28 | - https://github.com/saltstack/salt/issues/56279 29 | 30 | Joe fixed: 31 | - cmd.run with powershell: https://github.com/saltstack/salt/issues/55213 32 | 33 | ## Action Items 34 | After 3000.1 is released, we can start merging stuff in for Sodium 35 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-04-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-04-21 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus Kramer 6 | - Joe Eacott 7 | - Chad McMarrow 8 | 9 | ## Agenda 10 | - Welcome 11 | - Sodium Release Milestones 12 | - MSI on Windows 13 | - Python 3.7 14 | - WMI vs PythonNet 15 | - Windows Issues 16 | 17 | ### Windows Issues 18 | (github was degraded so we were unable to look at these) 19 | - Improved support for DSC: https://github.com/saltstack/salt/issues/43718 20 | - Non-admin Salt-Minion: https://github.com/saltstack/salt/issues/55161 21 | - Minion fails to start: https://github.com/saltstack/salt/issues/56296 22 | - Pip issues: https://github.com/saltstack/salt/issues/56390 23 | - TLS Support: https://github.com/saltstack/salt/issues/56276 24 | - CPU Usage: https://github.com/saltstack/salt/issues/56250 25 | - Minion restart loop: https://github.com/saltstack/salt/issues/56216 26 | 27 | ### Python 3 Issues 28 | - https://github.com/saltstack/salt/issues/36031 29 | - https://github.com/saltstack/salt/issues/56279 30 | 31 | ## Action Items 32 | - Joe and Shane: Profiling WMI vs PythonNET 33 | - Shane: Python3 and Python2removal PRs merged 34 | - Shane: Automate building the MSI 35 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-05-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-05-19 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus 6 | - Chad McMarrow 7 | - Tommy Chong 8 | - Robert Dale 9 | 10 | ## Agenda 11 | - Welcome 12 | - Python 3.7 13 | - Sodium Release Milestones 14 | - https://github.com/saltstack/community/wiki 15 | - May 22: Code Freeze 16 | - Jun 01: Release Candidate 17 | - Jun 17: GA Release 18 | - MSI on Windows 19 | - WMI vs PythonNet 20 | - Windows Issues 21 | 22 | ### Windows Issues (not discussed) 23 | (github was degraded so we were unable to look at these) 24 | - Improved support for DSC: https://github.com/saltstack/salt/issues/43718 25 | - Non-admin Salt-Minion: https://github.com/saltstack/salt/issues/55161 26 | - Minion fails to start: https://github.com/saltstack/salt/issues/56296 27 | - Pip issues: https://github.com/saltstack/salt/issues/56390 28 | - TLS Support: https://github.com/saltstack/salt/issues/56276 29 | - CPU Usage: https://github.com/saltstack/salt/issues/53885 30 | - CPU Usage: https://github.com/saltstack/salt/issues/56250 31 | - Minion restart loop: https://github.com/saltstack/salt/issues/56216 32 | 33 | ### Python 3 Issues to be tested 34 | - https://github.com/saltstack/salt/issues/36031 35 | - https://github.com/saltstack/salt/issues/54447 36 | - https://github.com/saltstack/salt/issues/56279 37 | - Markus' False Positive: https://github.com/saltstack/salt/pull/56028 38 | - Don't kill everything because one character failed to decode 39 | - Just return the bytestring/binary data/repr()? 40 | - After Sodium 41 | 42 | ## Action Items 43 | - Shane: Verify Unicode Issues are fixed with Python 3.7 44 | - Write tests for them 45 | - Shane: Automate building the MSI 46 | - Joe and Shane: Profiling WMI vs PythonNET 47 | 48 | ## Next Release 49 | - Minion Profiling (cross platform) 50 | - Where's the slowness, what's really going on 51 | - Multiprocessing vs Threading 52 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-06-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-06-16 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Tyler Johnson 6 | - Damon Atkinson 7 | - Thomas Hatch 8 | - Tommy Chong 9 | 10 | ## Agenda 11 | - Welcome 12 | - Sodium Release Status 13 | - WMI vs PythonNet Status 14 | - KB2999226 Discussion 15 | - Grains on Pop: Tyler 16 | - idem-windows 17 | - https://gitlab.com/saltstack/pop/idem-windows 18 | - related PRs 19 | - https://github.com/saltstack/salt/pull/57681 20 | - https://github.com/saltstack/salt/issues/57680 21 | - Make sure the artifacts do not require compiling when pip installing 22 | 23 | ## Action Items 24 | - Remove Patching Code 25 | - Add Docs about KB2999226 26 | - Request that Python add docs 27 | - Using Sysprep with Salt 28 | - How to reset the minion ID 29 | 30 | ## Next Release 31 | - Minion Profiling (cross platform) 32 | - Where's the slowness, what's really going on 33 | - Multiprocessing vs Threading 34 | - Tiamat Build 35 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-07-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-07-21 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Tommy Chong 6 | - Chad McMarrow 7 | - Markus Kramer 8 | - Damon Atkinson 9 | 10 | ## Agenda 11 | - Welcome 12 | - 3001.1 release 13 | - KB2999226 Removed from Windows Installer 14 | - Instead we are behaving the same way python installer behaves 15 | - Need to add the same behavior to the MSI installer 16 | - cmcmarrow: Powershell encoding 17 | 18 | ## Action Items 19 | - Remove Patching Code (done) 20 | - Python Windows Unicode issues (Chad and Markus) 21 | - Console 22 | - Service 23 | - Scripts 24 | - How does it affect the master 25 | - Using Sysprep with Salt (?) 26 | - How to reset the minion ID (?) 27 | - Write SEP to add the ability to rsync files from the master, make the file 28 | client more robust (Probably outside the scope of the Windows Working Group 29 | though it would be improve the speed of refresh_db in winrepo) 30 | 31 | ## Next Release (Magnesium) 32 | - Fix the Unicode Issue on Windows 33 | - Minion Profiling (cross platform) 34 | - Where's the slowness, what's really going on 35 | - Multiprocessing vs Threading 36 | - Tiamat Build 37 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-08-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-08-18 2 | 3 | ## Attendees 4 | - Chad McMarrow 5 | - Joe Eacott 6 | - Markus Kramer 7 | - Shane Lee 8 | - dafyddj 9 | 10 | ## Minutes 11 | - Profiling 12 | - We set up a Salt dev environment (pip -e .) 13 | - We discussed the instructions on https://github.com/markuskramerIgitt/LearnSalt/tree/master/cProfile_performance_profiler 14 | - We profiled the 3000.2 minion with `salt-call --local file.replace` and discussed known and unknown wastes of time: 15 | - We installed snakeviz ("snake vizualizer"): 16 | - Snakeviz has an upper, **image section** that you can drill down and drill out (Reset Zoom) 17 | - Snakeviz has an lower, **table section** that you can sort 18 | - From the **image section**: 19 | - `file.replace` takes 12 seconds 20 | - `esxi.py` takes 7 / 12 seconds and is not needed on Windows. It is no longer loaded on Windows in [3001.1 through PR #57743](https://github.com/saltstack/salt/pull/57743). 21 | - `loader.py` takes 8 / 12 seconds and loads grains, modules, dunders (`__salt__`) and probably other things, that individually detect the platform or compute other things. Because the platform is known, the individual detection is an unnecessary compation. Avoiding these (or other) unnecessary compations could speed up `loader.py`. 22 | - `esxi.py` has (probably) been called by `loader.py`, which could make [PR #57743](https://github.com/saltstack/salt/pull/57743) a blueprint for removing similar wastes of time in `loader.py`. 23 | - From the **table section**, sorted by `cumtime`: 24 | - `frozen importlib._bootstrap` is called ~5,000 times and takes 10 / 12 seconds. This probably leads back to the loader. 25 | - We discussed that snakeviz delivers a useful overview but we lack experience to read and interpret the result. 26 | 27 | ## Outlook 28 | We will continue to interpret the profile. 29 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-09-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-09-15 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Dafydd (dafyddj) 6 | - Joe Eacott 7 | 8 | ## Agenda 9 | - Welcome 10 | - Profiling 11 | - Following instructions on: 12 | - https://github.com/markuskramerIgitt/LearnSalt/tree/master/cProfile_performance_profiler 13 | - Setup a new Salt dev environment 14 | - Install snakeviz 15 | - Use Markus' repo 16 | - Slowness issues seem to be addressed in master branch 17 | - Dafyddj: https://github.com/saltstack/salt-winrepo-ng/pull/171 18 | - merged, we now have pre-commit 19 | - Setting up a schedule for full branch test runs 20 | - Weekly 21 | - Using Github Actions 22 | - Mostly done 23 | - An actual install test when Packages Definition file is changed (just for that one file) 24 | - Automating the release process for salt-winrepo-ng 25 | - Used in the Formulas Working Group 26 | - Use https://github.com/semantic-release/semantic-release 27 | - Commit messages would need to be formatted properly 28 | - Triggered by merge into master branch 29 | - A code jam to fix all the broken Package Definition Files (urls, yaml) 30 | - Migrate test.py to Python 3 31 | - Possibility of Running Salt Minion as Standard User 32 | - Have multiple minions running on the same machine 33 | - On for the System... one for handling/configuring a user account 34 | - User minion would only be able to manage those things that the user has 35 | access to (registry, files, software) 36 | - Need to write a SEP for this 37 | - /usr/local/bin => C:\Program Files\salt 38 | - /etc/salt => C:\ProgramData\salt 39 | - /srv/salt => 40 | 41 | ## Action Items 42 | - Let's profile some things and figure out why Salt is so much slower on Windows 43 | - Dafydd: Bring the scheduled tests into master 44 | - Dafydd: Automate semantic release (from salt-formulas) 45 | - Dafydd: Investigate the installation tests (stretch) 46 | - Shane/Joe: Start fixing broken Package Definition files 47 | - Shane: Transition .travis/tests.py to Python 3 (Python3.6 default on Travis) 48 | - Shane: Write a SEP for Install Salt Anywhere and address the possibility of 49 | having multiple instances of salt-minion on the same machine 50 | 51 | ## Next Release (Magnesium) 52 | - Fix the Unicode Issue on Windows 53 | - Minion Profiling (cross platform) 54 | - Where's the slowness, what's really going on 55 | - Multiprocessing vs Threading 56 | - Tiamat Build 57 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-10-20.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-10-20 2 | 3 | ## Attendees 4 | - Markus 5 | - Shane Lee 6 | - Dafydd (dafyddj) 7 | 8 | ## Agenda 9 | - Welcome 10 | - Pending Reboot Grain issue (https://github.com/saltstack/salt/issues/57628) 11 | - Looked at https://github.com/saltstack/salt/pull/58181 as a possible fix 12 | - Discussed the option of disabling the pending_reboot grain 13 | - Discussed slowness issues on Windows 14 | - Talked about the LazyLoader 15 | - grain_funcs (https://github.com/saltstack/salt/blob/master/salt/loader.py#L828) 16 | ``` 17 | funcs = grain_funcs(opts, proxy=proxy, context=context or {}) 18 | if force_refresh: # if we refresh, lets reload grain modules 19 | funcs.clear() 20 | # Run core grains 21 | for key in funcs: #<---- This line is really slow 22 | ``` 23 | notes from the LazyLoader 24 | ``` 25 | .. note:: 26 | Iterating over keys will cause all modules to be loaded. 27 | ``` 28 | - Discussed doing a PR merge jam on the winrepo during monthly Windows Working 29 | Group Meetings 30 | 31 | ## Action Items 32 | - Markus is going to try setting `multiprocessing: false` 33 | - Compare Linux vs Windows performance on `test.version` using snakeviz 34 | - Dafydd: Automate semantic release (from salt-formulas) 35 | - Dafydd: Investigate the installation tests (stretch) 36 | - Shane/Joe: Start fixing broken Package Definition files 37 | - Shane: Write a SEP for Install Salt Anywhere and address the possibility of 38 | having multiple instances of salt-minion on the same machine 39 | 40 | ## Next Release (Magnesium) 41 | - Fix the Unicode Issue on Windows 42 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-11-17.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-11-17 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus 6 | 7 | ## Agenda 8 | - Welcome 9 | 10 | ## Multiprocessing Off 11 | - Turning multiprocessing off worked very well for Markus 12 | - Need to keep an eye on the jobs and any other irregularities 13 | 14 | ## Timeout issue 15 | - Encountered a ``timeout`` issue in 3001 16 | - Includes the Unicode fixes 17 | - The minion service is running, but it cannot reach the master 18 | - Set ping_interval to 2 19 | - Stop the master 20 | - There will be a stacktrace in the log 21 | - https://github.com/saltstack/salt/issues/58942 22 | - Needs some more investigation, could not replicate 23 | 24 | ## Action Items 25 | - Markus will update the MSI so that it creates the minion service using SSM 26 | - Compare Linux vs Windows performance on `test.version` using snakeviz 27 | - Dafydd: Automate semantic release (from salt-formulas) 28 | - Dafydd: Investigate the installation tests (stretch) 29 | - Shane/Joe: Start fixing broken Package Definition files 30 | - Shane: Write a SEP for Install Salt Anywhere and address the possibility of 31 | having multiple instances of salt-minion on the same machine 32 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2020-12-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2020-12-15 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Markus 6 | - Dafydd 7 | 8 | ## Agenda 9 | - Welcome 10 | 11 | ## Multiprocessing Off 12 | - Turning multiprocessing off worked very well for Markus 13 | - Need to keep an eye on the jobs and any other irregularities 14 | - Markus has found an issue 15 | 16 | ## Timeout issue 17 | - Encountered a ``timeout`` issue in 3001 18 | - Includes the Unicode fixes 19 | - The minion service is running, but it cannot reach the master 20 | - Set ping_interval to 2 21 | - Stop the master 22 | - There will be a stacktrace in the log 23 | - Needs some more investigation, could not replicate 24 | - https://github.com/saltstack/salt/issues/59064 25 | 26 | ## NSSM Issue 27 | - The NSSM project (https://nssm.cc/) is no longer maintained and is considered 28 | a dead project 29 | - We used NSSM to make the salt-minion service restart every time it died for 30 | whatever reason. I believe we have addressed the issues causing the minion to 31 | fail after 7 tries... and we may no longer need NSSM. We need to try adding 32 | the service directly and NOT using NSSM 33 | - NSSM is also flagged by some Antivirus' as "potentially unwanted software" as 34 | it is used by many malware products to keep their services running 35 | - NSSM also leaves many events in the Windows Application Event logs with 36 | undefined Descriptions that cannot be updated because the project is not 37 | maintained 38 | Issue created here: https://github.com/saltstack/salt/issues/59148 39 | 40 | ## Master Key Rotation (Feature) 41 | Some security shops require all keys to be rotated on a periodic basis. There is 42 | currently no easy way to rotate the master key and have it propogate down to its 43 | minions. 44 | If a minion is offline when the master rolls its key, there is no way to get it 45 | after the fact... the minion fails to connect. 46 | Some sort of key management system that allows for expiring and future keys. 47 | The system would handle the roll over 48 | This is a problem with Windows Desktops/Laptops that aren't ALWAYS connected to 49 | the master. 50 | There may be some unknown ramifications to multi-master environments. 51 | Issue created here: https://github.com/saltstack/salt/issues/59149 52 | 53 | ## Action Items 54 | - Dafydd: Automate semantic release (from salt-formulas) 55 | - Dafydd: Investigate the installation tests (stretch) 56 | - Shane/Joe: Start fixing broken Package Definition files 57 | - Shane: Write a SEP for Install Salt Anywhere and address the possibility of 58 | having multiple instances of salt-minion on the same machine 59 | - Program Files 60 | - ProgramData 61 | - /Users/username/AppData 62 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-01-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-01-19 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Joe Eacott 6 | 7 | ## Agenda 8 | - Welcome 9 | 10 | ## Discussed in Previous 11 | - Timeout: https://github.com/saltstack/salt/issues/59064 12 | - NSSM: https://github.com/saltstack/salt/issues/59148 13 | - Master Key Rotation: https://github.com/saltstack/salt/issues/59149 14 | - Install Anywhere 15 | 16 | ## Discussed 17 | Salt Project Priorities for Windows next release 18 | 1. Install Anywhere 19 | 2. Functional Tests 20 | 3. NSSM Removal 21 | 22 | ## Action Items 23 | - Start fixing broken urls in winrepo 24 | - Create SEP for Install Anywhere -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-02-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-02-16 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Joe Eacott 6 | - Dave Boucha 7 | - Dafyd D 8 | - Johannes Scholz 9 | 10 | ## Agenda 11 | - Welcome 12 | 13 | ## Discussed in Previous 14 | - SEP for Install Anywhere 15 | - Functional Tests 16 | - NSSM Removal 17 | 18 | ## Discussed 19 | - Why is Windows 3 times slower than Linux? 20 | - Try turning off multiprocessing 21 | - We need to address directory permissions in the SEP 22 | https://github.com/saltstack/salt-enhancement-proposals/pull/41#issuecomment-775438365 23 | 24 | ## Action Items 25 | - Start fixing broken urls in winrepo 26 | - Update SEP to address directory permissions concerns -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-03-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-03-16 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Joe Eacott 6 | - Sage Robins 7 | - Markus Kramer 8 | 9 | ## Agenda 10 | - Welcome 11 | - Salt Priorities 12 | - Master on Windows being open 13 | - Install Anywhere 14 | - Heist 15 | - Migrate to Functional Tests 16 | - NSSM Removal 17 | 18 | ## Discussed in Previous 19 | - SEP for Install Anywhere 20 | - Functional Tests 21 | - NSSM Removal 22 | 23 | ## Discussed 24 | - Why is Windows 3 times slower than Linux? 25 | - Try turning off multiprocessing 26 | - Blazingly fast according to Markus 27 | - cmd.run, file.managed 28 | - Offline minions created multiple stacktraces in the log file until they reconnect 29 | - https://github.com/saltstack/salt/issues/59064 30 | - git pull upstream master --rebase 31 | - git rebase upstream/master 32 | - We need to address directory permissions in the SEP 33 | https://github.com/saltstack/salt-enhancement-proposals/pull/41#issuecomment-775438365 34 | - Tiamat builds for Windows 35 | - Single Binary vs One Dir 36 | - Heist using WinRM vs OpenSSH 37 | 38 | ## Action Items 39 | - Shane: Update SEP to address directory permissions concerns 40 | - Start fixing broken urls in winrepo 41 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-04-20.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-04-20 2 | 3 | ## Attendees 4 | - Shane Lee 5 | - Daffyddj 6 | - Markus 7 | 8 | ## Agenda 9 | - Welcome 10 | - Salt Priorities 11 | - Master on Windows 12 | - Open Sourcing Salt-SSH on Windows 13 | - Install Anywhere (https://github.com/saltstack/salt/issues/42801) 14 | - NSSM Removal (https://github.com/saltstack/salt/issues/59148) 15 | 16 | ## Discussed in Previous 17 | - Why is Windows 3 times slower than Linux? 18 | - Try turning off multiprocessing 19 | - Blazingly fast according to Markus 20 | - cmd.run, file.managed 21 | - Offline minions created multiple stacktraces in the log file until they reconnect 22 | - https://github.com/saltstack/salt/issues/59064 23 | - git pull upstream master --rebase 24 | - git rebase upstream/master 25 | - We need to address directory permissions in the SEP 26 | https://github.com/saltstack/salt-enhancement-proposals/pull/41#issuecomment-775438365 27 | - Tiamat builds for Windows 28 | - Single Binary vs One Dir 29 | - Heist using WinRM vs OpenSSH 30 | 31 | ## Discussed 32 | - git rebasing 33 | - Non-Windows packages in the Windows installer 34 | - Key rotation mechanism 35 | - https://github.com/saltstack/salt/issues/59149 36 | - https://github.com/saltstack/salt/issues/59342 37 | - Abandon NSSM 38 | - https://github.com/saltstack/salt/issues/59148 39 | - An issue with file.recurse when the directory is owned by TrustedInstaller 40 | - Discussed issue with the zscaler vpn 41 | - The minion cannot contact the master (split tunnel not working) 42 | 43 | ## Action Items 44 | - Write tests for https://github.com/saltstack/salt/issues/59064 45 | - Discuss Key rotation in the next meeting 46 | - Ask Bryce Larsen about zscaler 47 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-05-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-05-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | - Markus (@marbx) 7 | 8 | ## Agenda 9 | - Welcome 10 | - Windows Working Group Board 11 | - Add a card for NSSM Removal (https://github.com/saltstack/salt/issues/59148) 12 | 13 | ## Discussed 14 | - Key rotation 15 | - This is a security issue. Some security shops require key rotation. Salt 16 | needs to have a mechanism to do this. 17 | - Problems with Unicode on German Windows, probably any non-English Windows. 18 | There are issues with returns that contain unicode characters. 19 | - Removing unused libraries from PyWin32. The following seem to be fluff: 20 | - pythonwin 21 | - Possibly using Rust as a solution to the NSSM problem 22 | - Possibly use https://github.com/microsoft/windows-rs and https://github.com/PyO3/pyo3 23 | to replace PyWin32 since it is maintained by MS 24 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2021-09-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2021-09-21 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | - Markus (@marbx) 7 | - Glenn 8 | 9 | ## Agenda 10 | - Welcome 11 | - Calendar events? 12 | - Install Anywhere 13 | 14 | ## Discussed 15 | - Quoting in powershell commands using cmd.run in an unless requisite... 16 | - Double-quotes are being escaped using `\` instead of backtiks 17 | - _cmd_quote 18 | - Add comments to https://github.com/saltstack/salt/issues/59420 19 | - or create a new issue 20 | - Discussed https://github.com/saltstack/salt/pull/59770 21 | - Needs tests and lint/pre-commit fixes 22 | - Discussed and merged : https://github.com/saltstack/salt-windows-msi/pull/98 23 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-01-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-01-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Install Anywhere 10 | 11 | ## Discussed 12 | - new salt-windows-nsis, new release 3004-3 13 | - discussed possible issues with salt formulas where linux may be on a -2 release and windows is on a -4 14 | - /move-config bug 15 | - salt-winrepo-ng PR 1902 that addresses uninstaller issue 16 | - Need to accept some of those changes 17 | - Daffydj is going to open a new PR 18 | - Friday Meetings need to be focused on the Key Rotation issue 19 | - Created a new issue for some WUA issues: https://github.com/saltstack/salt/issues/61479 20 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-02-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-02-15 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Followup Items 10 | - Key Rotation 11 | 12 | ## Followup 13 | - new salt-windows-nsis, new release 3004-3 14 | - discussed possible issues with salt formulas where linux may be on a -2 release and windows is on a -4 15 | - salt-winrepo-ng PR 1902 that addresses uninstaller issue 16 | - Need to accept some of those changes 17 | - Daffydj is going to open a new PR 18 | - Friday Meetings need to be focused on the Key Rotation issue 19 | - Created a new issue for some WUA issues: https://github.com/saltstack/salt/issues/61479 20 | 21 | ## Discussed 22 | - Community involvement seems to have fallen off in the last 6 months 23 | - /move-config bug 24 | - Issue created in salt... transferred to salt-windows-nsis 25 | - https://github.com/saltstack/salt-windows-nsis/issues/15 26 | - Problems with custom-config 27 | - 32bit salt on 64bit windows 28 | - winrepo: 29 | - Need to move the tests to a Windows runner so that the `reg.read` commands execute properly 30 | - Script failures need to make the tests fail (false positive) 31 | - Add a some jinja parsing checks, perhaps? 32 | - winrepo: salt uninstall 33 | - Works, but breaks the tests... need to update the way we test 34 | - Added WUA issue to sprint: https://github.com/saltstack/salt/issues/61479 35 | - Discussed key-rotation 36 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-03-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-03-15 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Followup Items 10 | - Key Rotation 11 | 12 | ## Followup 13 | - Community involvement seems to have fallen off in the last 6 months 14 | - /move-config bug 15 | - Issue created in salt... transferred to salt-windows-nsis 16 | - https://github.com/saltstack/salt-windows-nsis/issues/15 17 | - Problems with custom-config 18 | - 32bit salt on 64bit windows 19 | - winrepo: 20 | - Need to move the tests to a Windows runner so that the `reg.read` commands execute properly 21 | - Script failures need to make the tests fail (false positive) 22 | - Add a some jinja parsing checks, perhaps? 23 | - winrepo: salt uninstall 24 | - Works, but breaks the tests... need to update the way we test 25 | - Added WUA issue to sprint: https://github.com/saltstack/salt/issues/61479 26 | - Discussed key-rotation 27 | 28 | ## Discussed 29 | - Community Involvement 30 | - /move-config bug 31 | - Problems with custom-config 32 | - winrepo url tests: 33 | - Need to move the tests to a Windows runner so that the `reg.read` commands execute properly 34 | - Script failures need to make the tests fail (false positive) 35 | - Add a some jinja parsing checks, perhaps? 36 | - Jinja failures aren't considered failures. 37 | - Current tests run on Linux Runners.... need to transition to Windows Runners to expose all windowzy stuff 38 | - winrepo: salt uninstall 39 | - Works, but breaks the tests... need to update the way we test 40 | - Need to find the uninstaller based on where salt was installed 41 | - Making Salt work as a standard user 42 | - permissions and documentation... maybe... 43 | - Standard user does not have permission to HKLM:\SOFTWARE\Salt Project\Salt 44 | - Is there a security reason why this is being locked down? I don't think so... 45 | - https://github.com/saltstack/salt/issues/61789 46 | 47 | ## TODO 48 | - Twangboy: Community Involvement: 49 | - Bring this up to the Core Team. Has anybody noticed a falling off of interest or involvement? 50 | - Is this a concern? How do we improve this? How do keep our momentum? 51 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 52 | - `/move-config` options works from the GUI, but not Silently 53 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 54 | - Twangboy: https://github.com/saltstack/salt/issues/61789 55 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-04-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-04-19 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Followup Items 10 | - Community Involvement 11 | 12 | ## Followup 13 | - /move-config bug 14 | - Issue created in salt... transferred to salt-windows-nsis 15 | - https://github.com/saltstack/salt-windows-nsis/issues/15 16 | - Problems with custom-config 17 | - winrepo url tests: 18 | - Need to move the tests to a Windows runner so that the `reg.read` commands execute properly 19 | - Script failures need to make the tests fail (false positive) 20 | - Add some jinja parsing checks, perhaps? 21 | - Jinja failures aren't considered failures. 22 | - Current tests run on Linux Runners... need to transition to Windows Runners to expose all windozy stuff 23 | - winrepo: salt uninstall 24 | - Works, but breaks the tests... need to update the way we test 25 | - Need to find the uninstaller based on where salt was installed 26 | - Making Salt work as a standard user 27 | - permissions and documentation... maybe... 28 | - Standard user does not have permission to HKLM:\SOFTWARE\Salt Project\Salt 29 | - Is there a security reason why this is being locked down? I don't think so... 30 | - https://github.com/saltstack/salt/issues/61789 31 | 32 | ## Discussed 33 | - winrepo url tests: 34 | - Migrate to Windows Runner 35 | - https://github.com/saltstack/salt-winrepo-ng/blob/master/.github/workflows/pre-commit.yml 36 | - Twangboy: https://github.com/saltstack/salt/issues/61789 37 | - Use one of our installers to set up salt 38 | - Use the python environment from the installer 39 | - salt-minion software definition needs to be fixed 40 | - It's pointing to ProgramData instead of Program Files 41 | - Making Salt work as a standard user 42 | - Test giving Non-Admin user permissions to the registry key 43 | 44 | ## TODO 45 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 46 | - `/move-config` options works from the GUI, but not Silently 47 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 48 | - Twangboy: Discuss removing pycurl from requirements for Windows 49 | - It's not being used by any other package (linux, darwin, freebsd) 50 | - Dafydd: Work on transitioning the winrepo tests to run on a Windows Runner 51 | - Migrating to requests from pycurl in the tests 52 | - Look into implementing the tests as a salt extension 53 | - Twangboy: Test giving Non-Admin user to registry key 54 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-05-17.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting: 2022-05-17 2 | Meeting not held 3 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-06-21.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting: 2022-06-21 2 | Meeting not held 3 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-07-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-07-19 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Followup Items 10 | - Community Involvement 11 | 12 | ## Discussed 13 | - winrepo url tests: 14 | - Migrate to Windows Runner 15 | - https://github.com/saltstack/salt-winrepo-ng/blob/master/.github/workflows/pre-commit.yml 16 | - Twangboy: https://github.com/saltstack/salt/issues/61789 17 | - Use one of our installers to set up salt 18 | - Use the python environment from the installer 19 | - Use requests instead of pycurl to verify URLs 20 | - salt-minion software definition needs to be fixed 21 | - It's pointing to ProgramData instead of Program Files 22 | - Making Salt work as a standard user 23 | - Dafydd has had more success recently running salt as a standard user 24 | 25 | ## TODO 26 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 27 | - `/move-config` options works from the GUI, but not Silently 28 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 29 | - I'm sure there are tests for this 30 | - Twangboy: Fix the Software Definition for salt-minion 31 | - Currently pointing to ProgramData for the uninstaller 32 | - Twangboy: Discuss removing pycurl from requirements for Windows 33 | - It's not being used by any other package (linux, darwin, freebsd) 34 | - Use requests instead 35 | - Team wants to NOT remove it... instead we'll need to build it 36 | - Dafydd: Work on transitioning the winrepo tests to run on a Windows Runner 37 | - Migrating to requests from pycurl in the tests 38 | - Look into implementing the tests as a salt extension 39 | - Twangboy: Test giving Non-Admin user to registry key 40 | - This may be working now... needs further testing 41 | - Need to be able to start the minion as a standard non-privileged user 42 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-08-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-08-16 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Followup Items 10 | - Fixed Software Definition for salt-minion uninstall 11 | - Discussed removing pyCurl with Core, they want to compile it for Windows 12 | - Community Issues 13 | 14 | ## Discussed 15 | - Removing PyCurl 16 | - Issues with the RC Release 17 | - Daffyd has brought up 2 issues: 18 | - A distutils warning 19 | - A stactrace when importing kernel_linux_yum.py 20 | - WinRepo PRs 21 | - Issues with LGPO 22 | - Issues with win_pkg logging 23 | - Moving the Windows Working Group meeting to the third Thursday so that Markus 24 | can attend 25 | 26 | ## TODO 27 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 28 | - `/move-config` options works from the GUI, but not Silently 29 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 30 | - I'm sure there are tests for this 31 | - Dafydd: Work on transitioning the winrepo tests to run on a Windows Runner 32 | - Migrating to requests from pycurl in the tests 33 | - Look into implementing the tests as a salt extension 34 | - Twangboy: Test giving Non-Admin user to registry key 35 | - This may be working now... needs further testing 36 | - Need to be able to start the minion as a standard non-privileged user 37 | - Dafydd: Make an issue for the kernel_linux_yum.py stacktrace (easy) 38 | - Dafydd: Open issue about LGPO caching 39 | - Dafydd: Open issue about win_pkg debug logging for pkg.install (easy) 40 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-09-22.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-09-22 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | - Maki 7 | 8 | ## Agenda 9 | - Welcome 10 | - New date/time for Windows Working Group meetings 11 | - Followup Items: 12 | - TODO Items 13 | - Community Issues and Discussion 14 | 15 | ## Discussed 16 | - Issue 62479: Done and Merged 17 | - Issue 62734: LGPO Caching 18 | - Issue 62480: win_pkg debug logging 19 | - Issues with WinRepo: 20 | - Issue with the inability to do Jinja tests because it is a Linux Runner and 21 | much of the jinja has Windows stuff in it 22 | - Issue with the 7zip definition where the indentation is wrong, causing only 23 | the first portion to be validated 24 | - Issue with the cache location and how to obtain that from salt in the 25 | definition file. Best to use `config.get root_dir` 26 | - The solution to all of this is to migrate to a Windows Runner, so we can 27 | include some Jinja parsing tests 28 | 29 | ## TODO 30 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 31 | - `/move-config` options works from the GUI, but not Silently 32 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 33 | - I'm sure there are tests for this 34 | - Dafydd: Work on transitioning the winrepo tests to run on a Windows Runner 35 | - Migrating to requests from pycurl in the tests 36 | - Look into implementing the tests as a salt extension 37 | - Twangboy: Test giving Non-Admin user to registry key 38 | - This may be working now... needs further testing 39 | - Need to be able to start the minion as a standard non-privileged user 40 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-10-20.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-10-20 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd 6 | - Markus 7 | - Jim Watson 8 | 9 | ## Agenda 10 | - Welcome 11 | - New date/time for Windows Working Group meetings 12 | - New Features: 13 | - LGPO: https://github.com/saltstack/salt/pull/62888 14 | - Followup Items: 15 | - Issue 62734: LGPO Caching 16 | - Issue 62480: win_pkg debug logging 17 | - https://github.com/saltstack/salt-winrepo-ng/pull/1959 18 | - Community Issues and Discussion 19 | 20 | ## Discussed 21 | - LGPO_REG module 22 | - Discussed how it works and why it's needed 23 | - Need to document precedence of Local GPO vs Domain GPO 24 | - New Winrepo-NG testing on Windows Runners by daffyd 25 | - Went over how it works 26 | - Merged 27 | - Discussed the current plan for Salt 3006 including plans for it being an LTS 28 | release 29 | 30 | ## TODO 31 | - Twangboy: Describe Group Policy precedence in the docs for LGPO/LGPO_REG 32 | - Local <= Domain 33 | - Provide a link to MS about what precedes what 34 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 35 | - `/move-config` options works from the GUI, but not Silently 36 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 37 | - I'm sure there are tests for this 38 | - Twangboy: Test giving Non-Admin user to registry key 39 | - This may be working now... needs further testing 40 | - Need to be able to start the minion as a standard non-privileged user 41 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-11-17.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-11-17 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd 6 | - Markus 7 | - TheBigBear 8 | 9 | ## Agenda 10 | - Welcome 11 | - New date/time for Windows Working Group meetings 12 | - Relenv and how it affects Windows 13 | - Community Issues and Discussion 14 | 15 | ## Discussed 16 | - The date/time of the Windows Working Group meeting 17 | - Relenv 18 | - A way to find how many updates are pending reboot (win_wua.py) 19 | - Problem with salt-formula: https://github.com/saltstack/salt/issues/63061 20 | - Erroring because it's trying to resolve user `root` 21 | - The CommandExecutionError should bubble up, but it's getting a Serialization Error 22 | - Issues in winrepo-ng 23 | - possibly use cp.cache_dest to get the location of the binary in the salt cache 24 | 25 | ## TODO 26 | Future: 27 | - Twangboy: Fix the date displayed on the Web Page to just Mountain Time 28 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 29 | - `/move-config` options works from the GUI, but not Silently 30 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 31 | - I'm sure there are tests for this 32 | - Twangboy: Test giving Non-Admin user to registry key 33 | - This may be working now... needs further testing 34 | - Need to be able to start the minion as a standard non-privileged user 35 | - 36 | Done: 37 | - Twangboy: Describe Group Policy precedence in the docs for LGPO/LGPO_REG 38 | - Local <= Domain 39 | - Provide a link to MS about what precedes what 40 | - DONE: https://github.com/saltstack/salt/pull/62985 41 | - Twangboy: https://github.com/saltstack/salt/issues/62480 42 | - IN PROGRESS: https://github.com/saltstack/salt/pull/63078 43 | - Test is failing 44 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2022-12-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2022-12-15 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafyddj 6 | 7 | ## Agenda 8 | - Welcome 9 | - 3005.1-4 release 10 | - 3006.0rc1 release 11 | - Relenv Builds and salt-windows-nsis / salt-windows-msi 12 | - Community Issues and Discussion 13 | 14 | ## Discussed 15 | - Upcoming Releases 16 | - Design problems to solve with Relenv 17 | - Running two minions on the same machine, but in different contexts 18 | 19 | ## TODO 20 | Future: 21 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 22 | - `/move-config` options works from the GUI, but not Silently 23 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 24 | - I'm sure there are tests for this 25 | - Twangboy: Test giving Non-Admin user to registry key 26 | - This may be working now... needs further testing 27 | - Need to be able to start the minion as a standard non-privileged user 28 | 29 | Done: 30 | - Twangboy: Fix the date displayed on the Web Page to just Mountain Time 31 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-01-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-01-19 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafyddj 6 | - jwatson 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3006.0rc1 release 11 | - Nightly builds and pipeline work 12 | - Community Issues and Discussion 13 | 14 | ## Discussed 15 | - Windows Groups (dafydd will submit an issue) 16 | - Runas and retcodes (https://github.com/saltstack/salt/issues/59977) 17 | - Marked for 3007 18 | 19 | ## TODO 20 | Future: 21 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 22 | - `/move-config` options works from the GUI, but not Silently 23 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 24 | - I'm sure there are tests for this 25 | - Twangboy: Test giving Non-Admin user to registry key 26 | - This may be working now... needs further testing 27 | - Need to be able to start the minion as a standard non-privileged user 28 | 29 | Done: 30 | - Twangboy: Fix minion not starting when user doesn't have permissions to 31 | root_dir registry key 32 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-02-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-02-16 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafyddj 6 | - jwatson 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3006.0rc1 release 11 | - Nightly builds and pipeline work 12 | - Community Issues and Discussion 13 | 14 | ## Discussed 15 | - Trimming the winrepo_ng repo 16 | - Move old, un-maintained Package Definitions to a contrib repository 17 | - Document how to use GitFS to keep winrepo in sync with upstream 18 | - Perhaps a good blogpost idea 19 | - https://github.com/saltstack/salt/issues/53969 20 | - We need to maybe add a `mirror` option so that it deletes items that are no 21 | - longer on the master 22 | 23 | ## TODO 24 | Future: 25 | - Twangboy: https://github.com/saltstack/salt/issues/53969 26 | - Let's talk about this in the next core meeting or on slack with the team 27 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 28 | - `/move-config` options works from the GUI, but not Silently 29 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 30 | - I'm sure there are tests for this 31 | - Twangboy: Test giving Non-Admin user to registry key 32 | - This may be working now... needs further testing 33 | - Need to be able to start the minion as a standard non-privileged user 34 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-03-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-03-16 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - 3006.0rc1 release 10 | - 3006.0rc2 release 11 | - Nightly builds and pipeline work 12 | - Moved build scripts back to Salt 13 | - Community Issues and Discussion 14 | 15 | ## Discussed 16 | - Need the ability to run the debugger ( python.exe -E -s -m pdb salt-minion args ) 17 | - Don't know if the non .exe scripts are being generated 18 | - Looked at some work that Dafydd had done with github actions on salt-winrepo-ng 19 | - Reviewed a pending PR in salt-winrepo-ng 20 | - Twangboy needs to look at running salt-minion as a Non-Admin user 21 | 22 | ## TODO 23 | Future: 24 | - Twangboy: https://github.com/saltstack/salt/issues/53969 25 | - Let's talk about this in the next core meeting or on slack with the team 26 | - Bring it up in Open Hour 27 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 28 | - `/move-config` options works from the GUI, but not Silently 29 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 30 | - I'm sure there are tests for this 31 | - Twangboy: Test giving Non-Admin user to registry key 32 | - This may be working now... needs further testing 33 | - Need to be able to start the minion as a standard non-privileged user 34 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-04-20.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-04-20 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Mark 6 | - Dafydd 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3006.0 has been released 11 | - Location of the python.exe changed, broke pip states 12 | - Pipeline work 13 | - Salt Bootstrap 14 | - Community Issues and Discussion 15 | 16 | ## Discussed Previously 17 | - Need the ability to run the debugger ( python.exe -E -s -m pdb salt-minion args ) 18 | - Don't know if the non .exe scripts are being generated 19 | - Looked at some work that Dafydd had done with github actions on salt-winrepo-ng 20 | - Reviewed a pending PR in salt-winrepo-ng 21 | - Twangboy needs to look at running salt-minion as a Non-Admin user 22 | 23 | ## Today's Discussion 24 | - How far back should bootstrap support? 25 | - 2 Major releases prior to supported 26 | - Talked about the release cycle 27 | - Looked at the layout of the salt/py3/windows 28 | - Still some work to be done here 29 | - Issue with winrepo and environments: 30 | - https://github.com/saltstack/salt/issues/60471 31 | - Maybe Thomas Phipps can give some more guidance 32 | 33 | ## TODO 34 | Future: 35 | - Twangboy: https://github.com/saltstack/salt/issues/53969 36 | - Let's talk about this in the next core meeting or on slack with the team 37 | - Bring it up in Open Hour 38 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 39 | - `/move-config` options works from the GUI, but not Silently 40 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 41 | - I'm sure there are tests for this 42 | - Twangboy: Test giving Non-Admin user to registry key 43 | - This may be working now... needs further testing 44 | - Need to be able to start the minion as a standard non-privileged user 45 | - Document how to do it 46 | - Provide a script to automate creating the service, setting the config, like 47 | macOS (salt-config.sh) 48 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-05-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-05-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd 6 | - Gayathri 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3006.1 has been released 11 | - salt-pip has been fixed 12 | - https://github.com/saltstack/salt/pull/64239 13 | - Community Issues and Discussion 14 | 15 | ## Discussed Previously 16 | - How far back should bootstrap support? 17 | - 2 Major releases prior to supported 18 | - Talked about the release cycle 19 | - Looked at the layout of the salt/py3/windows 20 | - Still some work to be done here 21 | - Issue with winrepo and environments: 22 | - https://github.com/saltstack/salt/issues/60471 23 | - Maybe Thomas Phipps can give some more guidance 24 | 25 | ## Today's Discussion 26 | - Talked about how to get debugging with the new Relenv/OneDir builds (Dafydd) 27 | - Create a python script that launches salt-minion 28 | - Launch that script with ``-m pdb`` 29 | - https://github.com/saltstack/salt/pull/64239 30 | - Make the script a part of the installation 31 | - Winrepo documentation (Gayathri) 32 | - PR Next week after talking to Alyssa 33 | - Dafydd is working on a workflow/script that will detect releases of software 34 | and create a PR when it detects a new release 35 | - Need a way to run an installer that is zipped up 36 | - Would need to unzip, then run the installer 37 | - Looked at the layout of the salt/py3/windows 38 | - Need to create some symlinks under ``latest`` that say ``latest`` instead of 39 | the version number 40 | 41 | ## TODO 42 | Future: 43 | - Twangboy: https://github.com/saltstack/salt/issues/53969 44 | - Let's talk about this in the next core meeting or on slack with the team 45 | - Bring it up in Open Hour 46 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 47 | - `/move-config` options works from the GUI, but not Silently 48 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 49 | - I'm sure there are tests for this 50 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-06-22.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-06-22 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - https://github.com/saltstack/salt/issues/64258 10 | - demo: multi-minion 11 | - Community Issues and Discussion 12 | 13 | ## Discussed Previously 14 | - https://github.com/saltstack/salt/pull/64239 15 | - Make the script a part of the installation 16 | - Done 17 | - Issue with winrepo and environments: 18 | - https://github.com/saltstack/salt/issues/60471 19 | - winrepo is meant to be a quick and easy way to set it up 20 | - for more complex configurations, use gitfs 21 | - provide some documentation 22 | 23 | ## Today's Discussion 24 | - https://github.com/saltstack/salt/issues/64258 25 | - Talked about protecting the salt-minion running under the user context from 26 | being shut down 27 | - https://learn.microsoft.com/en-gb/windows/win32/services/protecting-anti-malware-services-?redirectedfrom=MSDN 28 | - Demo'd the multi-minion script 29 | 30 | ## TODO 31 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 32 | - `/move-config` options works from the GUI, but not Silently 33 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 34 | - I'm sure there are tests for this 35 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-08-17.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-08-17 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - New & Upcoming Releases 10 | - Community Issues and Discussion 11 | 12 | ## Discussed Previously 13 | - https://github.com/saltstack/salt/issues/64258 14 | - Talked about protecting the salt-minion running under the user context from 15 | being shut down 16 | - So the user can't kill the multi-minion running under their target 17 | - https://learn.microsoft.com/en-gb/windows/win32/services/protecting-anti-malware-services-?redirectedfrom=MSDN 18 | 19 | ## Today's Discussion 20 | - multi-minion got included in the 3006.2 release 21 | - Daffyd has been testing and is displaying the double-return issue 22 | - We need to get that fixed or figured out... or something 23 | - Daffyd will open an issue depending on his findings 24 | - Could be linking off the UUID grain 25 | - Could also try setting the pidfile option in minion config 26 | - Nope, they have separate locations 27 | - rSync on Windows 28 | - Looked at the rsync-git package in winrepo 29 | - Maybe need to use cwrsync instead... less dependencies 30 | - Remove the version from the Display Name in the NSIS/MSI installer 31 | - The version is already recorded in ``appwiz.cpl`` under version 32 | - It looks cleaner and makes the state ``pkg.installed`` more clear when 33 | using ``test=True`` 34 | 35 | ## TODO 36 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 37 | - `/move-config` options works from the GUI, but not Silently 38 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 39 | - I'm sure there are tests for this 40 | - Twangboy: Issue with winrepo and environments: 41 | - https://github.com/saltstack/salt/issues/60471 42 | - winrepo is meant to be a quick and easy way to set it up 43 | - for more complex configurations, use gitfs 44 | - Need to provide documentation stating as much ^^^^ 45 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-09-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-09-21 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Lea (@leadevelop) 7 | - Will Albenzi (@walbenzi) 8 | - Chad McMarrow (@cmcmarrow) 9 | 10 | ## Agenda 11 | - Welcome 12 | - New & Upcoming Releases 13 | - https://github.com/saltstack/salt/issues/64925 14 | - Closing of Salt issue backlog 15 | - Community Issues and Discussion 16 | 17 | ## Discussed Previously 18 | - multi-minion got included in the 3006.2 release 19 | - Daffyd has been testing and is displaying the double-return issue 20 | - We need to get that fixed or figured out... or something 21 | - Daffyd will open an issue depending on his findings 22 | - Could be linking off the UUID grain 23 | - Could also try setting the pidfile option in minion config 24 | - Nope, they have separate locations 25 | - rSync on Windows 26 | - Looked at the rsync-git package in winrepo 27 | - Maybe need to use cwrsync instead... less dependencies 28 | - Remove the version from the Display Name in the NSIS/MSI installer 29 | - The version is already recorded in ``appwiz.cpl`` under version 30 | - It looks cleaner and makes the state ``pkg.installed`` more clear when 31 | using ``test=True`` 32 | 33 | ## Today's Discussion 34 | - Windows Beacons 35 | - https://github.com/saltstack/salt/issues/52270 (registry beacon) 36 | - https://github.com/saltstack/salt/issues/49965 (diskusage) 37 | - Lea wants to create a beacon for monitoring registry settings 38 | - Need to find a way to programmatically get the modified date-time for registry keys 39 | - Can possibly use win32api.RegQueryInfoKey 40 | - PS Module 41 | - https://github.com/saltstack/salt/issues/65252 42 | - the `ps.psaux` function needs to work on Windows 43 | - 3006.3 minion not able to connect to the master 44 | - There has been a slack user complaining about this issue 45 | - https://github.com/saltstack/salt/issues/65105 46 | - This should be a blocker for the next release 47 | - A basic rundown of how Salt works 48 | - Salt Execution and State modules 49 | - Highstates 50 | - Pillar 51 | 52 | ## TODO 53 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 54 | - `/move-config` options works from the GUI, but not Silently 55 | - Move this to Salt repo as the scripts have been moved there 56 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 57 | - I'm sure there are tests for this 58 | - Move this to Salt repo as the scripts have been moved there 59 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-10-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-10-19 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Lea (@leadevelop) 7 | 8 | ## Agenda 9 | - Welcome 10 | - Current Projects 11 | - Closing of Salt issue backlog 12 | - Coverage 13 | - Community Issues and Discussion 14 | 15 | ## Discussed Previously 16 | - Windows Beacons 17 | - https://github.com/saltstack/salt/issues/52270 (registry beacon) 18 | - https://github.com/saltstack/salt/issues/49965 (diskusage) 19 | - Lea wants to create a beacon for monitoring registry settings 20 | - Need to find a way to programmatically get the modified date-time for registry keys 21 | - Can possibly use win32api.RegQueryInfoKey 22 | - PS Module 23 | - https://github.com/saltstack/salt/issues/65252 24 | - the `ps.psaux` function needs to work on Windows 25 | - 3006.3 minion not able to connect to the master 26 | - There has been a slack user complaining about this issue 27 | - https://github.com/saltstack/salt/issues/65105 28 | - This should be a blocker for the next release 29 | - A basic rundown of how Salt works 30 | - Salt Execution and State modules 31 | - Highstates 32 | - Pillar 33 | 34 | ## Today's Discussion 35 | - WinRepo 36 | - Let's see about making Dafyddj a collaborator 37 | - Sent a message to the SRE's about this 38 | 39 | ## TODO 40 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 41 | - `/move-config` options works from the GUI, but not Silently 42 | - Move this to Salt repo as the scripts have been moved there 43 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 44 | - I'm sure there are tests for this 45 | - Move this to Salt repo as the scripts have been moved there 46 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-11-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-11-16 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Lea (@leadevelop) 7 | - Randy 8 | 9 | ## Agenda 10 | - Welcome 11 | - Current Projects 12 | - Coverage 13 | - 3006.5 / 3007 STS 14 | - Community Issues and Discussion 15 | 16 | ## Discussed Previously 17 | - WinRepo 18 | - Let's see about making Dafyddj a collaborator 19 | - Sent a message to the SRE's about this 20 | 21 | ## Today's Discussion 22 | - Randy's Issue: https://github.com/saltstack/salt/issues/65529 23 | - Need to research fileserver_backend 24 | - The files are being cached, but the state system can't find them 25 | - Bootstrap Script 26 | - Seems to be a release behind 27 | - Can't restart the minion service from the Task Manger -> Services tab 28 | - But it works from the services GUI 29 | - Slack notifications 30 | - Slack module looks to be out of date 31 | - Slack no longer uses an API key 32 | - Instead, you have a web-hook with a unique URL 33 | - Looked at using other methods to post to the webhook 34 | - https://docs.saltproject.io/en/latest/topics/tutorials/http.html#execution-module 35 | - Or just using `cmd.run curl` or something 36 | 37 | ## TODO 38 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 39 | - `/move-config` options works from the GUI, but not Silently 40 | - Move this to Salt repo as the scripts have been moved there 41 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 42 | - I'm sure there are tests for this 43 | - Move this to Salt repo as the scripts have been moved there 44 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2023-12-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2023-12-21 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Lea (@leadevelop) 7 | 8 | ## Agenda 9 | - Welcome 10 | - 3006.5 released 11 | - Current Projects 12 | - 3007 RC beginning of next year 13 | - 3006.6 soon after 14 | - Community Issues and Discussion 15 | 16 | ## Discussed Previously 17 | - Randy's Issue: https://github.com/saltstack/salt/issues/65529 18 | - Need to research fileserver_backend 19 | - The files are being cached, but the state system can't find them 20 | - Bootstrap Script 21 | - Seems to be a release behind 22 | 23 | ## Today's Discussion 24 | - Broadcom acquisition and its implications 25 | - Can't restart the minion service from the Task Manger -> Services tab 26 | - But it works from the services GUI 27 | - https://github.com/saltstack/salt/issues/65577 28 | - Slack notifications 29 | - Slack module looks to be out of date 30 | - Slack no longer uses an API key 31 | - Instead, you have a web-hook with a unique URL 32 | - Looked at using other methods to post to the webhook 33 | - https://docs.saltproject.io/en/latest/topics/tutorials/http.html#execution-module 34 | - Or just using `cmd.run curl` or something 35 | - https://docs.saltproject.io/en/latest/ref/returners/all/salt.returners.slack_webhook_return.html 36 | - Registry Key for the current user 37 | - Tracking locale of each machine 38 | - Wanting to get that information from the registry 39 | - Possibly use multi-minion solution 40 | - Using Powershell currently 41 | - The minion service is started under the user context 42 | - How to debug Salt 43 | - Dafyddj has some suggestions here: 44 | - https://saltstackcommunity.slack.com/archives/C7U9FLK8S/p1700155002286469 45 | - salt-call -l debug 46 | - Upgrading Salt to 3006 47 | - Some of the formulas are not working on 3006 48 | - They are unstable 49 | - Salt Package Manager (SPM) 50 | - Need to explore SPM to replace/supplement gitFS 51 | - WinGet -> OneGet -> AnyPackage -> Winrepo 52 | - Explore adding support for another package manager for software installation 53 | - It's hard to maintain winrepo... there are very few contributors 54 | - Chocolatey only knows about packages installed via chocolatey 55 | 56 | ## TODO 57 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 58 | - `/move-config` options works from the GUI, but not Silently 59 | - Move this to Salt repo as the scripts have been moved there 60 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 61 | - I'm sure there are tests for this 62 | - Move this to Salt repo as the scripts have been moved there 63 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-01-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-01-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Lea (@leadevelop) 7 | 8 | ## Agenda 9 | - Welcome 10 | - Salt Project Community Calendar 11 | - https://saltproject.io/calendar/ 12 | - Current Projects 13 | - 3007 RC beginning of this year 14 | - 3006.6 soon after 15 | - Utf-8 PR: 16 | - https://github.com/saltstack/salt/pull/65791 17 | - Test artifact: https://github.com/saltstack/salt/actions/runs/7558253685/artifacts/1176997457 18 | - PRs, Issues, and SEPs... Oh, my! 19 | - https://github.com/saltstack/salt/pull/65881 20 | - Community Issues and Discussion 21 | - salt.modules.win_event 22 | - need to add xmltodict as a requirement to Salt 23 | 24 | ## Discussed Previously 25 | - Broadcom acquisition and its implications 26 | - Can't restart the minion service from the Task Manger -> Services tab 27 | - But it works from the services GUI 28 | - https://github.com/saltstack/salt/issues/65577 29 | - Slack notifications 30 | - Slack module looks to be out of date 31 | - Slack no longer uses an API key 32 | - Instead, you have a web-hook with a unique URL 33 | - Looked at using other methods to post to the webhook 34 | - https://docs.saltproject.io/en/latest/topics/tutorials/http.html#execution-module 35 | - Or just using `cmd.run curl` or something 36 | - https://docs.saltproject.io/en/latest/ref/returners/all/salt.returners.slack_webhook_return.html 37 | - Registry Key for the current user 38 | - Tracking locale of each machine 39 | - Wanting to get that information from the registry 40 | - Possibly use multi-minion solution 41 | - Using Powershell currently 42 | - The minion service is started under the user context 43 | - How to debug Salt 44 | - Dafyddj has some suggestions here: 45 | - https://saltstackcommunity.slack.com/archives/C7U9FLK8S/p1700155002286469 46 | - salt-call -l debug 47 | - Upgrading Salt to 3006 48 | - Some of the formulas are not working on 3006 49 | - They are unstable 50 | - Salt Package Manager (SPM) 51 | - Need to explore SPM to replace/supplement gitFS 52 | - WinGet -> OneGet -> AnyPackage -> Winrepo 53 | - Explore adding support for another package manager for software installation 54 | - It's hard to maintain winrepo... there are very few contributors 55 | - Chocolatey only knows about packages installed via chocolatey 56 | 57 | ## Today's Discussion 58 | - salt.modules.win_event 59 | - need to add xmltodict as a requirement to Salt 60 | - Lea will follow up about being able to restart the minion service 61 | - Lea got the returner working on master, but needs help tying that in to the 62 | reactor. 63 | - Maybe need to configure the returner in the master config 64 | - Maybe use the `event_return` config option on the master 65 | - Lea has written a blog detailing her exploits writing a reactor and 66 | configuring it with Salt. Also, how she is using Salt to manage registry 67 | hives. 68 | - Staffing the Salt Project 69 | - What does the future hold for Salt-Analytics, Salt-Describe, Salt-Heist, etc 70 | - Unusual uses of Salt 71 | - Provide notifications of things happening on the minion 72 | 73 | ## TODO 74 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 75 | - `/move-config` options works from the GUI, but not Silently 76 | - Move this to Salt repo as the scripts have been moved there 77 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 78 | - I'm sure there are tests for this 79 | - Move this to Salt repo as the scripts have been moved there 80 | - Twangboy: Add xmltodict as a requirement to Salt on Windows 81 | - https://saltstackcommunity.slack.com/archives/C7K04SEJC/p1704493332436159 82 | - Investigate why it disappeared 83 | - Twangboy: What's going on with some projects that were managed by former Salt 84 | core team members: 85 | - Salt-Describe (Megan, Gareth) 86 | - Salt-Analytics (Caleb, Pedro) 87 | - https://saltproject.io/blog/new-salt-extension-salt-analytics/ 88 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-02-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-02-15 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Current Projects 10 | - 3005.5 and 3006.6 CVE release 11 | - 3006.7 12 | - 3007 RC after that 13 | - Great Module Migration 14 | - https://github.com/saltstack/great-module-migration 15 | - https://github.com/saltstack/salt/pull/65971 16 | - Community Issues and Discussion 17 | 18 | ## Discussed Previously 19 | - salt.modules.win_event 20 | - need to add xmltodict as a requirement to Salt 21 | - DONE: https://github.com/saltstack/salt/pull/65920 22 | - Lea will follow up about being able to restart the minion service 23 | - Lea got the returner working on master, but needs help tying that in to the 24 | reactor. 25 | - Maybe need to configure the returner in the master config 26 | - Maybe use the `event_return` config option on the master 27 | - Lea has written a blog detailing her exploits writing a reactor and 28 | configuring it with Salt. Also, how she is using Salt to manage registry 29 | hives. 30 | - Staffing the Salt Project 31 | - What does the future hold for Salt-Analytics, Salt-Describe, Salt-Heist, etc 32 | - Unusual uses of Salt 33 | - Provide notifications (slack/salt-analytics) of things happening on the 34 | minion. Ability to send to an external monitoring software 35 | (nagios/elastic/zabbix/datadog/checkmk). Can salt-analytics do that? 36 | 37 | ## Today's Discussion 38 | - Unusual uses of Salt 39 | - Provide notifications (slack/salt-analytics) of things happening on the 40 | minion. Ability to send to an external monitoring software 41 | (nagios/elastic/zabbix/datadog/checkmk). Can salt-analytics do that? 42 | - xmltodict will be in 3006.7 for Windows 43 | - Master on Windows: 44 | - $env:SALT_BUILD_ALL_BINS=1 45 | - pip install -e . 46 | - salt * test.ping 47 | 48 | ## TODO 49 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 50 | - `/move-config` options works from the GUI, but not Silently 51 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 52 | - I'm sure there are tests for this 53 | - Twangboy: What's going on with some projects that were managed by former Salt 54 | core team members: 55 | - Salt-Describe (Megan, Gareth) 56 | - Salt-Analytics (Caleb, Pedro) 57 | - Salt-Heist (Megan) -> (Tyler) 58 | - https://saltproject.io/blog/new-salt-extension-salt-analytics/ 59 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-03-21.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-03-21 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Current Projects 10 | - 3006.7 Released Feb 22, 2024 11 | - 3007.0 Released Mar 6, 2024 12 | - Great Module Migration 13 | - https://github.com/saltstack/great-module-migration 14 | - https://github.com/saltstack/salt/pull/65971 15 | - VCredist/UCRT 16 | - Community Issues and Discussion 17 | - https://github.com/apps/renovate 18 | 19 | ## Discussed Previously 20 | - Unusual uses of Salt 21 | - Provide notifications (slack/salt-analytics) of things happening on the 22 | minion. Ability to send to an external monitoring software 23 | (nagios/elastic/zabbix/datadog/checkmk). Can salt-analytics do that? 24 | - xmltodict will be in 3006.7 for Windows 25 | - Master on Windows: 26 | - $env:SALT_BUILD_ALL_BINS=1 27 | - pip install -e . 28 | - salt * test.ping 29 | 30 | ## Today's Discussion 31 | - mend renovate 32 | - We tried installing it... 33 | - GitHub Actions 34 | - Detect versions, including RC versions 35 | - Dafydd's runner will install the versions in the instance 36 | - Testing against the RC will expose unforeseen/untested problem cases 37 | - Salt RC needs some instructions for installing with the bootstrap 38 | - GitPython re-added to 3006.x+ 39 | - https://github.com/saltstack/salt/pull/66188 40 | 41 | ## TODO 42 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 43 | - `/move-config` options works from the GUI, but not Silently 44 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 45 | - I'm sure there are tests for this 46 | - Twangboy: What's going on with some projects that were managed by former Salt 47 | core team members: 48 | - Salt-Describe (Megan, Gareth) 49 | - Salt-Analytics (Caleb, Pedro) 50 | - Salt-Heist (Megan) -> (Tyler) 51 | - https://saltproject.io/blog/new-salt-extension-salt-analytics/ 52 | - Twangboy: Update bootstrap documentation on how to install RC 53 | - Update install guide with those instructions as well 54 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-04-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-04-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - krombel 7 | 8 | ## Agenda 9 | - Welcome 10 | - Recent PR Merges for Windows 11 | - Salt-Cloud: 12 | new options - https://github.com/saltstack/salt/pull/66380 13 | - system.master: 14 | use psutils - https://github.com/saltstack/salt/pull/66366 15 | - LGPO: 16 | clear context - https://github.com/saltstack/salt/pull/66355 17 | - Chocolatey: 18 | name comparison - https://github.com/saltstack/salt/pull/66344 19 | bootstrap version - https://github.com/saltstack/salt/pull/66309 20 | - Winrepo: 21 | directory structure - https://github.com/saltstack/salt/pull/66334 22 | package definitions - https://github.com/saltstack/salt-winrepo-ng/pull/2099 23 | - VCRedist 2013/UCRT: 24 | merge forward fix - https://github.com/saltstack/salt/pull/66318 25 | initial removal - https://github.com/saltstack/salt/pull/66250 26 | - VCRedist 2022: 27 | https://github.com/saltstack/salt/pull/66276 28 | - Bootstrap: 29 | https://github.com/saltstack/salt-bootstrap/pull/1993 30 | https://gitlab.com/saltstack/open/docs/salt-install-guide/-/merge_requests/203 31 | - Great Module Migration 32 | - https://github.com/saltstack/great-module-migration 33 | - https://github.com/saltstack/salt/pull/65971 34 | - Community Issues and Discussion 35 | 36 | ## Discussed Previously 37 | - mend renovate 38 | - We tried installing it... 39 | - GitHub Actions 40 | - Detect versions, including RC versions 41 | - Dafydd's runner will install the versions in the instance 42 | - Testing against the RC will expose unforeseen/untested problem cases 43 | - Salt RC needs some instructions for installing with the bootstrap 44 | - GitPython re-added to 3006.x+ 45 | - https://github.com/saltstack/salt/pull/66188 46 | 47 | ## Today's Discussion 48 | - Mend Renovate 49 | - A way to keep our package definitions and github actions versions updated 50 | - Copier: 51 | - Project template tool 52 | - Salt-call as a user without needing permissions 53 | - Winrepo: graylog-collector-sidecar PR from Krombel 54 | - Discussed options and changes 55 | 56 | ## TODO 57 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 58 | - `/move-config` options works from the GUI, but not Silently 59 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 60 | - I'm sure there are tests for this 61 | - dafyddj: Demo using copier to create a peronalized/custom winrepo 62 | https://github.com/dafyddj/copier-salt-winrepo 63 | - dafyddj: Demo the sandboxed salt call thing 64 | https://github.com/dafyddj/copier-salt-local 65 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-05-16.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-05-16 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Alex Angel 7 | - Lea 8 | - David G 9 | 10 | ## Agenda 11 | - Welcome 12 | - Releases 13 | - 3006.8 14 | - 3007.1 15 | - Recent PR Merges for Windows 16 | - modules/cmdmod.py: 17 | cmd.script with runas - https://github.com/saltstack/salt/pull/66447 18 | - utils/win_lgpo_netsh.py: 19 | use powershell instead of netsh - https://github.com/saltstack/salt/pull/66434 20 | 21 | ## Discussed Previously 22 | - Mend Renovate 23 | - A way to keep our package definitions and github actions versions updated 24 | - Copier: 25 | - Project template tool 26 | - Salt-call as a user without needing permissions 27 | - Winrepo: graylog-collector-sidecar PR from Krombel 28 | - Discussed options and changes 29 | 30 | ## Today's Discussion 31 | - Community Issues and Discussion 32 | - Demos 33 | - Dafyddj: salt-call 34 | - Demoed using salt-call using Saltfile to run in local mode in the user 35 | context without requiring permissions to `ProgramData\Salt Project\Salt` 36 | - Changes in 3006.5+ broke the Saltfile so this configuration no longer 37 | works. May be due to the CVE release that addressed some path injection 38 | vulnerabilities. The `Saltfile` uses relative paths that are outside the 39 | expected path 40 | - Salt Minion Chocolatey packages are out of date. 41 | - Older versions are using the wrong URL that becomes out of date with each 42 | release. They need to user the `minor` directory. 43 | - The `.nupkg` file is just a zip file that contains scripts and metadata 44 | about the script. We need to update the older `.nupkg` files and submit a 45 | pull request to get those updated. Hopefully the hashes are unchanged, they 46 | should be. 47 | - Lea volunteered to do this 48 | - Master config batch settings 49 | - Lea is trying to understand how to set the batch settings in the master 50 | config so that she doesn't have to apply them with each command on the CLI. 51 | Salt CLI doesn't seem to be picking those up. 52 | 53 | ## TODO 54 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 55 | - `/move-config` options works from the GUI, but not Silently 56 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 57 | - I'm sure there are tests for this 58 | - Lea: Update chocolatey salt minion installer definitions 59 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-06-27.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-06-27 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Releases 10 | - 3006.9 (in-progress) 11 | - Recent PR Merges for Windows 12 | - modules/cmdmod.py: 13 | `cmd.script` with runas - https://github.com/saltstack/salt/pull/66447 14 | - This one has some problems 15 | 16 | ## Discussed Previously 17 | - Demos 18 | - Dafyddj: salt-call 19 | - Demoed using salt-call using Saltfile to run in local mode in the user 20 | context without requiring permissions to `ProgramData\Salt Project\Salt` 21 | - Changes in 3006.5+ broke the Saltfile so this configuration no longer 22 | works. May be due to the CVE release that addressed some path injection 23 | vulnerabilities. The `Saltfile` uses relative paths that are outside the 24 | expected path 25 | - Salt Minion Chocolatey packages are out of date. 26 | - Older versions are using the wrong URL that becomes out of date with each 27 | release. They need to user the `minor` directory. 28 | - The `.nupkg` file is just a zip file that contains scripts and metadata 29 | about the script. We need to update the older `.nupkg` files and submit a 30 | pull request to get those updated. Hopefully the hashes are unchanged, they 31 | should be. 32 | - Great job, Lea: 33 | - https://github.com/barkingfoodog/ChocolateySaltMinion/pulls?q=is%3Apr+is%3Aclosed 34 | - Master config batch settings 35 | - Lea is trying to understand how to set the batch settings in the master 36 | config so that she doesn't have to apply them with each command on the CLI. 37 | Salt CLI doesn't seem to be picking those up. 38 | 39 | ## Today's Discussion 40 | - Community Issues and Discussion 41 | - Winrepo Renovate 42 | - There is now a pinned issue for manually updating versions in the package 43 | definitions. You just check the box in the issue and wait a few seconds. 44 | Renovate will pick it up and update everything that it has defined in its 45 | `renovate.json5` file. 46 | - We need to create some metadata comments in the sls files we want renovate 47 | to update 48 | - archive.repo.saltproject.io 49 | - I need to find out if this is still used and if we need to archive any of 50 | our more recent releases 51 | - https://github.com/saltstack/salt/issues/65265 52 | - This is a pretty active issue regarding connectivity issues. It has gotten 53 | worse in 3007. I'm going to bring it to dwoz's attention. 54 | 55 | ## TODO 56 | - Twangboy: https://github.com/saltstack/salt-windows-nsis/issues/15 57 | - `/move-config` options works from the GUI, but not Silently 58 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 59 | - I'm sure there are tests for this 60 | - Lea: Update chocolatey salt minion installer definitions 61 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-07-18.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-07-18 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | 7 | ## Agenda 8 | - Welcome 9 | - Releases 10 | - 3006.9 (in-progress) 11 | - Recent PR Merges for Windows 12 | - modules/cmdmod.py: 13 | `cmd.script` with runas - https://github.com/saltstack/salt/pull/66447 14 | Fixes here: https://github.com/saltstack/salt/pull/66727 15 | - NSIS Installer Test 16 | Tests and Fixes: https://github.com/saltstack/salt/pull/66708 17 | 18 | ## Discussed Previously 19 | - Winrepo Renovate 20 | - There is now a pinned issue for manually updating versions in the package 21 | definitions. You just check the box in the issue and wait a few seconds. 22 | Renovate will pick it up and update everything that it has defined in its 23 | `renovate.json5` file. 24 | - We need to create some metadata comments in the sls files we want renovate 25 | to update 26 | - archive.repo.saltproject.io 27 | - I need to find out if this is still used and if we need to archive any of 28 | our more recent releases 29 | - https://github.com/saltstack/salt/issues/65265 30 | - This is a pretty active issue regarding connectivity issues. It has gotten 31 | worse in 3007. I'm going to bring it to dwoz's attention. 32 | 33 | ## Today's Discussion 34 | - Community Issues and Discussion 35 | - win_wua issue. I'll take a look at it. 36 | - winrepo versions... tagging winrepo versions 37 | - Create winrepo packages that are installed with Salt Package Manager (SPM) 38 | - Publish a JSON file with the contents of the repository on a release 39 | - Create packages using SPM so people don't have to use Git to use winrepo 40 | 41 | ## TODO 42 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 43 | - I'm sure there are tests for this 44 | - Twangboy: archive.repo.saltproject.io 45 | - I need to find out if this is still used and if we need to archive any of 46 | our more recent releases 47 | - Daffydj: Renovate workshop for next meeting 48 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-08-15.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-08-15 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Mark Price 7 | 8 | ## Agenda 9 | - Welcome 10 | - Releases 11 | - 3006.9 (released) 12 | - 3007.2 (upcoming) 13 | 14 | ## Discussed Previously 15 | - Community Issues and Discussion 16 | - win_wua issue. I'll take a look at it. 17 | https://github.com/saltstack/salt/pull/66739 18 | - winrepo versions... tagging winrepo versions 19 | - Create winrepo packages that are installed with Salt Package Manager (SPM) 20 | - Publish a JSON file with the contents of the repository on a release 21 | - Create packages using SPM so people don't have to use Git to use winrepo 22 | 23 | ## Today's Discussion 24 | - Went through adding a renovate comment on Notepad++ and VLC 25 | After merge, renovate created a PR with the latest version 26 | - Mark brought up the ability to specify a source in a closed/air-gapped 27 | environment. We talked about adding some boilerplate code that defaults to 28 | the original location, but could be changed with a grain or minion config. 29 | 30 | ## TODO 31 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 32 | - I'm sure there are tests for this 33 | - Twangboy: archive.repo.saltproject.io 34 | - I need to find out if this is still used and if we need to archive any of 35 | our more recent releases 36 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-09-19.md: -------------------------------------------------------------------------------- 1 | # Notes from 2024-09-19 2 | 3 | ## Attendees 4 | - Shane Lee (@twangboy) 5 | - Dafydd Jones (@dafyddj) 6 | - Mark Price 7 | - DG 8 | 9 | ## Agenda 10 | - Welcome 11 | - Need to fix the links (again) 12 | - Community Calendar 13 | - Personal Calendar 14 | - Zoom Calendar 15 | - Discord Event 16 | - Releases: 17 | - 3006.10 (upcoming) 18 | - 3007.2 (upcoming) 19 | - Discussed Previously: 20 | - Went through adding a renovate comment on Notepad++ and VLC 21 | After merge, renovate created a PR with the latest version 22 | - Mark brought up the ability to specify a source in a closed/air-gapped 23 | environment. We talked about adding some boilerplate code that defaults to 24 | the original location, but could be changed with a grain or minion config. 25 | Jinja at the top that defaults to the public source, but lets you specify 26 | your own from pillar, minion config, or grains. (Firefox uses config.get) 27 | - Important Issues: 28 | - Reboot state has a hard-coded delay 29 | - Need to add the `wait_for_reboot` option to the state for `system.reboot` 30 | - Also needs to be documented to be clear that the wait isn't occurring on 31 | the master. 32 | - No issue was created 33 | - Noteable PRs: 34 | - 35 | - Community Issues and Discussion 36 | - Compartmentalizing Pillar Data 37 | - Shane needs to follow up with Daniel or CR 38 | - (Asked in open hour) 39 | 40 | ## Today's Discussion 41 | - Using renovate to get versions from software outside of github 42 | 43 | ## TODO 44 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 45 | - I'm sure there are tests for this 46 | - Twangboy: archive.repo.saltproject.io 47 | - I need to find out if this is still used and if we need to archive any of 48 | our more recent releases 49 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-10-17.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2024-10-17 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | 8 | ## Agenda 9 | - Welcome 10 | - I think I got the links fixed 11 | - Releases: 12 | - 3006.10 (upcoming) 13 | - 3007.2 (upcoming) 14 | - Discussed Previously: 15 | - Using renovate to get versions from software outside of github 16 | - Important Issues: 17 | - 18 | - Noteable PRs: 19 | - https://github.com/saltstack/salt/pull/66968 20 | - Community Issues and Discussion 21 | - Semantic Releases for Winrepo-NG 22 | - A naming scheme for commit messages that will trigger a release 23 | - Daffyd will work on this over the next few weeks or so 24 | - https://github.com/saltstack/salt/pull/65075 25 | - Use tools to get into the VM and try logging in and re-running the test 26 | - Daffyd may know of another way to get into the VM 27 | 28 | ## TODO 29 | - Twangboy: Test: https://github.com/saltstack/salt-windows-nsis/issues/11 30 | - I'm sure there are tests for this 31 | - Daffyddj: Automating Semantic Releases on Winrepo 32 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2024-12-19.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2024-12-19 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | 8 | ## Agenda 9 | - Welcome 10 | - Sorry we missed last month, I was sick and forgot to cancel 11 | - CICD/AWS Issues 12 | - Working through getting the pipeline fixed 13 | - Releases: 14 | - 3006.10 (after the new year) 15 | - 3007.2 (after the new year) 16 | - 3008 (after the new year) 17 | - Discussed Previously: 18 | - Semantic Releases for Winrepo-NG 19 | - A naming scheme for commit messages that will trigger a release 20 | - Dafydd will work on this over the next few weeks or so 21 | - https://github.com/saltstack/salt/pull/65075 22 | - Use tools to get into the VM and try logging in and re-running the test 23 | - Dafydd may know of another way to get into the VM 24 | - Important Issues: 25 | - 26 | - Noteable PRs: 27 | - 28 | - Community Issues and Discussion 29 | - Semantic Releases 30 | - Dafydd showed us around the new Semantic releases in winrepo 31 | - Semantic releases looks for keywords in the commit messages 32 | - When those are found it triggers a release 33 | - The type of release (major, minor, patch) is dependent upon the keyword used 34 | - The release itself also generates a json file for each package in winrepo 35 | that just contains the versions available for that package. It uses github 36 | pages and works like an API of sorts. There is currently no index.html, so 37 | you need to pass a version. Here are some examples. 38 | https://saltstack.github.io/salt-winrepo-ng/latest/7zip.json 39 | https://saltstack.github.io/salt-winrepo-ng/v2.0.10/git.json 40 | - Plans to create an artifact with each release that can be installed onto 41 | a Salt master or a masterless minion using SPM 42 | - We're going to investigate if spm works on Windows 43 | 44 | ## TODO 45 | - -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2025-01-16.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2025-01-16 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | 8 | ## Agenda 9 | - Welcome 10 | - CICD/AWS Issues 11 | - Working through getting the pipeline fixed 12 | - Releases: 13 | - 3006.10 (after the new year) 14 | - 3007.2 (after the new year) 15 | - 3008rc (after the new year) 16 | - Discussed Previously: 17 | - Semantic Releases 18 | - Dafydd showed us around the new Semantic releases in winrepo 19 | - Semantic releases looks for keywords in the commit messages 20 | - When those are found it triggers a release 21 | - The type of release (major, minor, patch) is dependent upon the keyword used 22 | - The release itself also generates a json file for each package in winrepo 23 | that just contains the versions available for that package. It uses github 24 | pages and works like an API of sorts. There is currently no index.html, so 25 | you need to pass a version. Here are some examples. 26 | https://saltstack.github.io/salt-winrepo-ng/latest/7zip.json 27 | https://saltstack.github.io/salt-winrepo-ng/v2.0.10/git.json 28 | - Plans to create an artifact with each release that can be installed onto 29 | a Salt master or a masterless minion using SPM 30 | - We're going to investigate if spm works on Windows 31 | - Important Issues: 32 | - 33 | - Noteable PRs: 34 | - 35 | - Community Issues and Discussion 36 | - Bug: WinRepo on Salt 3007.1 37 | - Has to do with a win_pkg function that doesn't exist 38 | - Dafydd will continue to try to reproduce 39 | - We need to have pkg tests for this 40 | - salt-extensions: 41 | - Perhaps more adoption/work when 3008rc is released 42 | - We'll need to see how it works in practice 43 | - Messaging about CICD 44 | - We need to have a blog or something outside of Discord to communicate to 45 | the community why there are no releases, why PRs aren't being merged, etc 46 | - NSClient Package Definition in WinRepo: 47 | - Currently it uses the /quiet switch in the installer_flags. 48 | - Needs to be /qn /noreboot 49 | 50 | ## TODO 51 | - -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2025-02-20.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2025-02-20 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | - David G 8 | 9 | ## Agenda 10 | - Welcome 11 | - CICD Status 12 | - Getting close 13 | - Releases: 14 | - 3006.10 : next week 15 | - 3007.2 : next week 16 | - 3008rc : maybe april 17 | - Discussed Previously: 18 | - Bug: WinRepo on Salt 3007.1 19 | - Has to do with a win_pkg function that doesn't exist 20 | - Dafydd will continue to try to reproduce 21 | - We need to have pkg tests for this 22 | - salt-extensions: 23 | - Perhaps more adoption/work when 3008rc is released 24 | - We'll need to see how it works in practice 25 | - Messaging about CICD 26 | - We need to have a blog or something outside of Discord to communicate to 27 | the community why there are no releases, why PRs aren't being merged, etc 28 | - NSClient Package Definition in WinRepo: 29 | - Currently it uses the /quiet switch in the installer_flags. 30 | - Needs to be /qn /norestart 31 | - Important Issues: 32 | - 3007.1 isn't installing in the CICD on WinRepo 33 | - It regularly times out, had to put a timeout on the job so that it doesn't 34 | run for hours. 35 | - It's intermittent 36 | - Noteable PRs: 37 | - 38 | - Community Issues and Discussion 39 | - WMIC Grains issue will be released in 3006.10/3007.2 40 | - OSConfig 41 | - To make your system conform to security requirements 42 | - Part of Server 2025 43 | - There are powershell tools to support this 44 | - https://learn.microsoft.com/en-us/windows-server/security/osconfig/osconfig-overview 45 | - win_lgpo 46 | - You have to run `gpupdate` to apply the policies 47 | - This would apply to the lgpo_reg module as well 48 | - Use a requisite (listen) to detect changes to the LGPO and then apply gpupdate 49 | - https://docs.saltproject.io/en/latest/ref/states/requisites.html 50 | 51 | ## TODO 52 | - Get the NSIS Installer changes into 3007.x. Figure out how they got missed 53 | in the merge forward 54 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2025-03-20.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2025-03-20 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | - Jake Worth 8 | - Jim 9 | 10 | ## Agenda 11 | - Welcome 12 | - CICD Status 13 | - Getting close 14 | - Releases: 15 | - 3006.10 : released 16 | - 3007.2 : next week 17 | - 3008rc : maybe april 18 | - Discussed Previously: 19 | - WMIC Grains issue will be released in 3006.10/3007.2 20 | - OSConfig 21 | - To make your system conform to security requirements 22 | - Part of Server 2025 23 | - There are powershell tools to support this 24 | - https://learn.microsoft.com/en-us/windows-server/security/osconfig/osconfig-overview 25 | - win_lgpo 26 | - You have to run `gpupdate` to apply the policies 27 | - This would apply to the lgpo_reg module as well 28 | - Use a requisite (listen) to detect changes to the LGPO and then apply gpupdate 29 | - https://docs.saltproject.io/en/latest/ref/states/requisites.html 30 | - Noteable PRs: 31 | - https://github.com/saltstack/salt/pull/67781 (missing winrepo.list_repo_pkgs) 32 | 33 | - Community Issues and Discussion 34 | - What's in the 3008 release 35 | - Issues testing Release Candidates 36 | - WinRepo: 37 | - Testing: Setting grains doesn't take effect until the next salt-call run 38 | 39 | ## TODO 40 | - Twangboy: Investigate the pkg.install 3006.10 issue 41 | https://github.com/saltstack/salt/issues/67902 42 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2025-04-17.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2025-04-17 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafydd Jones (@dafyddj) 7 | - Steve Corey 8 | - John (jlengeling) 9 | 10 | ## Agenda 11 | - Welcome 12 | - CICD Status 13 | - 3006.x looking good 14 | - 3007.x working on merge forward 15 | - Releases: 16 | - 3006.10 : released 17 | - 3007.2 : soon 18 | - 3008rc : tbd 19 | - Discussed Previously: 20 | - What's in the 3008 release 21 | - Issues testing Release Candidates 22 | - WinRepo: 23 | - Testing: Setting grains doesn't take effect until the next salt-call run 24 | - Noteable PRs: 25 | - https://github.com/saltstack/salt/pull/67952 26 | 27 | - Community Issues and Discussion 28 | - winrepo: Using grains to set environment 29 | Better to use the salt client and setup the environment directly 30 | - dummy salt-extension: 31 | - making powershell the default shell in Windows instead of CMD 32 | - A powershell engine? 33 | - Errors installing Salt Minion (MSI) 34 | - Error: 2738 35 | - Gonna try the NSIS installer 36 | - Localization on Windows with some salt modules 37 | - lgpo_reg vs lgpo modules 38 | - We need to communicate better with our community volunteers exactly what 39 | we want them to do... how they can contribute. 40 | 41 | ## TODO 42 | - Twangboy: Investigate the pkg.install 3006.10 issue 43 | https://github.com/saltstack/salt/issues/67902 44 | - Twangboy: Any idea when the next 3006.11 will happen 45 | - Twangboy: Investigate making powershell the default shell on Windows 46 | - Daffyd: Investigate pythonnet 47 | https://devblogs.microsoft.com/powershell/hosting-powershell-in-a-python-script/ 48 | 49 | -------------------------------------------------------------------------------- /working_groups/wg-Windows/meeting-notes/2025-05-15.md: -------------------------------------------------------------------------------- 1 | # Windows Working Group Meeting 2 | # Notes from 2025-05-15 3 | 4 | ## Attendees 5 | - Shane Lee (@twangboy) 6 | - Dafyddj 7 | 8 | ## Agenda 9 | - Welcome 10 | - CICD Status 11 | - 3006.x looking good 12 | - 3007.x looking good 13 | - master looking good 14 | - Releases: 15 | - 3006.10 : released 16 | - 3007.2 : released 17 | - 3008rc : fall 2025 18 | - Discussed Previously: 19 | - winrepo: Using grains to set environment 20 | Better to use the salt client and setup the environment directly 21 | - dummy salt-extension: 22 | - making powershell the default shell in Windows instead of CMD 23 | - A powershell engine? 24 | - Errors installing Salt Minion (MSI) 25 | - Error: 2738 26 | - Gonna try the NSIS installer 27 | - Localization on Windows with some salt modules 28 | - lgpo_reg vs lgpo modules 29 | - We need to communicate better with our community volunteers exactly what 30 | we want them to do... how they can contribute. 31 | - Noteable PRs: 32 | - py3.11: https://github.com/saltstack/salt/pull/68018 33 | - py3.11: https://github.com/saltstack/salt/pull/67964 34 | - py3.12: https://github.com/saltstack/salt/pull/68021 35 | 36 | - Community Issues and Discussion 37 | - dafyddj demonstrated the changes to winrepo using the salt client to set 38 | architecture grain so we can test urls properly. Using the salt loader 39 | directly and creating a dummy object for the registry module. This allows 40 | the tests to be run on Linux instead of Windows. 41 | - Making powershell the default shell on Windows needs to be a discussion 42 | - The MSI Error 2738 could have been the vbscript issue. Looks like this has 43 | been fixed. 44 | - pkg.install function on Windows needs a force option 45 | - lgpo_reg: 46 | - Currently writes the registry as well, maybe we need to make that 47 | configurable 48 | - User policies are set in the context of the service account. They probably 49 | shouldn't be written to the registry at all as that is applied when the 50 | user logs in. 51 | - Need to create a module that will generate a state based on the contents 52 | of the Registry.pol file. This could/should be a salt extension 53 | 54 | ## TODO 55 | - Twangboy: Investigate the pkg.install 3006.10 issue 56 | https://github.com/saltstack/salt/issues/67902 57 | - Twangboy: Any idea when the next 3006.11 will happen 58 | - Twangboy: Investigate making powershell the default shell on Windows 59 | - Twangboy: We need to communicate better with our community volunteers exactly 60 | what we want them to do... how they can contribute. 61 | - Dafydd: Investigate pythonnet 62 | https://devblogs.microsoft.com/powershell/hosting-powershell-in-a-python-script/ 63 | - Dafydd: Create an issue for the lgpo_reg module to not write user policies 64 | to the registry as those should be handled by Windows when the user 65 | logs in 66 | 67 | --------------------------------------------------------------------------------