The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #7483

ability to collate how many licenses are being used across multiple CA's

Added by Garrett Honeycutt almost 3 years ago. Updated almost 3 years ago.

Status:AcceptedStart date:05/10/2011
Priority:NormalDue date:
Assignee:Nigel Kersten% Done:

0%

Category:-
Target version:-
Keywords: Affected URL:
Branch: Affected PE version:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the ENTERPRISE project on JIRA using the button below:


Description

Faces to the rescue.

History

#1 Updated by Nigel Kersten almost 3 years ago

  • Subject changed from ability to colate how many licenses are being used across multiple CA's to ability to collate how many licenses are being used across multiple CA's

#2 Updated by James Turnbull almost 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#3 Updated by Chad Metcalf almost 3 years ago

This would be helpful. We’ve got 4 puppet masters. One running in each of the 4 distinct locations we’ve got servers.

#4 Updated by Nigel Kersten almost 3 years ago

  • Status changed from Needs Decision to Accepted

We will definitely be doing this. I apologize for leaving it in “Needs Decision” so long.

Chad (or anyone else), would you find a solution like this acceptable?

  • Modify auth.conf so Puppet CAs can interrogate each other.
  • Add an option to puppet license to allow you to specify other CA servers.
  • puppet license then collates unique certnames across all the CA servers.

The problem we have now is that Puppet CAs have no concept of “where are the other CA servers if any?”, and I’m wondering whether a more manual approach would be an acceptable first pass at this functionality.

#5 Updated by Daniel Pittman almost 3 years ago

Modify auth.conf so Puppet CAs can interrogate each other. Add an option to puppet license to allow you to specify other CA servers. puppet license then collates unique certnames across all the CA servers.

Document that this needs to be a direct path to the CA server: if you have a load balancer in front of the machines, we need to slip past that to ensure we talk to all the back-ends, not the same one five times.

Also available in: Atom PDF