from:"BW"

Yeah, killed PID’s for Java.  Clean restart. Filemgr shows up, workflow,
resource, crawler down all down.

On Sat, Apr 7, 2018 at 4:19 PM Chris Mattmann <mattm...@apache.org> wrote:

> Need to make sure that all java is off, PID files aren’t there for a clean
> restart
> then ./bin/oodt start.
>
>
>
> Should work fine.
>
>
>
>
>
>
>
> From: BW <bw...@mysoftcloud.com>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Date: Saturday, April 7, 2018 at 1:55 PM
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Subject: Re: OODT start
>
>
>
> vim oodt.out
>
>
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
>
> found. Is File Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> ID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
>
> found with PID 3795 but no matching process was found. Removed
>
> /Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid, now
>
> FileManager can be started.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> On Sat, Apr 7, 2018 at 1:29 PM, Chris Mattmann <mattm...@apache.org>
> wrote:
>
> Suggestion: ./bin/oodt stop
>
>
>
> Confirm that ps aux | grep java returns nothing (you may need to wait a
> few seconds)
>
> Then, ./bin/oodt start
>
>
>
> What is in the output of logs/oodt.out ?
>
>
>
>
>
>
>
> Cheers,
>
>
>
> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: BW <bw...@mysoftcloud.com>
>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
> Date: Saturday, April 7, 2018 at 1:23 PM
>
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
> Subject: Re: OODT start
>
>
>
>
>
>
>
> Well, shut down odor, restarted.   filemgr resource shows up, other
>
>
>
> mangers down.
>
>
>
>
>
>
>
> ps aux |grep jav

Re: OODT start

vim oodt.out

PID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
found. Is File Manager still running? Start aborted.

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found. Is Resource Manager still running? Start aborted.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found. Is Workflow Manager still running? Start aborted.

Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp

Using JRE_HOME:
/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home

ID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
found with PID 3795 but no matching process was found. Removed
/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid, now
FileManager can be started.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found but no matching process was found. Stop aborted.

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found but no matching process was found. Stop aborted.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found. Is Workflow Manager still running? Start aborted.

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found. Is Resource Manager still running? Start aborted.

Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp

Using JRE_HOME:
/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found but no matching process was found. Stop aborted.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found but no matching process was found. Stop aborted.

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found. Is Resource Manager still running? Start aborted.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found. Is Workflow Manager still running? Start aborted.

Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat

Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp

Using JRE_HOME:
/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home

PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
found but no matching process was found. Stop aborted.

PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
found but no matching process was found. Stop aborted.

On Sat, Apr 7, 2018 at 1:29 PM, Chris Mattmann <mattm...@apache.org> wrote:
> Suggestion: ./bin/oodt stop
>
> Confirm that ps aux | grep java returns nothing (you may need to wait a few 
> seconds)
> Then, ./bin/oodt start
>
> What is in the output of logs/oodt.out ?
>
>
>
> Cheers,
>
> Chris
>
>
>
>
>
>
>
> From: BW <bw...@mysoftcloud.com>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Date: Saturday, April 7, 2018 at 1:23 PM
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Subject: Re: OODT start
>
>
>
> Well, shut down odor, restarted.   filemgr resource shows up, other
>
> mangers down.
>
>
>
> ps aux |grep java
>
>
>
> bw   4168   0.3  2.1  8433916 348536 s000  S12:50PM
>
> 0:19.47 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
>
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>
> -Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/tomcat/conf/logging.properties
>
> -Djava.endorsed.dirs=/Users/bw/dev/workspace/oodt/tomcat/common/endorsed
>
> -classpath 
> :/Users/bw/dev/workspace/oodt/tomcat/bin/bootstrap.jar:/Users/bw/dev/workspace/oodt/tomcat/bin/commons-logging-api.jar
>
> -Dcatalina.base=/Users/bw/dev/workspace/oodt/tomcat
>
> -Dcatalina.home=/Users/bw/dev/workspace/oodt/tomcat
>
> -Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/tomcat/temp
>
> org.apache.catalina.startup.Bootstrap start start
>
>
>
> bw   4175   0.1  0.6  8273820 105576 s000  S12:50PM
>
> 0:03.66 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
>
> -Djava.ext.dirs=/Users/bw/dev/workspace/oodt/filemgr/lib
>
> -Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/filemgr/etc/logging.properties
>
> -Dorg.apache.oodt.cas.filemgr.properties=/Users/bw/dev/workspace/oodt/filemgr/etc/filemgr.properties
>
> -Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/temp
>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum 9000
>
>
>
> bw   3893   0.1  0.3  8229892  47624 s000  S12:29PM
>
> 0:04.3

Re: OODT start

Well, shut down odor, restarted.   filemgr resource shows up, other
mangers down.

ps aux |grep java

bw   4168   0.3  2.1  8433916 348536 s000  S12:50PM
0:19.47 /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/tomcat/conf/logging.properties
-Djava.endorsed.dirs=/Users/bw/dev/workspace/oodt/tomcat/common/endorsed
-classpath 
:/Users/bw/dev/workspace/oodt/tomcat/bin/bootstrap.jar:/Users/bw/dev/workspace/oodt/tomcat/bin/commons-logging-api.jar
-Dcatalina.base=/Users/bw/dev/workspace/oodt/tomcat
-Dcatalina.home=/Users/bw/dev/workspace/oodt/tomcat
-Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/tomcat/temp
org.apache.catalina.startup.Bootstrap start start

bw   4175   0.1  0.6  8273820 105576 s000  S12:50PM
0:03.66 /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
-Djava.ext.dirs=/Users/bw/dev/workspace/oodt/filemgr/lib
-Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/filemgr/etc/logging.properties
-Dorg.apache.oodt.cas.filemgr.properties=/Users/bw/dev/workspace/oodt/filemgr/etc/filemgr.properties
-Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/temp
org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum 9000

bw   3893   0.1  0.3  8229892  47624 s000  S12:29PM
0:04.39 /usr/bin/java -Djava.ext.dirs=../lib
org.apache.oodt.cas.resource.system.extern.XmlRpcBatchStub
-Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode=true
-Dorg.apache.oodt.cas.pge.task.status.legacyMode=true --portNum 2001

bw   4202   0.0  0.0  2432804   1988 s000  S+1:21PM
0:00.00 grep java

Webbs-MacBook-Pro-2:bin bw$


On Sat, Apr 7, 2018 at 1:03 PM, Chris Mattmann <mattm...@apache.org> wrote:
> What are the results of ps aux | grep filemgr
>
> Or ps aux | grep java?
>
>
>
>
>
>
>
> From: BW <w...@apache.org>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Date: Saturday, April 7, 2018 at 12:58 PM
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Subject: Re: OODT start
>
>
>
> Using https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT.
>
> Is that up to date?
>
>
>
> On Sat, Apr 7, 2018 at 12:38 PM, BW <w...@apache.org> wrote:
>
> Opened http://localhost:8080/opsui/status/ which shows Managers are
>
> down.  Thoughts?
>
>
>
> On Sat, Apr 7, 2018 at 12:25 PM, BW <w...@apache.org> wrote:
>
> Ok. Figured it out.  Had to set in profile.
>
>
>
>   echo "export JAVA_HOME=`/usr/libexec/java_home`" >> ~/.profile
>
>
>
> Webbs-MacBook-Pro-2:bin bw$ . ~/.profile
>
>
>
> Looks good.
>
>
>
> On Sat, Apr 7, 2018 at 11:44 AM, BW <w...@apache.org> wrote:
>
> Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
>
> is set; when they are set in etc/profile and echo's correctly.
>
> Confused.
>
>
>
> On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattm...@apache.org> wrote:
>
> Got it.
>
>
>
>
>
>
>
> I think that you should killall java, then make sure PID files are removed 
> from */run (e.g., filemgr, workflow and resmgr).
>
>
>
>
>
>
>
> Then try restarting.
>
>
>
>
>
>
>
> Cheers,
>
>
>
> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: BW <w...@apache.org>
>
> Reply-To: <dev@oodt.apache.org>
>
> Date: Saturday, April 7, 2018 at 10:56 AM
>
> To: <dev@oodt.apache.org>
>
> Subject: Re: OODT start
>
>
>
>
>
>
>
> Ok. I had lower case.  Should of been "../Contents/Home"
>
>
>
> Now though File/Resource/Workflow managers fail to start.  Nothing in browser.
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
>
>
>
> After mvn install:
>
>
>
> "
>
>
>
> ./bin/oodt start
>
>
>
>
>
>
>
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>
>
>
>
>
>
>
> At least one of these environment variable is needed to run this program
>
>
>
>
>
>
>
> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>
>
>
>
>
>
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>
>
>
>
>
>
>
> Any ideas, anybody?
>
>
>
>
>
>
>
> Thanks. -BW
>
>
>
>
>
>
>
>
>

Re: OODT start

Using https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT.
Is that up to date?

On Sat, Apr 7, 2018 at 12:38 PM, BW <w...@apache.org> wrote:
> Opened http://localhost:8080/opsui/status/ which shows Managers are
> down.  Thoughts?
>
> On Sat, Apr 7, 2018 at 12:25 PM, BW <w...@apache.org> wrote:
>> Ok. Figured it out.  Had to set in profile.
>>
>>  echo "export JAVA_HOME=`/usr/libexec/java_home`" >> ~/.profile
>>
>> Webbs-MacBook-Pro-2:bin bw$ . ~/.profile
>>
>> Looks good.
>>
>> On Sat, Apr 7, 2018 at 11:44 AM, BW <w...@apache.org> wrote:
>>> Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
>>> is set; when they are set in etc/profile and echo's correctly.
>>> Confused.
>>>
>>> On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattm...@apache.org> wrote:
>>>> Got it.
>>>>
>>>>
>>>>
>>>> I think that you should killall java, then make sure PID files are removed 
>>>> from */run (e.g., filemgr, workflow and resmgr).
>>>>
>>>>
>>>>
>>>> Then try restarting.
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Chris
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: BW <w...@apache.org>
>>>> Reply-To: <dev@oodt.apache.org>
>>>> Date: Saturday, April 7, 2018 at 10:56 AM
>>>> To: <dev@oodt.apache.org>
>>>> Subject: Re: OODT start
>>>>
>>>>
>>>>
>>>> Ok. I had lower case.  Should of been "../Contents/Home"
>>>>
>>>> Now though File/Resource/Workflow managers fail to start.  Nothing in 
>>>> browser.
>>>>
>>>>
>>>>
>>>> On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
>>>>
>>>> After mvn install:
>>>>
>>>> "
>>>>
>>>> ./bin/oodt start
>>>>
>>>>
>>>>
>>>> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>>>>
>>>>
>>>>
>>>> At least one of these environment variable is needed to run this program
>>>>
>>>>
>>>>
>>>> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>>>>
>>>>
>>>>
>>>> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>>>>
>>>>
>>>>
>>>> Any ideas, anybody?
>>>>
>>>>
>>>>
>>>> Thanks. -BW
>>>>
>>>>
>>>>

Re: OODT start

Opened http://localhost:8080/opsui/status/ which shows Managers are
down.  Thoughts?

