Switch puppetdb->openvoxdb module - #982
Conversation
| Optional[String[1]] $terminus_package = undef, | ||
| ) { | ||
| class { 'puppetdb::master::config': | ||
| class { 'openvoxdb::master::config': |
There was a problem hiding this comment.
Or we duplicate the class into puppet::server::openvoxdb? 🤔 Or call puppetdb::master::config vs openvoxdb::master::config depending on if we have puppetdb vs openvoxdb modules in our environment?
There was a problem hiding this comment.
Are you asking because:
- Preventing users from having to update their puppet code due to openvox support?
- Expecting there may be differences between openvox and puppet that require separate implementations?
There was a problem hiding this comment.
I don't expect a different implementation. But I don't know your support policy. Do you want to keep puppet support and openvox in parallel? Can we drop puppet in favour of openvox?
131a882 to
ece74b2
Compare
|
We've been running this exact unconditional switch in production since 2026-04-30 with puppet/openvoxdb 9.0.1 on RHEL 10. The catalog compiles cleanly, the puppetdb.service was unaffected during the Puppet agent run, and PuppetDB has been healthy since. Happy to confirm the approach works for sites that have already migrated their packages to OpenVox. |
For compatibility with puppet-openvoxdb. theforeman/puppet-puppet#982
5 participants
Vox Pupuli provides their own module to manage openvoxdb. Also openvox-server has the privatetmp setting that was explicitly configred.
This is still work in progress and we need to figure out a migration path.