The first release of OpenVox, the OSS implementation of Puppet
7 comments
·January 22, 2025NewJazz
haddonist
Configuration Management of one form or another is a way to ensure consistency across a fleet of servers, and reduce administration overhead. VMs aren't going away any time soon, despite SaaS companies best efforts.
Companies with 100s to 1000s of hours of investment in software like Puppet aren't going to rearchitect without being forced to. By the application becoming unsuitable for current needs, or due to cost.
Broadcom bought out VMWare and jacked the price up by unworkable amounts. Puppet is now owned by a venture capital company and the non-zero possibility is they'll follow Broadcom's playbook. That's why Puppet is being forked.
Why not contribute to Ansible or Salt? What individual programmers do in their spare time is irrelevant to the majority of users of those products.
yjftsjthsd-h
Per https://voxpupuli.org/openvox/ , this is a community fork of Puppet (the tool like ansible/chef/salt), not Puppet (the browser automation tool). In case anyone else was confused too.
leosanchez
> not Puppet (the browser automation tool)
Puppet or Puppeteer ?
ofrzeta
I just wanted to comment that there is no browser automation tool called Puppet when I found out there's a scraper thing that allows entering natural language description for the task (probably using LLM and Puppeteer under the hood). Given that this is quite obscure I guess they indeed mixed it up with Puppeteer.
1. I didn't realize puppet was open core.
2. OpenVox sounds like a text to speech engine.
3. What is the main use case of Puppet / OpenVox in 2025? Same as always? Isn't CM a lot less relevant in the age of platforms like Flatcar and Bottlerocket?
4. Why fork puppet instead of contributing to ansible or salt?