Skip to Content.
Sympa Menu

grouper-dev - [grouper-dev] Draft Minutes: Grouper call of Oct 8, 2014

Subject: Grouper Developers Forum

List archive

[grouper-dev] Draft Minutes: Grouper call of Oct 8, 2014


Chronological Thread 
  • From: Emily Eisbruch <>
  • To: "" <>
  • Subject: [grouper-dev] Draft Minutes: Grouper call of Oct 8, 2014
  • Date: Mon, 20 Oct 2014 21:09:21 +0000
  • Accept-language: en-US

Draft Minutes: Grouper call of Oct. 8, 2014

Attending:

Tom Barton, University of Chicago
Chris Hyzer, University of Pennsylvania
Jim Fox, University of Washington
Shilen Patel, Duke
Emily Eisbruch, Internet2, scribe

New Action Items

[AI] (Shilen) email Chris the  scripts associated w each DDL version

[AI] (Jim) write up thoughts on API, messaging for provisioing for the Grouper roadmap

[AI] (Emily) do some analysis on which campuses we might ask to add to their current contribution or start a new page summarizing how they use Grouper.

[AI] (Emily) touch base with Gail about leading the implementation feedback discussion

Carry Over Action Items

[AI] (Shilen) create a JIRA to add a subject identifier to the members table so it will be available for the messaging system and for the loader

[AI] (Tom) follow up on Pen testing of Grouper 2.2

[AI] (Shilen) create a Grouper training video on the new Grouper

[AI) (DaveL) look at PSP ChangeLogDataConnector Inconsistency issue

[AI] (Shilen) investigate ways to get new attributes in a single step

DISCUSSION

Grouper v2.2.1 status

Currently, it can be time-consuming to upgrade to Grouper 2.2
To address this, Chris is working on getting the Grouper installer to handle the upgrade steps.

Once this upgrade work is complete
- the admin will specify the directory where the installation is on the server
-The installer will download the needed components, unzip and build them
-merge in the config files that the site needs, keeping the previously configured settings
-copy over the libraries
 -optionally upgrade the database

 -Everything that is replaced will be put in a temp install directory and preserved there
-Scripts will provide a status during the upgrade.  This is important so the user does not think the process quit.

-Going through the database and migrating can be the time consuming process.
-This is site-specific and it's hard to know before starting how long it will take.

For upgrading from Grouper 2.2.0 to 2.2.1, there is a need for the script that handles "GrouperAll"
https://bugs.internet2.edu/jira/browse/GRP-1047
However, most of the steps for handling GrouperALL can be done while Grouper  is running, so no need to have much down time for this

Chris: as we go from different database versions need a script to handle the DDL.
-As the upgrader runs, the user can see it going from version to version in Grouper DDL. Then it kicks off the GSH scripts.

[AI] (Shilen) email Chris the  scripts associated w each DDL version

Other issues prior to release of Grouper 2.2.1

Issue on the Grouper-Users list from Yoann – Shilen will look into this

Need to change the build scripts to work with GIT, rathern than SVN
Chris will look into this

*** Goal is to release Grouper 2.2.1 prior to the Technology Exchange if possible


Grouper Working Gropu at Technology Exchange in Indianapolis
Wed Oct. 29, 2014 at 5:30pm 

* Grouper version 2.2.1 update (Chris)
* Community contributions - (Chris)
*       -spark conversation on what people are doing at their site
*      - maybe get one or two instances where there is community interest
*      - constructive statements on what would make a contribution successful
*               -supportability
*               -suggest a design beforehand on the list
*               -make use of an API, so components can be more swappable
*               -example of a previous contribution: ESB connector work from Bristol

* Grouper v2.2 implementation feedback (Gail)

* Provisioning discussion - strategy for Grouper v2.3 and potential partners (Dave)

*Roadmap (Tom)
*Topics from the Audience


[AI] (Emily) touch base with Gail about leading the implementation feedback discussion

Provisioning approach for v2.3


Current decisions are to focus first on 
Grouper to AD
Grouper to LDAP

Univ Washington has  a different approach to what goes in a message
[AI] (Jim) write up thoughts on API, messaging for provisioing for the Grouper roadmap
 
Community Contributions section of wiki
https://spaces.internet2.edu/display/Grouper/Community+Contributions

How to motivate campuses to do a community contribution and share their Grouper story?

[AI] (Emily) do some analysis on which campuses we might ask to add to their current contribution or start a new page summarizing how they use Grouper.


Next Grouper call: Wed. Oct. 22, at noon ET





Emily Eisbruch, Technology Transfer Analyst
Internet2
office: +1-734-352-4996 | mobile +1-734-730-5749




  • [grouper-dev] Draft Minutes: Grouper call of Oct 8, 2014, Emily Eisbruch, 10/20/2014

Archive powered by MHonArc 2.6.16.

Top of Page