[kepler-dev] proposed changes to .kepler

[ben leinfelder]

A few questions:
1) What other files in .kepler will be considered "persistent"
2) What is the plan for different versions of Kepler running with the  
same .kepler?
	a) do we have another directory branch for each version:
	~/.kepler/kepler-2.0/...
	~/.kepler/kepler-2.1/...
3) When thinking about multiple instances of Kepler on one machine are  
we aiming to support:
	a) different versions being run at different times
	b) the same version being run concurrently
	c) different versions being run concurrently

Depending on what we support, we'll have to revisit the embedded  
HSQLDB that is used for the cache and provenance in addition to these  
directory structures.

-ben

On Nov 18, 2009, at 2:08 PM, Derik Barseghian wrote:

> Kepler devs,
>
> After some discussion with Aaron, Ben, Dan, and Chad, I'm wondering  
> if anyone objects to dividing .kepler into two different areas --  
> there would be areas for 1) persistent items (e.g. provenance  
> database) and 2) temporary items (e.g. cache). This would make it  
> more apparent which things could be deleted without serious  
> ramification (temp/), and the idea would be items in peristent/  
> should stick around and be dealt with during kepler upgrades for  
> backwards compatibility.
>
> Also, I think we should utilize the InstanceAuthNamespace in these  
> paths, so that items from different Kepler instances are separated.
>
> This could look like (imagine multiple namespace dirs):
>
> a)
> .kepler/perisistent/gamma.msi.ucsb.edu.OpenAuth.1278/
> .kepler/temp/gamma.msi.ucsb.edu.OpenAuth.1278/
>
> or b)
> .kepler/gamma.msi.ucsb.edu.OpenAuth.1278/persistent/
> .kepler/gamma.msi.ucsb.edu.OpenAuth.1278/temp/
>
> or c)
> .kepler_temp/gamma.msi.ucsb.edu.OpenAuth.1278/
> .kepler_persistent/gamma.msi.ucsb.edu.OpenAuth.1278/
>
> I prefer a).
>
> This partly came out of a discussion of bug 4514. I think the  
> configuration files could be stored beneath these new paths,  
> probably in persistent.
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4514
>
> A better solution might be to just have a .kepler to store temporary  
> things, and to store persistent items in an OS-appropriate location,  
> but I think this might be a larger change than we want to take on at  
> the moment, as we try to get 2.0 out of the door.
>
> Let me know what you think,
> Derik
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev