Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-31649

Build and release openvox-agent 7 to client repository

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • None
    • Puppet
    • None
    • Build and release openvox-agent 7 to client repository
    • To Do
    • SAT-31648 - Switch from Perforce Puppet to OpenVox RPMs
    • False
    • sat-endeavour
    • None
    • None
    • None

      Goal:

      Build openvox-agent 7 and release it into the client repository as a replacement for puppet-agent to provide continuity for users.

       

      Acceptance Criteria:

      • openvox-agent-7.37.2 is available in Satellite client repository for all supported RHEL releases and arches that previously had puppet-agent (7/8/9 - x86_64)
      • the builds having provides/obsoletes for "puppet-agent" to smoothen the upgrade
      • Package upgrade on a client with puppet-agent results in the client system having openvox-agent and puppet-agent is removed
      • Puppet integration in Satellite (via foreman_puppet / smart-proxy) still works as before, hosts can be managed, reports are parsed as "Puppet", etc.
      • No workflow changes for users, no documentation changes required (we might still want to do some for clarification)

      Open questions

      • Should we also update RHEL6? OpenVox itself doesn't offer any builds there.
      • There are old builds for aarch64 (rhel8 puppet7, rhel7 puppet6) / i686 (rhel6 puppet7) / ppc64le (rhel7 puppet6)
      • RHEL10 didn't have puppet-agent, so probably doesn't need an openvox-agent 7 build
      • How much of the documentation do we want to update to a remove "Puppet" branding? There are mentions of the package name, that's easy. But we also have Guides of the style "managing with puppet"
         

              Unassigned Unassigned
              ehelms@redhat.com Eric Helms
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: