Actions
Architecture #1881
closed
Use a dynlist for nodeGroupId=hasPolicyServer-root
Status:
Rejected
Priority:
3
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
We have dynlist in OpenLDAP ( http://www.openldap.org/doc/admin24/overlays.html : 12.7. Dynamic Lists).
That would be much much more resilient and to use them in place of manually adding (and removing) a node at acceptation datetime.
The query could be based on the policyServerId attribute of nodes in accpeted inventories.
We have a special to manage for the root policy server itself, or relay server using it (and not in inventory).
Or we could add that information in Rudder nodes, as we thought to do (but then, we have to manage synchronisation between inventory data and rudderNode datas).
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 20 to Rudder
- Category set to Web - Nodes & inventories
Updated by Jonathan CLARKE over 9 years ago
- Tracker changed from User story to Architecture
Updated by François ARMAND over 4 years ago
- Status changed from New to Rejected
I think we never had a problem on that specific case. Closing that one.
Actions