Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1743

Separate check-for-updates call into new TK service

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 5.0.0
    • Component/s: None
    • Labels:
      None
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment

      Description

      As we complete the work to migrate the puppetserver metrics implementation from PE into OSS, I'd like to be able to have the master-service in OSS puppetserver be used directly in PE puppetserver, avoiding the duplication of logic that occurs between the master and pe-master services today - CA initialization, Puppet HTTP route registrations, etc.

      One major difference between the OSS and PE master services today is that the OSS master service does a check-for-updates call to dujour whereas in PE, the dujour work is done from a separate "analytics" trapperkeeper service. For this ticket, I'd like to mirror that approach in OSS puppetserver - moving the check-for-updates call into an OSS-specific "analytics" trapperkeeper service. We'd only bootstrap the appropriate service for the target puppetserver package - OSS vs. PE.

      Patrick Carlisle and Brian Cain have been discussing moving the analytics service in pe-puppet-server-extensions into its own repo at some point. Maybe it would make sense to move an OSS-based analytics service out to a new repo as well at some point. In the short term, though, I think at least separating the OSS check-for-updates work into a new TK service would allow for the OSS master service to be reusable in PE - with the possibility of the OSS analytics service potentially being moved to somewhere else later on.

        Attachments

          Activity

            People

            • Assignee:
              jeremy.barlow Jeremy Barlow
              Reporter:
              jeremy.barlow Jeremy Barlow
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support