The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
ability to collate how many licenses are being used across multiple CA's
|Assignee:||Nigel Kersten||% Done:|
|Branch:||Affected PE version:|
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:
Faces to the rescue.
#4 Updated by Nigel Kersten over 2 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 licenseto allow you to specify other CA servers.
puppet licensethen 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 over 2 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.