...
Next Action Items from this call
- Chris - create wiki about provisioning error codes and explain what they are
- Chad - update wiki for new SCIM provisioner
- Chad - add flag to enable SCIM provisioner and default it to TRUE
...
- Met with community members from Harvard, Illinois State
- walked them through the provisioner
- It will be important to provide support to the community
- Getting better ideas for documentation
- Grouper 2.6.16 is working well
- Grouper 2.6.17 will have new Azure work, and an improvements on selecting
- Have test case for Azure, should have test case for all the provisioners
- Hope to release 2.6.17 within a few days
- Chad notes that he has been supporting community members provisioning to Azure with Grouper v2.6.16 and there have been questions.
- AI Chris create wiki about provisioning error codes and explain what they are
- Carey: have a group in Grouper for people who did not make it in provisioning?
- Chris will think about this. Maybe have provisioning screen easy view. Now you can go to activity log in UI. But will try to make it easier, on membership screen
- Some would expect to see this on the provisioning screen
- In Grouper 2.7
- See Roadmap
- we want a pared down container
- To improve performance
- Start using new DDL strategy
- New integer primary key
- Dictionary table
- Go thru existing tables and add new columns
- Migration to Grouper 3.0 with changing tables
- Changing from Guids (40 chars) to integer IDs (8 bytes or 22 bytes) will be helpful.
- Will have a storage, network and memory benefit
- Less indexes
- Need on groups, members, maybe on stems
- Then build new system with ideal more database design
- Issues:
- Concern for how difficult it might be to do the upgrade for a current deployer
- Custom queries may need to be upgraded
- Loader jobs that depend on Grouper tables will need to be upgraded
...