On Sat, Apr 7, 2018 at 12:25 PM, BW <w...@apache.org> wrote:
> Ok. Figured it out.  Had to set in profile.
>
>  echo "export JAVA_HOME=`/usr/libexec/java_home`" >> ~/.profile
>
> Webbs-MacBook-Pro-2:bin bw$ . ~/.profile
>
> Looks good.
>
> On Sat, Apr 7, 2018 at 11:44 AM, BW <w...@apache.org> wrote:
>> Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
>> is set; when they are set in etc/profile and echo's correctly.
>> Confused.
>>
>> On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattm...@apache.org> wrote:
>>> Got it.
>>>
>>>
>>>
>>> I think that you should killall java, then make sure PID files are removed 
>>> from */run (e.g., filemgr, workflow and resmgr).
>>>
>>>
>>>
>>> Then try restarting.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Chris
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: BW <w...@apache.org>
>>> Reply-To: <dev@oodt.apache.org>
>>> Date: Saturday, April 7, 2018 at 10:56 AM
>>> To: <dev@oodt.apache.org>
>>> Subject: Re: OODT start
>>>
>>>
>>>
>>> Ok. I had lower case.  Should of been "../Contents/Home"
>>>
>>> Now though File/Resource/Workflow managers fail to start.  Nothing in 
>>> browser.
>>>
>>>
>>>
>>> On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
>>>
>>> After mvn install:
>>>
>>> "
>>>
>>> ./bin/oodt start
>>>
>>>
>>>
>>> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>>>
>>>
>>>
>>> At least one of these environment variable is needed to run this program
>>>
>>>
>>>
>>> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>>>
>>>
>>>
>>> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>>>
>>>
>>>
>>> Any ideas, anybody?
>>>
>>>
>>>
>>> Thanks. -BW
>>>
>>>
>>>

Re: OODT start

Ok. Figured it out.  Had to set in profile.

 echo "export JAVA_HOME=`/usr/libexec/java_home`" >> ~/.profile

Webbs-MacBook-Pro-2:bin bw$ . ~/.profile

Looks good.

On Sat, Apr 7, 2018 at 11:44 AM, BW <w...@apache.org> wrote:
> Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
> is set; when they are set in etc/profile and echo's correctly.
> Confused.
>
> On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattm...@apache.org> wrote:
>> Got it.
>>
>>
>>
>> I think that you should killall java, then make sure PID files are removed 
>> from */run (e.g., filemgr, workflow and resmgr).
>>
>>
>>
>> Then try restarting.
>>
>>
>>
>> Cheers,
>>
>> Chris
>>
>>
>>
>>
>>
>>
>>
>> From: BW <w...@apache.org>
>> Reply-To: <dev@oodt.apache.org>
>> Date: Saturday, April 7, 2018 at 10:56 AM
>> To: <dev@oodt.apache.org>
>> Subject: Re: OODT start
>>
>>
>>
>> Ok. I had lower case.  Should of been "../Contents/Home"
>>
>> Now though File/Resource/Workflow managers fail to start.  Nothing in 
>> browser.
>>
>>
>>
>> On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
>>
>> After mvn install:
>>
>> "
>>
>> ./bin/oodt start
>>
>>
>>
>> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>>
>>
>>
>> At least one of these environment variable is needed to run this program
>>
>>
>>
>> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>>
>>
>>
>> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>>
>>
>>
>> Any ideas, anybody?
>>
>>
>>
>> Thanks. -BW
>>
>>
>>

Re: OODT start

Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
is set; when they are set in etc/profile and echo's correctly.
Confused.

On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattm...@apache.org> wrote:
> Got it.
>
>
>
> I think that you should killall java, then make sure PID files are removed 
> from */run (e.g., filemgr, workflow and resmgr).
>
>
>
> Then try restarting.
>
>
>
> Cheers,
>
> Chris
>
>
>
>
>
>
>
> From: BW <w...@apache.org>
> Reply-To: <dev@oodt.apache.org>
> Date: Saturday, April 7, 2018 at 10:56 AM
> To: <dev@oodt.apache.org>
> Subject: Re: OODT start
>
>
>
> Ok. I had lower case.  Should of been "../Contents/Home"
>
> Now though File/Resource/Workflow managers fail to start.  Nothing in browser.
>
>
>
> On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
>
> After mvn install:
>
> "
>
> ./bin/oodt start
>
>
>
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>
>
>
> At least one of these environment variable is needed to run this program
>
>
>
> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>
>
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>
>
>
> Any ideas, anybody?
>
>
>
> Thanks. -BW
>
>
>

Re: OODT start

Ok. I had lower case.  Should of been "../Contents/Home"
Now though File/Resource/Workflow managers fail to start.  Nothing in browser.

On Sat, Apr 7, 2018 at 10:27 AM, BW <w...@apache.org> wrote:
> After mvn install:
> "
> ./bin/oodt start
>
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>
> At least one of these environment variable is needed to run this program
>
> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>
> Any ideas, anybody?
>
> Thanks. -BW

Re: [VOTE] Apache OODT 1.2.1 release candidate #1

2017-12-20 Thread BW

https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/

On Wed, Dec 20, 2017 at 9:15 AM Chris Mattmann  wrote:

> Thanks Sean, appreciate it. Do you know the magic command to do that
> revocation? (
>
>
>
> On 12/20/17, 9:14 AM, "Sean Kelly"  wrote:
>
> Chris:
>
> This time I get:
>
> gpg: Good signature from "Chris Mattmann "
>
> So I am now +1 to release!
>
> Thanks Chris!
> --k
>
> PS: You might want to revoke your two older keys and make FD01FEDB the
> go-to.
>
>
> Chris Mattmann wrote:
> > Can you try now – I updated with the KEYS file from Master that has
> my new KEY. For whatever
> > reason it didn’t make it into the tag, which I think is fine, since
> master always has the latest
> > and greatest.
> >
> >
> >
> > On 12/20/17, 8:58 AM, "Sean Kelly"  wrote:
> >
> >  Thanks Chris!
> >
> >  I imported the KEYS but I still get
> >
> >   gpg: Can't check signature: No public key
> >
> >  Is it possible you signed this with a newly generated key
> that's not in
> >  the KEYS file?
> >
> >  --k
> >
> >  Chris Mattmann wrote:
> >  >  KEYS file added! ( do I have your +1? (
> >  >
> >  >
> >  >
> >  >  On 12/20/17, 8:38 AM, "Sean Kelly"
>  wrote:
> >  >
> >  >   Strangely this (and the release announcement) ended up
> in my spam folder.
> >  >
> >  >   Here goes:
> >  >
> >  >   MD5: ✓
> >  >   SHA1: ✓
> >  >   Python tests: ✓
> >  >   Java tests: ✓
> >  >   Signature: gpg: Can't check signature: No public key
> >  >
> >  >   Don't we also put a convenience copy of the KEYS file
> in the release dir?
> >  >
> >  >   Take care
> >  >   --k
> >  >   >   Chris Mattmann
> >  >   >   2017-12-19 at 8.50 p
> >  >   >   Ping (
> >  >   >
> >  >   >   Can I get 2 more VOTEs here so I can push this
> release out? It’s kind
> >  >   >   of needed for DRAT.
> >  >   >   We can release a 1.2.2 with Tom’s patch later, but
> would really love
> >  >   >   to release this. Thanks.
> >  >   >
> >  >   >   Cheers,
> >  >   >   Chris
> >  >   >
> >  >   >
> >  >   >
> >  >   >
> >  >   >   On 11/12/17, 9:53 AM, "Chris Mattmann"<
> mattm...@apache.org>   wrote:
> >  >   >
> >  >   >   Hi Folks,
> >  >   >
> >  >   >
> >  >   >
> >  >   >   I have posted a 1st release candidate for the
> Apache OODT 1.2.1
> >  >   >   release. The
> >  >   >
> >  >   >   source code is at:
> >  >   >
> >  >   >   https://dist.apache.org/repos/dist/dev/oodt/
> >  >   >
> >  >   >
> >  >   >
> >  >   >   For more detailed information, see the included
> CHANGES.txt file for
> >  >   >   details on
> >  >   >
> >  >   >   release contents and latest changes. The release
> was made using the OODT
> >  >   >
> >  >   >   release process, documented on the Wiki here:
> >  >   >
> >  >   >
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
> >  >   >
> >  >   >
> >  >   >
> >  >   >   The release was made from the OODT 1.2 tag at:
> >  >   >
> >  >   >   https://github.com/apache/oodt/tree/1.2.1/
> >  >   >
> >  >   >
> >  >   >
> >  >   >   A staged Maven repository is available at:
> >  >   >
> >  >   >
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> >  >   >
> >  >   >
> >  >   >
> >  >   >   Please vote on releasing these packages as Apache
> OODT 1.2.1. The vote is
> >  >   >
> >  >   >   open for at least the next 72 hours.
> >  >   >
> >  >   >
> >  >   >
> >  >   >   Only votes from OODT PMC are binding, but folks are
> welcome to check the
> >  >   >
> >  >   >   release candidate and voice their approval or
> disapproval. The vote passes
> >  >   >
> >  >   >   if at least three binding +1 votes are cast.
> >  >   >
> >  >   >
> >  >   >
> >  >   >   [ ] +1 Release the packages as Apache OODT 1.2.1
> >  >   >
> >

Re: CVEs etc

2017-09-15 Thread BW

Utilizing more than one,if feasible, would be a good avenue to pursue.


On Fri, Sep 15, 2017 at 2:22 AM, lewis john mcgibbney 
wrote:
> More on this Tom and folks...
> Some of you may have seen on the news lately security 101 e.g. patch (and
> version) upgrades, are critical...
> @Tom, can we possibly have the checks reflected on dev@?
> Another option which has been thrown out there is the following
> https://www.owasp.org/index.php/OWASP_Dependency_Check
> I am by no means stating that any one is more appropriate, I do however
> think that a notification mechanism would be very approbate.
> Lewis
>
>
> On Sat, Sep 9, 2017 at 6:03 AM, Tom Barber  wrote:
>
>> Hi folks
>>
>> This isn't supposed to be an alarmist email, but quite enlightening all
the
>> same.
>>
>> I saw a link to a plugin on the Drill mailing list called Dependency
Check
>> Report so I wired it into  my OODT repo amongst others to see what was
>> flagged up since the Struts fallout.
>>
>> Anyway, of course its unlikely but not out of the question to run OODT
>> fronting on to the interwebs so I think this is decent food for thought
as
>> to why its useful to keep dependencies up to date as much as possible.
>>
>> Here's a selection of the output:
>>
>> https://www.dropbox.com/s/2ida8dk54yleedo/curator-webapp.html?dl=0
>> https://www.dropbox.com/s/wgt1facgjhqiqkq/fmbrowser.html?dl=0
>> https://www.dropbox.com/s/o8kqcaktplzjy4y/metadata.html?dl=0
>> https://www.dropbox.com/s/cli4pj4jc564f16/pge.html?dl=0
>>
>> Of course there is a bunch of repetition in there and plenty that aren't
>> over the top severe, some may also be false positives, but as we work
>> through to OODT 2.0 with the new stuff and chopping out the old stuff,
>> reducing these as much as possible I would posture.
>>
>> Tom
>>
>
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney

Re: Imesha's Blog post about Apache OODT and GSOC 2017

2017-08-30 Thread BW

Nice work Imesha!

On Wed, Aug 30, 2017 at 9:23 AM, Chris Mattmann  wrote:
> …is here: 
> https://loneidealist.wordpress.com/2017/08/24/gsoc-2017-distributed-configuration-management-for-apache-oodt/
>
> Great work Imesha!
>
> Cheers,
> Chris
>
>
>
>
>

Re: [GSoC2017] Distributed Configuration Management - Update

2017-08-12 Thread BW

Great job Imesha!

On Sat, Aug 12, 2017 at 6:28 AM Imesha Sudasingha 
wrote:

> Hi all,
>
> Basic implementation of distributed configuration management using Apache
> Zookeeper as the distributed storage has been completed successfully [1].
> It has been tested with File Manager located in DRAT [2] and it worked
> correctly as expected with distributed configuration management turned on.
> OODT logs for running DRAT can be found in [3].
>
> What is left now is improving the documentation on the design [4] and how
> to use [5]. Then this feature needs to be tested with resource manager and
> workflow manager as well. Finally, I have an idea to allow configuration of
> individual components to be refreshed at runtime without having to manually
> intervene.
>
> I will be grateful if you can provide me with your suggestions for further
> improvements and feedback. Also, thanks to Tom and Chris for guiding me
> this far.
>
> Thank you!
>
> [1] https://github.com/apache/oodt/tree/feature/zookeeper-config
> [2] https://github.com/chrismattmann/drat
> [3] https://drive.google.com/open?id=0B9XGJ8htsTdURTJCbUNvSUxZN1E
> [4]
>
> https://cwiki.apache.org/confluence/display/OODT/Rework+OODT+configuration+to+make+use+of+Zookeeper+for+distributed+configuration+management
> [5]
>
> https://cwiki.apache.org/confluence/display/OODT/OODT+Distributed+Configuration+Management
>
> Kind Regards,
> *Imesha Sudasingha*
> Undergraduate of Department of Computer Science and  Engineering,
> University of Moratuwa,
> Sri Lanka.
>
>   
> 
> 
>

Re: FW: [DISCUSS] Apache Distributed Release Audit Tool (DRAT)

2017-08-02 Thread BW

+1

On Wed, Aug 2, 2017 at 7:37 AM Chris Mattmann  wrote:

> Of interest – DRAT is a de facto standard use of Apache OODT (
>
> Proposal to bring it to Apache is mentioned below…
>
>
>
> On 8/2/17, 10:35 AM, "Chris Mattmann"  wrote:
>
> Hi Board-Chat@,
>
> CC/Incubator@
>
> We are proposing to bring DRAT (Distributed Release Audit Tool) to the
> ASF.
> DRAT is a parallelized version of Apache RAT that uses OODT, Solr and
> Tika to
> compute, visualize and interact with interesting statistics on code
> auditing as
> output by RAT and Tika. With DRAT you can:
>
> • Audit large code repositories (has been tested in 100s of M of lines
> of
> code, and 1000s of projects)  where RAT fails to complete – an example
> of running it across all of Apache
> SVN is here: http://drat.dyndns.org:8080/dratviz/ You can also see
> its output
> for a very large set of NSF funded geosciences code repositories here:
> http://drat.dyndns.org:8080/dratontoviz/
> • Visualize and interact with the output from RAT and Tika in a
> dynamic fashion
> • Get incremental status from code auditing
> • Audit individual code repos and integrate the results into your
> project
>
> DRAT was funded by DARPA, NASA, the NSF and other government entities.
>
> We have prepared a preliminary proposal here:
> https://wiki.apache.org/incubator/DRATProposal
>
> We are working on flushing it out more, should be done by this
> weekend. We propose
> DRAT to be a straight to TLP (pTLP). I will add a resolution into the
> Board agenda for August 2017
> for its consideration. I am CC’ing the Incubator so that we can
> potentially attract new contributors
> both seasoned and junior to the project. We also welcome any
> contributors from Creadur interested
> in learning more about OODT, Solr, Tika, etc. Also any Wicket gurus –
> we are using Wicket for one of
> DRAT’s key user interfaces, Proteus.
>
> OK, thanks!
>
> Cheers,
> Chris
>
>
>
>
>
>
>
>
>

Re: [VOTE] Apache OODT 1.1 RC #1

2017-07-21 Thread BW

Hi Chris. Haven't yet; deferred I guess. Sorry, on vacay..

On Fri, Jul 21, 2017 at 1:11 PM Chris Mattmann <mattm...@apache.org> wrote:

> Hi BW, have you tried RC #2? +1 still?
>
> Cheers,
> Chris
>
>
>
>
> On 7/19/17, 5:32 PM, "BW" <w...@apache.org> wrote:
>
> +1
>
> On Wed, Jul 19, 2017 at 8:51 AM Chris Mattmann <mattm...@apache.org>
> wrote:
>
> > Absolutely, here is a simple use case:
> >
> > If you look at CAS-PGE files, they typically include setup to “stage
> files”
> > (already archived in File Manager) to the local job working
> directly. Many
> > times
> > this is just handled in the bash script (or Python or whatever) that
> > CAS-PGE generates
> > itself. However it’s such a repetitive task and *part of* the actual
> > workflow for running
> > a job, we added a simple interface to do so. See here:
> >
> >
> >
> https://raw.githubusercontent.com/apache/oodt/master/pge/src/test/resources/pge-config.xml
> >
> > And notice this block:
> >
> >   
> > 
> >   
> >
> > What the above does is inspect the value of the InputFiles metadata
> as
> > provided
> > to CAS-PGE (even if it’s a list) and for each of those files, it
> “stages”
> > them (aka uses
> > the associated and declared DataTransferer for this CAS-PGE
> instance) to
> > the directory
> > defined by [StagingDir].
> >
> > Cool huh?
> >
> > Cheers,
> > Chris
> >
> >
> > P.S. It doesn’t work now, but will shortly ;)
> >
> >
> > On 7/19/17, 8:43 AM, "Mallder, Valerie" <valerie.mall...@jhuapl.edu>
> > wrote:
> >
> > Yes, adding a note to CHANGES.txt is fine.  The fix to the
> fileStaging
> > feature of CAS-PGE sounds good, although I've never understood what
> that
> > feature is supposed to do :)  When you have some free time I would
> love to
> > hear about what you are using it for.
> >
> > Thanks!
> >
> >
> > -Original Message-
> > From: Chris Mattmann [mailto:mattm...@apache.org]
> > Sent: Wednesday, July 19, 2017 11:37 AM
> > To: dev@oodt.apache.org
> > Subject: Re: [VOTE] Apache OODT 1.1 RC #1
> >
> > Thank you Val!
> >
> > I may spin another RC not only because of the below (which I
> think we
> > should just note in CHANGES.txt (I am happy to add a note on it),
> but also
> > b/c I found an interesting bug while testing OODT 1.1 RC #1 with
> DRAT – the
> > bug relates to using fileStaging – it doesn’t explicitly set a
> > Product.PRODUCT_STRUCTURE* and as so gets an NPE if you try and use
> it. I
> > never encountered this before b/c I never used OODT’s native file
> staging
> > support in CAS-PGE. It is a simple fix, and I think will add a lot
> of value
> > (fileStaging is inoperable without it in CAS-PGE).
> >
> > Due to that, I will spin another RC shortly.
> >
> > Thank you!
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 7/19/17, 7:55 AM, "Mallder, Valerie" <
> valerie.mall...@jhuapl.edu>
> > wrote:
> >
> > +1
> >
> > I downloaded the source and built it with "mvn package
> -skipTests"
> > and it built ok. I did a system test by running some data through my
> > pipeline that uses cas-workflow-1.1, cas-filemgr-1.1 and cas-pge-1.1
> and
> > everything worked as I expected.  And it even helped find some
> things that
> > I needed to tweak in my test environment :)
> >
> > The only problem I should note is that had to delete the
> workflow
> > repository directory and allow cas-workflow-1.1 to create a
> repository from
> > scratch. cas-workflow-1.1 reported an incompatibility with workflow
> > repository that was created with cas-workflow-0.10 and has been used
> with
> > cas-workflow-1.0 for a while now. (Also note that, if the repository
> > directory exists but it is empty, workflow manager will crash. So, I
> had to
> > delete the repository directory itself rather than just delete the
> contents
> &g

Re: [VOTE] Apache OODT 1.1 RC #1

2017-07-19 Thread BW

+1

On Wed, Jul 19, 2017 at 8:51 AM Chris Mattmann  wrote:

> Absolutely, here is a simple use case:
>
> If you look at CAS-PGE files, they typically include setup to “stage files”
> (already archived in File Manager) to the local job working directly. Many
> times
> this is just handled in the bash script (or Python or whatever) that
> CAS-PGE generates
> itself. However it’s such a repetitive task and *part of* the actual
> workflow for running
> a job, we added a simple interface to do so. See here:
>
>
> https://raw.githubusercontent.com/apache/oodt/master/pge/src/test/resources/pge-config.xml
>
> And notice this block:
>
>   
> 
>   
>
> What the above does is inspect the value of the InputFiles metadata as
> provided
> to CAS-PGE (even if it’s a list) and for each of those files, it “stages”
> them (aka uses
> the associated and declared DataTransferer for this CAS-PGE instance) to
> the directory
> defined by [StagingDir].
>
> Cool huh?
>
> Cheers,
> Chris
>
>
> P.S. It doesn’t work now, but will shortly ;)
>
>
> On 7/19/17, 8:43 AM, "Mallder, Valerie" 
> wrote:
>
> Yes, adding a note to CHANGES.txt is fine.  The fix to the fileStaging
> feature of CAS-PGE sounds good, although I've never understood what that
> feature is supposed to do :)  When you have some free time I would love to
> hear about what you are using it for.
>
> Thanks!
>
>
> -Original Message-
> From: Chris Mattmann [mailto:mattm...@apache.org]
> Sent: Wednesday, July 19, 2017 11:37 AM
> To: dev@oodt.apache.org
> Subject: Re: [VOTE] Apache OODT 1.1 RC #1
>
> Thank you Val!
>
> I may spin another RC not only because of the below (which I think we
> should just note in CHANGES.txt (I am happy to add a note on it), but also
> b/c I found an interesting bug while testing OODT 1.1 RC #1 with DRAT – the
> bug relates to using fileStaging – it doesn’t explicitly set a
> Product.PRODUCT_STRUCTURE* and as so gets an NPE if you try and use it. I
> never encountered this before b/c I never used OODT’s native file staging
> support in CAS-PGE. It is a simple fix, and I think will add a lot of value
> (fileStaging is inoperable without it in CAS-PGE).
>
> Due to that, I will spin another RC shortly.
>
> Thank you!
>
> Cheers,
> Chris
>
>
>
>
> On 7/19/17, 7:55 AM, "Mallder, Valerie" 
> wrote:
>
> +1
>
> I downloaded the source and built it with "mvn package -skipTests"
> and it built ok. I did a system test by running some data through my
> pipeline that uses cas-workflow-1.1, cas-filemgr-1.1 and cas-pge-1.1 and
> everything worked as I expected.  And it even helped find some things that
> I needed to tweak in my test environment :)
>
> The only problem I should note is that had to delete the workflow
> repository directory and allow cas-workflow-1.1 to create a repository from
> scratch. cas-workflow-1.1 reported an incompatibility with workflow
> repository that was created with cas-workflow-0.10 and has been used with
> cas-workflow-1.0 for a while now. (Also note that, if the repository
> directory exists but it is empty, workflow manager will crash. So, I had to
> delete the repository directory itself rather than just delete the contents
> within it.)
>
>  The error I received is below. It looks like the change from
> lucene-core-2.0.0.jar to the lucene-core-6.1.0.jar caused this
> incompatibility between cas-workflow-1.0 and cas-workflow-1.1. Deleting my
> pipeline's workflow respository and allowing  cas-workflow-1.1 to create a
> new one was not a problem for me, but I can't speak for everyone.
>
> Jul 19, 2017 10:45:02 AM
> org.apache.oodt.cas.workflow.instrepo.LuceneWorkflowInstanceRepository
> addWorkflowInstanceToCatalog
> WARNING: Unable to index workflow instance:
> [d8dad567-6c90-11e7-9e4e-7574e3a12106]: Message: Format version is not
> supported (resource
> BufferedChecksumIndexInput(MMapIndexInput(path="/project/oodt/dev/jedi/data/workflow/slothrop/segments"))):
> -1 (needs to be between 1071082519 and 1071082519). This version of Lucene
> only supports indexes created with release 5.0 and later.
> java.lang.NullPointerException
>
> Val
>
>
>
> -Original Message-
> From: Chris Mattmann [mailto:mattm...@apache.org]
> Sent: Tuesday, July 18, 2017 6:54 PM
> To: dev@oodt.apache.org
> Subject: [VOTE] Apache OODT 1.1 RC #1
>
> Hi Folks,
>
> I have posted a 1st release candidate for the Apache OODT 1.1
> release. The source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file
> for details on release contents and latest changes. The release was made
> using the OODT release process, documented on the Wiki here:
>
>

Re: Welcome Imesha

2017-05-04 Thread BW

Welcome Imesha!
On Thu, May 4, 2017 at 12:26 PM Chris Mattmann  wrote:

> Welcome Imesha!
>
>
>
> On 5/4/17, 11:19 AM, "Sean Kelly"  wrote:
>
> Welcome Imesha! Thanks for helping out.
>
> --k
>
> > Tom Barber 
> > 2017-05-4 at 1.00 p
> > I'd like to say an official Hi to Imesha who is our 2017 GSOC
> student for
> > OODT.
> >
> > Imesha will be working on adding Zookeeper support to the OODT
> > configuration codebase.
> >
> >
> > Tom
> >
>
>
>
>

Re: Doing a file move in the LocalDataTransferer

2016-10-21 Thread BW

+1

On Friday, October 21, 2016, Chris Mattmann  wrote:

> The rationale is to not make the staging area a moving target, whilst
> building controlled
> access storage. Creating a copy is always more safe in the area of
> preservation and provenance,
> than making everyting a moving target.
>
> I would strongly caution against doing a .moveFile() unless you add
> facilities in LocalDataTransfer to:
>
> 1. Make it configurable (by default off) maybe something like
> org.apache.oodt.cas.filemgr.datatransferer.local.move
> and settable in filemgr.properties
> 2. Preserve (in metadata) the original file location
> 3. Add locking to the addMetadata facilities and addReferences since they
> may be called in different control flows
>
> I would like to see a design that handles the above and unit tests before
> +1’ing such a change.
>
>
>
> On 10/21/16, 11:35 AM, "Tom Barber"  > wrote:
>
> Hello folks
>
> I'm asking here just incase someone knows a reason why this is a bad
> idea:
>
> We have a bunch of large files on a slow NFS mount which we're
> ingesting in
> bulk. Its using the LocalDataTransferer to do the ingestion move and in
> that code all the move calls are really file copies.
>
> As you'll all know in doing a copy the drive is actually writing bits
> to
> disk, where as doing a move is just moving the file pointer.
>
> Is there a reason why the moveFile method actually uses
>  FileUtils.copyFile() before I try FileUtils.moveFile() ?
>
> Because 1 min for a copy vs 0.06 seconds for a move is far more
> preferable.
>
> Thanks
>
> Tom
>
>
>
>

Re: New Website

2016-10-21 Thread BW

Great job!

On Thursday, October 20, 2016, Mattmann, Chris A (3010) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Looks great!
>
> ++
> Chris Mattmann, Ph.D.
> Principal Data Scientist, Engineering Administrative Office (3010)
> Manager, Open Source Projects Formulation and Development Office (8212)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 180-503E, Mailstop: 180-502
> Email: chris.a.mattm...@nasa.gov 
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
> On 10/18/16, 10:44 AM, "Lewis John Mcgibbney"  > wrote:
>
> No objection.
> 1) It looks dynamite,
> 2) It looks dynamite,
> 3) It looks dynamite
> #dynamite
>
> On Tue, Oct 18, 2016 at 8:06 AM, Tom Barber  > wrote:
>
> > Hello folks
> >
> > As ever my bandwidth shrunk and I didn't get through to completion
> on the
> > website, but I have got some time again not sure I should write
> that
> > when the boss is watching. I would like to get this new website
> > finished, but in parallel I'd like to kick off the changes required
> in
> > infra to move away from the OODT CMS
> >
> > So with the site I worked on: http://buggtb.github.io/oodt-website/
> >
> > Here is my todo:
> >
> > Add some usecase content to links on homepage
> > Add some Vagrant content to vagrant tab
> > Fix component docs so the front page links actually link somewhere
> >
> > Except those items does anyone have any objection to opening a vote
> to move
> > the website from Apache CMS to the Jekyll design hosted either in ASF
> > infrastructure using git-pub-sub or github pages if the ASF supports
> that
> > these days. The site is static so nothing database wise is required.
> >
> > Thanks
> >
> > Tom
> >
>
>
>
> --
>
> *Lewis*
> Dr. Lewis J. McGibbney Ph.D, B.Sc
> Director
> Phone: +1(626)498-3090
> Skype: lewis.john.mcgibbney
> Email: lewis.mcgibb...@gmail.com 
>
>
>

Re: VOTE Apache OODT 1.0 release

2016-06-21 Thread BW

+1

On Tuesday, June 21, 2016, Tom Barber  wrote:

> Hi Folks,
>
> OMG It's finally here
>
> Hyteria over, I have posted a 1st release candidate for the Apache
> OODT 1.0 release. The
> source code is at:
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file for
> details on
> release contents and latest changes. The release was made using the OODT
> release process, documented on the Wiki here:
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT 1.0 tag
> (b63b3ee0dfe6e6d7bb0da3eba855894e37761443) at:
> https://github.com/apache/oodt/tree/1.0
>
> A staged Maven repository is available at:
> https://repository.apache.org/content/groups/staging/org/apache/oodt/
>
> Please vote on releasing these packages as Apache OODT 1.0. The vote is
> open for at least the next 72 hours.
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OODT 1.0
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> Tom
>
> P.S. Here is my +1.
>

Re: [VOTE] OODT 0.12-RC1 Release

2016-02-17 Thread BW

+1

On Thu, Feb 11, 2016 at 3:47 PM, Tom Barber  wrote:
> In my tired state last night I failed to set a sane subject line in the
> email so here goes again, properly this time.
>
> Hi Folks,
>
> I have posted a 1st release candidate for the Apache OODT 0.12 release. The
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file for
> details on
> release contents and latest changes. The release was made using the OODT
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT hash
> 91d0bafe71124906bd94baad746189caf35fb39c
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1010
>
> Please vote on releasing these packages as Apache OODT 0.12. The vote is
> open for at least the next 72 hours.
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OODT 
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> The Magical Trout
>
> P.S. Here is my +1.

Re: VOTE Apache OODT 0.11-rc1 release

2015-12-29 Thread BW

+1

On Tuesday, December 29, 2015, Tom Barber  wrote:

> Hi Folks,
>
> I have posted the 1st release candidate for the Apache OODT 0.11 release.
>
>
> Trying to switch from SVN to Git, hopefully its not gone too wrong!
>
>
> The source code is at:
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file for
> details on release contents and latest changes. The release was made
> using the OODT release process, documented on the Wiki here:
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT 0.11 tag
> (052c87b72320b8015136d107acc2290fe32863c1) at:
> https://git-wip-us.apache.org/repos/asf/oodt.git
>
> A staged Maven repository is available at:
> https://repository.apache.org/content/repositories/orgapacheoodt-1008/
>
> Please vote on releasing these packages as Apache OODT . The vote
> is
> open for at least the next 72 hours.
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OODT 
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> Tom
>
> P.S. Here is my +1.
>

Re: [ATTENTION] Apache OODT Source Code Management

2015-10-02 Thread BW

Nice and simple, good job,

On Fri, Oct 2, 2015 at 5:56 PM, Lewis John Mcgibbney
 wrote:
> Hi dev@, (Val especially)
>
> A wee while ago we decided to migrate the OODT source code over to the
> writable Git repository at the following URL
>
> https://git-wip-us.apache.org/repos/asf?p=oodt.git
>
> I've put up, thanks to a few folk on here, a provisional migration guide
> (sorry for the delay).
> You can see it below
>
> http://oodt.apache.org/development.html#scm
>
> Please report any problems here and we will help you out.
> Thank you, have a great weekend folks.
> Lewis
>
> --
> *Lewis*

Re: Organising the Poms

2015-08-06 Thread BW

Nice +1

On Thursday, August 6, 2015, Ramirez, Paul M (398M) 
paul.m.rami...@jpl.nasa.gov wrote:

 I see what you're saying. Below is an example of what I'm saying. You have
 them as a dependency in the master pom now versus just a set of properties
 in the master pom. Both would accomplish the same thing. I agree mvn
 dependency:tree should not be affect on the child pom area but would list
 all those dependencies under the master too.


 master pom:

 properties

 org.mockito.mockito-all.version1.9.5/org.mockito.mockito-all.version
 /properties



 child pom:

 dependency
groupIdorg.mockito/groupId
artifactIdmockito-all/artifactId
version${org.mockito.mockito-all.version}/version
scopetest/scope
  /dependency

 Personal preference is this but since you created the patch already for
 the other version I'm +1 on it unless the above convinces you it's better.


 --Paul

 
 Paul Ramirez, M.S.
 Technical Group Supervisor
 Computer Science for Data Intensive Applications (398M)
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 158-264, Mailstop: 158-242
 Email: paul.m.rami...@jpl.nasa.gov javascript:;mailto:
 paul.m.rami...@jpl.nasa.gov javascript:;
 Office: 818-354-1015
 Cell: 818-395-8194
 

 On Aug 6, 2015, at 7:48 AM, Tom Barber tom.bar...@meteorite.bi
 javascript:;mailto:tom.bar...@meteorite.bi javascript:;
  wrote:

 Hi Paul

 I'm not at my desk so I can't check dependency:tree but I wouldn't expect a
 different output.

 You also shouldn't loose track of module dependency requirements the
 dependency is still listed in the child pom it's just missing it's version
 attribute. Parameterization seems like a lot of overkill and maintenance
 that would get ignored pretty quickly and gains you little.

 Tom
 On 6 Aug 2015 14:42, Ramirez, Paul M (398M) paul.m.rami...@jpl.nasa.gov
 javascript:;mailto:paul.m.rami...@jpl.nasa.gov javascript:;
 wrote:

 Tom,

 An alternate approach would be to leave the dependencies as is but manage
 the versions as properties in the top level pom. With this patch we lose
 traceability of what dependencies are required where. This alternate
 approach would make overrides easier for people too as it would stand as a
 placeholder for folks to substitute out a property reference with a
 version.

 With this we lose the utility of mvn dependency:tree

 I'd align the property name with the fully qualified artifact name that
 way there was a clear mapping. I think this would accomplish what you were
 looking to do.

 Thoughts?

 --Paul

 ~~
 Paul Ramirez - Group Supervisor
 Computer Science for Data Intensive Applications
 Jet Propulsion Laboratory
 4800 Oak Grove Dr.
 Pasadena, CA 91109
 Office: 818-354-1015
 Cell: 818-395-8194
 ~~

 Sent from my iPhone

 On Aug 6, 2015, at 5:18 AM, Tom Barber tom.bar...@meteorite.bi
 javascript:;mailto:tom.bar...@meteorite.bi javascript:; wrote:

 Hello folks,

 I sent a pull request last night but its also worth discussing on here.

 When me an StarchMD were having a chat in Austin, we wanted to sort out
 some of the build process and locations.

 Personally one of my issues when using OODT is the sheer amount of
 dependencies. Clearly most of these are required, but keeping track of
 the
 versions across modules is a pain. The pull request you see here:
 https://github.com/apache/oodt/pull/25 addresses that by moving the
 versions from the sub modules up to OODT Core so when a version is
 changed
 it is changed in all the submodules. This removes a lot of the
 duplication
 and I believe it makes it easier to see which version is being used.

 If there is a requirement to override a specific version of a dependency
 in
 a submodule this can still be done, but it would also be nicer, in my
 opinion, just upgrade the main dependency so that all modules rely on the
 same version which makes integration a whole lot easier.

 Let me know your thoughts.

 Thanks

 Tom

Re: Apache Avro - using strings or creating schema objects.

2015-06-23 Thread BW

You can also embed jannson in Avro-rpc.

On Tuesday, June 23, 2015, Lewis John Mcgibbney lewis.mcgibb...@gmail.com
wrote:

 Hi Radu,
 Did you check out the Objects I've created at
 https://issues.apache.org/jira/browse/OODT-658
 They may go a long way to helping you out.
 Lewis

 On Tue, Jun 23, 2015 at 3:06 PM, Radu Manole manole.v.r...@gmail.com
 javascript:;
 wrote:

  I have a question, in the catalog module, I want to use avro-rpc from
  CommunicationChannel, based on xmlrpc example. But xmlrpc implementation
 is
  using a Serializer class to transform OODT objects to strings. This is
 done
  because xmlrpc support strings by default. My question is,
  witch is better for avro-rpc, to create objects using avro schema, or to
  use Serializer class and send strings.
 
  Momentary I will implement using strings.
  Thanks,
  Radu.
 



 --
 *Lewis*

Re: Documentation-QuickStart

Can access.  Can't commit index.md.  Was refused.

On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com wrote:

 You should have access fine, please see here:

 https://svn.apache.org/repos/asf/oodt/cms_site/

 Cheers,
 Chris

 
 Chris Mattmann
 chris.mattm...@gmail.com javascript:;




 -Original Message-
 From: BW w...@apache.org javascript:;
 Reply-To: dev@oodt.apache.org javascript:;
 Date: Wednesday, May 20, 2015 at 11:51 AM
 To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
 javascript:;
 Subject: Re: Documentation-QuickStart

 No access.
 Push.
 
 This is from:
 OODT.APACHE.ORG\QUICKSTART.HTML
 
 It looks like there's no quickstart.html.
 
 There is a quick start section in the page that Documentation-wiki link
 goes to.  So, maybe Quick Start can be removed from Documentation drop
 down link; unless there really is a quickstart.html
 
 On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com
 javascript:;
 wrote:
 
  Cool, can you fix it Billy?
 
  
  Chris Mattmann
  chris.mattm...@gmail.com javascript:; javascript:;
 
 
 
 
  -Original Message-
  From: BW w...@apache.org javascript:; javascript:;
  Reply-To: dev@oodt.apache.org javascript:; javascript:;
  Date: Wednesday, May 20, 2015 at 11:26 AM
  To: dev@oodt.apache.org javascript:; javascript:; 
 dev@oodt.apache.org javascript:;
  javascript:;
  Subject: Documentation-QuickStart
 
  It appears that there is a broken link from the main OODT web page for
  Documentation-QuickStart.

Re: Documentation-QuickStart

Using Eclipse.  SVN:E175002 connection refused by the server.

On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com wrote:

 hmm, do your SVN permissions work? You should have
 access. Can you paste exactly what you tried, and
 the exact error message you got?


 
 Chris Mattmann
 chris.mattm...@gmail.com javascript:;




 -Original Message-
 From: BW bw...@mysoftcloud.com javascript:;
 Reply-To: dev@oodt.apache.org javascript:;
 Date: Wednesday, May 20, 2015 at 1:29 PM
 To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
 javascript:;
 Subject: Re: Documentation-QuickStart

 Can access.  Can't commit index.md.  Was refused.
 
 On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com
 javascript:;
 wrote:
 
  You should have access fine, please see here:
 
  https://svn.apache.org/repos/asf/oodt/cms_site/
 
  Cheers,
  Chris
 
  
  Chris Mattmann
  chris.mattm...@gmail.com javascript:; javascript:;
 
 
 
 
  -Original Message-
  From: BW w...@apache.org javascript:; javascript:;
  Reply-To: dev@oodt.apache.org javascript:; javascript:;
  Date: Wednesday, May 20, 2015 at 11:51 AM
  To: dev@oodt.apache.org javascript:; javascript:; 
 dev@oodt.apache.org javascript:;
  javascript:;
  Subject: Re: Documentation-QuickStart
 
  No access.
  Push.
  
  This is from:
  OODT.APACHE.ORG\QUICKSTART.HTML
  
  It looks like there's no quickstart.html.
  
  There is a quick start section in the page that Documentation-wiki
 link
  goes to.  So, maybe Quick Start can be removed from Documentation
 drop
  down link; unless there really is a quickstart.html
  
  On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com
 javascript:;
  javascript:;
  wrote:
  
   Cool, can you fix it Billy?
  
   
   Chris Mattmann
   chris.mattm...@gmail.com javascript:; javascript:;
 javascript:;
  
  
  
  
   -Original Message-
   From: BW w...@apache.org javascript:; javascript:;
 javascript:;
   Reply-To: dev@oodt.apache.org javascript:; javascript:;
 javascript:;
   Date: Wednesday, May 20, 2015 at 11:26 AM
   To: dev@oodt.apache.org javascript:; javascript:;
 javascript:; 
  dev@oodt.apache.org javascript:; javascript:;
   javascript:;
   Subject: Documentation-QuickStart
  
   It appears that there is a broken link from the main OODT web page
 for
   Documentation-QuickStart.

Re: Documentation-QuickStart

No access.
Push.

This is from:
OODT.APACHE.ORG\QUICKSTART.HTML

It looks like there's no quickstart.html.

There is a quick start section in the page that Documentation-wiki link
goes to.  So, maybe Quick Start can be removed from Documentation drop
down link; unless there really is a quickstart.html

On Wednesday, May 20, 2015, Chris Mattmann chris.mattm...@gmail.com wrote:

 Cool, can you fix it Billy?

 
 Chris Mattmann
 chris.mattm...@gmail.com javascript:;




 -Original Message-
 From: BW w...@apache.org javascript:;
 Reply-To: dev@oodt.apache.org javascript:;
 Date: Wednesday, May 20, 2015 at 11:26 AM
 To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
 javascript:;
 Subject: Documentation-QuickStart

 It appears that there is a broken link from the main OODT web page for
 Documentation-QuickStart.

Documentation-QuickStart

It appears that there is a broken link from the main OODT web page for
Documentation-QuickStart.

Re: RADix Vagrant provisioning

2015-04-21 Thread BW

No mysoftcloud... created, will get back with more log data.

On Tuesday, April 21, 2015, Verma, Rishi (398M) rishi.ve...@jpl.nasa.gov
wrote:

 Hi BW,

 That’s should be consistent with my thinking below. The OODT build failed,
 the tar didn’t get created, and the tar extraction step you documented
 below didn’t work.

 My question is, why did the OODT build (which creates the tar) fail. Need
 to see the log output to determine (after you manually run “mvn clean
 package”, following my steps below).

 Rishi

 On Apr 20, 2015, at 6:41 PM, BW w...@apache.org javascript:; wrote:

  It's not getting far enough to do the tar.
 
  On Monday, April 20, 2015, Verma, Rishi (398M) rishi.ve...@jpl.nasa.gov
 javascript:;
  wrote:
 
  Hi BW,
 
  Looks like the OODT build process within the VM didn’t succeed (i.e.
  failed on line 63 within
 
 https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh
  )
 
  Would you mind logging into the VM and building your mysoftcloud-myoodt
  project manually and sharing the error?
 
  i.e.
  $ vagrant ssh
  $ cd /usr/local/src/mysoftcloud-myoodt
  $ mvn clean package
 
  Rishi
 
  On Apr 20, 2015, at 4:04 PM, BW w...@apache.org javascript:;
 javascript:; wrote:
 
  Hey Rishi, had the following below problems on RADix Vagrant
  provisioning:
 
  The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
  things got better; ended up with errors in section 2 below.  (Also,
  suggest
  adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
  provision.sh where the tar occurs)
 
  1. ***
  == oodt_radix_vm: tar (child):
  == oodt_radix_vm:
 
 
 distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
  Cannot open
  == oodt_radix_vm: : No such file or directory
  == oodt_radix_vm: tar (child):
  == oodt_radix_vm: Error is not recoverable: exiting now
  == oodt_radix_vm: tar:
  == oodt_radix_vm: Child returned status 2
  == oodt_radix_vm: tar:
  == oodt_radix_vm: Error is not recoverable: exiting now
  == oodt_radix_vm: /tmp/vagrant-shell: line 67: cd:
 /usr/local/oodt/bin:
  No
  such file or directory
  == oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
  directory
  
  2.
 
  *== oodt_radix_vm: tar: option requires an argument -- 'C'*
 
  *== oodt_radix_vm: Try `tar --help' or `tar --usage' for more
  information.*
 
  *== oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file
 or
  directory*
 
 
  *-Thanks*
 
  *BW*
 
  ---
  Rishi Verma
  NASA Jet Propulsion Laboratory
  California Institute of Technology
 
 

 ---
 Rishi Verma
 NASA Jet Propulsion Laboratory
 California Institute of Technology

RADix Vagrant provisioning

2015-04-20 Thread BW

Hey Rishi, had the following below problems on RADix Vagrant provisioning:

The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
things got better; ended up with errors in section 2 below.  (Also, suggest
adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
provision.sh where the tar occurs)

1. ***
== oodt_radix_vm: tar (child):
== oodt_radix_vm:
distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
Cannot open
== oodt_radix_vm: : No such file or directory
== oodt_radix_vm: tar (child):
== oodt_radix_vm: Error is not recoverable: exiting now
== oodt_radix_vm: tar:
== oodt_radix_vm: Child returned status 2
== oodt_radix_vm: tar:
== oodt_radix_vm: Error is not recoverable: exiting now
== oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin: No
such file or directory
== oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
directory

2.

*== oodt_radix_vm: tar: option requires an argument -- 'C'*

*== oodt_radix_vm: Try `tar --help' or `tar --usage' for more information.*

*== oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
directory*


*-Thanks*

*BW*

Re: RADix Vagrant provisioning

2015-04-20 Thread BW

It's not getting far enough to do the tar.

On Monday, April 20, 2015, Verma, Rishi (398M) rishi.ve...@jpl.nasa.gov
wrote:

 Hi BW,

 Looks like the OODT build process within the VM didn’t succeed (i.e.
 failed on line 63 within
 https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh
 )

 Would you mind logging into the VM and building your mysoftcloud-myoodt
 project manually and sharing the error?

 i.e.
 $ vagrant ssh
 $ cd /usr/local/src/mysoftcloud-myoodt
 $ mvn clean package

 Rishi

 On Apr 20, 2015, at 4:04 PM, BW w...@apache.org javascript:; wrote:

  Hey Rishi, had the following below problems on RADix Vagrant
 provisioning:
 
  The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
  things got better; ended up with errors in section 2 below.  (Also,
 suggest
  adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
  provision.sh where the tar occurs)
 
  1. ***
  == oodt_radix_vm: tar (child):
  == oodt_radix_vm:
 
 distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
  Cannot open
  == oodt_radix_vm: : No such file or directory
  == oodt_radix_vm: tar (child):
  == oodt_radix_vm: Error is not recoverable: exiting now
  == oodt_radix_vm: tar:
  == oodt_radix_vm: Child returned status 2
  == oodt_radix_vm: tar:
  == oodt_radix_vm: Error is not recoverable: exiting now
  == oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin:
 No
  such file or directory
  == oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
  directory
  
  2.
 
  *== oodt_radix_vm: tar: option requires an argument -- 'C'*
 
  *== oodt_radix_vm: Try `tar --help' or `tar --usage' for more
 information.*
 
  *== oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
  directory*
 
 
  *-Thanks*
 
  *BW*

 ---
 Rishi Verma
 NASA Jet Propulsion Laboratory
 California Institute of Technology

Re: New Committer: Dana Freeborn

2015-03-31 Thread BW

Dana welcome aboard!

-Bill

On Tue, Mar 31, 2015 at 10:10 AM, Freeborn, Dana J (398G) 
dana.j.freeb...@jpl.nasa.gov wrote:

 Thanks Chris.  I have subscribed to the dev email list and I'm happy to
 introduce myself.

 My name is Dana Freeborn and I am the Group Supervisor for the Science
 Data Management Systems group of the Instrument Software and Science Data
 Systems Section at JPL.  I have been involved with OODT for over a decade
 with a focus on its application as the framework for for the ingestion,
 management and application of airborne and space borne remote sensing
 data.  With the new challenges facing our upcoming NASA earth orbiting
 missions in this era of big data, I am looking forward to being a part of
 the community of thinkers and doers who will provide the solutions.

 My thanks to the PMC for inviting me to join the Apache OODT community.
 I'm very honored.

 Dana

 From: Chris Mattmann mattm...@apache.orgmailto:mattm...@apache.org
 Date: Saturday, March 28, 2015 1:21 PM
 To: dev@oodt.apache.orgmailto:dev@oodt.apache.org dev@oodt.apache.org
 mailto:dev@oodt.apache.org
 Cc: cpi dana.j.freeb...@jpl.nasa.govmailto:dana.j.freeb...@jpl.nasa.gov
 
 Subject: Re: New Committer: Dana Freeborn

 Hi Dana,

 It would be great if you could introduce yourself since
 there are more folks here than JPL and NASA. Also not sure
 if you are subscribed to the dev@oodt.apache.orgmailto:
 dev@oodt.apache.org list yet.
 If you haven’t subscribed yet, from your preferred email
 send a blank email to dev-subscr...@oodt.apache.orgmailto:
 dev-subscr...@oodt.apache.org and please
 follow the instructions from there.

 Cheers,
 Chris



 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bimailto:tom.bar...@meteorite.bi
 Reply-To: dev@oodt.apache.orgmailto:dev@oodt.apache.org
 Date: Saturday, March 28, 2015 at 3:13 AM
 To: dev@oodt.apache.orgmailto:dev@oodt.apache.org
 Subject: Re: New Committer: Dana Freeborn

 Hopefully I did it right! ;)

 On 28/03/15 00:40, Cameron Goodale wrote:
 That's excellent news Tom. Thanks for keeping the process moving

 Cameron

 On Friday, March 27, 2015, Tom Barber tom.bar...@meteorite.bimailto:
 tom.bar...@meteorite.bi wrote:

 The Project Management Committee (PMC) for Apache OODT has asked Dana
 Freeborn to become a committer and we are pleased to announce that they
 have accepted.


 -- Tom




 --
 *Tom Barber* | Technical Director

 meteorite bi
 *T:* +44 20 8133 3730
 *W:* www.meteorite.bi | *Skype:* meteorite.consulting
 *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG,
 UK

Re: Data processing pipeline workflow management

2015-03-12 Thread BW

Any thoughts on integrating a plug in service with Marathon first then
layer Mesos on top?

On Wednesday, March 11, 2015, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Apache OODT now has a workflow plugin that connects to Mesos:

 http://oodt.apache.org/

 Cross posting this to dev@oodt.apache.org javascript:; so people like
 Mike Starch can chime in.

 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov javascript:;
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++






 -Original Message-
 From: Zameer Manji zma...@apache.org javascript:;
 Reply-To: d...@aurora.incubator.apache.org javascript:;
 d...@aurora.incubator.apache.org javascript:;
 Date: Wednesday, March 11, 2015 at 3:21 PM
 To: d...@aurora.incubator.apache.org javascript:; 
 d...@aurora.incubator.apache.org javascript:;
 Subject: Re: Data processing pipeline workflow management

 Hey,
 
 This is a great question. See my comments inline below.
 
 On Tue, Mar 10, 2015 at 8:28 AM, Lars Albertsson
 lars.alberts...@gmail.com javascript:;
 wrote:
 
  We are evaluating Aurora as a workflow management tool for batch
  processing pipelines. We basically need a tool that regularly runs
  batch processes that are connected as producers/consumers of data,
  typically stored in HDFS or S3.
 
  The alternative tools would be Azkaban, Luigi, and Oozie, but I am
  hoping that building something built on Aurora would result in a
  better solution.
 
  Does anyone have experience with building workflows with Aurora? How
  is Twitter handling batch pipelines? Would the approach below make
  sense, or are there better suggestions? Is there anything related to
  this in the roadmap or available inside Twitter only?
 
 
 As far as I know, you are the first person to consider Aurora for workflow
 management for batch processing. Currently Twitter does not use Aurora for
 batch pipelines.
 I'm not aware of the specifics of the design, but at Twitter there is an
 internal solution for pipelines built upon Hadoop/YARN.
 Currently Aurora is designed around being a service scheduler and I'm not
 aware of any future plans to support workflows or batch computation.
 
 
  In our case, the batch processes will be a mix of cluster
  computation's with Spark, and single-node computations. We want the
  latter to also be scheduled on a farm, and this is why we are
  attracted to Mesos. In the text below, I'll call each part of a
  pipeline a 'step', in order to avoid confusion with Aurora jobs and
  tasks.
 
  My unordered wishlist is:
  * Data pipelines consist of DAGs, where steps take one or more inputs,
  and generate one or more outputs.
 
  * Independent steps in the DAG execute in parallel, constrained by
  resources.
 
  * Steps can be written in different languages and frameworks, some
  clustered.
 
  * The developer code/test/debug cycle is quick, and all functional
  tests can execute on a laptop.
 
  * Developers can test integrated data pipelines, consisting of
  multiple steps, on laptops.
 
  * Steps and their intputs and outputs are parameterised, e.g. by date.
  A parameterised step is typically independent from other instances of
  the same step, e.g. join one day's impressions log with user
  demographics. In some cases, steps depend on yesterday's results, e.g.
  apply one day's user management operation log to the user dataset from
  the day before.
 
  * Data pipelines are specified in embedded DSL files (e.g. aurora
  files), kept close to the business logic code.
 
  * Batch steps should be started soon after the input files become
  available.
 
  * Steps should gracefully avoid recomputation when output files exist.
 
  * Backfilling a window back in time, e.g. 30 days, should happen
  automatically if some earlier steps have failed, or if output files
  have been deleted manually.
 
  * Continuous deployment in the sense that steps are automatically
  deployed and scheduled after 'git push'.
 
  * Step owners can get an overview of step status and history, and
  debug step execution, e.g. by accessing log files.
 
 
  I am aware that no framework will give us everything. It is a matter
  of how much we need to live without or build ourselves.
 
 
 Your wishlist looks pretty reasonable for batch computation workflows.
 
 I'm not aware of any batch/workflow Mesos framework. If you want some or
 all of the above features on top of Mesos, I think you would be venturing
 into writing your own framework.
 Aurora doesn't have the concept of DAG and it

Re: [DISCUSS] Cutting over the website from http://oodt.staging.apache.org

2015-02-08 Thread BW

Just an idea, might be nice to also have a graphical slide show banner
showing the essence then drill down to give Dan's vision:
1. Graphic showing NASA’s Soil Moisture Active Passive (SMAP) launched from
Vandenberg Air Force.
http://www.nasa.gov/press/2015/january/nasa-launches-groundbreaking-soil-moisture-mapping-satellite/#.VNfNdC5yHIs
2. Satellite/Earth graphics from space, data links
3. OODT data flow.
4. etc.

Regards,
BW

On Sun, Feb 8, 2015 at 12:46 PM, Crichton, Daniel J (3902)
daniel.j.crich...@jpl.nasa.gov wrote:

Hi guys,

Thanks for working on this.

In addition to what is there, I'd love to see some work on the front page
to hit a few more aspects:

* Architectural framework that exploits various data science patterns
* Integration of distributed data management and systems. The principles
related to a distributed data system/management architecture were a key
part of OODT from the inception.
* Integration of heterogeneous data
* Ability to integrate different ontology models
* Applications to NASA and space-based projects (satellite, airborne,
ground systems, archives, analytics) as well as other areas.

It would be good to call out projects beyond XDATA and EDRN. For example,
the PDS was a major part/driver behind OODT in 2003 when it won runner up
for NASA Software of the Year. Today, we can talk about expansion into
many different applications/domains.

Thanks,
Dan

On 2/8/15 11:26 AM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:

Yep I¹ve been helping to fix the links too

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

-Original Message-
From: Lewis John Mcgibbney lewis.mcgibb...@gmail.com
Reply-To: dev@oodt.apache.org dev@oodt.apache.org
Date: Sunday, February 8, 2015 at 11:17 AM
To: dev@oodt.apache.org dev@oodt.apache.org
Subject: Re: [DISCUSS] Cutting over the website from
http://oodt.staging.apache.org

+1
I am very keen for this to go live.
I know that Magicaltrout will put loads of time into the Website ;)
Honestly though, Tom and myself sorted out the downloads page and a
number
of other places so really it is a case of linking it all up and we will
be
laughing our socks off followed by another flurry of rampant linking.

On Fri, Feb 6, 2015 at 10:04 PM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:

Hey Guys,

I realize that the new version of the website that we built
during last summer for DARPA XDATA was not made ³whole² vis-a-vis
the content currently on http://oodt.apache.org/. However, they
both can co-exist in SVN, at least until we push all of the content
over.

But I¹m no longer of the opinion that that situation is a blocker
anymore. The new website can be updated using the ASF CMS by anyone
that reads the CMS documentation - and the CMS is more supported
than our current website process. Find out more about the Apache
CMS Here:

http://apache.org/dev/cms

The new version of the website that OODT web site is here:

http://oodt.staging.apache.org/

I figure if we publish it as our main site, we will force ourselves
to fixing all the bugs with it.

Considering how frequently our website is updated (compared to
the wiki), and in general who has knowledge or has ever published
our existing oodt.apache.org website (few) versus who has already
updated the CMS-based website (many), I wanted to gauge folks¹
opinions on asking infra@ to cut over the website. I just rolled
the 0.8.1 RC #2 so hopefully with the 0.8.1 release we can get the
new website up and running and start working on simply making it
better and cutting over the existing content to it.

WDYT?

Cheers,
Chris

--
*Lewis*

Re: [VOTE] Apache OODT 0.8.1 RC #2

2015-02-08 Thread BW

+1

On Friday, February 6, 2015, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Folks,

 I have posted a 2nd release candidate for the Apache OODT 0.8.1 release.
 The
 source code is at:

 https://dist.apache.org/repos/dist/dev/oodt/

 For more detailed information, see the included CHANGES.txt file for
 details on
 release contents and latest changes. The release was made using the OODT
 release process, documented on the Wiki here:

 https://cwiki.apache.org/confluence/display/dOODT/Release+Process

 The release was made from the OODT 0.8.1 tag (r1658019) at:

 http://svn.apache.org/repos/asf/oodt/tags/0.8.1/

 A staged Maven repository is available at:

 https://repository.apache.org/content/repositories/orgapacheoodt-1003/


 Please vote on releasing these packages as Apache OODT 0.8.1. The vote is
 open for at least the next 72 hours.

 Only votes from OODT PMC are binding, but folks are welcome to check the
 release candidate and voice their approval or disapproval. The vote passes
 if at least three binding +1 votes are cast.

 [ ] +1 Release the packages as Apache OODT 0.8.1

 [ ] -1 Do not release the packages because...

 Thanks!

 Cheers,
 Chris

 P.S. Here is my +1.


 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov javascript:;
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++

Re: OODT Tests

2015-01-24 Thread BW

+1

On Saturday, January 24, 2015, Chris Mattmann mattm...@apache.org wrote:

 +1 to having a common build env/area good
 suggestion Cam.




 -Original Message-
 From: Cameron Goodale good...@apache.org javascript:;
 Reply-To: dev@oodt.apache.org javascript:;
 Date: Saturday, January 24, 2015 at 7:43 AM
 To: dev@oodt.apache.org javascript:;
 Subject: Re: OODT Tests

 Hey Folks,
 
 I realize I am late to the discussion but in the past when one person has
 a
 working build and another person is having issues the problem/solution
 (depending on how you look at it) is in the local maven repo.
 
 On my local machine Mac OS X 10.9.5 I blew out my maven repo and did an
 install from a fresh checkout of trunk and I am getting the same error
 that
 Lewis has.  I believe that Jenkins does it's build/test against an empty
 local maven repo.
 
 This is kind of like asking if there is petrol in the tank when a car
 breaks down, but I figure it couldn't hurt to mention it.
 
 Good Luck,
 
 
 Cameron
 
 On Fri, Jan 23, 2015 at 9:37 AM, Tom Barber tom.bar...@meteorite.bi
 javascript:;
 wrote:
 
  Its a null pointer disguised as a broken url. I'll take a look later.
 
  Tom
  On 23 Jan 2015 17:20, Ramirez, Paul M (398M) 
  paul.m.rami...@jpl.nasa.gov javascript:;
  wrote:
 
   Weird one. Is there something wrong with your network connection? Is
 that
   URL being blocked? The stack trace says URL does not exist but I'm
 able
  to
   access it here on my phone.
  
   --Paul
  
   Sent from my iPhone
  
