Mastodon

1 post1 participant0 posts today

xyhhx 🔻 (plz hire me)i'm making my salts for my qubes set up distributable as rpms, which is also a convenient way to transfer them from domUs to dom0 in a more secure manner (since the rpms are signed)what i'm unsure of is this: currently, i have one rpm that is my whole repo, and the repo contains topfiles that a user can enable individually. should i instead offer the vms (or bundles of them, in some cases) as individual rpms?<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/salt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#salt</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltStack</a> <a href="https://nso.group/tags/rpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpm</a>

Derek | ScriptAutomateA Letter from David Murphy: Retiring from TechSerious thanks, to David, for all the work over the years in making Salt awesome and being a hero in the community!<a href="https://saltproject.io/blog/2025-04-02-david-murphy-retires/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/2025-04-02-david-murphy-retires/</a><a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a> <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a>

Derek | ScriptAutomateSalt Project posted notes from the March 20th, 2025 Open Hour call.In this month’s open hour, we talked about the completion of Salt Project CI work, the recent release of Salt v3006.10 LTS, and more!<a href="https://saltproject.io/blog/2025-03-26-open-hour/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/2025-03-26-open-hour/</a><a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a> <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a>

xyhhx 🔻 (plz hire me)on the topic of salt states for qubes, i found this extremely cool repo: <a href="https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user</a>brilliant way to organize the salts and distribute them imo<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltStack</a>

xyhhx 🔻 (plz hire me)calling all qubes users who use salt! is there a way to target domUs with `state.highstate` when using many topfiles? my repo is at <a href="https://git.sr.ht/~xyhhx/qubes-salts" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://git.sr.ht/~xyhhx/qubes-salts</a>(details in reply)<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/salt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#salt</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltStack</a>

Brad L. :verified:Dear <a href="https://hachyderm.io/tags/LazyWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LazyWeb</a> / <a href="https://hachyderm.io/tags/lazyfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lazyfedi</a>,I'm new to <a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#k8s</a> and am wondering how to handle templating large amounts of config files. I couldn't find anything super useful in my search so I have an <a href="https://hachyderm.io/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a> sidecar I run to generate the kustomizations and config files. My most recent Ansible change was 30 lines, it resulted in changing 5,000 lines of YAML which will further be fed to Kustomize.There has to be a better way?I've heard about Helm, Yoke, KRO, and using an operator pattern. My understanding of those options is:* Helm - My Org recommends avoiding (I don't know why) * KRO - Not stable, but FFS neither is Kustomize * Yoke - Almost kinda operator pattern * Operator Pattern - This feels like reinventing a fucking config manager (ala <a href="https://hachyderm.io/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a>, <a href="https://hachyderm.io/tags/Puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Puppet</a>, <a href="https://hachyderm.io/tags/Chef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chef</a>, <a href="https://hachyderm.io/tags/Saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Saltstack</a>) for every fucking project. What new hell this is.I'm hoping I'm missing something because the only workable flow for this workload is: 1) Create ansible roles/playbook to generate the kustomization.yaml and resources 2) Generate those kustomizations, check them into git 3) Use Kustomize via GitOps to expand the YAML even more 4) Push a metric fuckton of YAML to productionI'm losing my mind over here.

DefectiveWings ✈️:verified:My <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> now has a <a href="https://infosec.exchange/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a> config for installing/ configuring <a href="https://infosec.exchange/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a>!

Derek | ScriptAutomateNew Release from Salt Project: Salt v3006.10 LTS is available!<a href="https://saltproject.io/blog/2025-03-19-new-release-salt-3006-10/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/2025-03-19-new-release-salt-3006-10/</a><a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a> <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a>

Marianne SpillerOkay. Ich hab <a href="https://konfigurationsmanufaktur.de/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a> und <a href="https://konfigurationsmanufaktur.de/tags/molecule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#molecule</a> jetzt eine Weile weniger/kaum verwendet, da der Fokus auf <a href="https://konfigurationsmanufaktur.de/tags/Saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Saltstack</a> lag. Aus Gründen ändert sich das gerade. Und holy, vor allem in molecule wieder reinzufinden ist ein Drama: es hat sich viel geändert, die Doku stimmt nicht, die Beispiele funktionieren nicht, die Fehlermeldungen sind nicht aussagekräftig. Das macht ja mal so GAR keinen Spaß 🙄

Kevin Karhan :verified:<a href="https://bsd.network/@sizeofvoid" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sizeofvoid</a> I'd rather wish for good <a href="https://infosec.space/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ansible</a> support of <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> as well as other orchestration tools like <a href="https://infosec.space/tags/fleetdm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fleetdm</a>, <a href="https://infosec.space/tags/Landscape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Landscape</a>, <a href="https://infosec.space/tags/puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#puppet</a> and <a href="https://infosec.space/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a>...

Derek | ScriptAutomateNew blog post for Salt Project: POP and Idem Projects Will Soon be ArchivedPOP and Idem projects have been in maintenance mode since the acquisition of VMware by Broadcom. Now the projects are considered unmaintained, and are lined up to be archived. All projects will remain public, read-only OSS repositories available under the Apache v2 licenses for anyone who would like to maintain their own forks.<a href="https://saltproject.io/blog/2025-01-24-idem-pop-projects-archived/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/2025-01-24-idem-pop-projects-archived/</a><a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a> <a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a> <a href="https://fosstodon.org/tags/IdemProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IdemProject</a>

