[gram-user] questions about GRAM audit

[Tom Scavo]

On Wed, Apr 29, 2009 at 11:43 AM, Martin Feller <feller at mcs.anl.gov> wrote:
> Tom Scavo wrote:
>>
>> Looking at the differences between 4.0.8 and 4.0.9 more closely, it
>> seems the changes constitute an API change (but maybe my definition of
>> "API change" is faulty).  I thought API changes between minor point
>> revisions were forbidden (by policy)?
>
> I never really thought about the audit logging feature as being an API.
> This might be a wrong perception though, with respect to what you are trying
> to do.
> Can you point me to the specific change you mean?

Sure, I'm referring to the JNDI config differences between 4.0.9 and pre-4.0.9:

http://www.globus.org/toolkit/docs/4.0/execution/wsgram/WS_GRAM_Audit_Logging.html

I don't know if that's covered by policy.  My guess is that it is.

>> Hmm, why does the PostgreSQL schema document have "8.0" in its name?
>>
>
> I/We don't know why it has 8.0 in it, but my guess is that Peter named it
> so because he tested it with PostgreSQL 8.0.

That goes back a ways, which probably means that GRAM audit has not
been tested with pre-8.0, at least not lately.  Okay, that's good to
know.

>> gram_audit_schema_postgres-8.0.sql
>>
>> Has this schema been tested with pre-8.0 versions of PostgreSQL?  The
>> reason I ask is that I know of at least one TeraGrid resource provider
>> that is running 7.2 and wondering whether or not he should upgrade.
>
> I only tested it with PostgreSQL 8.x. But the table definition looks pretty
> basic, all used datatypes are supported in 7.2, according to
> http://www.postgresql.org/docs/7.2/static/datatype.html

Yes, that was my initial reaction as well.

> So I *think* it should also work with 7.2, but i didn't explicitly try it.
> Can you try it with your 7.2 DB? If you run into problems we'd be willing
> to help.

The NCSA folks already have 7.2 running in test, with no
version-related issues AFAIK.  The question has come up whether we
should upgrade, however.  As we all know, "if it isn't broke, don't
fix it", so we thought we'd ask here first before we did anything.

On the other hand, testing is one thing, while production is another.
I'd be inclined to recommend 8.x in production simply because of the
development history you reported above.  Thanks for helping me arrive
at that conclusion.

Tom