On Jan 23, 2015, at 9:10 AM, Lewis John Mcgibbney 
   lewis.mcgibb...@gmail.com javascript:; wrote:
   
Hi Tom,
Thanks for heads up.
I am kinda confused as to local failure, I'm reproducing failures on
   Jenkins
   
Regression on
   org.apache.oodt.cas.protocol.http.TestHttpProtocol.testLSandCD
Error Message
   
Failed to cd to {parent = 'null', path =
   
  
 
 'repos/asf/oodt/trunk/protocol/http/src/main/java/org/apache/oodt/cas/pro
 tocol/http',
isDir = 'true'} : URL does not exist
'
  
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/or
 g/apache/oodt/cas/protocol/http
   '
   
Stacktrace
   
org.apache.oodt.cas.protocol.exceptions.ProtocolException: Failed to
cd to {parent = 'null', path =
   
  
 
 'repos/asf/oodt/trunk/protocol/http/src/main/java/org/apache/oodt/cas/pro
 tocol/http',
isDir = 'true'} : URL does not exist
'
  
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/or
 g/apache/oodt/cas/protocol/http
   '
   at org.apache.oodt.cas.protocol.http.HttpProtocol.cd
   (HttpProtocol.java:78)
   at
  
 
 org.apache.oodt.cas.protocol.http.TestHttpProtocol.testLSandCD(TestHttpPr
 otocol.java:52)
Caused by: java.io.IOException: URL does not exist
'
  
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/or
 g/apache/oodt/cas/protocol/http
   '
   at
  
 
 org.apache.oodt.cas.protocol.http.util.HttpUtils.isDirectory(HttpUtils.ja
 va:126)
   at org.apache.oodt.cas.protocol.http.HttpProtocol.cd
   (HttpProtocol.java:72)
   ... 23 more
Caused by: java.lang.NullPointerException
   at
  
 
 org.apache.oodt.cas.metadata.util.MimeTypeUtils.autoResolveContentType(Mi
 meTypeUtils.java:223)
   at
  
 
 org.apache.oodt.cas.metadata.util.MimeTypeUtils.autoResolveContentType(Mi
 meTypeUtils.java:132)
   at
  
 
 org.apache.oodt.cas.protocol.http.util.HttpUtils.isDirectory(HttpUtils.ja
 va:122)
   ... 24 more
   
   
   
On Fri, Jan 23, 2015 at 8:45 AM, Tom Barber
 tom.bar...@meteorite.bi javascript:;
   wrote:
   
The only real problem with the build is that the Jersey Client 1.x
 POM
   has
been knackered for god knows how long, but as long as I can
 remember
working with REST stuff, and the Hadoop Client jar in the Resource
   Manager
has it hardcoded as a dependency. So the other night I forced it to
  use
   a
newer version, so it failed a few times and I stepped through the
   required
upgraded jars.
   
Apart from that and a few minor tweaks I think its alright.
   
Tom
   
   
On 23/01/15 16:41, Lewis John Mcgibbney wrote:
   
Hi Folks,
Builds have been dodgy for a while now.
Anyone have a clue what happened?
I just looked at out Jenkins build record for trunk and quite
 frankly
   it
kinda appalling.
I'm building RADiX for a customer right now then I'm going to take
  some
time looking at tests again.
Lewis
   
--
*Tom Barber* | Technical Director
   
meteorite bi
*T:* +44 20 8133 3730
*W:* www.meteorite.bi | *Skype:* meteorite.consulting
*A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
   7YG, UK
   
   
   
--
*Lewis*

Re: OODT Tests

2015-01-24 Thread BW

+1 It would be nice have build delegation distribution list for points of
where the build fails: if that makes sense, seems like a global broadcast.

On Saturday, January 24, 2015, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 +1

 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov javascript:;
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++






 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi javascript:;
 Reply-To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
 javascript:;
 Date: Saturday, January 24, 2015 at 2:20 PM
 To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
 javascript:;
 Subject: Re: OODT Tests

 Another thing that springs to mind, is the fact that the builds stay
 broken for a long time. This isn't just recently, the tests were borked
 for months. I think if people are going to make changes that may break
 the build for a while, there has to be either better communication as to
 why the builds are broken and/or backout the changes or develop on a
 branch.
 
 Just leaving Jenkins spamming people isn't much good and doesn't promote
 much confidence on people coming to look at the project(although I
 admit, they shouldn't necessarily be running trunk).
 
 Tom
 
 On 24/01/15 16:57, Tom Barber wrote:
  Aye well Jenkins building off an empty repo is certainly helpful, the
  amount of projects I've worked on when someone has some random jar
  cached up so it works for them but not anyone else.
 
  On 24/01/15 16:46, BW wrote:
  +1
 
  On Saturday, January 24, 2015, Chris Mattmannmattm...@apache.org
 javascript:;
 wrote:
 
  +1 to having a common build env/area good
  suggestion Cam.
 
 
 
 
  -Original Message-
  From: Cameron Goodale good...@apache.org javascript:;
 javascript:;
  Reply-To: dev@oodt.apache.org javascript:;  javascript:;
  Date: Saturday, January 24, 2015 at 7:43 AM
  To: dev@oodt.apache.org javascript:;  javascript:;
  Subject: Re: OODT Tests
 
  Hey Folks,
 
  I realize I am late to the discussion but in the past when one
 person has
  a
  working build and another person is having issues the
 problem/solution
  (depending on how you look at it) is in the local maven repo.
 
  On my local machine Mac OS X 10.9.5 I blew out my maven repo and did
 an
  install from a fresh checkout of trunk and I am getting the same
 error
  that
  Lewis has.  I believe that Jenkins does it's build/test against an
 empty
  local maven repo.
 
  This is kind of like asking if there is petrol in the tank when a car
  breaks down, but I figure it couldn't hurt to mention it.
 
  Good Luck,
 
 
  Cameron
 
  On Fri, Jan 23, 2015 at 9:37 AM, Tom Barber tom.bar...@meteorite.bi
 javascript:;
  javascript:;
  wrote:
 
  Its a null pointer disguised as a broken url. I'll take a look
 later.
 
  Tom
  On 23 Jan 2015 17:20, Ramirez, Paul M (398M) 
  paul.m.rami...@jpl.nasa.gov javascript:;  javascript:;
  wrote:
 
  Weird one. Is there something wrong with your network connection?
 Is
  that
  URL being blocked? The stack trace says URL does not exist but I'm
  able
  to
  access it here on my phone.
 
  --Paul
 
  Sent from my iPhone
 
  On Jan 23, 2015, at 9:10 AM, Lewis John Mcgibbney 
  lewis.mcgibb...@gmail.com javascript:;  javascript:; wrote:
  Hi Tom,
  Thanks for heads up.
  I am kinda confused as to local failure, I'm reproducing failures
 on
  Jenkins
  Regression on
  org.apache.oodt.cas.protocol.http.TestHttpProtocol.testLSandCD
  Error Message
 
  Failed to cd to {parent = 'null', path =
 
 
 'repos/asf/oodt/trunk/protocol/http/src/main/java/org/apache/oodt/cas
 /pro
  tocol/http',
  isDir = 'true'} : URL does not exist
  '
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/
 or
  g/apache/oodt/cas/protocol/http
  '
  Stacktrace
 
  org.apache.oodt.cas.protocol.exceptions.ProtocolException: Failed
 to
  cd to {parent = 'null', path =
 
 
 'repos/asf/oodt/trunk/protocol/http/src/main/java/org/apache/oodt/cas
 /pro
  tocol/http',
  isDir = 'true'} : URL does not exist
  '
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/
 or
  g/apache/oodt/cas/protocol/http
  '
  at org.apache.oodt.cas.protocol.http.HttpProtocol.cd
  (HttpProtocol.java:78)
  at
 
 org.apache.oodt.cas.protocol.http.TestHttpProtocol.testLSandCD(TestHt
 tpPr
  otocol.java:52)
  Caused by: java.io.IOException: URL does not exist
  '
 
 
 http://svn.apache.org/repos/asf/oodt/trunk/protocol/http/src/main/java/
 or
  g/apache/oodt

Re: VOTE Apache OODT 0.8 release

2014-12-19 Thread BW

+1

On Friday, December 19, 2014, Tom Barber tom.bar...@meteorite.bi wrote:

 Hi Folks,

 I have posted a first release candidate for the Apache OODT 0.8 release.
 The
 source code is at:

 https://dist.apache.org/repos/dist/dev/oodt/

 For more detailed information, see the included CHANGES.txt file for
 details on
 release contents and latest changes. The release was made using the OODT
 release process, documented on the Wiki here:

 https://cwiki.apache.org/confluence/display/OODT/Release+Process

 The release was made from the OODT 0.8 tag (r1646713) at:

 http://svn.apache.org/repos/asf/oodt/tags/0.8/

 A staged Maven repository is available at:

 https://repository.apache.org/content/repositories/orgapacheoodt-1001/

 Please vote on releasing these packages as Apache OODT 0.8. The vote is
 open for the next 72 hours.

 Only votes from OODT PMC are binding, but folks are welcome to check the
 release candidate and voice their approval or disapproval. The vote passes
 if at least three binding +1 votes are cast.

 [ ] +1 Release the packages as Apache OODT 0.8

 [ ] -1 Do not release the packages because...

 Thanks!

 Tom Barber

 P.S. Here is my +1.
 P.P.S I've not done a build before so don't complain too much if its wrong
 :)

Re: Evaluate Suitable Scientific Workflow Language for Airavata.

2014-09-18 Thread BW

Is there a list of graphical BEL workflow tools?

On Thursday, September 18, 2014, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Guys,

 I've been interested in this too - we don't per have a specific
 OODT workflow language, but we specific workflows using XML, and
 other configuration (we are also thinking of moving to JSON for
 this).

 In the past I've also looked at YAWL and BPEL - both seem complex
 to me.

 I wonder at the end of the day if we should adopt something more
 modern like PIG or some other data flow type of language (PIG
 is really neat).

 Cheers,
 Chris


 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov javascript:;
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++






 -Original Message-
 From: Shameera Rathnayaka shameerai...@gmail.com javascript:;
 Reply-To: architect...@airavata.apache.org javascript:;
 architect...@airavata.apache.org javascript:;
 Date: Thursday, September 18, 2014 8:26 AM
 To: architect...@airavata.apache.org javascript:; 
 architect...@airavata.apache.org javascript:;,
 dev d...@airavata.apache.org javascript:;
 Subject: Evaluate Suitable Scientific Workflow Language for Airavata.

 Hi All,
 
 As we all know Airavata has its own workflow language call XWF. When XWF
 was introduced, main focus points are interoperability and convertibility.
 But with years of experience it is convinced that above requirements are
 not really useful when we come to real world use cases. And XWF is XML
 based bulky language where we attache WSDLs and Workflow image it self.
 But
 with the recent changes WSDL part is being removed from XWF.
 
 It is worth to evaluate handy Scientific workflow languages in industry
 and
 find out pros and cons, at the end of this evaluation we need to come up
 with idea how we should improve Airavata workflow language, either we can
 improve existing XWF language, totally change to a new language available
 in industry or write a new light weight language. Basic requirements that
 we expect from new improvement are, high usability, flexible, light weight
 and real time monitoring support. As you can see above requirements are
 not
 direct comes with workflow languages but we need workflow language which
 help to support above requirements.
 
 After reading few papers and googling, initially i have come up with
 following three existing languages,
 1. YAWL http://www.yawlfoundation.org/
 2. WS-BPEL
 3. SIDL
 http://computation.llnl.gov/casc/components/index.html#page=home
 
 In my opinion SIDL is more familiar with scientific domain, Radical-SAGA
 also uses slightly modified version of SIDL. Other than above three
 languages we can come up with simple workflow language base on json(or
 yaml) which support all our requirements for some extends.
 
 It would be grate if I can get more input regarding the $Subject form the
 airavata community. You all are more than welcome to provide any type of
 suggestions.
 
 Thanks,
 Shameera.
 
 
 
 --
 Best Regards,
 Shameera Rathnayaka.
 
 email: shameera AT apache.org , shameerainfo AT gmail.com
 Blog : http://shameerarathnayaka.blogspot.com/

