You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a developer of @debops but am working with SaltStack at work for ~one year on/off (mostly off) and start to get some ideas how this can scale. The experience with Ansible definitely helps to see where default Salt deployments have shortages and how ideas from Ansible can help out there. Today (don’t know why it took me so long) I finally found a name I like enough to check if it is still free. SaltOps. As I now see, it is already taken but inactive. I just want to ask what your plans are with this project, if we can work together and so on? But this has time. I would first start out at the @geberit org probably. When it grows bigger (currently nothing to publish), maybe the current saltops organization here could be reborn. Let me know what you think.
My rough idea. CM for SLES systems and open to other distros, reusing all the good ideas of DebOps and re implement it natively in SaltStack. Debian is not on my agenda. I still use DebOps for my private Debian infra and will not migrate because it works so well.
Structure ideas: Pillarstack to manage the Pillar, use public Salt Formulas when available. I found the Formulas of much higher quality then the typical Ansible roles (that were the reason why DebOps rewrote most of the roles even when roles already existed).
@mjs, you might also be interested in this discussion as you are the most active dev of https://github.com/TheCacophonyProject/saltops which seems to be Debian focused and goes into other directions than what I have in mind.
@ypidhttps://github.com/TheCacophonyProject/saltops is just the Salt states and related stuff for a specific organisation. It's not intended to be used by anyone else and isn't related to your efforts here.
Hey guys,
I am a developer of @debops but am working with SaltStack at work for ~one year on/off (mostly off) and start to get some ideas how this can scale. The experience with Ansible definitely helps to see where default Salt deployments have shortages and how ideas from Ansible can help out there. Today (don’t know why it took me so long) I finally found a name I like enough to check if it is still free. SaltOps. As I now see, it is already taken but inactive. I just want to ask what your plans are with this project, if we can work together and so on? But this has time. I would first start out at the @geberit org probably. When it grows bigger (currently nothing to publish), maybe the current saltops organization here could be reborn. Let me know what you think.
My rough idea. CM for SLES systems and open to other distros, reusing all the good ideas of DebOps and re implement it natively in SaltStack. Debian is not on my agenda. I still use DebOps for my private Debian infra and will not migrate because it works so well.
Structure ideas: Pillarstack to manage the Pillar, use public Salt Formulas when available. I found the Formulas of much higher quality then the typical Ansible roles (that were the reason why DebOps rewrote most of the roles even when roles already existed).
@mjs, you might also be interested in this discussion as you are the most active dev of https://github.com/TheCacophonyProject/saltops which seems to be Debian focused and goes into other directions than what I have in mind.
For more background on me, you can refer to https://docs.debops.org/en/master/meta/philosophy.html#robin-ypid-schneider
CC: @drybjed as the main developer of DebOps.
The text was updated successfully, but these errors were encountered: