Support for OpenVox puppet within foreman katello

Team, I was told by Openvox Community there is a discussion to add support for openvox within foreman/katello installer for the opensource puppet users.

Can you please help me onto when can we expect that to release ? any tentative timeline would really help us plan our next steps in our infrastructure.

1 Like

I don’t think there is a strict planning on what exactly needs to be done. I know @binford2k has been investigating what’s needed and done some work in the general direction.

Because of that there’s no strict plan at the moment, though I’d love to have one.

1 Like

Thank You! I would be good if we get that released with 3.15 or so. hoping for that.

is there way I can get the foreman-installer not install puppet-agent, so that I can get openvox work? currently its not letting me bypass that step.

@binford2k has opened PRs:

Having said that, I think openvox-agent should have the metadata that it provides and replaces puppet-agent:

In practice I don’t see them showing up as I’d want them:

# rpm -q --provides openvox-agent
openvox-agent = 8.14.0-1.el9
openvox-agent(x86-64) = 8.14.0-1.el9
# rpm -q --obsoletes openvox-agent
puppet-agent

I’ve opened Provide puppet-agent on RPM by ekohl Ā· Pull Request #21 Ā· OpenVoxProject/openvox-agent Ā· GitHub for that. puppetserver probably needs the same treatment.

2 Likes

Any plans to continue with the migration from puppet to openvox?
I had a look at some of the openvox PRs and would be OK to work together with others to get this whole story finished.

4 Likes

I’ve been trying to get a handle on what’s going on with this and been working on template and template migration support, but I’m struggling to pull together the moving parts,

It seems openvox-agent has properly defined the Provides: puppet-agent = X and Obsoletes: puppet-agent < X+1 since 7.37.2 and 8.18.0 in June.

For those not deploying the Puppet Server integration, should this suffice for opting for OpenVox over Puppet? Similarly, is OpenVox intended to replace Puppet in an upcoming release of Satellite?

Yes, that was done in Provide puppet-agent on RPM by ekohl Ā· Pull Request #21 Ā· OpenVoxProject/openvox-agent Ā· GitHub. I haven’t verified the Debian fix in Correct provides statement for Debian packaging by ekohl Ā· Pull Request #120 Ā· OpenVoxProject/openvox-agent Ā· GitHub myself, but that.

However, I’m strongly of the opinion that the same should be done for the openvox-server and openvoxdb packages too.

It mostly should. What @ikonia is working is also important though: setting up the right provisioning bits. Most notable is the repository setup.

As for Satellite, this isn’t right place for official messages but as one of the Satellite product owners I can assure you it’s on our radar.

Agreed. I briefly looked at the server package and it sort of had it set, but not the way openvox-agent is defined.

For my own education, what does this mean, exactly?

:+1:

When you provision a new machine (with kickstart or preseed installations) then you need set up the repositories. That is, if you don’t used synced content by Katello.

Ah, you mean the actual OpenVox/Puppet repositories?

Correct.