Re: Review Request 24539: Fix Resource Manager in Trunk.

2014-08-18 Thread BW

Is there not a types package?

-BW


On Sun, Aug 10, 2014 at 9:36 PM, Chris Mattmann mattm...@apache.org wrote:


 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/24539/
 ---

 Review request for oodt.


 Bugs: OODT-669
 https://issues.apache.org/jira/browse/OODT-669


 Repository: oodt


 Description
 ---

 Related to OODT-669, get Resource manager working in trunk again.


 Diffs
 -


 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/cli/action/AddNodeCliAction.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/cli/action/SetNodeCapacityCliAction.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/examples/TestResmgr.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/AssignmentMonitor.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/AssignmentMonitorFactory.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Monitor.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ResourceMonitor.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ResourceMonitorFactory.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ganglia/GangliaResourceMonitor.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ganglia/GangliaResourceMonitorFactory.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ganglia/loadcalc/LoadCalculator.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/ganglia/loadcalc/WeightedAverageLoadCalc.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/scheduler/LRUScheduler.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/structs/Job.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/structs/ResourceNode.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpcResourceManager.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpcResourceManagerClient.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/GenericResourceManagerObjectFactory.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/XmlRpcStructFactory.java
 1617057

 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/XmlStructFactory.java
 1617057
   ./trunk/resource/src/main/resources/cmd-line-options.xml 1617057

 ./trunk/resource/src/test/org/apache/oodt/cas/resource/cli/TestResourceCli.java
 1617057

 ./trunk/resource/src/test/org/apache/oodt/cas/resource/monitor/TestAssignmentMonitor.java
 1617057

 ./trunk/resource/src/test/org/apache/oodt/cas/resource/monitor/TestGangliaResourceMonitor.java
 1617057

 ./trunk/resource/src/test/org/apache/oodt/cas/resource/system/MockXmlRpcResourceManagerClient.java
 1617057

 ./trunk/resource/src/test/org/apache/oodt/cas/resource/system/TestXmlRpcResourceManager.java
 1617057
   ./trunk/resource/src/testdata/policy/nodes.xml 1617057
   ./trunk/resource/src/testdata/resourcemon/nodes.xml 1617057

 Diff: https://reviews.apache.org/r/24539/diff/


 Testing
 ---

 testing this patch in XDATA. So far, resource manager starts up correctly,
 but it doesn't seem to respond to the resource manager client in OPSUI. I
 think this is a back compat issue. I went ahead and updated it to support
 double-based load values and capacity. I think that's the problem.


 Thanks,

 Chris Mattmann

Re: Review Request 24539: Fix Resource Manager in Trunk.

2014-08-18 Thread BW

In general, have a preference to redefine types for common and widely used
types.


On Mon, Aug 18, 2014 at 5:54 PM, Chris Mattmann mattm...@apache.org wrote:

 Hi BW, what do you mean, do you mean is there a types package

 in the resource manager?

 Cheers,
 Chris


 -Original Message-
 From: BW bw...@mysoftcloud.com
 Reply-To: dev@oodt.apache.org
 Date: Monday, August 18, 2014 5:48 PM
 To: dev@oodt.apache.org, Chris Mattmann mattm...@apache.org
 Subject: Re: Review Request 24539: Fix Resource Manager in Trunk.

 Is there not a types package?
 
 -BW
 
 
 On Sun, Aug 10, 2014 at 9:36 PM, Chris Mattmann mattm...@apache.org
 wrote:
 
 
  ---
  This is an automatically generated e-mail. To reply, visit:
  https://reviews.apache.org/r/24539/
  ---
 
  Review request for oodt.
 
 
  Bugs: OODT-669
  https://issues.apache.org/jira/browse/OODT-669
 
 
  Repository: oodt
 
 
  Description
  ---
 
  Related to OODT-669, get Resource manager working in trunk again.
 
 
  Diffs
  -
 
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/cli/action/Ad
 dNodeCliAction.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/cli/action/Se
 tNodeCapacityCliAction.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/examples/Test
 Resmgr.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Assig
 nmentMonitor.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Assig
 nmentMonitorFactory.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Monit
 or.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Resou
 rceMonitor.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/Resou
 rceMonitorFactory.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/gangl
 ia/GangliaResourceMonitor.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/gangl
 ia/GangliaResourceMonitorFactory.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/gangl
 ia/loadcalc/LoadCalculator.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/monitor/gangl
 ia/loadcalc/WeightedAverageLoadCalc.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/scheduler/LRU
 Scheduler.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/structs/Job.j
 ava
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/structs/Resou
 rceNode.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpc
 ResourceManager.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpc
 ResourceManagerClient.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/GenericR
 esourceManagerObjectFactory.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/XmlRpcSt
 ructFactory.java
  1617057
 
 
 ./trunk/resource/src/main/java/org/apache/oodt/cas/resource/util/XmlStruc
 tFactory.java
  1617057
./trunk/resource/src/main/resources/cmd-line-options.xml 1617057
 
 
 ./trunk/resource/src/test/org/apache/oodt/cas/resource/cli/TestResourceCl
 i.java
  1617057
 
 
 ./trunk/resource/src/test/org/apache/oodt/cas/resource/monitor/TestAssign
 mentMonitor.java
  1617057
 
 
 ./trunk/resource/src/test/org/apache/oodt/cas/resource/monitor/TestGangli
 aResourceMonitor.java
  1617057
 
 
 ./trunk/resource/src/test/org/apache/oodt/cas/resource/system/MockXmlRpcR
 esourceManagerClient.java
  1617057
 
 
 ./trunk/resource/src/test/org/apache/oodt/cas/resource/system/TestXmlRpcR
 esourceManager.java
  1617057
./trunk/resource/src/testdata/policy/nodes.xml 1617057
./trunk/resource/src/testdata/resourcemon/nodes.xml 1617057
 
  Diff: https://reviews.apache.org/r/24539/diff/
 
 
  Testing
  ---
 
  testing this patch in XDATA. So far, resource manager starts up
 correctly,
  but it doesn't seem to respond to the resource manager client in OPSUI.
 I
  think this is a back compat issue. I went ahead and updated it to
 support
  double-based load values and capacity. I think that's the problem.
 
 
  Thanks,
 
  Chris Mattmann

Re: [ANNOUNCE] Welcome Billy Webb as Apache OODT PMC member + committer

2012-04-05 Thread BW

Thx Chris. Sorry for the late reply, on travel..

BW

On Apr 3, 2012, at 7:46 AM, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Folks,
 
 I could have sworn that I did this earlier but I don't see it in the mail 
 archives, so I'm going to 
 announce it (possibly again). Please welcome Billy Webb as an Apache OODT 
 committer
 and PMC member!
 
 Billy, feel free to say a bit about yourself. Welcome!
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++

Re: Web-Grid

2012-02-02 Thread BW



BW

On Feb 2, 2012, at 11:28 AM, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi BW,
 
 On Feb 1, 2012, at 9:20 PM, B W wrote:
 
 Hi Chris.
 
 I was looking at the Product and Profile packages where the QueryHandler is
 located.  So, the deployed web-grid is decoupled from the Prod/Prof
 packages?
 
 Yep it sure it. Profile/Product handlers exist here:
 
 http://svn.apache.org/repos/asf/oodt/runk/profile
 http://svn.apache.org/repos/asf/oodt/trunk/product
 
 and Web-Grid exists here:
 
 http://svn.apache.org/repos/asf/oodt/trunk/grid
 
 
 But, the packages are used by an adopting organization to architect the
 definition and integration of profile and product components and the
 associated metadata?
 
 Yep they typically simply depend on the jar files produced as part of
 an independent, Maven-based module build. 
 
 
 I'm just trying to evaluate and document the Web-Grid architectural aspect
 and I'm not sure if I need to include those 2 packages.  Trying to keep it
 constrained given my schedule.
 
 NP, as it stands, web-grid must depend on those 2 packages, to at least
 define the interfaces (profile and product) for its subsequent ProfileHandlers
 and QueryHandlers that it exposes.

ok. Thx.  Is it sufficient enough to only show the relation as I did in the 
class diagram or should I further expand and document?
 HTH,
 Chris
 
 
 On Wed, Feb 1, 2012 at 6:43 PM, Mattmann, Chris A (388J) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Hey BW,
 
 At one point it was, yes, in the current Apache implementation, we opted
 for more interactivity and it serves as simply the REST-endpoint and
 marshaling
 of query and results and/or profiles back to the user.
 
 Cheers,
 Chris
 
 On Feb 1, 2012, at 8:37 AM, BW wrote:
 
 Is the QueryServlet responsible for aggregating the query results?
 
 BW
 
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 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: chris.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++

Web-Grid DisQuery

2012-02-01 Thread BW

Please help clarify:

The dispatching of a user query to multiple geographicaly seperated nodes is 
basically layer 7 routing via HTTP redirect.  The routing traversal entry point 
is a nodes web service endpoint where the query for each node is injected as an 
HTTP Servlet Request.

I'm a liitle confused.  I thought that a query was done as above and also 
broadcasted via base64 encoded xml packes at layer 3.

BW

Web-Grid

Overall OODT has a high level layered architecture but is Web-Grid better 
represented as an N-Tiered arch?

BW

Re: Web-Grid



BW

On Jan 31, 2012, at 9:38 AM, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi BW,
 
 I think the whole of OODT is actually better represented by its own 
 architectural style, described
 here [1] and here [2] which is a combination of a number of distributed 
 systems styles including
 Client/Server, P2P, layered, REST, etc.
 
 Does that make sense?
 
 Cheers,
 Chris
 
 [1] http://sunset.usc.edu/~mattmann/pubs/WICSA04-mattman.pdf

 [2] http://sunset.usc.edu/~mattmann/pubs/ICSE06.pdf
 
 On Jan 31, 2012, at 9:33 AM, BW wrote:
 
 Overall OODT has a high level layered architecture but is Web-Grid better 
 represented as an N-Tiered arch?
 
 BW
 
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++

Re: Web-Grid



BW

On Jan 31, 2012, at 9:38 AM, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi BW,
 
 I think the whole of OODT is actually better represented by its own 
 architectural style, described
 here [1] and here [2] which is a combination of a number of distributed 
 systems styles including
 Client/Server, P2P, layered, REST, etc.
 
 Does that make sense?
Yes.  Thx!
 
 Cheers,
 Chris
 
 [1] http://sunset.usc.edu/~mattmann/pubs/WICSA04.pdf
 [2] http://sunset.usc.edu/~mattmann/pubs/ICSE06.pdf
 
 On Jan 31, 2012, at 9:33 AM, BW wrote:
 
 Overall OODT has a high level layered architecture but is Web-Grid better 
 represented as an N-Tiered arch?
 
 BW
 
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++

Re: Web-Grid