Grouper Developers Forum

["GW Brown, Information Systems and Computing" <>]

Comments below.

Gary

--On 15 September 2008 16:05 -0500 Tom Zeller 
<>
 wrote:

> Please see my votes inline.
>
>
> TomZ
>
>
>
> On Sun, Sep 14, 2008 at 10:41 PM, Chris Hyzer 
> <>
> wrote:
>
>
>
>
> My proposal for a binary build is:
>
>
>
> Gzip file: grouper.1.4.tar.gz:
OK
> /lib/grouper: all jars that grouper needs, including grouper.jar
OK
> /lib/jdbcSamples: some drivers that the user can choose from? e.g. the
> ones we test with.  Note, the user can use these or get their own,
> explained in readme
OK

We should probably have a /lib/custom or similar as a placeholder for site 
specific JARS which always get added to the classpath
> Nice. That would save me a step. Mabye we could include
> grouper.hibernate.properties and sources.xml snippets for the various
> drivers as well (having forgotten one or the other more than once).
>
>
>
>
>
> /conf: all resources and all config example files, and the same files
> with the real name.  So there would be grouper.example.properties ==
> grouper.properties
OK
> /bin: all the example scripts, and the non-examples ones: gsh.example.bat
> == gsh.bat (note, all line endings need to be right? note, permissions
> might not be right [e.g. executable in unix], should be in readme).
OK
> /ext: any extensions (note, currently there are none to bundle in? should
> we include this or wait until there are extensions?  )
>
>
> Seems silly to include an empty directory, but I suggest keeping it for
> any grouper-extension-lurkers.
Agreed.

BTW getting an extension to work always involved first running an ant task 
- how would someone build their extension now - or can't they using a 
binary dist?
> Should we package javadoc or other docs (or keep in cvs?)
>
>
> I think web-based documentation is fine, so a link to the wiki seems
> sufficient.
Actually I think it is normal practice - and useful to include the javadoc
> Should logs go to base dir, or should we auto-create dirs for logs and
> keep in /logs dir?
>
>
> I like the logs directory rather than base dir, since if the binary
> grouper release is included in another project there might not be a
> grouper base dir.
logs is better
> Anything else?
For things like log dirs we can consider using environment variables - 
which get turned into system properties. Tomcat scripts choose sensible 
defaults but let you override / add values through setenv.sh. We could use 
this to allow users to set different JVM args i.e. memory usage, profiler 
agents, debugging

> Thanks,
>
> Chris
>
>
>
>
>
>
>
> From: Emily Eisbruch 
> [mailto:]
> Sent: Friday, September 05, 2008 9:16 AM
> To: Grouper Dev
> Subject: [grouper-dev] Draft minutes: Grouper Call 3-Sep-08
>
>
>
> **Grouper Call 3-Sep-08**
>
>  *Attending*
>
> Tom Barton, Chair
>
> Gary Brown, Bristol U.
>
> Shilen Patel, Duke
>
> Chris Hyzer, U. Penn
>
> Bill Kasenchar, U. Penn
>
> Tom Zeller, U. Memphis
>
> Dave Donnelly, Stanford
>
> Joy Veronneau, Cornell U.
>
> RL "Bob" Morgan, U. Washington
>
> Steve Olshansky, Internet2
>
> Emily Eisbruch, Internet2 (scribe)
>
>
>
> New Action Items
>
> [AI] {Chris} will make the encrypted password function external to
> Grouper.
>
> [AI] {TomZ} will create a JIRA issue summarizing today's discussion on
> handling of utilities by gsh.
>
>  Carry Over Action Items
>
> [AI] {Chris} will create a proposal for using a shell script to make
> binaries.
>
> [AI] {Chris} will develop guidelines for standardizing build script
> procedures across the I2 middleware products.
>
> [AI] {Kathryn} will do background research on a messaging system to be
> used as a test/example case for hooks.
>
> Discussion
>
> Grouper Release 1.3.1.
>
> Grouper Release 1.3.1 is ready for final testing and packaging, with all
> JIRA items having been marked completed. Chris will test web services;
> Chris, TomZ, and Shilen will do unit testing. Chris will tag the code for
> the 1.3.1 release in CVS and inform TomB.
>
> Binary Format for Grouper 1.4
>
> Binary format will be considered for Grouper 1.4, not for this 1.3.1
> release.
>
> https://mail.internet2.edu/wws/arc/grouper-dev/2008-08/msg00058.html
>
> Documentation for 1.3.1
>
> Shilen welcomes feedback on his Bad Membership Finder utility
> documentation at:
> https://wiki.internet2.edu/confluence/display/GrouperWG/Bad+Membership+Fi
> nder+Utility
>
> Gary will edit the documentation on the Grouper wiki for API
> configuration changes in Grouper 1.3.1.
>
> Encrypting passwords in config files
>
> (https://bugs.internet2.edu/jira/browse/GRP-122)
>
> Encrypting passwords in config files was deferred, to be reconsidered
> along with the release of Subject 1.0. This deferral decision was based
> on concern about creating a need for Grouper customized versions of 3rd
> party source, such as JDBC source files.  However, it makes sense now to
> proceed with putting encrypted passwords in a separate JAR.
>
> [AI] {Chris} will make the encrypted password function external to
> Grouper.
>
> Indexes
>
> What are the potential impacts of cleaning up and removing some indexes,
> as suggested in GRP-146?
>
> https://bugs.internet2.edu/jira/browse/GRP-146
>
> https://mail.internet2.edu/wws/arc/grouper-dev/2008-09/msg00013.html
>
> There is a risk that indexes that we consider redundant are not actually
> redundant in all cases. Making some indexes optional through a
> configuration file was discussed. There is a need to understand how
> various databases use indexes. The decision was not to make changes to
> indexes for 1.4.  Soon after 1.4, it might make sense to develop
> test/benchmark databases to be able to make a future determination on
> this issue.
>
> Packaging of Utilities
>
> The consensus was to use gsh for storing utilities.
>
> Utilities for 1.4 will include those needed to replace Apache Ant (Scheme
> export, run test, export import, XML, etc.), Bad Membership Finder, and
> more.
>
> TomB noted it will be important to maintain a wiki page or interactive,
> built-in help so people know what utilities are in gsh.
>
> [AI] {TomZ} will create a JIRA issue summarizing today's discussion on
> handling of utilities by gsh.
>
> Next call: Wed 17-Sep-08 Noon EDT.



----------------------
GW Brown, Information Systems and Computing