Attending 

  • Chris Hyzer, Penn, Chair
  • Chad Redmon, UNC
  •  Shilen Patel, Duke
  • JJ, Unicon
  • Drew Aschenbrener, Internet2
  • Emily Eisbruch, Internet2

DISCUSSION

  • Agenda bash

   

New Action Items from this call

AI Chris and Emily talk about wiki doc updates



Work Items

Vivek: not on this Grouper call

Shilen 

  • Subject Change Daemon
  • https://spaces.at.internet2.edu/display/Grouper/Subject+change+daemon
  • If subject data changes, could there be quicker way to update Grouper and provisioning data versus waiting for USDU to run once per day? 
  • Chris: Nothing updates sync table except provisioner
  • Some examples of sending messages to provisioner
  •     Need one for entity recalc
  • Shilen: update member table, where sync to provisioner, they should get entity recalc?
  • How fast is membership daemon running? 
  • Runs every minute
  • It resolves subjects and sends messages
  • It depends on the volume 
  • Column last edited field in config, 
  • Option to delete things you processed
  • Last edited thing, would help you get more recent things
  • If not deleting rows, when row gets inserted the column is null and put timestamp?
  • Chris: no , sync table has columns that keep track of things
  • Keep the table with last processed and you do things after that
  • Shilen can make the decisions
  • Wiki re udsu dependency
  • Might not have updates happening for a while
  • Shilen: Right now USDU does not ignore cache subjects
  • Does not go to the source
  • Shilen Will double check this
  • You have to wait a while
  • Skipping rows that are too old?
  • Wouldn’t care about things that happened prior to last USDU
  • So need to add a timestamp

  • JJ: tangential question: a client has a full sync job running, between time full sync starts and Grouer starts doing something a subject might disappear or change for some reason.  Then full sync fails.   Wondering does the daemon help fix the problem
  • Chris: might get one failure, but next incremental should fix it
  • JJ: If there is a subject error, could there be a flag to continue the provisioner? Now it just stops
  • Though not sure what version the client is on
  • AI Chris will open a ticket on this 
  • Chris thinking of implementing asynchronous full sync architecture , it would run at the same time as incremental , would send messages to recalc things.  Can handle the 30 minute window issue


Chris 

  • Worked on unit tests, every provisioning test works
  • Want to release new Grouper version  2.6.10
  • Scott C wants a fix for an issue
  • Worked on incremental memberships and entitlements, needed a fix
  • Making progress on object caching
  • Chris met w U Nebraska and U Michigan to get provisioners working
  • Chris will work on next Grouper release and then return to provisioning tasks
  • Chad did not update Grouper demo for the most recent Grouper release

JJ: issue with not shutting down; Want to use MVN test 

Chad

  • Updating doc on customizing the Grouper UI
  • Some of the info is very old and can be archived

  • Customising the Grouper UI

  • Org logo is in 2 places in GIT
  • Lang variable in URL - Chad will test this
  • In Slack there was a question about end date and membership in group, Chad created a JIRA
  • Logging issue , Shilen will handle

JJ:

  • Work needs to be done on the Grouper wiki doc
  • When you search for how do I set up an LDAP provisioner, you get old info
  • Will be helpful to tag pages as OLD INFO, only valid for version XX
  • Old grouper training videos should be tagged as old
  • JJ suggests having a jumpoff page for the various Grouper versions
  • Suggestion to add Confluence tags to pages for the pertinent version
  • AI Chris and Emily talk about wiki doc updates
  • See how many pages we have, go thru them, and mark them with a note about the version
  • JJ: be careful about deleting, maybe put a banner at top of page
  • Archived info comes up prominently in Confluence searches
  • Perhaps reorganize the release notes and jump off situation
  • Google 2.6 release notes because hard to find in confluence search
  • Quick Start versus quickstart can impact search
  • V2.6 or v  2.6 or v 2.6+
  • Suggestion to fully utilize maven and set up grouper as standard maven project
  • Checkstop is likely commented out
  • Unit tests, some tests disabled by default
  • Some of this info should be better documented in the README
  • Chad: These are more integration tests than unit tests
  • Integration tests take a long time to run
  • JJ reminds people to use Java 8
  • Coding standards wiki may have some old info
  • Need to add link to coding standards from  README 



Issue Roundup 


Jiras in past two weeks



Grouper Emails in recent weeks



Grouper wiki updates in past two weeks

Next Grouper Call: Wed July 20, 2022

  • No labels