Derek | ScriptAutomateNew blog post of the Salt Project Community Open Hour notes from January 16, 2025.In this month’s open hour, we talked about the state of Salt Project CI, extensions for Salt LTS and STS support, outlook on Salt 3008 LTS, and more.<a href="https://saltproject.io/blog/2025-01-16-open-hour/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/2025-01-16-open-hour/</a><a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a> <a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a>

Björn<a href="https://troet.cafe/@simondeutschl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simondeutschl</a> Habs auch vor ein paar Jahren gemacht. Sobald man drin ist in der Sache ist alles weitere sehr recht einfach, es kommt natürlich. Was ich direkt empfehle ist Konfiguration in Versions-Kontrolle z.B. git zu halten so ist es viel einfacher Übersicht zu halten. Gleiches gilt wenn es um Probleme geht, am besten todo listen machen. Das nächste Level ist dann alles deklarativ zu machen z.B. mit <a href="https://mastodon.social/tags/Saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Saltstack</a>. Es kompliziert das ganze aber auf lange sicht kann es vieles vereinfachen.

Freifunk Frankfurt a.M.Free and Open Source Infra and Software <a href="https://chaos.social/tags/Hackathon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hackathon</a> Wir laden euch zum gemeinsamen Arbeiten an <a href="https://chaos.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> in den <a href="https://chaos.social/@cccffm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cccffm</a> vom 17.–19. Januar 2025 ein.Pretix: <a href="https://pretix.ffffm.net/ffffmev/hackathon202401/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://pretix.ffffm.net/ffffmev/hackathon202401/</a>Raum zum Entwickeln und Austauschen bezüglich Freier und Offener <a href="https://chaos.social/tags/Infrastruktur" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Infrastruktur</a> und Software. Zum Beispiel Entwicklung an <a href="https://chaos.social/tags/OpenWrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWrt</a>, der Umbau von <a href="https://chaos.social/tags/Saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Saltstack</a> oder <a href="https://chaos.social/tags/Puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Puppet</a> auf <a href="https://chaos.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> oder <a href="https://chaos.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a>, genauso aber auch Dokumentationserweiterung oder das Erstellen von Anleitungen fürs Routing im Internet<a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a> <a href="https://chaos.social/tags/Frankfurt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frankfurt</a>

folken<a href="https://infosec.exchange/@paco" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@paco</a> <a href="https://chaos.social/tags/nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextcloud</a> has a history refusing to package its software. And refusing to work with distro maintainers.Appimages are useless for the reasons you mentioned.My nextcloud instance uses the offical docker image which I manage using a <a href="https://chaos.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a> state to keep it current.The clients get the snap package. Also salt managed. This setup has worked beautifully so far.It can be that the client lags behind, but sofar I havent had any problems, as I also use the stable docker image.

Elias Probst<a href="https://freie-re.de/@qbi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@qbi</a> <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a>'s Pepper kann das auch: 😄 <a href="https://github.com/saltstack/pepper/issues/219" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/saltstack/pepper/issues/219</a>

DefectiveWings ✈️:verified:<a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@geerlingguy</a> Do you still recommend <a href="https://infosec.exchange/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ansible</a>? We're a <a href="https://infosec.exchange/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a> shop currently, but we're nervous given the most recent changes.How's the health of the ansible project?

Philipp Krennbroadcom is wild. ☠️ <a href="https://mastodon.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a> <a href="https://nlogic.systems/objects/a46f7fba-ef30-4fee-bc3b-6cda7d158777" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nlogic.systems/objects/a46f7fba-ef30-4fee-bc3b-6cda7d158777</a>

Carlos D. Álvaro :apple:For those of you having troubles with the migration of <a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltProject</a> to <a href="https://fosstodon.org/tags/Broadcom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Broadcom</a>, and if you use <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a>, you can check <a href="https://github.com/cdalvaro/docker-salt-master" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cdalvaro/docker-salt-master</a> for running salt-master containerized.<a href="https://fosstodon.org/tags/SaltMaster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltMaster</a> <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltStack</a> <a href="https://fosstodon.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://fosstodon.org/tags/Containers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Containers</a> <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a> <a href="https://fosstodon.org/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IT</a> <a href="https://fosstodon.org/tags/SaltAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaltAPI</a> <a href="https://fosstodon.org/tags/Infrastructure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Infrastructure</a> <a href="https://fosstodon.org/tags/Podman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Podman</a>

🇺🇦 Sven Seeberg<a href="https://social.tsun.co/@kfdm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kfdm</a> <a href="https://mastodon.social/@eliasp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@eliasp</a> <a href="https://infosec.exchange/@isotopp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@isotopp</a> the decline of Saltstack is continuing. They shut down the repo.saltstack.io repos and switched to packages.broadcom.com. AFAICT they notified the community only 1 week in advance: <a href="https://saltproject.io/blog/upcoming-salt-project-docs-and-repo-migration/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://saltproject.io/blog/upcoming-salt-project-docs-and-repo-migration/</a>And the best: packages.broadcom.com does not support IPv6. I have dozens of servers right now that cannot update packages. 😡 <a href="https://gruene.social/tags/Broadcom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Broadcom</a> <a href="https://gruene.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saltstack</a>

Recent searches

Search options

Administered by:

Server stats:

#saltstack