[kepler-dev] [Bug 4578] tracking bug for changes to .kepler

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4578

Derik Barseghian <barseghian at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aschultz at nceas.ucsb.edu

--- Comment #3 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2010-02-05 13:58:47 PST ---
We've now got KeplerData with module dirs for persistent data, and .kepler for
temporary data. 

Chad recently added a versionMarker.txt to .kepler. I'm thinking we should
probably put similar files in all the modules dirs in KeplerData so that during
the install of a future post 2.0 Kepler we can easily id and upgrade data as
needed. Sound ok?

I think Chad did some work to upgrade existing 1.0 .kepler to 2.0, but not
everything can be safely upgraded. So we have a problem: .kepler can no longer
be deleted at will, since the user may still have 1.0 data that they wish to
use in with 1.0. Since kepler 1.0 is hardcoded to look for .kepler, we can't
move the data into KeplerData. Maybe a solution is to create .kepler2 for use
by 2.0 and beyond. Then we know .kepler2 can always safely be deleted, but
.kepler should be left alone.

We no longer use the AuthorizedNamespace as part of the directory structures in
KeplerData. This file resides in KeplerData/core/. So this file serves as a
unique identifier for a KeplerData dir, not for a Kepler instance. Multiple
instances of Kepler running on the same machine connect to the same databases
and KeplerData dir, and use this same namespace. Did we decided we're OK with
this?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.