Hey Chris,

Thanks for port updates. Some of those values were temporary placeholders so 
thanks for the update. "etc" is fine to keep the evolution of deployments 
intact but as far as changing the way people have done things, I'm not sure 
that would happen as I don't know that a goal of RADiX is to have people update 
their existing configuration of there deployed systems. I'm going to update the 
overview of RADiX to touch on this. I'm also going to add some goals to the 
RADiX Wiki as there is stuff that Cameron and I have talked about that is not 
on there and it needs to be captured somewhere.

The rationale behind the change to "conf" versus "etc" was that many Java 
frameworks use a "conf" directory to capture configuration but I do feel your 
point on changing just for changing sake. If somehow this has changed your mind 
in favor of "conf" great, if not long live "etc".

tldr; back to "etc"

Thanks,
Paul

On May 18, 2011, at 6:59 PM, Mattmann, Chris A (388J) wrote:

> Oh, also I just updated the port #s and changed conf->etc. There's no reason 
> to change the way that folks have been deploying things and anything other 
> than that would be a change...
> 
> Cheers,
> Chris
> 
> On May 18, 2011, at 6:21 PM, Mattmann, Chris A (388J) wrote:
> 
>> Hi Paul,
>> 
>> met could be for either the crawler or for the curator.
>> 
>> As for failed_ingest_files, why the rename? Just to be shorter? I think 
>> failed_ingest_files, though more verbose, conveys more meaning than 
>> failure...
>> 
>> Cheers,
>> Chris
>> 
>> On May 18, 2011, at 7:50 AM, Ramirez, Paul M (388J) wrote:
>> 
>>> Hey Chris,
>>> 
>>> The met directory was for generated metadata by the crawler or was it for 
>>> the curator? I updated the page with a description of the paths and renamed 
>>> failed_ingest_files to failure. On the next pass I'll start posting a 
>>> description of the source structure that will be available as output from 
>>> the RADiX archetype. 
>>> 
>>> Thanks,
>>> Paul
>>> 
>>> On May 17, 2011, at 7:45 PM, Mattmann, Chris A (388J) wrote:
>>> 
>>>> Hey Guys,
>>>> 
>>>> FYI: https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT
>>>> 
>>>> I updated the page to propose a:
>>>> 
>>>> /data
>>>> /archive
>>>> /staging
>>>> /work
>>>> /met
>>>> /failed_ingest_files
>>>> 
>>>> Dir structure for RADIX to more closely match our existing OODT 
>>>> deployments.
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: [email protected]
>>>> WWW:   http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>> 
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: [email protected]
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 

Reply via email to