PSP Moving Forward
Following on from the discussion on the July 3, 2013 Grouper Dev call and the July 29, 2014 Grouper call, this page captures thoughts about the future of the PSP and directions for provisioning strategy. General consensus:
- The PSP is weighted heavily towards trying to be all things to all people.
- Due of the above, it suffers horribly in the area of performance.
- Small, specially built modules focused on quickly and efficiently provisioning specific targets would be more useful to the community than a general solution until such time that a clear market direction emerges in the form of 90% of things speak (SPML/SCIM/Whatever-next-thing)
General Requirements
General requirements moving forward for these purpose built provisioners:
- Support incremental provisioning
- Support bulk reconciliation. Note: they may not be the same executable, but should retain and reuse code and configs where possible/practical.
- Each module should be capable of being run in parallel with other modules
- All provisioning modules will follow the Grouper configuration paradigms with properties overlays and expression language.
- Modules shall provision not based on a group's location in the grouper tree, but rather based on attributes indicating whether a group should be provisioned to various provisioners.
First Implementations
TBD