Re: [EXTERNAL] Welcome Nadeeshan to OODT PMC/Committers

[Chris Mattmann]

Welcome to Nadeeshan! 

 

Thanks for all of your work and welcome to the community in your
new official role.

 

Sincerely,

Chris Mattmann

 

 

 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Sunday, April 25, 2021 at 6:59 AM
To: dev 
Subject: [EXTERNAL] Welcome Nadeeshan to OODT PMC/Committers

 

Hi all,

 

Nadeeshan had been contributing continuously to OODT over the last 2 years.

Starting from GSoC 2019, Nadeeshan worked on ReactJs based novel OPSUI and

JDK 11 support as the key contributions.

 

As an appreciation for the selfless contributions and continuous efforts to

make OODT better, I'm pleased to welcome Nadeeshan as an OODT committer and

a PMC member.

 

Nadeeshan, congratulations and welcome! See you around.

 

Imesha

 

Re: OODT 2.0 planning

[Chris Mattmann]

+1 from me Imesha!

 

 

 

From: Imesha Sudasingha 
Reply-To: 
Date: Wednesday, November 11, 2020 at 7:49 AM
To: dev 
Subject: Re: OODT 2.0 planning

 

Hi All,

 

This is my suggestion, what if we include both Avro default support and JDK

11 support for OODT 2.0 as JDK 11 support seems to be critical as well.

 

What do you think?

 

Cheers,

Imesha

 



Virus-free.

www.avast.com



<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

 

On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha  wrote:

 

Hi Sean,

 

Regarding docker images, we haven't decided where to push them yet. Yasith

was the person who contributed to them for his GSoC.

 

Hi Yasith,

 

Your help is much appreciated and we will definitely need your help there.

Keep in touch with the mails in this list.

 

Thanks,

Imesha

 

 

On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith 

wrote:

 

Hello all,

 

I can make some time to help with the 2.3 release as well.

 

Best Regards,

Yasith

 

> On Nov 3, 2020, at 10:23 AM, Sean Kelly  wrote:

> 

> 

>> 2.0 – first release where we remove all the Xml-RPC and we change

nothing

>> else. Avro is the default, and only

>> comm option – though interface exists for anyone that wants to roll

their

>> own. We change nothing else*

> 

> Sounds fine by me. XML-RPC was "fun while it lasted".

> 

>> 

>> 2.1 – first release with newer JDK support (everyone is asking for

this,

>> and it screws up people like me with

>> new Macs, or computers and newer JDKs by default). We also begin

cleaning

>> up dependencies and removing

>> old ones, and pointing at new stuff.

> 

> Oh my glob yes, yes, yes!

>> 

>> 2.2 – OpsUi React with GSoC 2019 output.

> 

> I can't comment on 2.2 since I've never used it.

>> 

>> 2.3 – We integrate, test and demo the Docker builds. We also test and

fully

>> bake the ZK deployments and

>> scaled up Docker.

> 

> Are these the images owned by "oodthub" on hub.docker.com?

> 

> Take care,

> -SK

 

 

 

Re: OODT 2.0 planning

[Chris Mattmann]

+1 from me

 

 

 

From: Imesha Sudasingha 
Reply-To: 
Date: Thursday, October 29, 2020 at 6:56 PM
To: dev 
Subject: Re: OODT 2.0 planning

 

Hi All,

 

This is an old thread where we discussed the plan for next releases. In

summary, following was the plan:

 

2.0 – first release where we remove all the Xml-RPC and we change nothing

else. Avro is the default, and only

comm option – though interface exists for anyone that wants to roll their

own. We change nothing else*

 

2.1 – first release with newer JDK support (everyone is asking for this,

and it screws up people like me with

new Macs, or computers and newer JDKs by default). We also begin cleaning

up dependencies and removing

old ones, and pointing at new stuff.

 

2.2 – OpsUi React with GSoC 2019 output.

 

2.3 – We integrate, test and demo the Docker builds. We also test and fully

bake the ZK deployments and

scaled up Docker.

 

Any changes/suggestions to the above plan?

What if we release the OpsUI ahead of others?

 

Thanks,

Imesha

 

On Sun, 6 Oct 2019 at 06:20, Tom Barber  wrote:

 

Sounds good to me. Should also increase the release cadence as well.

 

 

On 5 October 2019 at 09:06:35, Chris Mattmann (mattm...@apache.org) wrote:

 

Here is my suggested Roadmap here:

 

 

 

2.0 – first release where we remove all the Xml-RPC and we change nothing

else. Avro is the default, and only

comm option – though interface exists for anyone that wants to roll their

own. We change nothing else*

 

 

 

2.1 – first release with newer JDK support (everyone is asking for this,

and it screws up people like me with

new Macs, or computers and newer JDKs by default). We also begin cleaning

up dependencies and removing

old ones, and pointing at new stuff.

 

 

 

2.2 – OpsUi React with Breno’s stuff.

 

 

 

2.3 – We integrate, test and demo the Docker builds. We also test and fully

bake the ZK deployments and

scaled up Docker.

 

 

 

2.4+ … who knows

 

 

 

 

 

 

 

From: Tom Barber 

Reply-To: 

Date: Saturday, October 5, 2019 at 3:31 AM

To: , Imesha Sudasingha 

Subject: Re: OODT 2.0 planning

 

 

 

On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org)

wrote:

 

 

 

I think there was a plan to

 

remove XML rpc support completely and use avro only in 2.0.

 

 

 

 

 

That is true. XMLRPC needs to die.

 

 

 

Not sure about Knative, but certainly a Kubernetes operator would be

 

something interesting to look at if we could.

 

 

 

--

 

 

 

 

 

Spicule Limited is registered in England & Wales. Company Number:

 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

 

 

 

 

 

All engagements

 

are subject to Spicule Terms and Conditions of Business. This email and its

 

contents are intended solely for the individual to whom it is addressed and

 

may contain information that is confidential, privileged or otherwise

 

protected from disclosure, distributing or copying. Any views or opinions

 

presented in this email are solely those of the author and do not

 

necessarily represent those of Spicule Limited. The company accepts no

 

liability for any damage caused by any virus transmitted by this email. If

 

you have received this message in error, please notify us immediately by

 

reply email before deleting it from your system. Service of legal notice

 

cannot be effected on Spicule Limited by email.

 

--

 

 

Spicule Limited is registered in England & Wales. Company Number:

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements

are subject to Spicule Terms and Conditions of Business. This email and

its

contents are intended solely for the individual to whom it is addressed

and

may contain information that is confidential, privileged or otherwise

protected from disclosure, distributing or copying. Any views or opinions

presented in this email are solely those of the author and do not

necessarily represent those of Spicule Limited. The company accepts no

liability for any damage caused by any virus transmitted by this email. If

you have received this message in error, please notify us immediately by

reply email before deleting it from your system. Service of legal notice

cannot be effected on Spicule Limited by email.

 

 

Re: [EXTERNAL] OODT 1.9.1 Release and DRAT

[Chris Mattmann]

Thanks Imesha, I’ll add it to my list of things to test ☺

You ROCK would love to get a DRAT 1.0 out

 

 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Saturday, February 8, 2020 at 10:18 AM
To: dev 
Subject: [EXTERNAL] OODT 1.9.1 Release and DRAT

 

Hi All,

 

When DRAT 1.0 RC which relied on OODT 1.9 was being tested, we encountered

several issues [1]. I have fixed OODT related things under OODT-1031 and

those fixes have now been committed. Now we need to release OODT 1.9.1 with

those fixes.

 

On DRAT side, I have sent a PR [2] containing updates required to be done

to DRAT to be compatible with OODT 1.9.1 once released. If you can have a

look at the PR and preferably test it locally, it will help expedite the

release process.

 

Thanks,

Imesha

 

[1] https://issues.apache.org/jira/projects/OODT/issues/OODT-1031

[2] https://github.com/apache/drat/pull/204

 

FW: [EXTERNAL] DRAT 1.0 RC2 warnings

[Chris Mattmann]

So I think this is actually an OODT bug, sending to OODT and CC to DRAT.

 

so @imesha i think the issue is here

9:55 PM

you actually don’t allow override of the client factory at runtime since at 
this line in RpcCommFactory for workflow

9:55 PM

https://github.com/apache/oodt/blob/master/workflow/src/main/java/org/apache/oodt/cas/workflow/system/rpc/RpcCommunicationFactory.java#L41

workflow/src/main/java/org/apache/oodt/cas/workflow/system/rpc/RpcCommunicationFactory.java:41
InputStream prpFileStream = 
RpcCommunicationFactory.class.getResourceAsStream("/workflow.properties");
apache/oodt | Added by GitHub

9:55 PM

you force it to load /workflow.properties which is shipped with the JAR

9:55 PM

you can’t override it

9:57 PM

same goes for resource

9:58 PM

you can’t actually override it b/c you load and force the one shipped with the 
JAR

 

Let me know what you think. I think we need to make the client code in OODT 
workflow and resmgr look like the filemgr
client code so that we can actually override it at runtime and not just pick 
the version that shipped with the JAR.

 

Thoughts?


I think we may need a 1.9.1 for this…


Cheers,

Chris

 

 

 

From: Chris Mattmann 
Reply-To: "d...@drat.apache.org" 
Date: Saturday, October 5, 2019 at 9:45 PM
To: "d...@drat.apache.org" 
Subject: [EXTERNAL] DRAT 1.0 RC2 warnings

 

Team,

 

 

One thing I noticed about DRAT 1.0 RC2 after upgrading to OODT 1.9. By default 
XmlRpc is

available, but the behavior of certain functions have changed where we were 
creating the

clients for FM and WM and RM – by default we get Avro ones back now. We should 
be able

to control this via system properties, for example the following 3 properties 
should fix this

problem in $TOMCAT/conf/catalina.properties (but they only fix it for FM 
client). Any ideas,

Imesha?

 

 

# OODT Avro stuff

 

filemgr.client=org.apache.oodt.cas.filemgr.system.rpc.XmlRpcFileManagerClientFactory

 

workflow.client.factory=org.apache.oodt.cas.workflow.system.rpc.XmlRpcWorkflowManagerFactory

 

resmgr.manager.client=org.apache.oodt.cas.resource.system.XmlRpcResourceManagerClient

 

 

That fixes the FM client, but the web apps in DRAT’s OPSUI are still creating  
the Avro versions of 

workflow manager client and resource client. What am I doing wrong here?

 

 

Cheers,

 

Chris

 

 

 

Re: OODT 2.0 planning

[Chris Mattmann]

Here is my suggested Roadmap here:

 

2.0 – first release where we remove all the Xml-RPC and we change nothing else. 
Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their own. 
We change nothing else*

 

2.1 – first release with newer JDK support (everyone is asking for this, and it 
screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning up 
dependencies and removing 
old ones, and pointing at new stuff.

 

2.2 – OpsUi React with Breno’s stuff. 

 

2.3 – We integrate, test and demo the Docker builds. We also test and fully 
bake the ZK deployments and 
scaled up Docker.

 

2.4+ … who knows

 

 

 

From: Tom Barber 
Reply-To: 
Date: Saturday, October 5, 2019 at 3:31 AM
To: , Imesha Sudasingha 
Subject: Re: OODT 2.0 planning

 

On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org) wrote:

 

I think there was a plan to

remove XML rpc support completely and use avro only in 2.0.

 

 

That is true. XMLRPC needs to die.

 

Not sure about Knative, but certainly a Kubernetes operator would be

something interesting to look at if we could.

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

OK I’m crazy (or more likely we have sporadic tests oh well),  but even the 
tag builds now:

 

[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @ oodt ---

[INFO] 

[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---

[INFO] Installing /Users/mattmann/git/oodt/pom.xml to 
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.10-SNAPSHOT/oodt-1.10-SNAPSHOT.pom

[INFO] 

[INFO] Reactor Summary for Apache OODT 1.10-SNAPSHOT:

[INFO] 

[INFO] OODT Core .. SUCCESS [  2.212 s]

[INFO] Common Utilities ... SUCCESS [ 21.411 s]

[INFO] CAS Command Line Interface . SUCCESS [  6.008 s]

[INFO] OODT - Configuration Management  SUCCESS [ 22.287 s]

[INFO] Process Control System Input Data Package .. SUCCESS [  1.766 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  2.755 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [03:59 min]

[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 31.948 s]

[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 47.830 s]

[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 20.061 s]

[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  1.467 s]

[INFO] CAS Curation Web Services .. SUCCESS [  7.288 s]

[INFO] Process Control System Core Package  SUCCESS [ 14.349 s]

[INFO] OODT Wicket Web Components . SUCCESS [  4.068 s]

[INFO] CAS Curation Interface . SUCCESS [  8.496 s]

[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 19.104 s]

[INFO] CAS Installer Maven Mojo ... SUCCESS [  2.667 s]

[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  1.080 s]

[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  1.068 s]

[INFO] OODT :: Archetypes . SUCCESS [  0.033 s]

[INFO] CAS File Manager Browser Web App ... SUCCESS [  8.131 s]

[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  3.029 s]

[INFO] CAS Product Server Web Application . SUCCESS [ 16.092 s]

[INFO] CAS Workflow REST Services . SUCCESS [  2.272 s]

[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 15.593 s]

[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [  6.821 s]

[INFO] Apache OODT  SUCCESS [  0.018 s]

[INFO] 

[INFO] BUILD SUCCESS

[INFO] 

[INFO] Total time:  08:27 min

[INFO] Finished at: 2019-10-02T09:59:22-07:00

[INFO] 

pomodoro:oodt mattmann$ 

 

 

All good +1 to release 1.9-rc4.

 

Cheers,

Chris

 

 

 

 

From: Chris Mattmann 
Reply-To: "dev@oodt.apache.org" 
Date: Wednesday, October 2, 2019 at 9:38 AM
To: "dev@oodt.apache.org" , Chris Mattmann 

Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

OK tests are still failing. Sigh.

 

 

[INFO] Running org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager

 

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.643 s 
<<< FAILURE! - in org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager

 

[ERROR] 
testGetWorkflowInstances(org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager)
  Time elapsed: 1.617 s  <<< FAILURE!

 

junit.framework.AssertionFailedError: expected:<2> but was:<1>

 

   at 
org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager.testGetWorkflowInstances(TestAvroRpcWorkflowManager.java:71)

 

 

 

also it hung and I had to quit:

 

 

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.527 s 
- in org.apache.oodt.cas.workflow.engine.TestThreadPoolWorkflowEngine

 

[INFO] Running 
org.apache.oodt.cas.workflow.engine.TestAsynchronousLocalEngineRunner

 

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.625 s 
- in org.apache.oodt.cas.workflow.engine.TestAsynchronousLocalEngineRunner

 

[INFO] Running org.apache.oodt.cas.workflow.engine.TestTaskRunner

 

^C[INFO] 

 

[INFO] Results:

 

[INFO] 

 

[ERROR] Failures: 

 

[ERROR]   TestAvroRpcWorkflowManager.testGetWorkflowInstances:71 expected:<2> 
but was:<1>

 

[INFO] 

 

[ERROR] Tests run: 115, Failures: 1, Errors: 0, Skipped: 9

 

[INFO] 

 

pomodoro:oodt mattmann$ 

 

 

 

 

 

pomodoro:oodt mattmann$ git branch

 

* (HEAD detached at 1.9-rc4)

 

  0.12-release

 

  1.2

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

OK tests are still failing. Sigh.

 

[INFO] Running org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.643 s 
<<< FAILURE! - in org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager

[ERROR] 
testGetWorkflowInstances(org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager)
  Time elapsed: 1.617 s  <<< FAILURE!

junit.framework.AssertionFailedError: expected:<2> but was:<1>

   at 
org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager.testGetWorkflowInstances(TestAvroRpcWorkflowManager.java:71)

 

 

also it hung and I had to quit:

 

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.527 s 
- in org.apache.oodt.cas.workflow.engine.TestThreadPoolWorkflowEngine

[INFO] Running 
org.apache.oodt.cas.workflow.engine.TestAsynchronousLocalEngineRunner

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.625 s 
- in org.apache.oodt.cas.workflow.engine.TestAsynchronousLocalEngineRunner

[INFO] Running org.apache.oodt.cas.workflow.engine.TestTaskRunner

^C[INFO] 

[INFO] Results:

[INFO] 

[ERROR] Failures: 

[ERROR]   TestAvroRpcWorkflowManager.testGetWorkflowInstances:71 expected:<2> 
but was:<1>

[INFO] 

[ERROR] Tests run: 115, Failures: 1, Errors: 0, Skipped: 9

[INFO] 

pomodoro:oodt mattmann$ 

 

 

 

 

pomodoro:oodt mattmann$ git branch

* (HEAD detached at 1.9-rc4)

  0.12-release

  1.2.1

  OODT-967

  OODT-972

  OODT-973

  OODT-978

  asf-site

  development

  feature/zookeeper-config

  master

  merge-avro-dynworkflow

  regex-exclude-merge

  release-1.2.3

  site-dev

  upreadme

pomodoro:oodt mattmann$ 

 

pomodoro:oodt mattmann$ java -version

openjdk version "1.8.0_212"

OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03)

OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)

pomodoro:oodt mattmann$ mvn -V

Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 
2019-04-04T12:00:29-07:00)

Maven home: /usr/local/Cellar/maven/3.6.1/libexec

Java version: 1.8.0_212, vendor: AdoptOpenJDK, runtime: 
/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"

[INFO] Scanning for projects...

 

 

From: Tom Barber 
Reply-To: 
Date: Wednesday, October 2, 2019 at 9:18 AM
To: , Chris Mattmann 
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

https://github.com/apache/oodt/commits/1.9

 

You can see Imesha’s fix in the list from 2 days ago.

 

Which test failed?

 

 

On 2 October 2019 at 17:12:54, Chris Mattmann (mattm...@apache.org) wrote:

 

OK another build failure, note in Workflow this time. I am on the 1.9

detached tag:

 

 

 

[INFO] CAS File Manager Browser Web App ... SKIPPED

 

[INFO] CAS Workflow Manager Monitor Web App ... SKIPPED

 

[INFO] CAS Product Server Web Application . SKIPPED

 

[INFO] CAS Workflow REST Services . SKIPPED

 

[INFO] Process Control System Operator Interface Webapp ... SKIPPED

 

[INFO] OODT Process Control System JAX-RS service layer ... SKIPPED

 

[INFO] Apache OODT  SKIPPED

 

[INFO]



 

[INFO] BUILD FAILURE

 

[INFO]



 

[INFO] Total time: 06:43 min

 

[INFO] Finished at: 2019-10-02T09:08:20-07:00

 

[INFO]



 

[ERROR] Failed to execute goal

org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test)

on project cas-workflow: There are test failures.

 

[ERROR]

 

[ERROR] Please refer to

/Users/mattmann/git/oodt/workflow/target/surefire-reports for the

individual test results.

 

[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,

[date].dumpstream and [date]-jvmRun[N].dumpstream.

 

[ERROR] -> [Help 1]

 

[ERROR]

 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e

switch.

 

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

 

[ERROR]

 

[ERROR] For more information about the errors and possible solutions,

please read the following articles:

 

[ERROR] [Help 1]

http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

 

[ERROR]

 

[ERROR] After correcting the problems, you can resume the build with the

command

 

[ERROR] mvn  -rf :cas-workflow

 

pomodoro:oodt mattmann$ git branch

 

* (HEAD detached at 1.9)

 

0.12-release

 

1.2.1

 

OODT-967

 

OODT-972

 

OODT-973

 

OODT-978

 

asf-site

 

development

 

feature/zookeeper-config

 

master

 

merge-avro-dynworkf

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

The one that Imesha fixed, for whatever reason I was not seeing 1.9-rc4 in 
GH….but it’s there now (when I tried to push it).

Anyways rebuilding stand by

 

 

 

From: Tom Barber 
Date: Wednesday, October 2, 2019 at 9:18 AM
To: "dev@oodt.apache.org" , Chris Mattmann 

Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

https://github.com/apache/oodt/commits/1.9

 

You can see Imesha’s fix in the list from 2 days ago.

 

Which test failed?

 

 

On 2 October 2019 at 17:12:54, Chris Mattmann (mattm...@apache.org) wrote:

OK another build failure, note in Workflow this time. I am on the 1.9 detached 
tag: 



[INFO] CAS File Manager Browser Web App ... SKIPPED 

[INFO] CAS Workflow Manager Monitor Web App ... SKIPPED 

[INFO] CAS Product Server Web Application . SKIPPED 

[INFO] CAS Workflow REST Services . SKIPPED 

[INFO] Process Control System Operator Interface Webapp ... SKIPPED 

[INFO] OODT Process Control System JAX-RS service layer ... SKIPPED 

[INFO] Apache OODT  SKIPPED 

[INFO]  

[INFO] BUILD FAILURE 

[INFO]  

[INFO] Total time: 06:43 min 

[INFO] Finished at: 2019-10-02T09:08:20-07:00 

[INFO]  

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on 
project cas-workflow: There are test failures. 

[ERROR] 

[ERROR] Please refer to 
/Users/mattmann/git/oodt/workflow/target/surefire-reports for the individual 
test results. 

[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream. 

[ERROR] -> [Help 1] 

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch. 

[ERROR] Re-run Maven using the -X switch to enable full debug logging. 

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please 
read the following articles: 

[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException 

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the 
command 

[ERROR] mvn  -rf :cas-workflow 

pomodoro:oodt mattmann$ git branch 

* (HEAD detached at 1.9) 

0.12-release 

1.2.1 

OODT-967 

OODT-972 

OODT-973 

OODT-978 

asf-site 

development 

feature/zookeeper-config 

master 

merge-avro-dynworkflow 

regex-exclude-merge 

release-1.2.3 

site-dev 



Is there a possibility Tom didn’t push Imesha’s fix and create a new tag? 







From: Chris Mattmann  
Date: Wednesday, October 2, 2019 at 9:08 AM 
To: "dev@oodt.apache.org"  
Cc: Chris Mattmann  
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4 



It is building further now and I already had brew cask. I am going to update 
the wiki with 
the export command to build b/c it is something we will want to capture. 



Speaking of which I don’t have perms to edit the wiki anymore. Imesha or Tom 
can you 
can me perms? 







From: Imesha Sudasingha  
Reply-To: "dev@oodt.apache.org"  
Date: Tuesday, October 1, 2019 at 6:42 PM 
To: dev  
Cc: Chris Mattmann  
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4 



Hi Chris, 



I think from jdk 10 or 11, xml related libraries (jaxb) have been removed 

from default libraries. That's why you should be getting that error. By the 

look, it seems like an XML related issue. 



Thanks, 

Imesha 



On Wed, 2 Oct 2019, 3:21 am Tom Barber,  wrote: 



brew tap caskroom/versions 

brew cask install java8 





I think 





export JAVA_HOME=`/usr/libexec/java_home -v 1.8` 







On 1 October 2019 at 22:42:42, Mattmann, Chris A (US 1761) ( 

chris.a.mattm...@jpl.nasa.gov.invalid) wrote: 



Any links to install one that old on mac? 



Sent from my iPhone 



> On Oct 1, 2019, at 2:28 PM, Tom Barber  wrote: 

> 

> 8, 9 I think will be okay 10+ will be questionable due the change in API 

> and jars that need upgrading for compatibility. 

> 

> 

> On 1 October 2019 at 21:58:35, Chris Mattmann (mattm...@apache.org) 

wrote: 

> 

> OK so I need JDK8 to build, is that right? 

> 

> 

> 

> 

> 

> 

> 

> From: Tom Barber  

> Reply-To:  

> Date: Tuesday, October 1, 2019 at 1:57 PM 

> To: , Chris Mattmann , Imesha 

> Sudasingha  

> Subject: Re: [VOTE] OODT 1.9 RC 4 

> 

> 

> 

> Yeah, I’m amazed you got that far through with 12. I know from other apps 

> 

> migrating from 8 through 12 is a right PITA and something we should look 

at 

> 

> for 2.0. 

> 

> 

> 

> 

> 

> On 1 October 2019 at 21:48:08, Chris Mattmann (mattm...@apache.org) 

wrote: 

> 

> 

> 

> Pom shouldn’t be 

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

OK another build failure, note in Workflow this time. I am on the 1.9 detached 
tag:

 

[INFO] CAS File Manager Browser Web App ... SKIPPED

[INFO] CAS Workflow Manager Monitor Web App ... SKIPPED

[INFO] CAS Product Server Web Application . SKIPPED

[INFO] CAS Workflow REST Services . SKIPPED

[INFO] Process Control System Operator Interface Webapp ... SKIPPED

[INFO] OODT Process Control System JAX-RS service layer ... SKIPPED

[INFO] Apache OODT  SKIPPED

[INFO] 

[INFO] BUILD FAILURE

[INFO] 

[INFO] Total time:  06:43 min

[INFO] Finished at: 2019-10-02T09:08:20-07:00

[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on 
project cas-workflow: There are test failures.

[ERROR] 

[ERROR] Please refer to 
/Users/mattmann/git/oodt/workflow/target/surefire-reports for the individual 
test results.

[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.

[ERROR] -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please 
read the following articles:

[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn  -rf :cas-workflow

pomodoro:oodt mattmann$ git branch

* (HEAD detached at 1.9)

  0.12-release

  1.2.1

  OODT-967

  OODT-972

  OODT-973

  OODT-978

  asf-site

  development

  feature/zookeeper-config

  master

  merge-avro-dynworkflow

  regex-exclude-merge

  release-1.2.3

  site-dev

 

Is there a possibility Tom didn’t push Imesha’s fix and create a new tag?

 

 

 

From: Chris Mattmann 
Date: Wednesday, October 2, 2019 at 9:08 AM
To: "dev@oodt.apache.org" 
Cc: Chris Mattmann 
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

It is building further now and I already had brew cask. I am going to update 
the wiki with
the export command to build b/c it is something we will want to capture. 

 

Speaking of which I don’t have perms to edit the wiki anymore. Imesha or Tom 
can you 
can me perms?

 

 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, October 1, 2019 at 6:42 PM
To: dev 
Cc: Chris Mattmann 
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

Hi Chris,

 

I think from jdk 10 or 11, xml related libraries (jaxb) have been removed

from default libraries. That's why you should be getting that error. By the

look, it seems like an XML related issue.

 

Thanks,

Imesha

 

On Wed, 2 Oct 2019, 3:21 am Tom Barber,  wrote:

 

brew tap caskroom/versions

brew cask install java8

 

 

I think

 

 

export JAVA_HOME=`/usr/libexec/java_home -v 1.8`

 

 

 

On 1 October 2019 at 22:42:42, Mattmann, Chris A (US 1761) (

chris.a.mattm...@jpl.nasa.gov.invalid) wrote:

 

Any links to install one that old on mac?

 

Sent from my iPhone

 

> On Oct 1, 2019, at 2:28 PM, Tom Barber  wrote:

> 

> 8, 9 I think will be okay 10+ will be questionable due the change in API

> and jars that need upgrading for compatibility.

> 

> 

> On 1 October 2019 at 21:58:35, Chris Mattmann (mattm...@apache.org)

wrote:

> 

> OK so I need JDK8 to build, is that right?

> 

> 

> 

> 

> 

> 

> 

> From: Tom Barber 

> Reply-To: 

> Date: Tuesday, October 1, 2019 at 1:57 PM

> To: , Chris Mattmann , Imesha

> Sudasingha 

> Subject: Re: [VOTE] OODT 1.9 RC 4

> 

> 

> 

> Yeah, I’m amazed you got that far through with 12. I know from other apps

> 

> migrating from 8 through 12 is a right PITA and something we should look

at

> 

> for 2.0.

> 

> 

> 

> 

> 

> On 1 October 2019 at 21:48:08, Chris Mattmann (mattm...@apache.org)

wrote:

> 

> 

> 

> Pom shouldn’t be a blocker.

> 

> 

> 

> 

> 

> 

> 

> Here is my Java version am I using the right one?

> 

> 

> 

> 

> 

> 

> 

> pomodoro:oodt mattmann$ java -version

> 

> 

> 

> openjdk version "12.0.1" 2019-04-16

> 

> 

> 

> OpenJDK Runtime Environment (build 12.0.1+12)

> 

> 

> 

> OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)

> 

> 

> 

> pomodoro:oodt mattmann$

> 

> 

> 

> 

> 

> 

> 

> Should I switch?

> 

> 

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

It is building further now and I already had brew cask. I am going to update 
the wiki with
the export command to build b/c it is something we will want to capture. 

 

Speaking of which I don’t have perms to edit the wiki anymore. Imesha or Tom 
can you 
can me perms?

 

 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, October 1, 2019 at 6:42 PM
To: dev 
Cc: Chris Mattmann 
Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

 

Hi Chris,

 

I think from jdk 10 or 11, xml related libraries (jaxb) have been removed

from default libraries. That's why you should be getting that error. By the

look, it seems like an XML related issue.

 

Thanks,

Imesha

 

On Wed, 2 Oct 2019, 3:21 am Tom Barber,  wrote:

 

brew tap caskroom/versions

brew cask install java8

 

 

I think

 

 

export JAVA_HOME=`/usr/libexec/java_home -v 1.8`

 

 

 

On 1 October 2019 at 22:42:42, Mattmann, Chris A (US 1761) (

chris.a.mattm...@jpl.nasa.gov.invalid) wrote:

 

Any links to install one that old on mac?

 

Sent from my iPhone

 

> On Oct 1, 2019, at 2:28 PM, Tom Barber  wrote:

> 

> 8, 9 I think will be okay 10+ will be questionable due the change in API

> and jars that need upgrading for compatibility.

> 

> 

> On 1 October 2019 at 21:58:35, Chris Mattmann (mattm...@apache.org)

wrote:

> 

> OK so I need JDK8 to build, is that right?

> 

> 

> 

> 

> 

> 

> 

> From: Tom Barber 

> Reply-To: 

> Date: Tuesday, October 1, 2019 at 1:57 PM

> To: , Chris Mattmann , Imesha

> Sudasingha 

> Subject: Re: [VOTE] OODT 1.9 RC 4

> 

> 

> 

> Yeah, I’m amazed you got that far through with 12. I know from other apps

> 

> migrating from 8 through 12 is a right PITA and something we should look

at

> 

> for 2.0.

> 

> 

> 

> 

> 

> On 1 October 2019 at 21:48:08, Chris Mattmann (mattm...@apache.org)

wrote:

> 

> 

> 

> Pom shouldn’t be a blocker.

> 

> 

> 

> 

> 

> 

> 

> Here is my Java version am I using the right one?

> 

> 

> 

> 

> 

> 

> 

> pomodoro:oodt mattmann$ java -version

> 

> 

> 

> openjdk version "12.0.1" 2019-04-16

> 

> 

> 

> OpenJDK Runtime Environment (build 12.0.1+12)

> 

> 

> 

> OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)

> 

> 

> 

> pomodoro:oodt mattmann$

> 

> 

> 

> 

> 

> 

> 

> Should I switch?

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> From: Tom Barber 

> 

> Reply-To: 

> 

> Date: Tuesday, October 1, 2019 at 1:41 PM

> 

> To: , Imesha Sudasingha 

> 

> Subject: Re: [VOTE] OODT 1.9 RC 4

> 

> 

> 

> 

> 

> 

> 

> Results :

> 

> 

> 

> 

> 

> 

> 

> Tests run: 65, Failures: 0, Errors: 0, Skipped: 0

> 

> 

> 

> 

> 

> 

> 

> [INFO]

> 

> 

> 

> 

> 

> 

> 

> [INFO] BUILD SUCCESS

> 

> 

> 

> [INFO]

> 

> 

> 

> 

> 

> 

> 

> [INFO] Total time: 14.723 s

> 

> 

> 

> [INFO] Finished at: 2019-10-01T22:39:58+02:00

> 

> 

> 

> [INFO] Final Memory: 15M/353M

> 

> 

> 

> [INFO]

> 

> 

> 

> 

> 

> 

> 

> (superset) bugg@spicule-dev:~/oodt/commons>

> 

> 

> 

> 

> 

> 

> 

> So I can’t replicate Chris’ test failure either, and you’re right Imesha

> 

> 

> 

> the pom asc appears to be a copy of the pom, but I’ve not touched it so I

> 

> 

> 

> don’t know why that would be.

> 

> 

> 

> 

> 

> 

> 

> Does a missing pom asc mean a failed release? I’ve honestly no idea. It

> 

> 

> 

> would be easier to fix these in 2.x.

> 

> 

> 

> 

> 

> 

> 

> Tom

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> On 1 October 2019 at 19:36:43, Imesha Sudasingha (ime...@apache.org)

wrote:

> 

> 

> 

> 

> 

> 

> 

> Hi Tom,

> 

> 

> 

> 

> 

> 

> 

> Thanks for the release. Builds fine for me.

> 

> 

> 

> One concern: oodt-1.9.pom.asc seems to be a copy of the pom itself. Not

the

> 

> 

> 

> signature

> 

> 

> 

> 

> 

> 

> 

> Could you check that?

> 

> 

> 

> 

> 

> 

> 

> Thanks,

> 

> 

> 

> Imesha

> 

> 

> 

> 

> 

&

Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

OK so I need JDK8 to build, is that right?

 

 

 

From: Tom Barber 
Reply-To: 
Date: Tuesday, October 1, 2019 at 1:57 PM
To: , Chris Mattmann , Imesha 
Sudasingha 
Subject: Re: [VOTE] OODT 1.9 RC 4

 

Yeah, I’m amazed you got that far through with 12. I know from other apps

migrating from 8 through 12 is a right PITA and something we should look at

for 2.0.

 

 

On 1 October 2019 at 21:48:08, Chris Mattmann (mattm...@apache.org) wrote:

 

Pom shouldn’t be a blocker.

 

 

 

Here is my Java version am I using the right one?

 

 

 

pomodoro:oodt mattmann$ java -version

 

openjdk version "12.0.1" 2019-04-16

 

OpenJDK Runtime Environment (build 12.0.1+12)

 

OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)

 

pomodoro:oodt mattmann$

 

 

 

Should I switch?

 

 

 

 

 

From: Tom Barber 

Reply-To: 

Date: Tuesday, October 1, 2019 at 1:41 PM

To: , Imesha Sudasingha 

Subject: Re: [VOTE] OODT 1.9 RC 4

 

 

 

Results :

 

 

 

Tests run: 65, Failures: 0, Errors: 0, Skipped: 0

 

 

 

[INFO]

 



 

[INFO] BUILD SUCCESS

 

[INFO]

 



 

[INFO] Total time: 14.723 s

 

[INFO] Finished at: 2019-10-01T22:39:58+02:00

 

[INFO] Final Memory: 15M/353M

 

[INFO]

 



 

(superset) bugg@spicule-dev:~/oodt/commons>

 

 

 

So I can’t replicate Chris’ test failure either, and you’re right Imesha

 

the pom asc appears to be a copy of the pom, but I’ve not touched it so I

 

don’t know why that would be.

 

 

 

Does a missing pom asc mean a failed release? I’ve honestly no idea. It

 

would be easier to fix these in 2.x.

 

 

 

Tom

 

 

 

 

 

On 1 October 2019 at 19:36:43, Imesha Sudasingha (ime...@apache.org) wrote:

 

 

 

Hi Tom,

 

 

 

Thanks for the release. Builds fine for me.

 

One concern: oodt-1.9.pom.asc seems to be a copy of the pom itself. Not the

 

signature

 

 

 

Could you check that?

 

 

 

Thanks,

 

Imesha

 

 

 

On Tue, 1 Oct 2019 at 10:32, Chris Mattmann  wrote:

 

 

 

Release checks out, but I get a test error:

 

 

 

Running org.apache.oodt.commons.util.XMLTest

 

 

 

Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.323 sec

 

<<< FAILURE!

 

 

 

Running org.apache.oodt.commons.io.FixedBufferOutputStreamTest

 

 

 

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec

 

 

 

Running org.apache.oodt.commons.MultiServerTest

 

 

 

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec

 

 

 

Running org.apache.oodt.commons.util.Base64Test

 

 

 

Tests run: 1, Failures:

 

 

 

 

 

 

 

 

 

 

 

Here is the RC verify checksums and MD5, and SIG:

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ /Users/mattmann/bin/stage_apache_rc

 

apache-oodt 1.9-src https://dist.apache.org/repos/dist/dev/oodt/

 

 

 

% Total % Received % Xferd Average Speed Time Time Time

 

Current

 

 

 

Dload Upload Total Spent Left

 

Speed

 

 

 

100 14.6M 100 14.6M 0 0 1869k 0 0:00:08 0:00:08 --:--:--

 

1948k

 

 

 

% Total % Received % Xferd Average Speed Time Time Time

 

Current

 

 

 

Dload Upload Total Spent Left

 

Speed

 

 

 

100 473 100 473 0 0 2654 0 --:--:-- --:--:-- --:--:--

 

2657

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ ls

 

 

 

apache-oodt-1.9-src.zip apache-oodt-1.9-src.zip.asc

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_gpg_sigs

 

 

 

Verifying Signature for file apache-oodt-1.9-src.zip.asc

 

 

 

gpg: assuming signed data in 'apache-oodt-1.9-src.zip'

 

 

 

gpg: Signature made Mon Sep 30 06:40:14 2019 PDT

 

 

 

gpg: using RSA key AC57783AB30355CA

 

 

 

gpg: Can't check signature: No public key

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ curl -O

 

https://raw.githubusercontent.com/apache/oodt/master/KEYS

 

 

 

% Total % Received % Xferd Average Speed Time Time Time

 

Current

 

 

 

Dload Upload Total Spent Left

 

Speed

 

 

 

100 26954 100 26954 0 0 68787 0 --:--:-- --:--:-- --:--:--

 

68936

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEY

 

 

 

-bash: KEY: No such file or directory

 

 

 

pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEYS

 

 

 

gpg: key 70F09CC6B876884A: "Chris Mattmann (CODE SIGNING KEY) <

 

mattm...@apache.org>" not changed

 

 

 

gpg: key 170B657EF9D98BFA: public key "Sean Colin-Patrick Kelly (CODE

 

SIGNING KEY) " imported

 

 

 

gpg: key 11911679FF5B0BD5: public key "David Woollard (CODE SIGNING KEY)

 

< 

 

wooll...@apache.org>" imported

 

 

 

gpg: key A5DBC0182C47D568: public key "Paul Michael Ramirez (CODE SIGNING

 

KEY) " imported

 

 

 

gpg: key 7189700880EF652D: public key &quo

Re: [VOTE] OODT 1.9 RC 4

[Chris Mattmann]

Pom shouldn’t be a blocker.

 

Here is my Java version am I using the right one?

 

pomodoro:oodt mattmann$ java -version

openjdk version "12.0.1" 2019-04-16

OpenJDK Runtime Environment (build 12.0.1+12)

OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)

pomodoro:oodt mattmann$ 

 

Should I switch?

 

 

From: Tom Barber 
Reply-To: 
Date: Tuesday, October 1, 2019 at 1:41 PM
To: , Imesha Sudasingha 
Subject: Re: [VOTE] OODT 1.9 RC 4

 

Results :

 

Tests run: 65, Failures: 0, Errors: 0, Skipped: 0

 

[INFO]



[INFO] BUILD SUCCESS

[INFO]



[INFO] Total time: 14.723 s

[INFO] Finished at: 2019-10-01T22:39:58+02:00

[INFO] Final Memory: 15M/353M

[INFO]



(superset) bugg@spicule-dev:~/oodt/commons>

 

So I can’t replicate Chris’ test failure either, and you’re right Imesha

the pom asc appears to be a copy of the pom, but I’ve not touched it so I

don’t know why that would be.

 

Does a missing pom asc mean a failed release? I’ve honestly no idea. It

would be easier to fix these in 2.x.

 

Tom

 

 

On 1 October 2019 at 19:36:43, Imesha Sudasingha (ime...@apache.org) wrote:

 

Hi Tom,

 

Thanks for the release. Builds fine for me.

One concern: oodt-1.9.pom.asc seems to be a copy of the pom itself. Not the

signature

 

Could you check that?

 

Thanks,

Imesha

 

On Tue, 1 Oct 2019 at 10:32, Chris Mattmann  wrote:

 

Release checks out, but I get a test error:

 

Running org.apache.oodt.commons.util.XMLTest

 

Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.323 sec

<<< FAILURE!

 

Running org.apache.oodt.commons.io.FixedBufferOutputStreamTest

 

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec

 

Running org.apache.oodt.commons.MultiServerTest

 

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec

 

Running org.apache.oodt.commons.util.Base64Test

 

Tests run: 1, Failures:

 

 

 

 

 

Here is the RC verify checksums and MD5, and SIG:

 

pomodoro:apache-oodt-1.9 mattmann$ /Users/mattmann/bin/stage_apache_rc

apache-oodt 1.9-src https://dist.apache.org/repos/dist/dev/oodt/

 

% Total % Received % Xferd Average Speed Time Time Time

Current

 

Dload Upload Total Spent Left

Speed

 

100 14.6M 100 14.6M 0 0 1869k 0 0:00:08 0:00:08 --:--:--

1948k

 

% Total % Received % Xferd Average Speed Time Time Time

Current

 

Dload Upload Total Spent Left

Speed

 

100 473 100 473 0 0 2654 0 --:--:-- --:--:-- --:--:--

2657

 

pomodoro:apache-oodt-1.9 mattmann$ ls

 

apache-oodt-1.9-src.zip apache-oodt-1.9-src.zip.asc

 

pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_gpg_sigs

 

Verifying Signature for file apache-oodt-1.9-src.zip.asc

 

gpg: assuming signed data in 'apache-oodt-1.9-src.zip'

 

gpg: Signature made Mon Sep 30 06:40:14 2019 PDT

 

gpg: using RSA key AC57783AB30355CA

 

gpg: Can't check signature: No public key

 

pomodoro:apache-oodt-1.9 mattmann$ curl -O

https://raw.githubusercontent.com/apache/oodt/master/KEYS

 

% Total % Received % Xferd Average Speed Time Time Time

Current

 

Dload Upload Total Spent Left

Speed

 

100 26954 100 26954 0 0 68787 0 --:--:-- --:--:-- --:--:--

68936

 

pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEY

 

-bash: KEY: No such file or directory

 

pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEYS

 

gpg: key 70F09CC6B876884A: "Chris Mattmann (CODE SIGNING KEY) <

mattm...@apache.org>" not changed

 

gpg: key 170B657EF9D98BFA: public key "Sean Colin-Patrick Kelly (CODE

SIGNING KEY) " imported

 

gpg: key 11911679FF5B0BD5: public key "David Woollard (CODE SIGNING KEY)

< 

wooll...@apache.org>" imported

 

gpg: key A5DBC0182C47D568: public key "Paul Michael Ramirez (CODE SIGNING

KEY) " imported

 

gpg: key 7189700880EF652D: public key "Andrew Hart (CODE SIGNING KEY) <

ah...@apache.org>" imported

 

gpg: key D8167171783CE7BB: public key "Tom Barber (CODE SIGNING KEY) <

magicaltr...@apache.org>" imported

 

gpg: key 4EAAF8B60C1E654B: "Chris Mattmann (CODE SIGNING KEY - Apr 2016)

< 

mattm...@apache.org>" not changed

 

gpg: key 2B12271BFD01FEDB: "Chris Mattmann " not

changed

 

gpg: key AC57783AB30355CA: public key "Tom Barber "

 

imported

 

gpg: Total number processed: 9

 

gpg: imported: 6

 

gpg: unchanged: 3

 

pomodoro:apache-oodt-1.9 mattmann$ ls

 

KEYS apache-oodt-1.9-src.zip

apache-oodt-1.9-src.zip.asc

 

pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_gpg_sigs

 

Verifying Signature for file apache-oodt-1.9-src.zip.asc

 

gpg: assuming signed data in 'apache-oodt-1.9-src.zip'

 

gpg: Signature made Mon Sep 30 06:40:

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC3

[Chris Mattmann]

I'm getting a similar test error, see here:

 

[INFO] --- maven-surefire-plugin:2.4:test (default-test) @ oodt-commons ---

[INFO] Surefire report directory: 
/Users/mattmann/git/oodt/commons/target/surefire-reports

 

---

 T E S T S

---

Running org.apache.oodt.commons.activity.ActivityTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec

Running org.apache.oodt.commons.util.EnterpriseEntityResolverTest

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.165 sec

Running org.apache.oodt.commons.util.LDAPTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec

Running org.apache.oodt.commons.io.NullOutputStreamTest

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec

Running org.apache.oodt.commons.util.CacheMapTest

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec

Running org.apache.oodt.commons.activity.ActivityStoppedTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.124 sec

Running org.apache.oodt.commons.net.NetTest

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec

Running org.apache.oodt.commons.util.XMLTest

Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.316 sec <<< 
FAILURE!

Running org.apache.oodt.commons.io.FixedBufferOutputStreamTest

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec

Running org.apache.oodt.commons.MultiServerTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.188 sec

Running org.apache.oodt.commons.util.Base64Test

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec

Running org.apache.oodt.commons.AppTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec

Running org.apache.oodt.commons.io.NullInputStreamTest

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec

Running org.apache.oodt.commons.exec.TestEnvUtilities

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec

Running org.apache.oodt.commons.filter.TestTimeEventWeightedHash

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec

Running org.apache.oodt.commons.activity.HistoryTest

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.878 sec

Running org.apache.oodt.commons.ConfigurationTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.188 sec

Running org.apache.oodt.commons.activity.IncidentTest

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec

Running org.apache.oodt.commons.io.TestLoggerOutputStream

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec

Running org.apache.oodt.commons.activity.CompositeActivityTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec

Running org.apache.oodt.commons.AvroMultiServerTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.211 sec

Running org.apache.oodt.commons.object.jndi.ObjectContextTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec

Running org.apache.oodt.commons.ConfiguredTestCaseTest

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.289 sec

Running org.apache.oodt.commons.activity.DatagramLoggingActivityFactoryTest

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.102 sec

Running org.apache.oodt.commons.util.UtilityTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec

Running org.apache.oodt.commons.io.DirectorySelectorTest

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec

Running org.apache.oodt.commons.NaughtyTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.03 sec

Running org.apache.oodt.commons.object.jndi.TestContextTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec

Running org.apache.oodt.commons.activity.ActivityTrackerTest

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec

 

Results :

 

Failed tests: 

 

Tests run: 65, Failures: 1, Errors: 0, Skipped: 0

 

[INFO] 

[INFO] Reactor Summary for Apache OODT 1.9:

[INFO] 

[INFO] OODT Core .. SUCCESS [  2.244 s]

[INFO] Common Utilities ... FAILURE [ 19.069 s]

[INFO] CAS Command Line Interface . SKIPPED

[INFO] OODT - Configuration Management  SKIPPED

[INFO] Process Control System Input Data Package .. SKIPPED

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SKIPPED

[INFO] Catalog and Archive File Management Component .. SKIPPED

[INFO] Catalog and Archive Resource Management Component .. SKIPPED

[INFO] Catalog and Archive 

Re: [EXTERNAL] Re: OODT 1.9 / 2.0

[Chris Mattmann]

+1

 

 

 

From: Tom Barber 
Reply-To: "d...@drat.apache.org" 
Date: Tuesday, September 17, 2019 at 1:42 PM
To: "d...@drat.apache.org" 
Subject: [EXTERNAL] Re: OODT 1.9 / 2.0

 

Yeah DRAT 1.0 with 1.9, then 2.x in line with OODT 2.x and Breno’s UI

updates and stuff which I know he’s got on standby.

 

 

On 17 September 2019 at 21:25:10, Chris Mattmann (mattm...@apache.org)

wrote:

 

Perfect looking forward to reviewing it along with DRAT 1.0. Though on the

DRAT side

 

CC’ing them BTW I think we should ship 1.x DRAT with OODT 1.9.x…and then

DRAT 2.x should

be with Avro and the new stuff.

 

 

 

Cheers,

 

Chris

 

 

 

 

 

 

 

From: Tom Barber 

Reply-To: 

Date: Tuesday, September 17, 2019 at 12:46 PM

To: 

Subject: OODT 1.9 / 2.0

 

 

 

Hey folks,

 

 

 

I’ve finally cleared my decks of a bunch of stuff taking up too much of my

 

time, with that done, I’d like to volunteer to be the RM for 1.9 and

 

following that a 2.0 release.

 

 

 

If no one objects I’ll start working to a 1.9 release next week so we can

 

ship DRAT as well and get them both out the door.

 

 

 

Tom

 

 

 

-- 

 

 

 

 

 

Spicule Limited is registered in England & Wales. Company Number:

 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

 

 

 

 

 

All engagements

 

are subject to Spicule Terms and Conditions of Business. This email and its

 

contents are intended solely for the individual to whom it is addressed and

 

may contain information that is confidential, privileged or otherwise

 

protected from disclosure, distributing or copying. Any views or opinions

 

presented in this email are solely those of the author and do not

 

necessarily represent those of Spicule Limited. The company accepts no

 

liability for any damage caused by any virus transmitted by this email. If

 

you have received this message in error, please notify us immediately by

 

reply email before deleting it from your system. Service of legal notice

 

cannot be effected on Spicule Limited by email.

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: [GSOC] OODT docker build meeting summary

[Chris Mattmann]

The requirements for the scripts are:

 
Filemanager as a component must work without docker, and without
RADIX, so any changes to that core script need to satisfy that. 
Additionally Filemanager has no dependencies on workflow, other
envs, or resource, etc., so any updates to the FM script in the core 
FM component would need to respect that
RADIX on the other hand, depends on everything, env variables, everything
else, the core package. Given that, it makes sense to have its filemgr script
be different and part of something bigger.
 

Does this make sense?

 

Cheers,

Chris

 

 

 

 

From: Imesha Sudasingha 
Reply-To: 
Date: Wednesday, June 5, 2019 at 11:08 PM
To: dev , Chris Mattmann 
Subject: Re: [GSOC] OODT docker build meeting summary

 

Hi Yasith,

 

Thanks for the meeting notes. Regarding those two questions,

 

1. Yes, I have noticed that those scripts are out of sync. But, we cannot

make those two even directly since, the script within Radix is supposed to

be run by another shell script which exports some variables like OODT_HOME,

RUN_JAVA. In contrast, shell script within filmgr module is supposed to be

run in standalone mode. Therefore, if we are to sync those two scripts,

only possibility is to add any missing lines and etc. @Chris Mattmann

 what is your opinion on this?

 

2. They should definitely be updated. Could you create Jira issues for

those pom files (one issue containing all pom files will be enough)? It

will be great if you can send a fix for that as well.

 

Thanks,

Imesha

 

On Tue, 4 Jun 2019 at 22:20, Jayawardana, Yasith  wrote:

 

Hi All,

 

Here are the meeting minutes from the discussion today with Imesha, and

the discussion last week with Tom.

 

 

05/28 - GSOC Meeting [with Tom] (9 AM EST)

 

   *   Status

  *   I have created the DMB repository before the meeting as first

step, and plan to add the dockerfile-maven plugin next.

   *   Discussion

  *   Set default docker image name to project build name and the

default tag to project version

  *   Run the shell script for file manager in docker container and see

fix errors.

  *   Also create a diagram indicating which components depend on the

others so that others can benefit.

  *   Goal for the week is to get to a stage where dockerfile maven

generates the docker image, and filemgr can run in it without errors

 

 

06/04 - GSOC Meeting [with Imesha] (9 AM EST)

 

   *   Status

  *   I created a dockerfile for filemgr and made a few changes to the

filemgr script, so that filemgr start works inside docker as well. Now the

maven build process generates a docker image from the dockerfile at the

package phase, and I’m able to start it without encountering any issues.

   *   Discussion

  *   Instead of running the shell script, run the command directly in

Dockerfile. Makes things easier.

  *   For the development purposes, create the docker images on the

default build profile itself. Later move them to a separate profile.

  *   Once the image works and confirmed running well, discuss with

others on which directories should be mounted in volumes.

 

There are also a few concerns that I forgot to discuss on today’s meeting

which I want to mention.

 

   *   I saw that filemgr shell script inside radix is different from the

one in core distribution. Is this intentional or is it a bug?

   *   I saw some plugin versions in pom files are beta (especially

maven-assembly-plugin). Shouldn’t these be updated to non-beta versions?

 

Appreciate any suggestions on these.

 

Best Regards,

Yasith Jayawardana

 

 

On May 27, 2019, at 10:04 PM, Jayawardana, Yasith mailto:yas...@cs.odu.edu>> wrote:

 

[MEETING NOTES - 05/21/2019]

 

 

  *   As the first step of the project, create a new repository from the

RADIX build.

  *   Customize it such that it creates Docker Images at “mvn install”, and

publishes them to DockerHub at “mvn deploy”.

  *   To achieve this, the first component that should be containerized is

OODT file manager, as it contains the least dependencies on other

components of OODT.

  *   Maven assembly plugin is used at the "mvn build" stage. Therefore,

the docker image creation should happen in a later stage. i.e. “mvn

install” stage.

  *   Use the tar.gz file created from the maven assembly plugin as the

source for generating the docker image for that component.

  *   The docker image creation should not be enabled by default, and

should be designed as an optional output. User should be able to configure

the credentials of DockerHub, etc somewhere in the build step.

 

Apologies for taking long to post this update.

 

[PROGRESS UPDATE]

So far, I created a new repository (

https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyasithmilinda%2Foodt-dmbdata=02%7C01%7Cyasith%40cs.odu.edu%7C562ed13a48344223267608d6e310e8ac%7C48bf86e811a24b8a8cb368d8be2227f3%7C0%7C0%7C6369460

Re: [EXTERNAL] GSOC Projects

[Chris Mattmann]

Welcome to the party!

 

Cheers,

Chris Mattmann

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, May 6, 2019 at 11:07 AM
To: "dev@oodt.apache.org" 
Subject: [EXTERNAL] GSOC Projects

 

Just a quick note to say congrats and welcome to Nadeeshan and Yasith as

both of their GSOC proposals got approved.

 

For those not paying attention assuming that we are successful then we’ll

have a bunch of new work done on a new React based OPSUI and a new Docker

(K8S) deployment technique to bring OODT to Kubernetes for large scale

deployments.

 

Thanks to you both for taking the time to submit the proposals and good

luck!

 

Tom

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: [EXTERNAL] What is where?

[Chris Mattmann]

Development and master should be sync’ed and are version 1.9-dev
Release of 1.9-dev is blocked on testing Avro in DRAT – I’ll get it done this 
week promise! ;)
Once tested AvroRPC in DRAT, we are good to release 1.9-dev (will include 
AvroRPC AND Xml-RPC
with Avro as default)
Last release with XML-RPC
Post 1.9-dev release, update master to 2.0-dev
2.0-dev should remove XML-RPC as an option
2.0 first release includes no XML-RPC
 

Let’s set a deadline of 2 weeks to get 1-3 done. 

That’s it ☺ Deal?

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, April 1, 2019 at 12:25 PM
To: "dev@oodt.apache.org" 
Subject: [EXTERNAL] What is where?

 

Hello folks,

 

I have to admit with the OODT code I’m a bit lost and I figure we could do

with a clean up prior to GSOC if we get that approved.

 

What branches are stuff on?

 

Can we merge everything into a stable & dev branch and close down a load of

the old ones?

 

Where are we with making Avro the default?

 

 

Cheers

 

Tom

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: [EXTERNAL] GSoC 2019 mentor request for Tom Barber

[Chris Mattmann]

ACK

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, March 12, 2019 at 2:44 PM
To: "ment...@community.apache.org" , 
"dev@oodt.apache.org" 
Subject: [EXTERNAL] GSoC 2019 mentor request for Tom Barber

 

OODT PMC,

 

please acknowledge my request to become a mentor for Google Summer of Code

2018 projects for Apache OODT.

 

I would like to receive the mentor invite to t...@spicule.co.uk

 

Lets make OODT amazing!

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: Updating Workflow Status to Post-Ingest

[Chris Mattmann]

I think it needs to be “ProductTypeName” specifically so try changing the
met field name to exactly that, and yes it needs to be GenericFileIngest.

So you want basically an event named that in events.xml and then you want
to map that to the workflow you want it to automatically kick off in the 
event-to-worfklow-map.xml.

 

 

 

From: Lewis John McGibbney 
Reply-To: 
Date: Tuesday, December 4, 2018 at 10:43 AM
To: 
Subject: Re: Updating Workflow Status to Post-Ingest

 

Hi Chris,

 

On 2018/12/04 16:51:35, Chris Mattmann  wrote: 

Do you have a workflow with the name [ProductTypeName]Ingest?

 

No I do not. Is the key within the square brackets a variable e.g. would it 
look like 'GenericFileIngest'?

I'm not entirely sure how and where to define this.

 

Is ProductTypeName one of the extracted metadata fields? 

 

In my Solr Catalog every record ends up with a field '"CAS.ProductTypeName": 
"GenericFile",' however I will most likely change this from 'GenericFile' to 
something more specific and relevant e.g. 'AVIRIS-NGDataFile', for each crawler 
daemon I have set up. This can be set in tika.conf.

 

If not, then

that part will be null when it goes to look it up in the crawler. Please check.

 

Is my above understanding correct?

Thanks

 

Re: Updating Workflow Status to Post-Ingest

[Chris Mattmann]

Do you have a workflow with the name [ProductTypeName]Ingest?

Is ProductTypeName one of the extracted metadata fields? If not, then
that part will be null when it goes to look it up in the crawler. Please check.

 

Thanks,

Chris

 

 

From: Lewis John McGibbney 
Reply-To: 
Date: Tuesday, December 4, 2018 at 8:40 AM
To: 
Subject: Re: Updating Workflow Status to Post-Ingest

 

The current state of my PGE and Workflow policy can be seen at

https://github.com/capstone-coal/coal-sds/tree/master/workflow/src/main/resources/policy

 

On 2018/12/04 05:11:02, lewis john mcgibbney  wrote: 

Hi Folks,

Whilst executing the following command

./crawler/bin/crawler_launcher \

   --filemgrUrl http://localhost:9000 \

   --operation --launchMetCrawler \

   --clientTransferer

org.apache.oodt.cas.filemgr.datatransfer.LocalDataTransferFactory \

   --productPath /usr/local/coal-sds-deploy/data/staging \

   --metExtractor

org.apache.oodt.cas.metadata.extractors.TikaCmdLineMetExtractor \

   --metExtractorConfig /usr/local/coal-sds-deploy/data/met/tika.conf \

   --failureDir /usr/local/coal-sds-deploy/data/failure \

   --daemonPort 9003 \

   --daemonWait 2 \

   --successDir /usr/local/coal-sds-deploy/data/archive \

   --actionIds DeleteDataFile UpdateWorkflowStatusToIngest \

   --workflowMgrUrl http://localhost:9001

As you can see, I am trying to kick off a workflow post a successful file

ingestion task. The error I'm getting is as follows

INFO: Performing action (id = UpdateWorkflowStatusToIngest : description =

Triggers workflow event with the name [ProductType]Ingest)

21:00:22.537 [main] DEBUG

org.apache.oodt.cas.workflow.system.rpc.RpcCommunicationFactory - Using

workflow manager client factory : class

org.apache.oodt.cas.workflow.system.rpc.AvroRpcWorkflowManagerFactory

21:00:22.549 [main] INFO

org.apache.oodt.cas.workflow.system.AvroRpcWorkflowManagerClient - Client

created successfully for workflow manager URL: http://localhost:9001

Dec 03, 2018 9:00:22 PM org.apache.oodt.cas.crawl.ProductCrawler

performProductCrawlerActions

WARNING: Failed to perform crawler action : Action (id =

UpdateWorkflowStatusToIngest : description = Triggers workflow event with

the name [ProductType]Ingest) returned false

java.lang.Exception: Action (id = UpdateWorkflowStatusToIngest :

description = Triggers workflow event with the name [ProductType]Ingest)

returned false

 at

org.apache.oodt.cas.crawl.ProductCrawler.performProductCrawlerActions(ProductCrawler.java:362)

 at

org.apache.oodt.cas.crawl.ProductCrawler.performPostIngestOnSuccessActions(ProductCrawler.java:334)

 at

org.apache.oodt.cas.crawl.ProductCrawler.handleFile(ProductCrawler.java:198)

 at

org.apache.oodt.cas.crawl.ProductCrawler.crawl(ProductCrawler.java:109)

 at

org.apache.oodt.cas.crawl.ProductCrawler.crawl(ProductCrawler.java:76)

 at

org.apache.oodt.cas.crawl.daemon.CrawlDaemon.startCrawling(CrawlDaemon.java:84)

 at

org.apache.oodt.cas.crawl.cli.action.CrawlerLauncherCliAction.execute(CrawlerLauncherCliAction.java:56)

 at

org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:331)

 at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:188)

 at

org.apache.oodt.cas.crawl.CrawlerLauncher.main(CrawlerLauncher.java:37)

I have configured workflow manager and have a PGE named 'pycoal-pge' which

includes several tasks. I am just not sure how to reference it from the

crawler_launcher input parameters.

Any ideas? Thanks in advance,

Lewis

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: Updating Workflow Status to Post-Ingest

[Chris Mattmann]

Probably a good idea to read this too:

https://cwiki.apache.org/confluence/display/OODT/Understanding+the+flow+of+Metadata+during+PGE+based+Processing
 

https://cwiki.apache.org/confluence/display/OODT/Understanding+CAS-PGE+Metadata+Precendence


 

From: Lewis John McGibbney 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, December 4, 2018 at 8:40 AM
To: "dev@oodt.apache.org" 
Subject: Re: Updating Workflow Status to Post-Ingest

 

The current state of my PGE and Workflow policy can be seen at

https://github.com/capstone-coal/coal-sds/tree/master/workflow/src/main/resources/policy

 

On 2018/12/04 05:11:02, lewis john mcgibbney  wrote: 

Hi Folks,

Whilst executing the following command

./crawler/bin/crawler_launcher \

   --filemgrUrl http://localhost:9000 \

   --operation --launchMetCrawler \

   --clientTransferer

org.apache.oodt.cas.filemgr.datatransfer.LocalDataTransferFactory \

   --productPath /usr/local/coal-sds-deploy/data/staging \

   --metExtractor

org.apache.oodt.cas.metadata.extractors.TikaCmdLineMetExtractor \

   --metExtractorConfig /usr/local/coal-sds-deploy/data/met/tika.conf \

   --failureDir /usr/local/coal-sds-deploy/data/failure \

   --daemonPort 9003 \

   --daemonWait 2 \

   --successDir /usr/local/coal-sds-deploy/data/archive \

   --actionIds DeleteDataFile UpdateWorkflowStatusToIngest \

   --workflowMgrUrl http://localhost:9001

As you can see, I am trying to kick off a workflow post a successful file

ingestion task. The error I'm getting is as follows

INFO: Performing action (id = UpdateWorkflowStatusToIngest : description =

Triggers workflow event with the name [ProductType]Ingest)

21:00:22.537 [main] DEBUG

org.apache.oodt.cas.workflow.system.rpc.RpcCommunicationFactory - Using

workflow manager client factory : class

org.apache.oodt.cas.workflow.system.rpc.AvroRpcWorkflowManagerFactory

21:00:22.549 [main] INFO

org.apache.oodt.cas.workflow.system.AvroRpcWorkflowManagerClient - Client

created successfully for workflow manager URL: http://localhost:9001

Dec 03, 2018 9:00:22 PM org.apache.oodt.cas.crawl.ProductCrawler

performProductCrawlerActions

WARNING: Failed to perform crawler action : Action (id =

UpdateWorkflowStatusToIngest : description = Triggers workflow event with

the name [ProductType]Ingest) returned false

java.lang.Exception: Action (id = UpdateWorkflowStatusToIngest :

description = Triggers workflow event with the name [ProductType]Ingest)

returned false

 at

org.apache.oodt.cas.crawl.ProductCrawler.performProductCrawlerActions(ProductCrawler.java:362)

 at

org.apache.oodt.cas.crawl.ProductCrawler.performPostIngestOnSuccessActions(ProductCrawler.java:334)

 at

org.apache.oodt.cas.crawl.ProductCrawler.handleFile(ProductCrawler.java:198)

 at

org.apache.oodt.cas.crawl.ProductCrawler.crawl(ProductCrawler.java:109)

 at

org.apache.oodt.cas.crawl.ProductCrawler.crawl(ProductCrawler.java:76)

 at

org.apache.oodt.cas.crawl.daemon.CrawlDaemon.startCrawling(CrawlDaemon.java:84)

 at

org.apache.oodt.cas.crawl.cli.action.CrawlerLauncherCliAction.execute(CrawlerLauncherCliAction.java:56)

 at

org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:331)

 at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:188)

 at

org.apache.oodt.cas.crawl.CrawlerLauncher.main(CrawlerLauncher.java:37)

I have configured workflow manager and have a PGE named 'pycoal-pge' which

includes several tasks. I am just not sure how to reference it from the

crawler_launcher input parameters.

Any ideas? Thanks in advance,

Lewis

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: Question about Dynamic Workflows

[Chris Mattmann]

Lewis, check out DRAT’s PGE config. I think you will find good help there. 

Also you can use the ConfigFileWriter (there is a template one, for an example
I will dig one up and commit one from one of our airborne missions).

 

 

 

From: lewis john mcgibbney 
Reply-To: "dev@oodt.apache.org" 
Date: Thursday, November 29, 2018 at 2:12 PM
To: "dev@oodt.apache.org" 
Subject: Question about Dynamic Workflows

 

Hi dev@,

I am working on a PGE which will essentially execute a (Python) command

line tool but i am struggling with definition of parameters from the input

data product to the PGE XML definition. Specifically I am not sure of how

to map the product name to an input parameter for the command line tool

invocation.

The following PGE configuration snippet shows this

 

...



 

  

pycoal-mineral ${flag#1} ${parameter#1} ${flag#2} ${parameter#2}

${flag#3} ${parameter#3} ...

  

 

In the above example ${flag#1} would be something like '-i' and the

parameter value should be the name of a data product which has already been

catalogued and archived to a success directory during a previous data

acquisition task.

 

The full CLI command execution would ultimately look something like the

following

 

pycoal-mineral \

  --image /usr/local/pycoal_data/

avng.jpl.nasa.gov/AVNG_2015_data_distribution/L2/ang20150420t182050_rfl_v1e/ang20150420t182050_corr_v1e_img.hdr

\

  --slib /usr/local/pycoal/pycoal/tests/s07_AV95_envi.hdr \

  --rgb_filename ang20150420t182050_corr_v1e_img_rgb.hdr

  --classified_filename ang20150420t182050_corr_v1e_img_mineral.hdr

  --algorithm SAM

 

I need to

 

   1. automatically infer the 1st parameter value for '--image' from the

   input data file which has been processed and archived to a specific

   directory

   2. infer the 3rd parameter value for '--rgb_filename' from the 1st

   parameter and edit it slightly, and

   3. infer the 4th parameter value for '--classified_filename' from the

   1st parameter and edit it slightly

 

Thanks for any help folks I really appreciate it.

Lewis

 

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: Deprecated File.toURL() and issues with space characters in paths

[Chris Mattmann]

Let’s add some unit tests to expose the issue, and then with your PR you can 
have your
fix show that it makes those unit tests pass. Let’s try that?

 

 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, November 6, 2018 at 8:06 PM
To: dev 
Subject: Re: Deprecated File.toURL() and issues with space characters in paths

 

Hi Madhawa,

 

Thanks for pointing this issue out.

 

IMO this is an issue which should be fixed in order to make sure that new

comers are not experiencing failures/difficulties in the first go (since

you too got blocked in the first attempt) and in overall for the stability

of OODT.

 

However, I would like if a more experienced member comment his/her opinion

on fixing this issue.

@Chris, @Tom what do you think?

 

Thanks,

Imesha

 

 

 

 

On Mon, 5 Nov 2018 at 21:56, Madhawa Vidanapathirana <

madhawavidanapathir...@gmail.com> wrote:

 

Hi,

I am Madhawa, a recent graduate from Department of Computer Science and

Engineering, University of Moratuwa, Sri Lanka. I am new to Apache OODT and

I thought of starting off with the file manager module. However, from the

very beginning, I had trouble due to space characters in paths and I am

interested in fixing these issues.

 

I already fixed a space character related issue [1] on the start script of

filemgr, which is now merged. Afterward, I realized that when the

repository path contains space characters, ingest operations fail. After

observing the code, I identified that this error occurs because the

method *File.toURL

(which is now deprecated) fails to automatically escape illegal characters

in paths*. This deprecated method is used in multiple places of the

codebase and I raised the issue [2] mentioning this situation.

 

As a solution to the above issue, JAVADOC [3] recommends to first convert

the File to a URI (using File.toURI() method) and then convert the URI to a

URL (using URI.toURL() method). *Before going forward, since this code

change affects multiple areas of the code, I would like to know suggestions

and comments from the community on this approach.*

 

My plan is to clone the project to a path with space characters and run

unit tests to validate the fix. However, it seems this approach is not so

trivial since some of the unit tests are written under the assumption that

space characters would not appear in paths. Therefore, *we may have to

modify those unit tests as well. *

 

I would like to know your opinion on above-mentioned approaches to fix the

issue and modify the unit tests

 

[1] - https://issues.apache.org/jira/projects/OODT/issues/OODT-998

[2] - https://issues.apache.org/jira/projects/OODT/issues/OODT-999

[3] - https://docs.oracle.com/javase/7/docs/api/java/io/File.html#toURL()

 

Kind Regards

 

*Madhawa Vidanapathirana*

Department of Computer Science and Engineering

University of Moratuwa

Sri Lanka

 

Mobile: (+94) 716874425

Email: madhawavidanapathir...@gmail.com

Linked-In: *https://www.linkedin.com/in/madhawav/

*

 

 

Re: Forcing invocation of specific Tika parser when running TikaCmdLineMetExtractor

[Chris Mattmann]

Hmm if your mime-types.xml in Tika has that MIME format it should call the 
right parser.

 

Alternatives:

 

Try the AutoDetectCrawler where you can feed it your own MIME repo mapping.

Use the ExternMetExtractor and wire it up to call Tika from the command line or 
tika-python and then customize as needed

 

Cheers,

Chris

 

 

 

 

From: lewis john mcgibbney 
Reply-To: "dev@oodt.apache.org" 
Date: Thursday, October 18, 2018 at 9:41 PM
To: "dev@oodt.apache.org" 
Subject: Forcing invocation of specific Tika parser when running 
TikaCmdLineMetExtractor

 

Hi Folks,

I asked a similar question a while back but I don't think I

communicated it clearly enough.

I'm running the crawler_launcher as follows

 

./crawler_launcher --filemgrUrl http://localhost:9000 --operation

--launchMetCrawler --clientTransferer

org.apache.oodt.cas.filemgr.datatransfer.InPlaceDataTransferFactory

--productPath /usr/local/coal-sds-deploy/data/staging --metExtractor

org.apache.oodt.cas.metadata.extractors.TikaCmdLineMetExtractor

--metExtractorConfig

/usr/local/coal-sds-deploy/crawler/etc/tika_aviris_hdr.properties

 

The project is parsers and ingested into File Manager, however Tika only

uses the org.apache.tika.parser.DefaultParser... which is not sufficient as

I am working with application/envi.hdr files which are rich in metadata.

 

The --metExtractorConfig file contains the following primitive metadata

 

ProductType=GenericFile

Content-type=application/envi.hdr

 

And yes the 'Content-type=application/envi.hdr' is successfully added to

the metadata record in File Manager. I am just not sure how to force Tika

to invoke a specific parser.

 

Thanks for any help,

Lewis

 

 

 

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: [jira] [Created] (OODT-997) JAXRS endpoints broken

[Chris Mattmann]

Ahh, good to hear. Please fix…why would this break though since it worked 
before?

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, October 15, 2018 at 4:40 PM
To: "dev@oodt.apache.org" , Chris Mattmann 

Subject: Re: [jira] [Created] (OODT-997) JAXRS endpoints broken

 

Hmm its a ClassNotFound exception.

 

If I update CXF to the latest 3.2.6 it works without any changes to my

deployment.

 

 

On 15 October 2018 at 23:13:34, Chris Mattmann (mattm...@apache.org) wrote:

 

You’re missing an env var, see here:

 

https://github.com/apache/drat/wiki/Installation#bash

 

 

 

FMPROD*

 

 

 

Cheers,

 

Chris

 

 

 

 

 

From: "Tom Barber (JIRA)" 

Reply-To: "dev@oodt.apache.org" 

Date: Monday, October 15, 2018 at 3:12 PM

To: "dev@oodt.apache.org" 

Subject: [jira] [Created] (OODT-997) JAXRS endpoints broken

 

 

 

Tom Barber created OODT-997:

 

---

 

 

 

Summary: JAXRS endpoints broken

 

Key: OODT-997

 

URL: https://issues.apache.org/jira/browse/OODT-997

 

Project: OODT

 

Issue Type: Bug

 

Reporter: Tom Barber

 

Assignee: Tom Barber

 

 

 

 

 

Calling something like:

 

 

 

 

 

 

 

:8080/fmprod/jaxrs/product?productID=ad4b2df4-d0c5-11e8-90f6-ad8c0b53f3f7

 

 

 

Throws:

 

 

 

 

 

 

 

javax.servlet.ServletException: No Resource class

org.apache.cxf.jaxrs.provider.json.JSONProvider, can be found

org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.loadClass(CXFNonSpringJaxrsServlet.java:392)

org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.loadClass(CXFNonSpringJaxrsServlet.java:385)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

-- 

 

This message was sent by Atlassian JIRA

 

(v7.6.3#76005)

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: [jira] [Created] (OODT-997) JAXRS endpoints broken

[Chris Mattmann]

You’re missing an env var, see here:

https://github.com/apache/drat/wiki/Installation#bash 

 

FMPROD*

 

Cheers,

Chris

 

 

From: "Tom Barber (JIRA)" 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, October 15, 2018 at 3:12 PM
To: "dev@oodt.apache.org" 
Subject: [jira] [Created] (OODT-997) JAXRS endpoints broken

 

Tom Barber created OODT-997:

---

 

 Summary: JAXRS endpoints broken 

 Key: OODT-997

 URL: https://issues.apache.org/jira/browse/OODT-997

 Project: OODT

  Issue Type: Bug

Reporter: Tom Barber

Assignee: Tom Barber

 

 

Calling something like:

 

 

 

:8080/fmprod/jaxrs/product?productID=ad4b2df4-d0c5-11e8-90f6-ad8c0b53f3f7

 

Throws:

 

 

 

javax.servlet.ServletException: No Resource class 
org.apache.cxf.jaxrs.provider.json.JSONProvider, can be found 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.loadClass(CXFNonSpringJaxrsServlet.java:392)
 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.loadClass(CXFNonSpringJaxrsServlet.java:385)

 

 

 

 

 

 

 

 

 

--

This message was sent by Atlassian JIRA

(v7.6.3#76005)

 

Re: OODT docker builds

[Chris Mattmann]

Interesting OK. B/c the more containers for me on my local laptop 
typically eat up way more memory and CPU…but maybe that’s just
me on a Mac lol

 

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, October 15, 2018 at 9:44 AM
To: Imesha Sudasingha , Chris Mattmann 

Cc: dev 
Subject: Re: OODT docker builds

 

Not at all and if you want to run OODT on Kubernetes for example, that

would be how you’d do it, that way you can upgrade, scale, restart and fail

components without the entire stack falling over.

 

In terms of disk space, don’t forget each image is built on layers, so for

example, openjdk-8 on alpine is 56mb, that layer would then be used across

all base images so its only installed once on each host, then you’ve got

your file manager for example which would check in currently at 62MB, so

the entire image size would be 118MB which you could then deploy on 1 node,

or 100 nodes.

 

Then say you’ve got opsui as another dependency, that would be

 

tomcat:8 (463mb)+ opsui(73mb)==536mb

 

But say you have no interest in workflow etc, thats all you’d deploy.

 

In reality it would be much more flexible and much more inline with how

docker containers should be deployed,  which is as a single process

container not as a bunch of processes all stuck into 1 unit.

 

 

 

 

 

On 15 October 2018 at 17:32:32, Chris Mattmann (mattm...@apache.org) wrote:

 

Isn’t an image per component really heavyweight?

 

 

 

 

 

 

 

*From: *Tom Barber 

*Date: *Monday, October 15, 2018 at 8:26 AM

*To: *Imesha Sudasingha 

*Cc: *dev , Chris Mattmann 

*Subject: *Re: OODT docker builds

 

 

 

Why aren’t we doing so?! :)

 

 

 

Lack of cycles and young kids ;)

 

 

 

I’ll take a stab at it and see where we get to outside of RADIX to get the

stack in distinct containers and then we’ll look at integrating it into the

main build then.

 

 

 

 

 

Tom

 

 

 

On 15 October 2018 at 13:07:56, Imesha Sudasingha (imesha...@cse.mrt.ac.lk)

wrote:

 

Yes. Agree with you. That is something I have been planning to ask you for

long; why aren't we doing so.

 

I like the idea of having a docker image per component and as you suggested

we can create docker-compose

 

or kubernetes setup for deployments. I like that direction ;-)

 

 

 

As an starting point, we can add an all-in-one docker image to be built in

the RADIX build, right?

 

If you start off, I will be able to join you along the way.

 

 

 

Thanks,

 

Imesha

 

 

 

 

 

 

 

On Mon, 15 Oct 2018 at 16:33, Tom Barber  wrote:

 

I was thinking about the outputs. Currently everything is 1 docker file

which is fine for some deployments and not for others.

 

 

 

In the RADIX build we should also build individual containers for each

component. For the deployment we could also have a docker-compose file and

a K8S Helm setup so that you could deploy a distributed OODT setup from

your RADIX output, this could also have the ZK stuff in it so we can

properly utilise the distributed nature we started constructing with the FM

ZK changes.

 

 

 

 

 

On 15 October 2018 at 05:08:41, Imesha Sudasingha (imesha...@cse.mrt.ac.lk)

wrote:

 

Hi Tom,

 

I think this will be great since people are adopting docker more and more

and even for a user

once they have built a customized docker image, they can share it among the

peers

reducing the time spent for configuration by each individual.

 

Also we have another option ;-) With distributed configuration management

which I implemented,

users can ask OODT components to download configuration published in

zookeeper. But this will

require zookeeper to be running (either as a container or standalone). As

per my understanding,

configuration is the problem we need to solve when using a pre-built docker

image?

 

In future, if we are able to implement

https://issues.apache.org/jira/browse/OODT-977

we will be able to run multiple file managers in multiple containers which

will allow

the load to be distributed and query all at once. So, docker will be the

way to go as I see it.

What do you think?

 

Thanks,

Imesha

 

 

On Sun, 14 Oct 2018 at 15:40, Tom Barber  wrote:

 

I’m interested in the Dockerization of OODT but also conscious that most

people use RADIX to build their stuff, which make’s overriding bits of a

prebuilt image tricky.

 

I’m wondering if its worth adding an optional Docker profile to RADIX to

add a Docker build step to the backend of people’s RADIX builds if they so

wanted.

 

Thoughts?

 

--

 

 

Spicule Limited is registered in England & Wales. Company Number:

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements

are subject to Spicule Terms and Conditions of Business. This email and

its

contents are intended solely for the individual to whom it is addressed

and

may conta

Re: OODT docker builds

[Chris Mattmann]

Isn’t an image per component really heavyweight?

 

 

 

From: Tom Barber 
Date: Monday, October 15, 2018 at 8:26 AM
To: Imesha Sudasingha 
Cc: dev , Chris Mattmann 
Subject: Re: OODT docker builds

 

Why aren’t we doing so?! :)

 

Lack of cycles and young kids ;)

 

I’ll take a stab at it and see where we get to outside of RADIX to get the 
stack in distinct containers and then we’ll look at integrating it into the 
main build then.

 

 

Tom

 

On 15 October 2018 at 13:07:56, Imesha Sudasingha (imesha...@cse.mrt.ac.lk) 
wrote:

Yes. Agree with you. That is something I have been planning to ask you for 
long; why aren't we doing so. 

I like the idea of having a docker image per component and as you suggested we 
can create docker-compose 

or kubernetes setup for deployments. I like that direction ;-)

 

As an starting point, we can add an all-in-one docker image to be built in the 
RADIX build, right? 

If you start off, I will be able to join you along the way.

 

Thanks,

Imesha




 

 

On Mon, 15 Oct 2018 at 16:33, Tom Barber  wrote:

I was thinking about the outputs. Currently everything is 1 docker file which 
is fine for some deployments and not for others.

 

In the RADIX build we should also build individual containers for each 
component. For the deployment we could also have a docker-compose file and a 
K8S Helm setup so that you could deploy a distributed OODT setup from your 
RADIX output, this could also have the ZK stuff in it so we can properly 
utilise the distributed nature we started constructing with the FM ZK changes.

 

 

On 15 October 2018 at 05:08:41, Imesha Sudasingha (imesha...@cse.mrt.ac.lk) 
wrote:

Hi Tom,

I think this will be great since people are adopting docker more and more
and even for a user
once they have built a customized docker image, they can share it among the
peers
reducing the time spent for configuration by each individual.

Also we have another option ;-) With distributed configuration management
which I implemented,
users can ask OODT components to download configuration published in
zookeeper. But this will
require zookeeper to be running (either as a container or standalone). As
per my understanding,
configuration is the problem we need to solve when using a pre-built docker
image?

In future, if we are able to implement
https://issues.apache.org/jira/browse/OODT-977
we will be able to run multiple file managers in multiple containers which
will allow
the load to be distributed and query all at once. So, docker will be the
way to go as I see it.
What do you think?

Thanks,
Imesha


On Sun, 14 Oct 2018 at 15:40, Tom Barber  wrote:

> I’m interested in the Dockerization of OODT but also conscious that most
> people use RADIX to build their stuff, which make’s overriding bits of a
> prebuilt image tricky.
>
> I’m wondering if its worth adding an optional Docker profile to RADIX to
> add a Docker build step to the backend of people’s RADIX builds if they so
> wanted.
>
> Thoughts?
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>

 

Spicule Limited is registered in England & Wales. Company Number: 09954122. 
Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, 
England, BN1 6AF. VAT No. 251478891.

 

All engagements are subject to Spicule Terms and Conditions of Business. This 
email and its contents are intended solely for the individual to whom it is 
addressed and may contain information that is confidential, privileged or 
otherwise protected from disclosure, distributing or copying. Any views or 
opinions presented in this email are solely those of the author and do not 
necessarily represent those of Spicule Limited. The company accepts no 
liability for any damage caused by any virus transmitted by this email. If you 
have received this message in error, please notify us immediately by reply 
email before deleting it from your system. Service of legal notice cannot be 
effected on Spicule Limited by em

Re: Updated docker image

[Chris Mattmann]

Please make sure that this docker is consistent with the 
uscdatascience/imagecat OODT 
since that is getting some significant use. Wouldn’t want them to look 
drastically different ;)

 

 

 

From: lewis john mcgibbney 
Reply-To: 
Date: Wednesday, October 10, 2018 at 8:45 AM
To: 
Subject: Re: Updated docker image

 

Hi Tom,

I tried out the image and it looks great.

Some suggestions,

* would it be possible to publish the Dockerfile?

* In the README, it states the following command

 

docker run -d -p 8080:8080 -name my_first_oodt -i -t oodt

 

this should be

 

docker run -d -p 8080:8080 --name my_first_oodt -i -t buggtb/oodt

 

notice '--name' and final image parameter 'buggtb/oodt'

 

I would also add a line or two the the documentation to reference OPSUI

e.g. now navigate to http://localhost:8080/opsui/ and you will see the

operations user interface.

 

Good work, this is very convenient.

Lewis

 

On Tue, Oct 9, 2018 at 3:14 PM  wrote:

 

 

dev Digest 9 Oct 2018 22:14:17 - Issue 1327

 

Topics (messages 8498 through 8498)

 

Updated docker image

 8498 by: Tom Barber

 

Administrivia:

 

-

To post to the list, e-mail: dev@oodt.apache.org

To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org

For additional commands, e-mail: dev-digest-h...@oodt.apache.org

 

--

 

 

 

 

-- Forwarded message --

From: Tom Barber 

To: dev@oodt.apache.org

Cc:

Bcc:

Date: Tue, 9 Oct 2018 18:14:11 -0400

Subject: Updated docker image

Evening,

 

After prodding by Lewis, I’ve pushed an updated Radix docker image to

https://hub.docker.com/r/buggtb/oodt/

 

This is built off of the 1.2.3 release.

 

Happy to extend or enhance it if anyone has any good ideas, and I’ll figure

out a 1.9 version shortly. Happy OODT-ing.

 

Tom

 

--

 

 

Spicule Limited is registered in England & Wales. Company Number:

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements

are subject to Spicule Terms and Conditions of Business. This email and

its

contents are intended solely for the individual to whom it is addressed

and

may contain information that is confidential, privileged or otherwise

protected from disclosure, distributing or copying. Any views or opinions

presented in this email are solely those of the author and do not

necessarily represent those of Spicule Limited. The company accepts no

liability for any damage caused by any virus transmitted by this email. If

you have received this message in error, please notify us immediately by

reply email before deleting it from your system. Service of legal notice

cannot be effected on Spicule Limited by email.

 

 

 

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: Upcoming releases

[Chris Mattmann]

We should also reach out to Sally when we release 1.9 and/or 2.0 and
publish a press release which would announce:

 
OODT and its use upcoming in DRAT 1.0
OODT’s movement to Avro
OODT’s 8 year anniversary at Apache
Imesha as the new chair
 

Cheers,

Chris

 

 

 

 

From: Chris Mattmann 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, September 3, 2018 at 9:12 AM
To: "dev@oodt.apache.org" 
Subject: Re: Upcoming releases

 

My understanding is:

 

 

1.2.x series – 

 

  > 1.2.5 -> same as 1.2.4 except with logging tone down PRs by Ryan and Tom 
and Imesha. (needs forward port to master?)

 

  > 1.2.6 -> Lewis’s JDK10 fixes so will build on 10? (needs testing and 
forward port to master?)

 

 

1.9.x series – 

 

  > 1.9 – first release that makes AvroRPC the default. XmlRpc support remains, 
but is deprecated and turned off by default.

   (needs testing by Chris in DRAT).

 

2.0.x series – 

 

   > 2.0 – first release that complete removes XML-RPC as a communication 
medium. AvroRpc is left and only implementation. 

 

 

Make sense? I think this is consistent with Tom’s below. 

 

 

From: Imesha Sudasingha 

Reply-To: "dev@oodt.apache.org" 

Date: Monday, September 3, 2018 at 8:58 AM

To: dev 

Subject: Re: Upcoming releases

 

 

Hi Tom,

 

 

As per my understanding, 1.9 will be the next release which will make avro

 

the default communication provider over XML rpc. 1.9 will also include

 

logging framework change to log4j2.

 

Don't know much about 1.2.x releases.

 

 

Thanks,

 

Imesha

 

 

 

 

 

 

On Mon, 3 Sep 2018 at 18:25, Tom Barber  wrote:

 

 

Just curious to get some feedback on the upcoming release organisation.

 

 

If I understand correctly we’re shipped 1.2.5 with the logging fix for DRAT

 

release.

 

 

Then in reasonably short order, we’re going to ship 1.9 RC1 or 2.0RC1 for

 

Avro?

 

 

We should also ship 1.2.6 and 1.9RC2 or 2.0RC2 to incorporate Lewis’ JDK10

 

fixes and other bits?

 

 

Cheers

 

 

Tom

 

 

--

 

 

 

Spicule Limited is registered in England & Wales. Company Number:

 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

 

All engagements

 

are subject to Spicule Terms and Conditions of Business. This email and

 

its

 

contents are intended solely for the individual to whom it is addressed

 

and

 

may contain information that is confidential, privileged or otherwise

 

protected from disclosure, distributing or copying. Any views or opinions

 

presented in this email are solely those of the author and do not

 

necessarily represent those of Spicule Limited. The company accepts no

 

liability for any damage caused by any virus transmitted by this email. If

 

you have received this message in error, please notify us immediately by

 

reply email before deleting it from your system. Service of legal notice

 

cannot be effected on Spicule Limited by email.

 

 

 

 

Re: Upcoming releases

[Chris Mattmann]

My understanding is:

 

1.2.x series – 

  > 1.2.5 -> same as 1.2.4 except with logging tone down PRs by Ryan and Tom 
and Imesha. (needs forward port to master?)

  > 1.2.6 -> Lewis’s JDK10 fixes so will build on 10? (needs testing and 
forward port to master?)

 

1.9.x series – 

  > 1.9 – first release that makes AvroRPC the default. XmlRpc support remains, 
but is deprecated and turned off by default.
   (needs testing by Chris in DRAT).

2.0.x series – 

   > 2.0 – first release that complete removes XML-RPC as a communication 
medium. AvroRpc is left and only implementation. 

 

Make sense? I think this is consistent with Tom’s below. 

 

From: Imesha Sudasingha 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, September 3, 2018 at 8:58 AM
To: dev 
Subject: Re: Upcoming releases

 

Hi Tom,

 

As per my understanding, 1.9 will be the next release which will make avro

the default communication provider over XML rpc. 1.9 will also include

logging framework change to log4j2.

Don't know much about 1.2.x releases.

 

Thanks,

Imesha

 

 

 

 

 

On Mon, 3 Sep 2018 at 18:25, Tom Barber  wrote:

 

Just curious to get some feedback on the upcoming release organisation.

 

If I understand correctly we’re shipped 1.2.5 with the logging fix for DRAT

release.

 

Then in reasonably short order, we’re going to ship 1.9 RC1 or 2.0RC1 for

Avro?

 

We should also ship 1.2.6 and 1.9RC2 or 2.0RC2 to incorporate Lewis’ JDK10

fixes and other bits?

 

Cheers

 

Tom

 

--

 

 

Spicule Limited is registered in England & Wales. Company Number:

09954122. Registered office: First Floor, Telecom House, 125-135 Preston

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements

are subject to Spicule Terms and Conditions of Business. This email and

its

contents are intended solely for the individual to whom it is addressed

and

may contain information that is confidential, privileged or otherwise

protected from disclosure, distributing or copying. Any views or opinions

presented in this email are solely those of the author and do not

necessarily represent those of Spicule Limited. The company accepts no

liability for any damage caused by any virus transmitted by this email. If

you have received this message in error, please notify us immediately by

reply email before deleting it from your system. Service of legal notice

cannot be effected on Spicule Limited by email.

 

 

Re: Looking for apache packages

[Chris Mattmann]

These packages can easily be recreated. For example, check out the 1.0
tag on GH:

 

https://github.com/apache/oodt/tree/1.0 


For Balance: https://github.com/apache/oodt/tree/1.0/balance/lib/pear (run sudo 
pear package && sudo pear install)

For CAS FM: https://github.com/apache/oodt/tree/1.0/filemgr/src/main/php (run 
sudo pear package && sudo pear install)

For CAS Security: https://github.com/apache/oodt/tree/1.0/sso/src/main/php/pear 
(run sudo pear package && sudo pear install)

 

Since we are using version control you can always go back and find them….

 

Cheers,

Chris

 

 

 

 

From: Tom Barber 
Reply-To: 
Date: Friday, August 31, 2018 at 2:42 PM
To: , "Cheng, Cecilia S (398A)" 

Cc: "Lee, Hyun H (398G)" , "Ramirez, Paul M (398N)" 

Subject: Re: Looking for apache packages

 

Erk! Hi Cecilia,

 

The Apache Pear server went away a while ago now, and I think the artefacts

went with it. I don’t know if they were ever mirrored anywhere, Sean Kelly

might have a clue.

 

Tom

 

 

On 31 August 2018 at 03:29:48, Cheng, Cecilia S (398A) (

cecilia.s.ch...@jpl.nasa.gov) wrote:

 

Hi All,

 

We’ve been using the OODT File Manager GUI and it’s been working really

well. We recently got a new server and we’re trying to follow our old notes

& install the following packages only to find out that pear.apache.org/oodt

was shut down. Does anyone know where the new location where these packages

are hosted?

 

Installed packages, channel pear.apache.org/oodt:<

http://pear.apache.org/oodt:>

=

Package Version State

Apache_OODT_Balance 0.5 stable

Apache_OODT_CAS_Filemgr 0.4 stable

Apache_OODT_Security 0.4 stable

 

Thanks!

 

---

Cecilia Cheng

Jet Propulsion Laboratory

818-216-6256

cecilia.ch...@jpl.nasa.gov

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

FW: [HEADS UP] Apache DRAT prototype

[Chris Mattmann]

For those interested … Apache DRAT is built on Apache OODT.

 

 

 

From: Chris Mattmann 
Reply-To: "d...@drat.apache.org" 
Date: Thursday, August 23, 2018 at 9:40 AM
To: "gene...@incubator.apache.org" 
Cc: "d...@drat.apache.org" 
Subject: [HEADS UP] Apache DRAT prototype

 

Hi Incubator@,

 

 

Just to give you a heads up, over in Apache DRAT land we now have a 

pretty solid UI and a weekly scan process set up to scan all of the Gitbox

repos using our Proteus (new) system UI. You can see our demo/prototype

here:

 

 

http://drat-vm.apache.org:8080/proteus-new/ 

 

 

It goes down every now and then as we are making a few last minute 

tweaks to the UI (for example probably the last update we will make before

beginning a 1.0-RC1 process is to update the projects table to be paginated).

 

 

The UI is based on Vue.js and is the result of amazing work this summer by 

our GSOC 2018 student Ahmed Ifhaam and also work by Tom Barber, and 

others in DRAT.

 

 

Our intention is to provide this as a service to the ASF community and to set

up weekly or bi-weekly full scans. We haven’t fully decided how often to run 

it (yet) since during the process of it running some elements of the UI are 
inaccessible

for short periods of time. We may do run one week, let it sit for a week, then 
run

another week, etc. There are some interesting visualizations that give you a 
feel 

for how people are doing development at the ASF. Take a gander.

 

 

Please send any feedback to d...@drat.apache.org Thanks everyone.

 

 

Cheers,

 

Chris Mattmann

(on behalf of die-hard Apache DRAT fans everywhere) 

 

 

 

 

Re: Spring WARNING's during master build and test

[Chris Mattmann]

Hey Lewis, I haven’t seen anything on this…no. Are you still seeing the warnings
after the log updates from Ryan and Tom?

 

 

 

From: lewis john mcgibbney 
Reply-To: 
Date: Thursday, August 16, 2018 at 4:12 PM
To: 
Subject: Spring WARNING's during master build and test

 

WARNING: PropertyEditor [com.sun.beans.editors.EnumEditor] found through

deprecated global PropertyEditorManager fallback - consider using a more

isolated form of registration, e.g. on the BeanWrapper/BeanFactory!

 

Does anyone else see this? I saw the following thread which touches this

topic

 

https://stackoverflow.com/questions/13776878/deprecation-warning-from-spring

 

Lewis

 

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Re: OODT 1.2.4 Release Candidate 1

[Chris Mattmann]

yay

 

pretty please pretty please

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Wednesday, August 15, 2018 at 9:42 AM
To: "dev@oodt.apache.org" 
Subject: Re: OODT 1.2.4 Release Candidate 1

 

Chris is like my kids when they get a new toy ;)

 

Can we have another +1 from someone so we can ship this and get it

incorporated into DRAT?

 

 

On 14 August 2018 at 22:02:40, Chris Mattmann (mattm...@apache.org) wrote:

 

 

+1 from me.

 

Re: OODT 1.2.4 Release Candidate 1

[Chris Mattmann]

Tested in DRAT works great.

 

+1 from me.

 

Cheers,

Chris

 

 

From: Chris Mattmann 
Date: Tuesday, August 14, 2018 at 8:58 AM
To: Tom Barber , "dev@oodt.apache.org" 
, Chris Mattmann 
Subject: Re: OODT 1.2.4 Release Candidate 1

 

Yeah hilarious.

 

I think it was probably a Central issue then with a corrupt jar, b/c this 
morning
it builds fine for me too – without changing a thing.

 

O] 

[INFO] 

[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oodt ---

[INFO] Deleting /Users/mattmann/git/oodt/target

[INFO] 

[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oodt ---

[INFO] 

[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ oodt 
---

[INFO] 

[INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) > 
generate-sources @ oodt >>>

[INFO] 

[INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) < 
generate-sources @ oodt <<<

[INFO] 

[INFO] 

[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @ oodt ---

[INFO] 

[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---

[INFO] Installing /Users/mattmann/git/oodt/pom.xml to 
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.2.4/oodt-1.2.4.pom

[INFO] 

[INFO] Reactor Summary:

[INFO] 

[INFO] OODT Core .. SUCCESS [  3.349 s]

[INFO] Common Utilities ... SUCCESS [ 35.406 s]

[INFO] CAS Command Line Interface . SUCCESS [ 14.487 s]

[INFO] Process Control System Input Data Package .. SUCCESS [  5.426 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  8.176 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [03:42 min]

[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 33.749 s]

[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 42.586 s]

[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 23.329 s]

[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  2.329 s]

[INFO] CAS Curation Web Services .. SUCCESS [  9.349 s]

[INFO] Process Control System Core Package  SUCCESS [ 21.241 s]

[INFO] OODT Wicket Web Components . SUCCESS [  7.360 s]

[INFO] CAS Curation Interface . SUCCESS [ 16.206 s]

[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 21.562 s]

[INFO] CAS Installer Maven Mojo ... SUCCESS [  4.750 s]

[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  1.842 s]

[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  1.814 s]

[INFO] OODT :: Archetypes . SUCCESS [  0.051 s]

[INFO] CAS File Manager Browser Web App ... SUCCESS [ 10.177 s]

[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  6.149 s]

[INFO] CAS Product Server Web Application . SUCCESS [ 14.668 s]

[INFO] CAS Workflow REST Services . SUCCESS [  5.175 s]

[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 32.429 s]

[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [ 11.121 s]

[INFO] Apache OODT  SUCCESS [  0.065 s]

[INFO] 

[INFO] BUILD SUCCESS

[INFO] 

[INFO] Total time: 09:15 min

[INFO] Finished at: 2018-08-14T08:53:49-07:00

[INFO] Final Memory: 95M/1521M

[INFO] 

nonas:oodt mattmann$ 

 

 

I’ll test it in DRAT now and get back to you.

 

Cheers

Chris

 

 

 

 

From: Tom Barber 
Date: Tuesday, August 14, 2018 at 12:20 AM
To: "dev@oodt.apache.org" , Chris Mattmann 

Subject: Re: OODT 1.2.4 Release Candidate 1

 

So how about I told you, I saw the same error last night, but this morning it 
was gone?

 

On my dev box today:

 

bugg@spicule-dev:~/oodt> java -version

openjdk version "1.8.0_181"

OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13)

OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)

 

bugg@spicule-dev:~/oodt> mvn -version

Apache Maven 3.3.9

Maven home: /usr/share/maven

Java version: 1.8.0_181, vendor: Oracle Corporation

Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "linux", version: "4.4.0-119-generic", arch: "amd64", family: “unix"

 

bugg@spicule-dev:~/oodt> git status

HEAD

Re: OODT 1.2.4 Release Candidate 1

[Chris Mattmann]

Yeah hilarious.

 

I think it was probably a Central issue then with a corrupt jar, b/c this 
morning
it builds fine for me too – without changing a thing.

 

O] 

[INFO] 

[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oodt ---

[INFO] Deleting /Users/mattmann/git/oodt/target

[INFO] 

[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oodt ---

[INFO] 

[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ oodt 
---

[INFO] 

[INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) > 
generate-sources @ oodt >>>

[INFO] 

[INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) < 
generate-sources @ oodt <<<

[INFO] 

[INFO] 

[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @ oodt ---

[INFO] 

[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---

[INFO] Installing /Users/mattmann/git/oodt/pom.xml to 
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.2.4/oodt-1.2.4.pom

[INFO] 

[INFO] Reactor Summary:

[INFO] 

[INFO] OODT Core .. SUCCESS [  3.349 s]

[INFO] Common Utilities ... SUCCESS [ 35.406 s]

[INFO] CAS Command Line Interface . SUCCESS [ 14.487 s]

[INFO] Process Control System Input Data Package .. SUCCESS [  5.426 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  8.176 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [03:42 min]

[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 33.749 s]

[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 42.586 s]

[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 23.329 s]

[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  2.329 s]

[INFO] CAS Curation Web Services .. SUCCESS [  9.349 s]

[INFO] Process Control System Core Package  SUCCESS [ 21.241 s]

[INFO] OODT Wicket Web Components . SUCCESS [  7.360 s]

[INFO] CAS Curation Interface . SUCCESS [ 16.206 s]

[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 21.562 s]

[INFO] CAS Installer Maven Mojo ... SUCCESS [  4.750 s]

[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  1.842 s]

[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  1.814 s]

[INFO] OODT :: Archetypes . SUCCESS [  0.051 s]

[INFO] CAS File Manager Browser Web App ... SUCCESS [ 10.177 s]

[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  6.149 s]

[INFO] CAS Product Server Web Application . SUCCESS [ 14.668 s]

[INFO] CAS Workflow REST Services . SUCCESS [  5.175 s]

[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 32.429 s]

[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [ 11.121 s]

[INFO] Apache OODT  SUCCESS [  0.065 s]

[INFO] 

[INFO] BUILD SUCCESS

[INFO] 

[INFO] Total time: 09:15 min

[INFO] Finished at: 2018-08-14T08:53:49-07:00

[INFO] Final Memory: 95M/1521M

[INFO] 

nonas:oodt mattmann$ 

 

 

I’ll test it in DRAT now and get back to you.

 

Cheers

Chris

 

 

 

 

From: Tom Barber 
Date: Tuesday, August 14, 2018 at 12:20 AM
To: "dev@oodt.apache.org" , Chris Mattmann 

Subject: Re: OODT 1.2.4 Release Candidate 1

 

So how about I told you, I saw the same error last night, but this morning it 
was gone?

 

On my dev box today:

 

bugg@spicule-dev:~/oodt> java -version

openjdk version "1.8.0_181"

OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13)

OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)

 

bugg@spicule-dev:~/oodt> mvn -version

Apache Maven 3.3.9

Maven home: /usr/share/maven

Java version: 1.8.0_181, vendor: Oracle Corporation

Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "linux", version: "4.4.0-119-generic", arch: "amd64", family: “unix"

 

bugg@spicule-dev:~/oodt> git status

HEAD detached at 1.2.4

nothing to commit, working directory clean

 

[INFO] Reactor Summary:

[INFO]

[INFO] OODT Core .. SUCCESS [  1.768 s]

[INFO] Common Utilities ... SUCCESS [ 14.881 s]

[INF

Re: OODT 1.2.4 Release Candidate 1

[Chris Mattmann]

Tom, I can’t get this to build:

 

nonas:oodt mattmann$ java -version

mvnjava version "1.8.0_144"

Java(TM) SE Runtime Environment (build 1.8.0_144-b01)

Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

nonas:oodt mattmann$ mvn -version

Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
2017-04-03T12:39:06-07:00)

Maven home: /usr/local/Cellar/maven/3.5.0/libexec

Java version: 1.8.0_144, vendor: Oracle Corporation

Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"

nonas:oodt mattmann$ 

 

 

 

[INFO] Process Control System Input Data Package .. SUCCESS [  2.550 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  6.201 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [02:50 min]

[INFO] Catalog and Archive Resource Management Component .. FAILURE [  0.574 s]

[INFO] Catalog and Archive Workflow Management Component .. SKIPPED

[INFO] Catalog and Archive Crawling Framework . SKIPPED

[INFO] OODT CAS Curator Single Sign On Security Package ... SKIPPED

[INFO] CAS Curation Web Services .. SKIPPED

[INFO] Process Control System Core Package  SKIPPED

[INFO] OODT Wicket Web Components . SKIPPED

[INFO] CAS Curation Interface . SKIPPED

[INFO] CAS PGE Adaptor Framework .. SKIPPED

[INFO] CAS Installer Maven Mojo ... SKIPPED

[INFO] OODT :: Archetypes :: OpsUI  SKIPPED

[INFO] OODT :: Archetypes :: RADiX  SKIPPED

[INFO] OODT :: Archetypes . SKIPPED

[INFO] CAS File Manager Browser Web App ... SKIPPED

[INFO] CAS Workflow Manager Monitor Web App ... SKIPPED

[INFO] CAS Product Server Web Application . SKIPPED

[INFO] CAS Workflow REST Services . SKIPPED

[INFO] Process Control System Operator Interface Webapp ... SKIPPED

[INFO] OODT Process Control System JAX-RS service layer ... SKIPPED

[INFO] Apache OODT  SKIPPED

[INFO] 

[INFO] BUILD FAILURE

[INFO] 

[INFO] Total time: 03:43 min

[INFO] Finished at: 2018-08-13T20:03:39-07:00

[INFO] Final Memory: 56M/720M

[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.4:test (default-test) on 
project cas-resource: 
org/apache/oodt/config/test/AbstractDistributedConfigurationTest; nested 
exception is java.lang.NoClassDefFoundError: 
org/apache/oodt/config/test/AbstractDistributedConfigurationTest: 
org.apache.oodt.config.test.AbstractDistributedConfigurationTest -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please 
read the following articles:

[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn  -rf :cas-resource

nonas:oodt mattmann$ 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, August 13, 2018 at 2:36 PM
To: "dev@oodt.apache.org" 
Subject: OODT 1.2.4 Release Candidate 1

 

Hi Folks,

 

To restore JDK 1.8 support I have shipped a 1.2.4 RC.

 

I have posted a 1st release candidate for the Apache OODT 1.2.4 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.4 tag at:

https://github.com/apache/oodt

 

 

A staged Maven repository is available at:

 

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

 

Please vote on releasing these packages as Apache OODT 1.2.4. 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.4

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

 

Thanks!

 

Tom

 

P.S. Here is my +1.

 

-- 

 

 

Spicule Limited is registered 

Re: [VOTE] Apache OODT 1.2.3 Release

[Chris Mattmann]

+1 from me tested and integrated into Apache DRAT master and it
fixes the core issue in Lucene heavy ingests.

 

See my comments here:

 

https://github.com/apache/oodt/pull/67 

 

Cheers,

Chris

 

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Monday, August 6, 2018 at 4:26 PM
To: "dev@oodt.apache.org" 
Subject: [VOTE] Apache OODT 1.2.3 Release

 

Hi Folks,

 

I have posted a 1st release candidate for the Apache OODT 1.2.3 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.3 tag at:

https://github.com/apache/oodt/tree/1.2.3

 

A staged Maven repository is available at:

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

 

 

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.2.3

 

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

 

Thanks!

 

Magicaltrout

 

P.S. Here is my +1.

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Re: 1.2.3 Release

[Chris Mattmann]

Hey Tom,

 

I tested this in DRAT and it fixes the bugs. I also forward ported it to 
1.9-master.

 

Please release 1.2.3! ☺

 

DRAT build in GSOC 2018 branch is waiting on this ;)

 

Cheers,

Chris

 

 

 

 

From: Tom Barber 
Reply-To: "dev@oodt.apache.org" 
Date: Friday, July 20, 2018 at 4:39 AM
To: "dev@oodt.apache.org" 
Subject: 1.2.3 Release

 

Hi folks,

 

In fixing some stuff in DRAT I’ve also had to fix some stuff in the Lucene

Catalog which fails under pressure. There’s a PR open and when Chris tests

and validates it we’ll need to ship OODT 1.2.3. I messed up so I’ll do the

release.

 

Tom

 

-- 

 

 

Spicule Limited is registered in England & Wales. Company Number: 

09954122. Registered office: First Floor, Telecom House, 125-135 Preston 

Road, Brighton, England, BN1 6AF. VAT No. 251478891.

 

 

 

 

All engagements 

are subject to Spicule Terms and Conditions of Business. This email and its 

contents are intended solely for the individual to whom it is addressed and 

may contain information that is confidential, privileged or otherwise 

protected from disclosure, distributing or copying. Any views or opinions 

presented in this email are solely those of the author and do not 

necessarily represent those of Spicule Limited. The company accepts no 

liability for any damage caused by any virus transmitted by this email. If 

you have received this message in error, please notify us immediately by 

reply email before deleting it from your system. Service of legal notice 

cannot be effected on Spicule Limited by email.

 

Native Github integration with Apache OODT

[Chris Mattmann]

Hey Folks,

 

Now that https://issues.apache.org/jira/browse/INFRA-16582 
is closed, we have native integration with Github and Apache OODT!

 

My advice: take a look at http://wiki.apache.org/tika/UsingGit as a 
guide for how to use Gitbox/GH integration with Apache. Also see 
http://gitbox.apache.org and make sure you set up GH 2 factor authentication
and integration with Gitbox so that you can commit to the repo.

 

Thanks,

Chris

 

Re: [DISCUSSION] Logging in OODT

[Chris Mattmann]

I think this is a great approach and am +1 for it.

 

Cheers,

Chris

 

 

 

From: Imesha Sudasingha 
Reply-To: 
Date: Sunday, June 3, 2018 at 4:13 AM
To: dev 
Subject: [DISCUSSION] Logging in OODT

 

Hi All,

 

When I was working on stabilizing Avro RPC versions of file manager,

workflow manager and resource manager, it became extremely difficult to

debug due to lack of logging in OODT. Therefore, we need more logging

support throughout the project. Personally, I find *java.util.Logging (JUL)*

not convenient to use since it requires explicit string concatenation when

logging.

 

As a solution, I suggest to use SLF4J which has already been used partially

in same components in OODT. Therefore, I have re-opened an existing issue

[1] related to this and created few sub tasks. I want to know your opinion

on following,

 

1. As for now, we can redirect [2] JUL logs to SLF4J logs by adding a new

handler to existing logging.properties files. Will that be ok? In future we

can completely remove JUL log lines.

 

2. Will there be any backward compatibility issue if we add log4j2 along

with log4j2.xml's to distributions from 1.9 onwards?

 

What are your thoughts?

 

[1] https://issues.apache.org/jira/browse/OODT-693

[2]

https://stackoverflow.com/questions/6020545/send-redirect-route-java-util-logging-logger-jul-to-logback-using-slf4j

 

Cheers,

Imesha

 

FW: [RESULT] [VOTE] Move Apache OODT to use Apache's Gitbox (Full Github integration)

[Chris Mattmann]

I’ve filed this ticket to track the migration: 
https://issues.apache.org/jira/browse/INFRA-16582

 

Thanks,

Chris

 

 

 

From: Chris Mattmann <mattm...@apache.org>
Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Date: Saturday, May 26, 2018 at 11:51 AM
To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: [RESULT] [VOTE] Move Apache OODT to use Apache's Gitbox (Full Github 
integration)

 

This VOTE has PASSED with the following tallies:

 

 

+1

 

Chris Mattmann

 

Tom Barber

 

Imesha Sudasingha

 

 

I’ll file a ticket with INFRA requesting the move.

 

 

Thanks,

 

Chris

 

 

 

From: Chris Mattmann <mattm...@apache.org>

Date: Friday, May 18, 2018 at 10:15 AM

To: <dev@oodt.apache.org>

Subject: [VOTE] Move Apache OODT to use Apache's Gitbox (Full Github 
integration)

 

 

See DISCUSS thread here: https://s.apache.org/mYgX 

 

 

Please VOTE to make Apache OODT use the Gitbox integration for full R/W 
multi-master

Github and ASF integration. This will allow merging of pull requests directly 
from Github

and other useful features.

 

 

Please VOTE accordingly:

 

 

[ ]+1 Move Apache OODT to use Gitbox.

 

[ ] +0 Abstain

 

[ ] -1 Don’t move Apache OODT to use Gitbox because

 

 

Please keep the discussion on the discussion thread referenced above and the 
VOTE thread

here.

 

 

I am +1.

 

 

Thanks,

 

Chris

 

 

 

 

 

[RESULT] [VOTE] Move Apache OODT to use Apache's Gitbox (Full Github integration)

[Chris Mattmann]

This VOTE has PASSED with the following tallies:

 

+1

Chris Mattmann

Tom Barber

Imesha Sudasingha

 

I’ll file a ticket with INFRA requesting the move.

 

Thanks,

Chris

 

 

From: Chris Mattmann <mattm...@apache.org>
Date: Friday, May 18, 2018 at 10:15 AM
To: <dev@oodt.apache.org>
Subject: [VOTE] Move Apache OODT to use Apache's Gitbox (Full Github 
integration)

 

See DISCUSS thread here: https://s.apache.org/mYgX 

 

Please VOTE to make Apache OODT use the Gitbox integration for full R/W 
multi-master
Github and ASF integration. This will allow merging of pull requests directly 
from Github
and other useful features.

 

Please VOTE accordingly:

 

[ ]+1 Move Apache OODT to use Gitbox.

[ ] +0 Abstain

[ ] -1 Don’t move Apache OODT to use Gitbox because

 

Please keep the discussion on the discussion thread referenced above and the 
VOTE thread
here.

 

I am +1.

 

Thanks,

Chris

 

 

 

Re: Build failed in Jenkins: oodt-2.0-development #57

[Chris Mattmann]

Lauren, send a blank email to dev-unsubscr...@oodt.apache.org and then 
follow the instructions from there (send it from your desired unsubscribe email
address).

 

That should take care of it.

 

Thanks,

Chris

 

 

 

From: "Lauren A. Wong" 
Reply-To: 
Date: Friday, May 18, 2018 at 9:41 AM
To: 
Subject: Re: Build failed in Jenkins: oodt-2.0-development #57

 

UNSUBSCRIBE

 

On Fri, May 18, 2018 at 9:27 AM Apache Jenkins Server <

jenk...@builds.apache.org> wrote:

 

See <

https://builds.apache.org/job/oodt-2.0-development/57/display/redirect>

 

--

[...truncated 7.91 KB...]

[INFO] Common Utilities

[INFO] CAS Command Line Interface

[INFO] OODT - Configuration Management

[INFO] Process Control System Input Data Package

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container

[INFO] Catalog and Archive File Management Component

[INFO] Catalog and Archive Resource Management Component

[INFO] Catalog and Archive Workflow Management Component

[INFO] Catalog and Archive Crawling Framework

[INFO] OODT CAS Curator Single Sign On Security Package

[INFO] CAS Curation Web Services

[INFO] Process Control System Core Package

[INFO] OODT Wicket Web Components

[INFO] CAS Curation Interface

[INFO] CAS PGE Adaptor Framework

[INFO] CAS Installer Maven Mojo

[INFO] OODT :: Archetypes :: OpsUI

[INFO] OODT :: Archetypes :: RADiX

[INFO] OODT :: Archetypes

[INFO] CAS File Manager Browser Web App

[INFO] CAS Workflow Manager Monitor Web App

[INFO] CAS Product Server Web Application

[INFO] CAS Workflow REST Services

[INFO] Process Control System Operator Interface Webapp

[INFO] OODT Process Control System JAX-RS service layer

[INFO] Apache OODT

[INFO]

[INFO]



[INFO] Building OODT Core 1.9-SNAPSHOT

[INFO]



[INFO]

[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oodt-core ---

[INFO] Deleting <

https://builds.apache.org/job/oodt-2.0-development/ws/core/target>

[INFO]

[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oodt-core

---

[INFO]

[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @

oodt-core ---

[INFO]

[INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) >

generate-sources @ oodt-core >>>

[INFO]

[INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) <

generate-sources @ oodt-core <<<

[INFO]

[INFO]

[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @

oodt-core ---

[INFO]

[INFO] --- maven-install-plugin:2.5.2:install (default-install) @

oodt-core ---

[INFO] Installing <

https://builds.apache.org/job/oodt-2.0-development/ws/core/pom.xml> to <

https://builds.apache.org/job/oodt-2.0-development/ws/.repository/org/apache/oodt/oodt-core/1.9-SNAPSHOT/oodt-core-1.9-SNAPSHOT.pom

> 

[INFO] Installing <

https://builds.apache.org/job/oodt-2.0-development/ws/core/target/oodt-core-1.9-SNAPSHOT-site.xml>

to <

https://builds.apache.org/job/oodt-2.0-development/ws/.repository/org/apache/oodt/oodt-core/1.9-SNAPSHOT/oodt-core-1.9-SNAPSHOT-site.xml

> 

[INFO]

[INFO]



[INFO] Building Common Utilities 1.9-SNAPSHOT

[INFO]



[INFO]

[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oodt-commons ---

[INFO] Deleting <

https://builds.apache.org/job/oodt-2.0-development/ws/commons/target>

[INFO]

[INFO] --- maven-remote-resources-plugin:1.5:process (default) @

oodt-commons ---

[INFO]

[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @

oodt-commons ---

[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 1 resource to org/apache/oodt/commons

[INFO] Copying 1 resource to org/apache/oodt/commons/util

[INFO] Copying 3 resources

[INFO]

[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @

oodt-commons ---

[INFO] Changes detected - recompiling the module!

[INFO] Compiling 88 source files to <

https://builds.apache.org/job/oodt-2.0-development/ws/commons/target/classes

> 

[WARNING] <

https://builds.apache.org/job/oodt-2.0-development/ws/commons/src/main/java/org/apache/oodt/commons/ExecServer.java>:

Some input files use or override a deprecated API.

[WARNING] <

https://builds.apache.org/job/oodt-2.0-development/ws/commons/src/main/java/org/apache/oodt/commons/ExecServer.java>:

Recompile with -Xlint:deprecation for details.

[WARNING] <

https://builds.apache.org/job/oodt-2.0-development/ws/commons/src/main/java/org/apache/oodt/commons/activity/SQLDatabaseRetrieval.java>:

Some input files use unchecked or unsafe operations.

[WARNING] <

[VOTE] Move Apache OODT to use Apache's Gitbox (Full Github integration)

[Chris Mattmann]

See DISCUSS thread here: https://s.apache.org/mYgX 

 

Please VOTE to make Apache OODT use the Gitbox integration for full R/W 
multi-master
Github and ASF integration. This will allow merging of pull requests directly 
from Github
and other useful features.

 

Please VOTE accordingly:

 

[ ]+1 Move Apache OODT to use Gitbox.

[ ] +0 Abstain

[ ] -1 Don’t move Apache OODT to use Gitbox because

 

Please keep the discussion on the discussion thread referenced above and the 
VOTE thread
here.

 

I am +1.

 

Thanks,

Chris

 

 

 

[DISCUSS] Move Apache OODT to use Apache's Gitbox (Full Github integration)

[Chris Mattmann]

Folks,

 

We currently have Apache R/W Github repositories, and GH mirroring turned on 
which 
allows Apache OODT to simulate Git integration. Apache has now widespread 
ability to 
use full Github integration and multi-master sync through the 
http://gitbox.apache.org 
project.

 

I am proposing that we move Apache OODT to Gitbox. Many other ASF projects are 
doing
this now (SIS just recently completed a VOTE). We’ve used it in DRAT too and it 
works great.
You can merge pull requests, simply interact with the project at Github like 
others do and 
get emails and notifications here on ASF email and servers, etc.

 

I am going to simultaneously call a VOTE on this, and then leave this 
discussion thread open
for any questions related to that VOTE.

 

The VOTE will run for 72 hours at least. Please respond on my [VOTE] thread 
with the same
subject with your VOTE (+1, +/-0, -1, because etc.) and keep the discussion 
here.

 

Thanks,

Chris

 

Re: Joining on board

[Chris Mattmann]

Welcome Ahmed, thanks for working on DRAT. We are here to help!

 

Cheers,

Chris

 

 

 

From: Ahmed Ifhaam 
Reply-To: "d...@drat.apache.org" 
Date: Sunday, May 13, 2018 at 12:30 PM
To: "d...@drat.apache.org" 
Subject: Joining on board

 

hi all,

 

As part of GSOC_2018 i'll be working on DRAT. I'm very pleased to work on

this and expect your support and advice as well. I'ts great to joining you

all. Thank you

 

-- 

*Ahmed Ifhaam *

University of Kelaniya | MIT '19

Tel :- 0662244937 | Mob :- 0776699609

ahmedifha...@gmail.com 

 

Re: maven-cas-install-plugin.iml.orig and maven-cas-install-plugin.iml.rej files present in SCM

[Chris Mattmann]

I think you are right Lewis, can you delete them?

 

 

From: lewis john mcgibbney 
Reply-To: "dev@oodt.apache.org" 
Date: Tuesday, April 24, 2018 at 10:46 PM
To: "dev@oodt.apache.org" 
Subject: maven-cas-install-plugin.iml.orig and maven-cas-install-plugin.iml.rej 
files present in SCM

 

Hi Folks,

I assume that there following files are not meant to be in SCM?

https://github.com/apache/oodt/blob/master/mvn/plugins/cas-install/maven-cas-install-plugin.iml.orig

https://github.com/apache/oodt/blob/master/mvn/plugins/cas-install/maven-cas-install-plugin.iml.rej

Lewis

 

-- 

http://home.apache.org/~lewismc/

http://people.apache.org/keys/committer/lewismc

 

Welcome to our new Chair: Imesha Sudasingha!

[Chris Mattmann]

Hi,

 

At this past week’s Board meeting, the Apache OODT project elected and nominated
a new chair: Imesha Sudasingha. The Board accepted the nomination. Congrats 
Imesha!

 

I would also like to take this opportunity to thank Tom Barber, who has served 
admirably
in this role for the many of the past years. Thank you Tom we appreciate it!

 

 

Sincerely,
Chris Mattmann

 

 

 

Re: OODT start

[Chris Mattmann]

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 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/fil

Re: OODT start

[Chris Mattmann]

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.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

[Chris Mattmann]

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

[Chris Mattmann]

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 
Reply-To: 
Date: Saturday, April 7, 2018 at 10:56 AM
To: 
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  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

 

[ANNOUNCE] Apache OODT 1.2.1 release

[Chris Mattmann]

The Apache OODT project is pleased to announce the release of Apache OODT 

1.2.1. The release contents have been pushed out to the main Apache release 
site and to the

Maven Central sync, so the releases should be available as soon as the mirrors 
get the syncs.

 

Apache OODT is a software framework as well as an architectural style for the

rapid construction of scientific data systems.  It provides components for

data capture, curation, metadata extraction, workflow management, resource

management, and data processing.

 

Apache OODT 1.2.1 contains a number of improvements and bug fixes. Details

can be found in the changes file:

http://www.apache.org/dist/oodt/CHANGES-1.2.1.txt 

 

Apache OODT is available in source form from the following download page:

http://www-us.apache.org/dist/oodt/apache-oodt-1.2.1-src.zip 

 

Apache OODT is also available in binary form or for use using Maven 2 from

the Central Repository:

http://repo1.maven.org/maven2/org/apache/oodt/

 

In the initial 48 hours, the release may not be available on all mirrors.

When downloading

from a mirror site, please remember to verify the downloads using

signatures found on the

Apache site:

https://people.apache.org/keys/group/oodt.asc

 

For more information on Apache OODT, visit the project home page:

http://oodt.apache.org/

 

-- Chris Mattmann, on behalf of the Apache OODT community

 

 

 

 

[RESULT] [VOTE] Apache OODT 1.2.1 release candidate #1

[Chris Mattmann]

Hi,

 

This VOTE has PASSED with the following tallies:

 

+1

Chris Mattmann

Tom Barber

Sean Kelly

Lewis John McGibbney

 

I’ll push it out, ahead of Tom spinning a 1.2.2.

 

Thanks for VOTE’ing!

 

Cheers,

Chris

 

 

 

From: Chris Mattmann <mattm...@apache.org>
Date: Sunday, November 12, 2017 at 9:53 AM
To: <dev@oodt.apache.org>
Subject: [VOTE] Apache OODT 1.2.1 release candidate #1

 

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

 

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

 

Thanks!

 

Chris

 

P.S. Here is my +1.

 

 

 

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

[Chris Mattmann]

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" <ke...@apache.org> 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"<ke...@apache.org>  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<mailto:mattm...@apache.org>
>  >  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
>  >
>  >
>  >
>  >  [ ] -1 Do not release the packages because...
>  >
>  >
>  >
>  >  Thanks!
>  >
>  >
>  >
>  >  Chris
>  >
>  >
>  >
>  >  P.S. Here is my +1.
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>
>
>

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

[Chris Mattmann]

KEYS file added! ( do I have your +1? (



On 12/20/17, 8:38 AM, "Sean Kelly" <ke...@apache.org> 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 <mailto:mattm...@apache.org>
> 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
>
>
>
> [ ] -1 Do not release the packages because...
>
>
>
> Thanks!
>
>
>
> Chris
>
>
>
> P.S. Here is my +1.
>
>
>
>
>
>
>
>
>
>

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

[Chris Mattmann]

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

 

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

 

Thanks!

 

Chris

 

P.S. Here is my +1.

 

 

 

Re: Apache OODT balance framework

[Chris Mattmann]

My advice is to use the Wicket-based components and web apps which are
still actively maintained.

Cheers,
Chris




On 12/14/17, 12:54 AM, "lewis john mcgibbney"  wrote:

I recently wrote the packing code for the Sitepod project, which is a
Sitemap generator written in PHP. For those interested they can see the
source at [0].
For the build and dependency management I used composer [1] and packagist
[2] to host the release distribution artifact.
@Yun, if your current project requires use of the OODT Balance PHP
framework then I would encourage you to spend a day researching composer
and packagist then simply sending a pull request for bring it up to date.
We could then possibly push a backdated 'release' of the artifact or else
vote on a new release such that releasing balance to packagist becomes the
normal procedures inline with every OODT release.
Hth
Lewis

[0] https://github.com/nasa/sitepod
[1] https://getcomposer.org/
[2] https://packagist.org/packages/nasa/sitepod

On Thu, Dec 14, 2017 at 03:55 Ramirez, Paul M (398N) <
paul.m.rami...@jpl.nasa.gov> wrote:

> Hyun,
>
> Looks like pear.apache.org was shut down.
>
>
> 
http://apache-logging.6191.n7.nabble.com/NOTICE-pear-apache-org-is-being-shut-down-April-20th-2017-td75208.html
>
> The sentiment on that list was that the packages should be hosted
> somewhere else. I don’t know much about PHP. I wonder if the pear packages
> build from source. If not I’d suggest find the packages installed 
somewhere
> and working to host them somewhere that pear can find. Potentially the 
site
> suggested in that list. It would be great if you did this and then updated
> the build information via a patch.
>
> It would be helpful if you could also open a Jira ticket to log this issue
> and any details that describe how (i.e. commands) you were using to build.
>
> Unfortunately I’ve never written a line of PHP so take the above with a
> grain of salt.
>
> HTH,
> Paul
> _
> From: Lee, Hyun H (398G) 
> Sent: Wednesday, December 13, 2017 7:14 PM
> Subject: Apache OODT balance framework
> To: Ramirez, Paul M (398N) 
>
>
> Paul,
>
> Albert and I tried to set up a portal using Apache OODT balance framework
> for COWVR project.
>
> However, pear.apache.org is no longer online, so
> we cannot install Apache OODT balance and Security pakages anymore.
>
> It seems like Shakeh is no longer at JPL. Who should I ask for help?
>
> Thanks,
> Hyun
>
>
> --
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: Apache OODT balance framework

[Chris Mattmann]

Team, Balance isn’t a part of Apache anymore, see:

https://issues.apache.org/jira/browse/OODT-837 
https://issues.apache.org/jira/browse/OODT-836

So, fixing it would only be possible in a release older than 
1.1. and on that branch.

Cheers,
Chris




On 12/14/17, 12:54 AM, "lewis john mcgibbney"  wrote:

I recently wrote the packing code for the Sitepod project, which is a
Sitemap generator written in PHP. For those interested they can see the
source at [0].
For the build and dependency management I used composer [1] and packagist
[2] to host the release distribution artifact.
@Yun, if your current project requires use of the OODT Balance PHP
framework then I would encourage you to spend a day researching composer
and packagist then simply sending a pull request for bring it up to date.
We could then possibly push a backdated 'release' of the artifact or else
vote on a new release such that releasing balance to packagist becomes the
normal procedures inline with every OODT release.
Hth
Lewis

[0] https://github.com/nasa/sitepod
[1] https://getcomposer.org/
[2] https://packagist.org/packages/nasa/sitepod

On Thu, Dec 14, 2017 at 03:55 Ramirez, Paul M (398N) <
paul.m.rami...@jpl.nasa.gov> wrote:

> Hyun,
>
> Looks like pear.apache.org was shut down.
>
>
> 
http://apache-logging.6191.n7.nabble.com/NOTICE-pear-apache-org-is-being-shut-down-April-20th-2017-td75208.html
>
> The sentiment on that list was that the packages should be hosted
> somewhere else. I don’t know much about PHP. I wonder if the pear packages
> build from source. If not I’d suggest find the packages installed 
somewhere
> and working to host them somewhere that pear can find. Potentially the 
site
> suggested in that list. It would be great if you did this and then updated
> the build information via a patch.
>
> It would be helpful if you could also open a Jira ticket to log this issue
> and any details that describe how (i.e. commands) you were using to build.
>
> Unfortunately I’ve never written a line of PHP so take the above with a
> grain of salt.
>
> HTH,
> Paul
> _
> From: Lee, Hyun H (398G) 
> Sent: Wednesday, December 13, 2017 7:14 PM
> Subject: Apache OODT balance framework
> To: Ramirez, Paul M (398N) 
>
>
> Paul,
>
> Albert and I tried to set up a portal using Apache OODT balance framework
> for COWVR project.
>
> However, pear.apache.org is no longer online, so
> we cannot install Apache OODT balance and Security pakages anymore.
>
> It seems like Shakeh is no longer at JPL. Who should I ask for help?
>
> Thanks,
> Hyun
>
>
> --
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: oodt git commit: close connection to release client

[Chris Mattmann]

Good show bravo mate



On 12/12/17, 3:06 PM, "Tom Barber" <t...@spicule.co.uk> wrote:

Yeah I was going to write one method but with 4 or 5 different exception 
types you'd need to generalize the thrown exception or do something else 
funky to get the different exceptions thrown.

Any how, I can do more on it but lets get it run through some tests and 
see if its any happier than it was.

Tom

On 12/12/17 23:03, Chris Mattmann wrote:
> Good lord, nevermind yeah looks like a future candidate for a refactoring
> since it’s the same line over and over again.
>
>
>
>
>
> On 12/12/17, 3:01 PM, "Tom Barber" <t...@spicule.co.uk> wrote:
>
>  I'm not following, the change was to add a finally block to each 
client
>  call to shut it down after the execution. Those finally blocks I've 
just
>  added in, the only other change was an import clean up.
>  
>  On 12/12/17 22:58, Chris Mattmann wrote:
>  > Tom, please revert this commit and do a commit that doesn’t 
include a billion lines of
>  > formatting change and includes the actual change? (
>  >
>  > Cheers,
>  > Chris
>  >
>  >
>  >
>  >
>  > On 12/12/17, 2:56 PM, "magicaltr...@apache.org" 
<magicaltr...@apache.org> wrote:
>  >
>  >  Repository: oodt
>  >  Updated Branches:
>  >refs/heads/development bfb78c9a0 -> 82b522516
>  >
>  >
>  >  close connection to release client
>  >
>  >
>  >  Project: http://git-wip-us.apache.org/repos/asf/oodt/repo
>  >  Commit: 
http://git-wip-us.apache.org/repos/asf/oodt/commit/82b52251
>  >  Tree: 
http://git-wip-us.apache.org/repos/asf/oodt/tree/82b52251
>  >  Diff: 
http://git-wip-us.apache.org/repos/asf/oodt/diff/82b52251
>  >
>  >  Branch: refs/heads/development
>  >  Commit: 82b5225162f78ee092e473218769bea61e3e510f
>  >  Parents: bfb78c9
>  >  Author: Tom Barber <tom.bar...@jpl.nasa.gov>
>  >  Authored: Tue Dec 12 22:56:39 2017 +
>  >  Committer: Tom Barber <tom.bar...@jpl.nasa.gov>
>  >  Committed: Tue Dec 12 22:56:39 2017 +
>  >
>  >  
--
>  >   .../filemgr/system/AvroFileManagerClient.java   | 320 
+--
>  >   1 file changed, 301 insertions(+), 19 deletions(-)
>  >  
--
>  >
>  >
>  >  
http://git-wip-us.apache.org/repos/asf/oodt/blob/82b52251/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  >  
--
>  >  diff --git 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  >  index 3feda3d..043330a 100644
>  >  --- 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  >  +++ 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  >  @@ -17,45 +17,46 @@
>  >
>  >   package org.apache.oodt.cas.filemgr.system;
>  >
>  >  +import java.io.IOException;
>  >  +import java.net.InetSocketAddress;
>  >  +import java.net.URL;
>  >  +import java.nio.ByteBuffer;
>  >  +import java.util.ArrayList;
>  >  +import java.util.List;
>  >  +import java.util.logging.Level;
>  >  +import java.util.logging.Logger;
>  >   import org.apache.avro.AvroRemoteException;
>  >   import org.apache.avro.ipc.NettyTransceiver;
>  >   import org.apache.avro.ipc.Transceiver;
>  >   import org.apache.avro.ipc.specific.SpecificRequestor;
>  >   import org.apache.oodt.cas.filemgr.datatransfer.DataTransfer;
>  >  +import 
org.apache.oodt.cas.filemgr.exceptions.FileManagerException;
>  >   import org.apache.oodt.cas.filemgr.structs

Re: oodt git commit: close connection to release client

[Chris Mattmann]

Good lord, nevermind yeah looks like a future candidate for a refactoring
since it’s the same line over and over again.





On 12/12/17, 3:01 PM, "Tom Barber" <t...@spicule.co.uk> wrote:

I'm not following, the change was to add a finally block to each client 
call to shut it down after the execution. Those finally blocks I've just 
added in, the only other change was an import clean up.

On 12/12/17 22:58, Chris Mattmann wrote:
> Tom, please revert this commit and do a commit that doesn’t include a 
billion lines of
> formatting change and includes the actual change? (
>
> Cheers,
> Chris
>
>
>
>
> On 12/12/17, 2:56 PM, "magicaltr...@apache.org" <magicaltr...@apache.org> 
wrote:
>
>  Repository: oodt
>  Updated Branches:
>refs/heads/development bfb78c9a0 -> 82b522516
>  
>  
>  close connection to release client
>  
>  
>  Project: http://git-wip-us.apache.org/repos/asf/oodt/repo
>  Commit: http://git-wip-us.apache.org/repos/asf/oodt/commit/82b52251
>  Tree: http://git-wip-us.apache.org/repos/asf/oodt/tree/82b52251
>  Diff: http://git-wip-us.apache.org/repos/asf/oodt/diff/82b52251
>  
>  Branch: refs/heads/development
>  Commit: 82b5225162f78ee092e473218769bea61e3e510f
>  Parents: bfb78c9
>  Author: Tom Barber <tom.bar...@jpl.nasa.gov>
>  Authored: Tue Dec 12 22:56:39 2017 +
>  Committer: Tom Barber <tom.bar...@jpl.nasa.gov>
>  Committed: Tue Dec 12 22:56:39 2017 +
>  
>  
--
>   .../filemgr/system/AvroFileManagerClient.java   | 320 
+--
>   1 file changed, 301 insertions(+), 19 deletions(-)
>  
--
>  
>  
>  
http://git-wip-us.apache.org/repos/asf/oodt/blob/82b52251/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  
--
>  diff --git 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  index 3feda3d..043330a 100644
>  --- 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  +++ 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
>  @@ -17,45 +17,46 @@
>   
>   package org.apache.oodt.cas.filemgr.system;
>   
>  +import java.io.IOException;
>  +import java.net.InetSocketAddress;
>  +import java.net.URL;
>  +import java.nio.ByteBuffer;
>  +import java.util.ArrayList;
>  +import java.util.List;
>  +import java.util.logging.Level;
>  +import java.util.logging.Logger;
>   import org.apache.avro.AvroRemoteException;
>   import org.apache.avro.ipc.NettyTransceiver;
>   import org.apache.avro.ipc.Transceiver;
>   import org.apache.avro.ipc.specific.SpecificRequestor;
>   import org.apache.oodt.cas.filemgr.datatransfer.DataTransfer;
>  +import org.apache.oodt.cas.filemgr.exceptions.FileManagerException;
>   import org.apache.oodt.cas.filemgr.structs.Element;
>  -import org.apache.oodt.cas.filemgr.structs.Product;
>   import org.apache.oodt.cas.filemgr.structs.FileTransferStatus;
>  +import org.apache.oodt.cas.filemgr.structs.Product;
>   import org.apache.oodt.cas.filemgr.structs.ProductPage;
>   import org.apache.oodt.cas.filemgr.structs.ProductType;
>  -import org.apache.oodt.cas.filemgr.structs.Reference;
>   import org.apache.oodt.cas.filemgr.structs.Query;
>  +import org.apache.oodt.cas.filemgr.structs.Reference;
>  +import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroElement;
>   import 
org.apache.oodt.cas.filemgr.structs.avrotypes.AvroFileManager;
>   import 
org.apache.oodt.cas.filemgr.structs.avrotypes.AvroFileTransferStatus;
>   import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroProduct;
>  -import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroElement;
>  -import 
org.apache.oodt.cas.filemgr.structs.avrotypes.AvroQueryResult;
>   import 
org.apache.oodt.cas.filemgr.structs.avrotypes.AvroProductType;
>  +import 
org.apache.oodt.cas.filemgr.structs.a

Re: oodt git commit: close connection to release client

[Chris Mattmann]

Tom, please revert this commit and do a commit that doesn’t include a billion 
lines of
formatting change and includes the actual change? (

Cheers,
Chris




On 12/12/17, 2:56 PM, "magicaltr...@apache.org"  wrote:

Repository: oodt
Updated Branches:
  refs/heads/development bfb78c9a0 -> 82b522516


close connection to release client


Project: http://git-wip-us.apache.org/repos/asf/oodt/repo
Commit: http://git-wip-us.apache.org/repos/asf/oodt/commit/82b52251
Tree: http://git-wip-us.apache.org/repos/asf/oodt/tree/82b52251
Diff: http://git-wip-us.apache.org/repos/asf/oodt/diff/82b52251

Branch: refs/heads/development
Commit: 82b5225162f78ee092e473218769bea61e3e510f
Parents: bfb78c9
Author: Tom Barber 
Authored: Tue Dec 12 22:56:39 2017 +
Committer: Tom Barber 
Committed: Tue Dec 12 22:56:39 2017 +

--
 .../filemgr/system/AvroFileManagerClient.java   | 320 +--
 1 file changed, 301 insertions(+), 19 deletions(-)
--



http://git-wip-us.apache.org/repos/asf/oodt/blob/82b52251/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
--
diff --git 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
index 3feda3d..043330a 100644
--- 
a/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
+++ 
b/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
@@ -17,45 +17,46 @@
 
 package org.apache.oodt.cas.filemgr.system;
 
+import java.io.IOException;
+import java.net.InetSocketAddress;
+import java.net.URL;
+import java.nio.ByteBuffer;
+import java.util.ArrayList;
+import java.util.List;
+import java.util.logging.Level;
+import java.util.logging.Logger;
 import org.apache.avro.AvroRemoteException;
 import org.apache.avro.ipc.NettyTransceiver;
 import org.apache.avro.ipc.Transceiver;
 import org.apache.avro.ipc.specific.SpecificRequestor;
 import org.apache.oodt.cas.filemgr.datatransfer.DataTransfer;
+import org.apache.oodt.cas.filemgr.exceptions.FileManagerException;
 import org.apache.oodt.cas.filemgr.structs.Element;
-import org.apache.oodt.cas.filemgr.structs.Product;
 import org.apache.oodt.cas.filemgr.structs.FileTransferStatus;
+import org.apache.oodt.cas.filemgr.structs.Product;
 import org.apache.oodt.cas.filemgr.structs.ProductPage;
 import org.apache.oodt.cas.filemgr.structs.ProductType;
-import org.apache.oodt.cas.filemgr.structs.Reference;
 import org.apache.oodt.cas.filemgr.structs.Query;
+import org.apache.oodt.cas.filemgr.structs.Reference;
+import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroElement;
 import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroFileManager;
 import 
org.apache.oodt.cas.filemgr.structs.avrotypes.AvroFileTransferStatus;
 import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroProduct;
-import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroElement;
-import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroQueryResult;
 import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroProductType;
+import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroQueryResult;
 import org.apache.oodt.cas.filemgr.structs.avrotypes.AvroReference;
-import 
org.apache.oodt.cas.filemgr.structs.exceptions.RepositoryManagerException;
 import org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException;
+import org.apache.oodt.cas.filemgr.structs.exceptions.ConnectionException;
 import 
org.apache.oodt.cas.filemgr.structs.exceptions.DataTransferException;
+import 
org.apache.oodt.cas.filemgr.structs.exceptions.RepositoryManagerException;
 import 
org.apache.oodt.cas.filemgr.structs.exceptions.ValidationLayerException;
 import org.apache.oodt.cas.filemgr.structs.exceptions.VersioningException;
-import org.apache.oodt.cas.filemgr.structs.exceptions.ConnectionException;
 import org.apache.oodt.cas.filemgr.structs.query.ComplexQuery;
 import org.apache.oodt.cas.filemgr.structs.query.QueryResult;
 import org.apache.oodt.cas.filemgr.util.AvroTypeFactory;
 import org.apache.oodt.cas.filemgr.util.GenericFileManagerObjectFactory;
 import org.apache.oodt.cas.filemgr.versioning.Versioner;
 import org.apache.oodt.cas.metadata.Metadata;
-import java.io.IOException;
-import java.net.InetSocketAddress;
-import java.net.URL;
-import java.nio.ByteBuffer;

Re: SIGSEV from Lucene upgrades in OODT....

[Chris Mattmann]

Hey Lewis,

Agreed here is the info (BTW I believe you should be able to access 
drat-vm.a.o):

javmattmann@drat-vm:~$ java -version
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
mattmann@drat-vm:~$

Let me know what you find Lewis….check the steps below.

Cheers,
Chris


On 11/16/17, 6:01 PM, "lewis john mcgibbney" <lewi...@apache.org> wrote:

Which version of Java is running on drat-vm Chris?
Can you post a link to the DRAT Solr schema being used?
It would be nice to address this before releasing current OODT RC. Not a
total requirement but would be good to get to the bottom of.
Lewis

On Thu, Nov 16, 2017 at 3:36 PM Tom Barber <tom.bar...@meteorite.bi> wrote:

> Hr, I shall take a look!
    >
    > On 16/11/17 23:30, Chris Mattmann wrote:
> > Hey Tom,
> >
> >
> >
> > I’ve noticed while testing in Apache DRAT that the Lucene upgrades you
> did
> > for the file manager regularly on the drat-vm Ubuntu box cause SIGSEV
> failures
> > like the following:
> >
> >
> >
> > WARNING: No Metadata specified for product [TestMetReader.java] for
> required field [DataVersion]: Attempting to continue processing metadata
> >
> > #
> >
> > # A fatal error has been detected by the Java Runtime Environment:
> >
> > #
> >
> > #  SIGSEGV (0xb) at pc=0x7f5afcc030f7, pid=30823,
> tid=0x7f5ab9d4f700
> >
> > #
> >
> > # JRE version: Java(TM) SE Runtime Environment (8.0_151-b12) (build
> 1.8.0_151-b12)
> >
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.151-b12 mixed mode
> linux-amd64 compressed oops)
> >
> > # Problematic frame:
> >
> > # J 1360 C2 org.apache.lucene.store.ByteBufferIndexInput.readByte()B
> (126 bytes) @ 0x7f5afcc030f7 [0x7f5afcc030a0+0x57]
> >
> > #
> >
> > # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> >
> > #
> >
> > # An error report file with more information is saved as:
> >
> > # /home/mattmann/drat/deploy/filemgr/bin/hs_err_pid30823.log
> >
> > Nov 16, 2017 11:25:40 PM
> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog toDoc
> >
> > WARNING: No Metadata specified for product [TestMetReader.java] for
> required field [DataVersion]: Attempting to continue processing metadata
> >
> > Nov 16, 2017 11:25:40 PM
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager runExtractors
> >
> > INFO: Running Met Extractor:
> [org.apache.oodt.cas.filemgr.metadata.extractors.CoreMetExtractor] for
> product type: [GenericFile]
> >
> > Nov 16, 2017 11:25:40 PM
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager runExtractors
> >
> > INFO: Running Met Extractor:
> 
[org.apache.oodt.cas.filemgr.metadata.extractors.examples.MimeTypeExtractor]
> for product type: [GenericFile]
> >
> > Nov 16, 2017 11:25:40 PM
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager runExtractors
> >
> > INFO: Runn
> >
> >
> >
> >
> >
> > Steps to reproduce:
> >
> >
> >
> > 1.   Clone and install Apache DRAT 1.0-SNAPSHOT from apache/drat:
> >
> > 2.   Run DRAT on Apache OODT github
> https://github.com/apache/oodt.git or any repo with thousands of files
> using Proteus
> >
> > 3.   Watch an error like the above appear consistently about
> half-way through crawling…
> >
> >
> >
> > There are some links online and this open LUCENE issue:
> >
> >
> >
> > https://issues.apache.org/jira/browse/LUCENE-6943
> >
> >
> >
> > Tom can you help investigate?
> >
> >
> >
> > Cheers,
> >
> > Chris
> >
> >
> >
> >
> >
> >
>
> --
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

SIGSEV from Lucene upgrades in OODT....

[Chris Mattmann]

Hey Tom,

 

I’ve noticed while testing in Apache DRAT that the Lucene upgrades you did
for the file manager regularly on the drat-vm Ubuntu box cause SIGSEV failures
like the following:

 

WARNING: No Metadata specified for product [TestMetReader.java] for required 
field [DataVersion]: Attempting to continue processing metadata

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x7f5afcc030f7, pid=30823, tid=0x7f5ab9d4f700

#

# JRE version: Java(TM) SE Runtime Environment (8.0_151-b12) (build 
1.8.0_151-b12)

# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 
compressed oops)

# Problematic frame:

# J 1360 C2 org.apache.lucene.store.ByteBufferIndexInput.readByte()B (126 
bytes) @ 0x7f5afcc030f7 [0x7f5afcc030a0+0x57]

#

# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# /home/mattmann/drat/deploy/filemgr/bin/hs_err_pid30823.log

Nov 16, 2017 11:25:40 PM org.apache.oodt.cas.filemgr.catalog.LuceneCatalog toDoc

WARNING: No Metadata specified for product [TestMetReader.java] for required 
field [DataVersion]: Attempting to continue processing metadata

Nov 16, 2017 11:25:40 PM org.apache.oodt.cas.filemgr.system.XmlRpcFileManager 
runExtractors

INFO: Running Met Extractor: 
[org.apache.oodt.cas.filemgr.metadata.extractors.CoreMetExtractor] for product 
type: [GenericFile]

Nov 16, 2017 11:25:40 PM org.apache.oodt.cas.filemgr.system.XmlRpcFileManager 
runExtractors

INFO: Running Met Extractor: 
[org.apache.oodt.cas.filemgr.metadata.extractors.examples.MimeTypeExtractor] 
for product type: [GenericFile]

Nov 16, 2017 11:25:40 PM org.apache.oodt.cas.filemgr.system.XmlRpcFileManager 
runExtractors

INFO: Runn

 

 

Steps to reproduce:

 

1.   Clone and install Apache DRAT 1.0-SNAPSHOT from apache/drat:

2.   Run DRAT on Apache OODT github https://github.com/apache/oodt.git or 
any repo with thousands of files using Proteus 

3.   Watch an error like the above appear consistently about half-way 
through crawling…

 

There are some links online and this open LUCENE issue:

 

https://issues.apache.org/jira/browse/LUCENE-6943 

 

Tom can you help investigate?

 

Cheers,

Chris

 

 

[VOTE] Apache OODT 1.2.1 release candidate #1

[Chris Mattmann]

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

 

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

 

Thanks!

 

Chris

 

P.S. Here is my +1.

 

 

 

Re: DRAT VM up and running and some bugs found

[Chris Mattmann]

/Cross Posting to Apache OODT list of interest

Here’s another bug, thanks to Trout: ( [1] 

That upgrade to 6.2.1 SolrJ and its release with Apache OODT 1.2 [2] 
makes DRAT unusable since it relies on the SolrIndexer component and 
since DRAT uses RADIX Solr Webapp which in turn uses Solr 4.2.1 causing
it to be incompatible. So SolrIndexer is broken in 1.2, until I fixed it in 
[3], 
which was post 1.2 release. 

I’m tempted to upgrade DRAT to use Apache OODT 1-9-SNAPSHOT, however
that includes the AvroRPC merge, and I noticed some weirdness with it when
trying with DRAT at least initially.

Cheers,
Chris



[1] https://git.io/vFaWI 
[2] https://git.io/vFaWz 
[3] https://git.io/vFaW4 




On 11/10/17, 9:04 AM, "Chris Mattmann" <mattm...@apache.org> wrote:

Hey Team,

 

While getting Proteus and DRAT installed on drat-vm.apache.org (which is 
now up and running
thanks to INFRA-15304 [1]), I found that the default installed Solr version 
4.2.1 would not start
on Tomcat. I’m running:

 

~/drat/deploy

mattmann@drat-vm:~/drat/deploy$ java -version

java version "1.8.0_151"

Java(TM) SE Runtime Environment (build 1.8.0_151-b12)

Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)

mattmann@drat-vm:~/drat/deploy$ 

 

And Tomcat7

 

And Solr 4.2.1

 

But I just had to manually install Solr to get it running. We package a 
default 4.2.1 installation
from Maven and then set Solr home via CATALNA_OPTS 
–Dsolr.solr.home=”$DRAT_HOME”/solr”
This seems to work fine on Mac, but for whatever reason didn’t work 
natively on Ubuntu. Does anyone
know why?

 

Anyways Proteus is up and running at:

 

http://drat-vm.apache.org/demo 

And DRAT stats is up at 
http://drat-vm.apache.org/asfgit 
(but there is no data in there yet)

 

Feedback is welcomed!

 

Chris

 

 

 

 

[1] https://issues.apache.org/jira/browse/INFRA-15304 

 

 

Re: Docker and Oracle License Agreement

[Chris Mattmann]

Luca,

Thanks. Things don’t always start out general – sometimes they are committed 
here
to Apache and generalized over time. I would say what you did is a great 
candidate for
a specific “product” of the Apache OODT PMC. Either way, it either a) should 
come as
a “product” of the Apache OODT PMC, realizing it’s not general yet, and will 
possibly
never be generalized, but given the broad exposure here would open it up to 
more 
possibility that it will be generalized; or b) the name of the Docker image and 
GH org
you created for this needs to be changed from “OODT” to not include that in its 
name.
Of course my preference is a).

Cheers,
Chris


On 11/9/17, 8:46 AM, "Sean Kelly" <ke...@apache.org> wrote:

Looks great Luca! Thanks!

--k

Cinquini, Luca (398G) wrote:
> Hi Sean,
> here it is:
>
> https://store.docker.com/community/images/oodthub/oodt-node
>
> Maybe I should mention that these images were created as part of a
> project to run OODT in a scalable architecture on the Cloud… We never
> really meant to generate a completely generic Docker version of the full
> OODT distribution. For example, the FM is always built with the Solr
> back-end. There was no attempt of generality here, rather we wanted to
> build a specific architecture that could be reused across NASA missions.
>
> thanks, L
>
>> On Nov 9, 2017, at 8:43 AM, Sean Kelly <ke...@apache.org
>> <mailto:ke...@apache.org>> wrote:
>>
>> Thanks, Luca.
>>
>> For the short term, please go ahead and add the warning like on [1]
>> that using the image = agreeing to Oracle's license.
>>
>> Another issue that we should address is the size of the image:
>>
>> alpine latest 76da55c8019d 8 weeks ago 3.97MB
>> nutjob4life/catpics latest de30a9f84796 6 weeks ago 57.4MB
>> lwieske/java-8 jdk-8u131-slim 326f0b00e419 4 months ago 164MB
>> python 2.7-slim 451c85955bc2 3 months ago 182MB
>> plone latest e9918460c2e8 9 months ago 424MB
>> oodthub/oodt-node latest cac1bf988d5d 3 months ago 1.38GB
>>
>> 1.38 *giga* bytes! I'm going to wager you're not using a multi-stage
>> build here because that's enormous. Once you commit the Dockerfile we
>> can work together to see if we can trim it down a bit.
>>
>> Take care
>> --k
>>
>>
>>> Cinquini, Luca (398G) <mailto:luca.cinqu...@jpl.nasa.gov>
>>> 2017-11-8 at 1.41 p
>>> Hi Sean,
>>> I am afraid I am responsible for creating those images :)…
>>>
>>> Chris asked me already to move them to the official Apache repo,
>>> which is on my list of things to do.
>>> In the past, openJDK gave me problem when using some advanced SSL
>>> features, like certificate authentication - not sure if that is the
>>> case any more.
>>> I think we could start with your proposal [1] and then possibly
>>> implement [3].
>>>
>>> BTW all these images are based on OODT-1.0, and contain only a few
>>> core services (File Manager, Workflow Manager, Crawler).
>>>
>>> thanks, Luca
>>>
>>>
>>> Chris Mattmann <mailto:mattm...@apache.org>
>>> 2017-11-8 at 1.34 p
>>> Great catch!
>>>
>>> I would vote to just switch it to OpenJDK yay….
>>>
>>> Cheers
>>> Chris
>>>
>>>
>>>
>>>
>>> On 11/8/17, 11:33 AM, "Sean Kelly" <ke...@apache.org
>>> <mailto:ke...@apache.org>> wrote:
>>>
>>> Hi folks:
>>>
>>> I'm playing more and more with Docker and happily discovered that
>>> there's already an OODT presence on the Docker Store [1].
>>>
>>> So I pulled the oodt-node image [2] and looked inside ("docker history
>>> --no-trunc") and saw that one of the steps performed is:
>>>
>>> /bin/sh -c wget --no-cookies --no-check-certificate --header "Cookie:
>>> oraclelicense=accept-securebackup-cookie" -O
>>> /tmp/jdk-8-linux-x64.rpm
>>> 
"http://download.oracle.com/otn-pub/java/jdk/${JAVA_VERSION}-${JAVA_BUILD_VERSION}/d54c1d3a095b4ff2b6607d096fa80163/jdk-${JAVA_VERSION}-linux-x64.rpm;
>>>
>>> What stands out is the cookie.
>>>
>>> My fear is that using this image effect

Re: Docker and Oracle License Agreement

[Chris Mattmann]

Great catch!

I would vote to just switch it to OpenJDK yay….

Cheers
Chris




On 11/8/17, 11:33 AM, "Sean Kelly"  wrote:

Hi folks:

I'm playing more and more with Docker and happily discovered that 
there's already an OODT presence on the Docker Store [1].

So I pulled the oodt-node image [2] and looked inside ("docker history 
--no-trunc") and saw that one of the steps performed is:

/bin/sh -c wget --no-cookies --no-check-certificate --header "Cookie: 
oraclelicense=accept-securebackup-cookie" -O 
/tmp/jdk-8-linux-x64.rpm 

"http://download.oracle.com/otn-pub/java/jdk/${JAVA_VERSION}-${JAVA_BUILD_VERSION}/d54c1d3a095b4ff2b6607d096fa80163/jdk-${JAVA_VERSION}-linux-x64.rpm;

What stands out is the cookie.

My fear is that using this image effectively makes the user accept 
Oracle's license agreement for Java but in no way notifies the user this 
is happening.

Could we at least update the page at [1] to warn users, similar to the 
way this unofficial Java 8 image does it [3]? Or even better, try OpenJDK?

--Sean

[1] https://store.docker.com/profiles/oodthub
[2] https://store.docker.com/community/images/oodthub/oodt-node
[3] https://store.docker.com/community/images/lwieske/java-8

-- 
Sean Kelly
Member, Apache Software Foundation

Re: Need Ganglia configuration info!

[Chris Mattmann]

Ahh gotcha. Paul Zimdars has installed Ganglia before, CC’ing him here he may 
be able to help (




On 11/2/17, 8:48 AM, "Mallder, Valerie" <valerie.mall...@jhuapl.edu> wrote:

Hi Chris,

I'm not looking for information on how to integrate Ganglia with OODT. 
Sorry if I wasn't clear enough. 

I'm looking for information on how to install and configure Ganglia so that 
it can run on our system so that it can THEN be integrated with OODT.  We've 
never used Ganglia in my group, and I don't have system administration 
privileges to install anything, so I'm looking for information I can provide to 
our system administrator to try to get it up and running on a cluster of 7 
machines.

I did find a ganglia.html file that might provide all we need, but it is 
impossible for me to view it right now via firefox running on the linux box, 
displaying on my PC via ssh and cygwin's XWin, and running over VPN to my home 
with Comcast internet.  It is so slow I want to shoot yourself.

Thanks for the reply though. :)

Val







-Original Message-
From: Chris Mattmann [mailto:mattm...@apache.org] 
Sent: Thursday, November 02, 2017 11:38 AM
To: dev@oodt.apache.org
Cc: Deller, Cheryl L.
Subject: Re: Need Ganglia configuration info!

Val if you just set this to any valid URL e.g., http://localhost/, OPSUI 
will work fine … 



On 11/2/17, 7:20 AM, "Mallder, Valerie" <valerie.mall...@jhuapl.edu> wrote:

Hi All,

I am making my umpteenth attempt to make the OODT OPSUI/PCS software 
useful for the JUNO JEDI Instrument science data pipeline and I am looking for 
information on how to configure 'ganglia'.  The website for ganglia and the 
github repository seems to be sparse on documentation for how to configure it 
to run on a cluster of 7 machines, unless I am looking in the wrong places.

Can anyone who is using Ganglia please put me in touch with your system 
administrator who installed it and configured it for you?  Or point me to some 
good documentation.

Thank you!
Valerie


Valerie A. Mallder
JHU/APL Principal Staff
Office: 443-778-7846 (landline), 410-504-2233 (cell)
Email: valerie.mall...@jhuapl.edu<mailto:valerie.mall...@jhuapl.edu>

Re: Need Ganglia configuration info!

[Chris Mattmann]

Val if you just set this to any valid URL e.g., http://localhost/, OPSUI will 
work fine … 



On 11/2/17, 7:20 AM, "Mallder, Valerie"  wrote:

Hi All,

I am making my umpteenth attempt to make the OODT OPSUI/PCS software useful 
for the JUNO JEDI Instrument science data pipeline and I am looking for 
information on how to configure 'ganglia'.  The website for ganglia and the 
github repository seems to be sparse on documentation for how to configure it 
to run on a cluster of 7 machines, unless I am looking in the wrong places.

Can anyone who is using Ganglia please put me in touch with your system 
administrator who installed it and configured it for you?  Or point me to some 
good documentation.

Thank you!
Valerie


Valerie A. Mallder
JHU/APL Principal Staff
Office: 443-778-7846 (landline), 410-504-2233 (cell)
Email: valerie.mall...@jhuapl.edu

Re: AVRO-RPC

[Chris Mattmann]

Dear Radu,

 

Thanks. I am CC’ing the Apache OODT dev list. 

 

1.   In 1.9 (current master to be released), XML-RPC will remain the 
default. The plan
is to release 1.9 with BOTH XML-RPC *and working* AvroRPC support with XML-RPC
turned on as master, with @Deprecated XML-RPC then to forward to 2.0 and in 2.0…

2.   In 2.0 to make AvroRPC the default, and completely remove the XML-RPC 
support. So,
remove all @Deprecated classes for XML-RPC.

3.   Yes, I need help finishing off PCS and Resource can you please help? 
Also need help
finishing Crawler. We should deprecate CrawlDaemon and Controller (the XMLRPC 
ones)
and make AvroRPC versions in 1.9. 

 

Does this plan make sense? If so can you also help me figure out why AvroRPC 
*works* but the client
hangs on my computer running Java8 and MVN3. I can build and test File Manager 
and try out AvroRPC,
it successfully connects to the server, and tells me 0 products for Generic 
File, but unless I hit Ctrl + C on the
client it doesn’t automatically close out the server connection.

 

Any idea there?


Cheers,

Chris

 

 

 

 

From: Radu Manole <manole.v.r...@gmail.com>
Date: Thursday, October 26, 2017 at 6:34 AM
To: Chris Mattmann <mattm...@apache.org>
Subject: AVRO-RPC

 

Hi,  

sorry I'm so late, was busy last week, I looked at the all the modules where 
avro is implemented. 

most important modules are done In my opinion, but need some tweaks, 

should the avro be the default if if xmlrpc is deprecated? 

resource module its not finished, and tested. 

pcs module uses resource module xmlrpc classes, should be useing abstract class.

And the crawler module the CrawlDeamon and CrawlDeamonController are 
deprecated, should they be replaced to avrorpc implementation (like is written 
in the comments)? 

I may find some more things that should be changed.

Sorry, but what is the best approach for working on the project at this time. 

Apache DRAT!

[Chris Mattmann]

Hey Apache OODT’ers,

 

Just wanted to make everyone aware of Apache DRAT, which is now an Apache Top 
Level
project:

 

http://github.com/apache/drat/

 

We are still working on the website but the Github has a lot of documentation, 
a wiki, and
videos and papers to read and presentations to review.

 

DRAT is a full up example built on top of Apache OODT showing how to do Map 
Reduce with
OODT and the benefits and advantages of using OODT for code analysis, but as a 
platform and
a system too.

 

I recommend checking it out! Join our d...@drat.apache.org mailing list and 
help us out!

 

Thanks,

Chris

 

 

 

Re: Merge Avro RPC

[Chris Mattmann]

Hey Radu,

Hope you are well! Your work is now merged in our master: branch with OODT and 
also merged
with distributed configuration management/Zookeeper! Not sure you have been 
keeping up 
but wanted to get you involved. I am testing out the Avro stuff. Starting with 
the File Manager.
Seems to work great! The one thing I’m seeing though is that when I run the 
filemgr-client 
script, e.g., --getNumProducts, the script hangs, and doesn’t return after 
returning the correct
value, see this sequence:

https://paste.apache.org/r8Uz

1. Do you know why it’s doing this?
2. Can you help debug and stabilize master so that we can release Apache OODT 
1.9 with
this featured prominently?

Thanks!

Cheers,
Chris



On 10/5/16, 2:22 PM, "Radu Manole" <manole.v.r...@gmail.com> wrote:

Hello, I I revisited every module where avrorpc was implemented and where
xmlrpc is,
and marked every class where avro rpc is not implemented. What kind of
transition to avro-rpc should be implemented? The easiest way is to remove
xml-rpc and give up on compatibility with old version. Or make the client
compatible to connect to both xml-rpc or avro-rpc servers, for the
transition.

2016-09-09 19:23 GMT+03:00 lewis john mcgibbney <lewi...@apache.org>:

> So what's the plan then? Where is work going into? Did we define a 
roadmap?
> Maybe we are best working off of 2.x branch then.
>
> On Wednesday, September 7, 2016, Tom Barber <tom.bar...@meteorite.bi>
> wrote:
>
> > Be warned folks,  don't forget we've merged into mainline and have a
> > development branch for 2.0!
> >
> > On Wed, Sep 7, 2016 at 7:38 PM, lewis john mcgibbney <lewi...@apache.org
> > <javascript:;>>
> > wrote:
> >
> > > Hi Radu,
> > > Yes this is great.
> > > I would suggest that you submit a patch to '@Deprecate' all of the
> XMLRPC
> > > code for this current development drive.
> > > I also suggest that we make the AvroRPC material default from now on
> and
> > > get more people using it.
> > > We can also make upgrades to Avro 1.8.X
> > > Would be great if others can chime in here to discuss the path for a
> > > complete replacement of the XMLRPC logic with AvroRPC for the next
> > release
> > > or two.
> > > Thanks
> > > Lewis
> > >
> > > P.S. @Radu, in the meantime please log an issue for @Deprecat'ing all
> of
> > > the XMLRPC stuff. This should be clearly stated and present within
> > > generated Javadoc such that people know to use the AvroRPC
> > implementation.
> > > Thanks
> > >
> > > On Mon, Sep 5, 2016 at 6:17 AM, Radu Manole <manole.v.r...@gmail.com
> > <javascript:;>>
> > > wrote:
> > >
> > > > Hello, great to hear that avro rpc support is still wanted, if there
> is
> > > > anything else to be done, I have a lot of free time now.
> > > >
> > > > 2016-07-06 17:09 GMT+03:00 Mattmann, Chris A (3980) <
> > > > chris.a.mattm...@jpl.nasa.gov <javascript:;>>:
> > > >
> > > > > +1 awesome
> > > > >
> > > > > ++
> > > > > 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/
> > > > > ++
> > > > > 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 7

FW: Build failed in Jenkins: oodt-trunk #2198

[Chris Mattmann]

Hi,

We are getting a lot of errors like this that look like the build slaves don’t 
have JDK8.
Can someone that has Jenkins admin check?

Thanks,
Chris




On 10/12/17, 11:04 AM, "Apache Jenkins Server"  
wrote:

See 

--
Started by an SCM change
Started by an SCM change
No JDK named ‘JDK 1.8.0_102’ found
ERROR: Issue with creating launcher for agent qnode1. The agent is being 
disconnected
[EnvInject] - Loading node environment variables.
ERROR: SEVERE ERROR occurs
org.jenkinsci.lib.envinject.EnvInjectException: 
hudson.remoting.ChannelClosedException: channel is already closed
at 
org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvVarsForNode(EnvironmentVariablesNodeLoader.java:95)
at 
org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:80)
at 
org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:43)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:534)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:454)
at hudson.model.Run.execute(Run.java:1737)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:419)
Caused by: hudson.remoting.ChannelClosedException: channel is already closed
at hudson.remoting.Channel.send(Channel.java:613)
at hudson.remoting.Request.call(Request.java:130)
at hudson.remoting.Channel.call(Channel.java:838)
at hudson.FilePath.act(FilePath.java:1082)
at 
org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvVarsForNode(EnvironmentVariablesNodeLoader.java:64)
... 8 more
Caused by: java.io.IOException
at hudson.remoting.Channel.close(Channel.java:1301)
at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:180)
at hudson.remoting.PingThread.ping(PingThread.java:130)
at hudson.remoting.PingThread.run(PingThread.java:86)
Caused by: java.util.concurrent.TimeoutException: Ping started at 
1507828255928 hasn't completed by 1507828496865
... 2 more
No JDK named ‘JDK 1.8.0_102’ found
[EnvInject] - [ERROR] - SEVERE ERROR occurs: channel is already closed
No JDK named ‘JDK 1.8.0_102’ found
No JDK named ‘JDK 1.8.0_102’ found

Re: Stable Development/2.0 branch and Plan

[Chris Mattmann]

Hey Val,

Yep it’s already there hidden away in the client layers and server layers. You 
won’t
have to change your server or client apps. One thing though is that you can’t 
use a 
pre 2.x server with a client, and vice versa. 1.9 will still support both. 

I’ll make sure to test/work on docs, etc. I am using OODT with DRAT (now a top 
level
Apache project, check it out: http://github.com/apache/drat) and so will be 
motivated
to make this all work and document it.

Help in doing so is welcomed (

Cheers,
Chris




On 10/12/17, 10:52 AM, "Mallder, Valerie" <valerie.mall...@jhuapl.edu> wrote:

Hey Folks,

Will you be providing new workflow, filemgr, resource, etc applications 
that are all avro-based? 

Val


-Original Message-
From: Chris Mattmann [mailto:mattm...@apache.org] 
Sent: Thursday, October 12, 2017 1:33 PM
To: dev@oodt.apache.org
Subject: Stable Development/2.0 branch and Plan

Hey Folks,

 

Thanks to the amazing work from Imesha and some of my own work on the 
development: 
branch, we now have a merged ZK feature and Avro RPC feature branch 
stabilized, and building fine:

 

[INFO] OODT Core .. SUCCESS [  
2.089 s]

[INFO] Common Utilities ... SUCCESS [ 
23.410 s]

[INFO] CAS Command Line Interface . SUCCESS [  
8.908 s]

[INFO] OODT - Configuration Management  SUCCESS [ 
24.494 s]

[INFO] Process Control System Input Data Package .. SUCCESS [  
1.604 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  2.893 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [03:17 
min]

[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 
19.712 s]

[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 
34.483 s]

[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 
28.783 s]

[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  
1.913 s]

[INFO] CAS Curation Web Services .. SUCCESS [ 
10.401 s]

[INFO] Process Control System Core Package  SUCCESS [ 
19.273 s]

[INFO] OODT Wicket Web Components . SUCCESS [  
4.770 s]

[INFO] CAS Curation Interface . SUCCESS [ 
10.254 s]

[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 
22.754 s]

[INFO] CAS Installer Maven Mojo ... SUCCESS [  
3.097 s]

[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  
1.194 s]

[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  
1.341 s]

[INFO] OODT :: Archetypes . SUCCESS [  
0.033 s]

[INFO] CAS File Manager Browser Web App ... SUCCESS [  
8.492 s]

[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  
5.006 s]

[INFO] CAS Product Server Web Application . SUCCESS [ 
13.420 s]

[INFO] CAS Workflow REST Services . SUCCESS [  
4.638 s]

[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 
19.873 s]

[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [  
8.082 s]

[INFO] Apache OODT  SUCCESS [  
0.040 s]

[INFO] 


[INFO] BUILD SUCCESS

[INFO] 


[INFO] Total time: 07:58 min

[INFO] Finished at: 2017-10-12T10:28:04-07:00

[INFO] Final Memory: 123M/1584M

[INFO] 


nonas:oodt mattmann$ git push -u origin development

 

Great work in OODT-963 and OODT-964 wrapped this up. My proposal:

 

1.   I am going to merge development into master:

2.   Let’s make an OODT 1.9 release that will be the last release in 
the 1.x series, which 
includes XML-RPC (optionally), but also gives you the AvroRPC the 
recommended solution (along with ZK and distributed config)

3.   After 1.9, we change the version in master: to 2.0-dev, and then 
in 2.0-dev we 
remove XML-RPC, and fix any breaks. Then we release 2.0 with only AvroRPC 
as the default.

 

I will execute step one of this plan in the next few minutes. Feedback is 
welcomed!


Cheers

Chris

 

 

 

Stable Development/2.0 branch and Plan

[Chris Mattmann]

Hey Folks,

 

Thanks to the amazing work from Imesha and some of my own work on the 
development: 
branch, we now have a merged ZK feature and Avro RPC feature branch stabilized, 
and 
building fine:

 

[INFO] OODT Core .. SUCCESS [  2.089 s]

[INFO] Common Utilities ... SUCCESS [ 23.410 s]

[INFO] CAS Command Line Interface . SUCCESS [  8.908 s]

[INFO] OODT - Configuration Management  SUCCESS [ 24.494 s]

[INFO] Process Control System Input Data Package .. SUCCESS [  1.604 s]

[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  2.893 s]

[INFO] Catalog and Archive File Management Component .. SUCCESS [03:17 min]

[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 19.712 s]

[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 34.483 s]

[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 28.783 s]

[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  1.913 s]

[INFO] CAS Curation Web Services .. SUCCESS [ 10.401 s]

[INFO] Process Control System Core Package  SUCCESS [ 19.273 s]

[INFO] OODT Wicket Web Components . SUCCESS [  4.770 s]

[INFO] CAS Curation Interface . SUCCESS [ 10.254 s]

[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 22.754 s]

[INFO] CAS Installer Maven Mojo ... SUCCESS [  3.097 s]

[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  1.194 s]

[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  1.341 s]

[INFO] OODT :: Archetypes . SUCCESS [  0.033 s]

[INFO] CAS File Manager Browser Web App ... SUCCESS [  8.492 s]

[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  5.006 s]

[INFO] CAS Product Server Web Application . SUCCESS [ 13.420 s]

[INFO] CAS Workflow REST Services . SUCCESS [  4.638 s]

[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 19.873 s]

[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [  8.082 s]

[INFO] Apache OODT  SUCCESS [  0.040 s]

[INFO] 

[INFO] BUILD SUCCESS

[INFO] 

[INFO] Total time: 07:58 min

[INFO] Finished at: 2017-10-12T10:28:04-07:00

[INFO] Final Memory: 123M/1584M

[INFO] 

nonas:oodt mattmann$ git push -u origin development

 

Great work in OODT-963 and OODT-964 wrapped this up. My proposal:

 

1.   I am going to merge development into master:

2.   Let’s make an OODT 1.9 release that will be the last release in the 
1.x series, which 
includes XML-RPC (optionally), but also gives you the AvroRPC the recommended 
solution (along with ZK and distributed config)

3.   After 1.9, we change the version in master: to 2.0-dev, and then in 
2.0-dev we 
remove XML-RPC, and fix any breaks. Then we release 2.0 with only AvroRPC as
the default.

 

I will execute step one of this plan in the next few minutes. Feedback is 
welcomed!


Cheers

Chris

 

 

 

Re: Problem with Zookeeper-config feature in development branch

[Chris Mattmann]

Thanks Imesha, appreciate it. I think there is more going on with the 2nd test 
though. I think it has to do with the workflow manager not being able to read 
system properties from the distributed configuration. That test hasn’t failed in
years, and it has always read the needed properties from the workflow.properties
file locally. My guess is that the test is failing due to distributed 
configuration reading.
Can you double check? Or perhaps property files were moved?

Cheers,
Chris




On 10/11/17, 6:06 AM, "Imesha Sudasingha" <imesha...@cse.mrt.ac.lk> wrote:

Hey Chris,

The problem was with maven surefire plugin which had  set to
"never". Changed it to "perTest" which solved majority of the cases. I
fixed it and sent a PR. please merge it to development if you feel ok. That
PR include some changes in zookeeper module as well.

Still there is an NPE in

"org.apache.oodt.cas.workflow.repository.DataSourceWorkflowRepositoryFactory"
at line 68. The problem there is, we are trying to use a JDBC connection
even at the testing phase. But the property
*org.apache.oodt.cas.workflow.repo.datasource.jdbc.driver* is always null.
Can you look into that?

Other tests are passing now.

Regards,
Imesha

Kind Regards,
*Imesha Sudasingha*
Undergraduate of Department of Computer Science and  Engineering,
University of Moratuwa,
Sri Lanka.

<https://lk.linkedin.com/in/imeshasudasingha>  <https://github.com/IMS94>
<http://stackoverflow.com/users/4012073/imesha-sudasingha>

On 11 October 2017 at 00:17, Chris Mattmann <mattm...@apache.org> wrote:

> Hey Imesha,
>
> I’m working with ZK-config feature and trying to merge it into the
> development
> branch but running into errors related to the workflow manager tests:
>
> https://paste.apache.org/Vd4a
>
> FYI: it seems that the ZK config publishes workflow configuration here:
> /projects/primary/components/wmgr/
>
> But then expects to read it here:
> /oodt/projects/default/components/wmgr
>
> Which seems like a mismatch, no?
>
> Can you help resolve this? I’m trying to get AvroRPC and ZK-config,
> merged, and
> working in development branch, so that we can release a stable OODT 2.0.
>
> Cheers,
> Chris
>
>
>
>

Problem with Zookeeper-config feature in development branch

[Chris Mattmann]

Hey Imesha,

I’m working with ZK-config feature and trying to merge it into the development
branch but running into errors related to the workflow manager tests:

https://paste.apache.org/Vd4a 

FYI: it seems that the ZK config publishes workflow configuration here:
/projects/primary/components/wmgr/

But then expects to read it here:
/oodt/projects/default/components/wmgr

Which seems like a mismatch, no?

Can you help resolve this? I’m trying to get AvroRPC and ZK-config, merged, and
working in development branch, so that we can release a stable OODT 2.0.

Cheers,
Chris
 

Re: Adding New Workflows in OODT

[Chris Mattmann]

Gotcha.

 

#1 should work fine…and there is API support for it.

 

#2 is committed, but untested. If you want I can help you work with you but I 
haven’t 
tested it.

 

Cheers,

Chris

 

 

 

 

From: "Malarout, Namrata (398M)" <namrata.malar...@jpl.nasa.gov>
Date: Thursday, September 28, 2017 at 1:57 PM
To: Chris Mattmann <mattm...@apache.org>
Cc: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: Re: Adding New Workflows in OODT

 

Chris,

 

I did consider using dynamic workflows but it requires the tasks to already be 
defined, which is not the case. It becomes more complicated when there are 
tasks that need to run in parallel.

Scientists decide how they want their data to be processed. They design the 
workflow and choose which services they want. I receive a JSON which describes 
the workflow in the form of a graph. Each node’s description contains a URL to 
a CMDA service. Each service is executed as a task. My first PGE is parsing the 
JSON file to determine the structure of the workflow.

 

Since I only get an idea about the workflow structure after the workflow 
manager is already up and running, I need a way to add tasks and workflows 
dynamically.

The approaches I am considering are:

1.  Create the new workflow.xml and update task.xml, then refreshRepository

2.  Or use addTask() and executeWorkflow()

It would great to get some input on how to make this happen. 

 

Thanks,

Namrata

 

From: Chris Mattmann <mattm...@apache.org>
Date: Thursday, September 28, 2017 at 8:56 AM
To: "Malarout, Namrata (398M)" <namrata.malar...@jpl.nasa.gov>
Cc: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: Re: Adding New Workflows in OODT

 

Namrata, why not just use dynamicWorkflows? It will achieve the same effect, 
and has already 
been exposed at the XML-RPC API level? 

 

I’m CC’ing dev@oodt.a.o as this would be a great thing to discuss on list.

 

Cheers,

Chris

 

 

 

 

From: "Malarout, Namrata (398M)" <namrata.malar...@jpl.nasa.gov>
Date: Thursday, September 28, 2017 at 8:44 AM
To: "Mattmann, Chris A (3010)" <chris.a.mattm...@jpl.nasa.gov>
Subject: Adding New Workflows in OODT

 

Hey Chris,

 

How are you doing? Hope everything is well. Congratulations again on your 
adorable baby girl! J 

 

For CMDA, I am looking for a way to add and execute new workflows without 
having to restart the workflow engine. I was going through the OODT change log 
and came across OODT-563 “Modifying Workflow Manager to allow adding new 
workflows” (varunr). Based on the JIRA issue 
(https://issues.apache.org/jira/browse/OODT-563), I seems like 
executeWorkflow() and addTask() would be useful for our use case. Please 
correct me if I misunderstood the ticket. And is there any documentation or 
example of how to use these features?

 

Thanks, in advance for your help. 

 

Regards,

Namrata

Re: Adding New Workflows in OODT

[Chris Mattmann]

Namrata, why not just use dynamicWorkflows? It will achieve the same effect, 
and has already 
been exposed at the XML-RPC API level? 

 

I’m CC’ing dev@oodt.a.o as this would be a great thing to discuss on list.

 

Cheers,

Chris

 

 

 

 

From: "Malarout, Namrata (398M)" 
Date: Thursday, September 28, 2017 at 8:44 AM
To: "Mattmann, Chris A (3010)" 
Subject: Adding New Workflows in OODT

 

Hey Chris,

 

How are you doing? Hope everything is well. Congratulations again on your 
adorable baby girl! J 

 

For CMDA, I am looking for a way to add and execute new workflows without 
having to restart the workflow engine. I was going through the OODT change log 
and came across OODT-563 “Modifying Workflow Manager to allow adding new 
workflows” (varunr). Based on the JIRA issue 
(https://issues.apache.org/jira/browse/OODT-563), I seems like 
executeWorkflow() and addTask() would be useful for our use case. Please 
correct me if I misunderstood the ticket. And is there any documentation or 
example of how to use these features?

 

Thanks, in advance for your help. 

 

Regards,

Namrata

Imesha's Blog post about Apache OODT and GSOC 2017

[Chris Mattmann]

…is here: 
https://loneidealist.wordpress.com/2017/08/24/gsoc-2017-distributed-configuration-management-for-apache-oodt/

Great work Imesha!

Cheers,
Chris

Re: Welcome Imesha

[Chris Mattmann]

Welcome Imesha!



On 8/28/17, 7:56 AM, "Tom Barber"  wrote:

Hi folks,

For those who haven't been following, Imesha has been doing some great work
in bringing Zookeeper config management to OODT, hopefully this is an
ongoing thing and we can roll it out across the board to better aid
distribution.

That aside, as  ever we like to thank those who contribute and as such,
Imesha is now a fully fledged OODT committer and PMC member.

Congrats and welcome to Imesha.

Tom

Re: [RESULT] Apache OODT 1.2 release

[Chris Mattmann]

Congrats! I’ll try and test it in DRAT and VOTE post mortem soon.




On 8/25/17, 3:55 PM, "Tom Barber"  wrote:

Thanks to Sean and Lewis for sparing some time for this 1.2 release.

After 10 days we have collated

+1: 3
0: 0
-1: 0

I'll call this release a wrap and get the artifacts prepared for release.

Thanks again

Tom


On Wed, Aug 23, 2017 at 11:04 PM, Tom Barber  wrote:

> Thanks for your attention chaps, unless anything surfaces I'll release 1.2
> on Friday when I have some spare cycles.
>
> On Wed, Aug 23, 2017 at 10:26 PM, lewis john mcgibbney  > wrote:
>
>> +1 same tests carried out as Nutjob.
>> Thank you
>> Lewis
>>
>> On Tue, Aug 15, 2017 at 12:27 PM, Tom Barber 
>> wrote:
>>
>> > Hi Folks,
>> >
>> > I have posted a 1st release candidate for the Apache OODT 1.2 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://git-wip-us.apache.org/repos/asf?p=oodt.git;a=commit;h=
>> > 0ac41fe873dee7ec2bb897364af121d645579c7a
>> >
>> > A staged Maven repository is available at:
>> > https://repository.apache.org/content/repositories/orgapacheoodt-1014/
>> >
>> > Please vote on releasing these packages as Apache OODT 1.2. 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!
>> >
>> > Trout
>> >
>> > P.S. Here is my +1.
>> >
>>
>>
>>
>> --
>> http://home.apache.org/~lewismc/
>> @hectorMcSpector
>> http://www.linkedin.com/in/lmcgibbney
>>
>
>
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316 <+44%2056%200364%201316>
> US: +18448141689 <(844)%20814-1689>
>
> 
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689

Re: [GSoC2017] Distributed Configuration Management - Update

[Chris Mattmann]

Fantastic progress, Imesha, as usual.

Please connect with me as you test out workflow and resource manager, since
both are present in DRAT and can be used to test your code too.

Cheers,
Chris




On 8/12/17, 6:27 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: ComplexQuery, queryTool, and LuceneQuery not functional in file manager?

[Chris Mattmann]

Let me run another DRAT session look at the logs and get back to you ASAP.

Cheers,
Chris




On 8/3/17, 7:49 AM, "Tom Barber" <tom.bar...@meteorite.bi> wrote:

Hey Chris,

I tested master against drat a bit earlier in the week and couldn't find
any more HitCollector exceptions, do you know of any more, or should I
start a 1.2 release?

Tom

On Thu, Jul 27, 2017 at 3:02 AM, Chris Mattmann <mattm...@apache.org> wrote:

> Thanks Trout. Can you also fix the Lucene catalog? I’m seeing a ton of
> exceptions in
> it dealing with HitCollector and TotalHitCount…
>
>
>
> On 7/26/17, 5:32 AM, "Tom Barber" <tom.bar...@meteorite.bi> wrote:
>
> Sorry I think this is collateral from the Lucene 4.x to 6.x upgrade we
> did
> the other month. I'm sure there will be a few other minor niggles in
> there
> as people use it but we've been using that code internally for months
> and
> not yet hit anything major. Patch went into development to fix the
> lucene
> queryability I believe
>
> https://asciinema.org/a/1zXRxx3OeWxwYaLSW0UqM8S3J
>
> Assuming it checks out, and it seems to work here. Want me to roll a
> 1.1.1
> over the weekend?
>
> Tom
>
>
> On Wed, Jul 26, 2017 at 9:36 AM, Tom Barber <tom.bar...@meteorite.bi>
> wrote:
>
> > Thanks for the letting me know where on the scale of badness where
> this
> > one lies. That said, the fix for the XMLRPC stuff appears to be
> there. I'll
> > slap a debugger on it and check a fresh RADIX build.
> >
> > Tom
> >
> > On Wed, Jul 26, 2017 at 1:06 AM, Mattmann, Chris A (3010) <
> > chris.a.mattm...@jpl.nasa.gov> wrote:
> >
> >> Tom,
> >>
> >> Did you break all of the referenced in the subject line?
> >>
> >> Bad, bad, Tom. Bad…
> >>
> >> Thoughts?
> >>
> >> They all need fixing as the only way I can page through the
> >> FM at the moment is to use the paging API.
> >>
> >> Cheers,
> >> Chris
> >>
> >>
> >> 
> >> ++
> >> Chris Mattmann, Ph.D.
> >> Principal Data Scientist, Engineering Administrative Office (3010)
> >> Manager, NSF & Open Source Projects Formulation and Development
> Offices
> >> (8212)
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 180-503E, Mailstop: 180-503
> >> 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/
> >> 
> >> ++
> >>
> >>
> >>
> >
>
>
>
>

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

[Chris Mattmann]

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" <mattm...@apache.org> 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: Website update blocked on: https://issues.apache.org/jira/browse/INFRA-14725

[Chris Mattmann]

OK addressed and website updated, release complete! (

Cheers,
Chris




On 7/27/17, 8:10 PM, "Chris Mattmann" <mattm...@apache.org> wrote:

Git Pub Sub not working and Git mirroring for asf-site/site-dev not working…

Website update blocked on: https://issues.apache.org/jira/browse/INFRA-14725

[Chris Mattmann]

Git Pub Sub not working and Git mirroring for asf-site/site-dev not working…

[ANNOUNCE] Apache OODT 1.1 release

[Chris Mattmann]

The Apache OODT project is pleased to announce the release of Apache OODT 
1.1. The release contents have been pushed out to the main Apache release site 
and to the
Maven Central sync, so the releases should be available as soon as the mirrors 
get the syncs.

Apache OODT is a software framework as well as an architectural style for the
rapid construction of scientific data systems.  It provides components for
data capture, curation, metadata extraction, workflow management, resource
management, and data processing.

Apache OODT 1.1 contains a number of improvements and bug fixes. Details
can be found in the changes file:
http://www.apache.org/dist/oodt/CHANGES-1.1.txt 

Apache OODT is available in source form from the following download page:
http://www-us.apache.org/dist/oodt/apache-oodt-1.1-src.zip 

Apache OODT is also available in binary form or for use using Maven 2 from
the Central Repository:
http://repo1.maven.org/maven2/org/apache/oodt/ 

In the initial 48 hours, the release may not be available on all mirrors.
When downloading
from a mirror site, please remember to verify the downloads using
signatures found on the
Apache site:
https://people.apache.org/keys/group/oodt.asc 

For more information on Apache OODT, visit the project home page:
http://oodt.apache.org/

-- Chris Mattmann, on behalf of the Apache OODT community

[RESULT] [VOTE] Apache OODT 1.1 Release Candidate #2

[Chris Mattmann]

Hi Everyone,

The below VOTE has passed with the following tallies:

+1s

Chris Mattmann
Tom Barber
Sean Kelly
Valerie Mallder
Lewis John McGibbney
Paul Ramirez
Billy Webb (note he VOTEd +1 on RC #1)

I’ll go ahead and push out the release!

Cheers,
Chris


On 7/19/17, 12:01 PM, "Chris Mattmann" <mattm...@apache.org> wrote:

Hi Folks,

I have posted a 2nd 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:

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

The release was made from the OODT 1.1 tag at:

https://github.com/apache/oodt/tree/1.1/

A staged Maven repository is available at:

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

Please vote on releasing these packages as Apache OODT 1.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.1

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

Thanks!

    Chris Mattmann

P.S. Here is my +1.

Re: ComplexQuery, queryTool, and LuceneQuery not functional in file manager?

[Chris Mattmann]

Thanks Trout. Can you also fix the Lucene catalog? I’m seeing a ton of 
exceptions in 
it dealing with HitCollector and TotalHitCount…



On 7/26/17, 5:32 AM, "Tom Barber" <tom.bar...@meteorite.bi> wrote:

Sorry I think this is collateral from the Lucene 4.x to 6.x upgrade we did
the other month. I'm sure there will be a few other minor niggles in there
as people use it but we've been using that code internally for months and
not yet hit anything major. Patch went into development to fix the lucene
queryability I believe

https://asciinema.org/a/1zXRxx3OeWxwYaLSW0UqM8S3J

Assuming it checks out, and it seems to work here. Want me to roll a 1.1.1
over the weekend?

Tom


On Wed, Jul 26, 2017 at 9:36 AM, Tom Barber <tom.bar...@meteorite.bi> wrote:

> Thanks for the letting me know where on the scale of badness where this
> one lies. That said, the fix for the XMLRPC stuff appears to be there. 
I'll
> slap a debugger on it and check a fresh RADIX build.
>
> Tom
>
> On Wed, Jul 26, 2017 at 1:06 AM, Mattmann, Chris A (3010) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
>
>> Tom,
>>
>> Did you break all of the referenced in the subject line?
>>
>> Bad, bad, Tom. Bad…
>>
>> Thoughts?
>>
>> They all need fixing as the only way I can page through the
>> FM at the moment is to use the paging API.
>>
>> Cheers,
    >> Chris
>>
>>
>> 
>> ++
>> Chris Mattmann, Ph.D.
>> Principal Data Scientist, Engineering Administrative Office (3010)
>> Manager, NSF & Open Source Projects Formulation and Development Offices
>> (8212)
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 180-503E, Mailstop: 180-503
>> 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/
>> 
>> ++
>>
>>
>>
>

Re: ComplexQuery, queryTool, and LuceneQuery not functional in file manager?

[Chris Mattmann]

Thanks – can you push into master (just these updates and yes roll a 1.2 let’s 
just call it 1.2) say this weekend?
I’ll get 1.1 out hopefully today and the website updated.

Cheers,
Chris




On 7/26/17, 5:32 AM, "Tom Barber" <tom.bar...@meteorite.bi> wrote:

Sorry I think this is collateral from the Lucene 4.x to 6.x upgrade we did
the other month. I'm sure there will be a few other minor niggles in there
as people use it but we've been using that code internally for months and
not yet hit anything major. Patch went into development to fix the lucene
queryability I believe

https://asciinema.org/a/1zXRxx3OeWxwYaLSW0UqM8S3J

Assuming it checks out, and it seems to work here. Want me to roll a 1.1.1
over the weekend?

Tom


On Wed, Jul 26, 2017 at 9:36 AM, Tom Barber <tom.bar...@meteorite.bi> wrote:

> Thanks for the letting me know where on the scale of badness where this
> one lies. That said, the fix for the XMLRPC stuff appears to be there. 
I'll
> slap a debugger on it and check a fresh RADIX build.
>
> Tom
>
> On Wed, Jul 26, 2017 at 1:06 AM, Mattmann, Chris A (3010) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
>
>> Tom,
>>
>> Did you break all of the referenced in the subject line?
>>
>> Bad, bad, Tom. Bad…
>>
>> Thoughts?
>>
>> They all need fixing as the only way I can page through the
>> FM at the moment is to use the paging API.
>>
>> Cheers,
    >> Chris
>>
>>
>> 
>> ++
>> Chris Mattmann, Ph.D.
>> Principal Data Scientist, Engineering Administrative Office (3010)
>> Manager, NSF & Open Source Projects Formulation and Development Offices
>> (8212)
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 180-503E, Mailstop: 180-503
>> 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/
>> 
>> ++
>>
>>
>>
>

Re: oodt git commit: add mattmann's new key

[Chris Mattmann]

Woot woot!

Thanks SK I’ll push the approved RC tomorrow! (

On 7/25/17, 7:52 AM, "Sean Kelly" <ke...@apache.org> wrote:

You already have the 3 needed votes, but of course you have my support 
as well!

+1 to release Apache™ OODT 1.1.

Can we get a "woot woot" in here? 
    
--k

> Chris Mattmann <mailto:mattm...@apache.org>
> 2017-07-24 at 6.52 p
> Sean, Tom, updated the KEYS file please provide your +1s on the RC
>
>
>
> On 7/24/17, 4:51 PM, "mattm...@apache.org" <mattm...@apache.org> wrote:
>
> Repository: oodt
> Updated Branches:
> refs/heads/master 87274d65a -> 4589b58ec
>
>
> add mattmann's new key
>
> Project: http://git-wip-us.apache.org/repos/asf/oodt/repo
> Commit: http://git-wip-us.apache.org/repos/asf/oodt/commit/4589b58e
> Tree: http://git-wip-us.apache.org/repos/asf/oodt/tree/4589b58e
> Diff: http://git-wip-us.apache.org/repos/asf/oodt/diff/4589b58e
>
> Branch: refs/heads/master
> Commit: 4589b58ec126a5c60dfc7223ee02676fbbcda858
> Parents: 87274d6
    > Author: Chris Mattmann <mattm...@apache.org>
> Authored: Mon Jul 24 16:51:10 2017 -0700
> Committer: Chris Mattmann <mattm...@apache.org>
> Committed: Mon Jul 24 16:51:10 2017 -0700
>
> --
> KEYS | 39 +++
> 1 file changed, 39 insertions(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/oodt/blob/4589b58e/KEYS
> --
> diff --git a/KEYS b/KEYS
> index d3856f9..1dc1aeb 100644
> --- a/KEYS
> +++ b/KEYS
> @@ -343,3 +343,42 @@ 
> IGuODo8x0hnGrvAOZYb5BUL7/CRo9PMt91DLPOREFSMHVEsA12OnaTQ2hPZrVOcV
> HSTj1SAfoZ5erxSk3/eMd3H52/6jBg==
> =yBb7
    > -END PGP PUBLIC KEY BLOCK-
> +
> +pub 2048R/0C1E654B 2016-04-29
> +uid Chris Mattmann (CODE SIGNING KEY - Apr 2016) <mattm...@apache.org>
> +sig 3 0C1E654B 2016-04-29 Chris Mattmann (CODE SIGNING KEY - Apr 
> 2016) <mattm...@apache.org>
> +sub 2048R/FFD0461C 2016-04-29
> +sig 0C1E654B 2016-04-29 Chris Mattmann (CODE SIGNING KEY - Apr 2016) 
> <mattm...@apache.org>
> +
> +-BEGIN PGP PUBLIC KEY BLOCK-
> +Version: GnuPG v1
> +
> +mQENBFcjwYIBCACpLaKDNBeVnvIFRHYyoNvfro81tzNzpUBwClyBtJWeu6tpBZiH
> +fb6JgPu2p1z8N4b2NLS9T+cbmeyVvVrqF1vqFFK4EVBqNEms9dyNektBU1SjBgy5
> +RzYM7lM67RgII7s7l3CpxL7t8znGKB95w8p09jm4cOFk8n0upeqTXvfD06mzK/MK
> +xk45ljoFWJbo468l0xLDBuTg+UdQQe2nbBe2TY65SC9ZFkcVd0drUq7o/S/DtzfW
> +yMcYUSYXoMvS9rSAuRi3BAknW7hU9hHM50ZZEu+JfW5yqarXxTWb+gr2U/WcIN5q
> +mdzsdl/LyS5RTzQwpjzfQKP1OYGPvJJL4Z19ABEBAAG0QkNocmlzIE1hdHRtYW5u
> +IChDT0RFIFNJR05JTkcgS0VZIC0gQXByIDIwMTYpIDxtYXR0bWFubkBhcGFjaGUu
> +b3JnPokBOAQTAQIAIgUCVyPBggIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
> +CgkQTqr4tgweZUuSUwgAgzrSzAftgUh2qWUCJUfQPhoUOcAiC8YSr998DnrAn6x+
> +oHCA7+Yl+5K2dTunqGlphU4Smr5xcg/CLZ/2YxXqH7kUQ98bKfITsUJWcAejY4J/
> +mnHI+p2lo071rK8UQI/s75G23QFBjDD5PNaT8iMRRS4WNlkERTMnNlyBVQ74Lhxp
> +hEmzfAm/1qOhcgTl7OG+zptti35qHOmdH4XslsZx1mbNh1wYH8epbRkJp3Rtdqe+
> +hAz6VhG7JtOmnhYMSXXtDFuuepSdcpOJVGWybklloVG7QFyNmag4lpSDOzQE0V7g
> +KEVR5Ctp9By13baQ6DATCoVGccxIEgddldSxQPOGxbkBDQRXI8GCAQgA03oPMb/Y
> +SQWAnB/oyY7xCjdEs1jo0yZ3Oga3uUxNenNmkbYnXqdFX3qqvspHVTbeNhCHIn4R
> +sOe4aZvaV5iJfhmNn+kMIqjtE44d/3CG6MlJKcPJFB2oCLhm738z20lZ5tn179tt
> +dRSenbw53Zp9Fil8MnAxc+z4YupNsAHL9rv/T29Q3Uof0YIlKCuzG6/Wi36lMcpx
> +ujaB15Eyv8ZV/HErqvzrjePOOHvZxg9KXX6pNwipfbPHGsaIWWZij7Z9b/PZidNz
> +yxBueiiawU5FzmYgVYVReuTkXlirjnJnQJ2/aKtypVpAKHO8R+fVV0sNDy5i+gR0
> +mqu34ZoN5wSurwARAQABiQEfBBgBAgAJBQJXI8GCAhsMAAoJEE6q+LYMHmVLNaAH
> +/RJGs9gqTTArW4gSsPx3FwRSm2NyDLwFVm1Dg4pFbPG5PpKxyMTnUCRl1opR9WC6
> +FFZFDnsPTSyC/5vVo/y+4GqqRJMJrGVGyogQ2HYxtHZYBlIA2h0oQFFpMHuwq5LQ
> +EIvrvgOqcmbISxQJ/R0KBc96ResburE22I3Gw05x/HBBXtgolMKiqu8Z1Ndkl4vm
> +3I4yvlqdx80fyx7xImFHmRH5nLgmmftlc1s53aP1mh+qpksn/rQul3YhfvnIIg8Y
> +2U1YEFhUh86UCUhoZzIOounLuz889pKcNOwQXdX04MzMfGr4V1/o9TRyNXY5HaMf
> +YPi9ISfsd7U8El0OiV2G0PY=
> +=YRz1
> +-END PGP PUBLIC KEY BLOCK-
> +
>
>
>
>
> mattm...@apache.org <mailto:mattm...@apache.org>
> 2017-07-24 at 6.51 p
> Repository: oodt
> Updated Branches:
> refs/heads/master 87274d65a -> 4589b58ec
>
>
> add mattmann's new key
&g

FW: oodt git commit: add mattmann's new key

[Chris Mattmann]

Sean, Tom, updated the KEYS file please provide your +1s on the RC



On 7/24/17, 4:51 PM, "mattm...@apache.org" <mattm...@apache.org> wrote:

Repository: oodt
Updated Branches:
  refs/heads/master 87274d65a -> 4589b58ec


add mattmann's new key

Project: http://git-wip-us.apache.org/repos/asf/oodt/repo
Commit: http://git-wip-us.apache.org/repos/asf/oodt/commit/4589b58e
Tree: http://git-wip-us.apache.org/repos/asf/oodt/tree/4589b58e
Diff: http://git-wip-us.apache.org/repos/asf/oodt/diff/4589b58e

Branch: refs/heads/master
Commit: 4589b58ec126a5c60dfc7223ee02676fbbcda858
Parents: 87274d6
Author: Chris Mattmann <mattm...@apache.org>
Authored: Mon Jul 24 16:51:10 2017 -0700
Committer: Chris Mattmann <mattm...@apache.org>
Committed: Mon Jul 24 16:51:10 2017 -0700

--
 KEYS | 39 +++
 1 file changed, 39 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/oodt/blob/4589b58e/KEYS
--
diff --git a/KEYS b/KEYS
index d3856f9..1dc1aeb 100644
--- a/KEYS
+++ b/KEYS
@@ -343,3 +343,42 @@ 
IGuODo8x0hnGrvAOZYb5BUL7/CRo9PMt91DLPOREFSMHVEsA12OnaTQ2hPZrVOcV
 HSTj1SAfoZ5erxSk3/eMd3H52/6jBg==
 =yBb7
 -END PGP PUBLIC KEY BLOCK-
+
+pub   2048R/0C1E654B 2016-04-29
    +uid  Chris Mattmann (CODE SIGNING KEY - Apr 2016) 
<mattm...@apache.org>
    +sig 3    0C1E654B 2016-04-29  Chris Mattmann (CODE SIGNING KEY - Apr 
2016) <mattm...@apache.org>
+sub   2048R/FFD0461C 2016-04-29
    +sig  0C1E654B 2016-04-29  Chris Mattmann (CODE SIGNING KEY - Apr 
2016) <mattm...@apache.org>
+
+-BEGIN PGP PUBLIC KEY BLOCK-
+Version: GnuPG v1
+
+mQENBFcjwYIBCACpLaKDNBeVnvIFRHYyoNvfro81tzNzpUBwClyBtJWeu6tpBZiH
+fb6JgPu2p1z8N4b2NLS9T+cbmeyVvVrqF1vqFFK4EVBqNEms9dyNektBU1SjBgy5
+RzYM7lM67RgII7s7l3CpxL7t8znGKB95w8p09jm4cOFk8n0upeqTXvfD06mzK/MK
+xk45ljoFWJbo468l0xLDBuTg+UdQQe2nbBe2TY65SC9ZFkcVd0drUq7o/S/DtzfW
+yMcYUSYXoMvS9rSAuRi3BAknW7hU9hHM50ZZEu+JfW5yqarXxTWb+gr2U/WcIN5q
+mdzsdl/LyS5RTzQwpjzfQKP1OYGPvJJL4Z19ABEBAAG0QkNocmlzIE1hdHRtYW5u
+IChDT0RFIFNJR05JTkcgS0VZIC0gQXByIDIwMTYpIDxtYXR0bWFubkBhcGFjaGUu
+b3JnPokBOAQTAQIAIgUCVyPBggIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
+CgkQTqr4tgweZUuSUwgAgzrSzAftgUh2qWUCJUfQPhoUOcAiC8YSr998DnrAn6x+
+oHCA7+Yl+5K2dTunqGlphU4Smr5xcg/CLZ/2YxXqH7kUQ98bKfITsUJWcAejY4J/
+mnHI+p2lo071rK8UQI/s75G23QFBjDD5PNaT8iMRRS4WNlkERTMnNlyBVQ74Lhxp
+hEmzfAm/1qOhcgTl7OG+zptti35qHOmdH4XslsZx1mbNh1wYH8epbRkJp3Rtdqe+
+hAz6VhG7JtOmnhYMSXXtDFuuepSdcpOJVGWybklloVG7QFyNmag4lpSDOzQE0V7g
+KEVR5Ctp9By13baQ6DATCoVGccxIEgddldSxQPOGxbkBDQRXI8GCAQgA03oPMb/Y
+SQWAnB/oyY7xCjdEs1jo0yZ3Oga3uUxNenNmkbYnXqdFX3qqvspHVTbeNhCHIn4R
+sOe4aZvaV5iJfhmNn+kMIqjtE44d/3CG6MlJKcPJFB2oCLhm738z20lZ5tn179tt
+dRSenbw53Zp9Fil8MnAxc+z4YupNsAHL9rv/T29Q3Uof0YIlKCuzG6/Wi36lMcpx
+ujaB15Eyv8ZV/HErqvzrjePOOHvZxg9KXX6pNwipfbPHGsaIWWZij7Z9b/PZidNz
+yxBueiiawU5FzmYgVYVReuTkXlirjnJnQJ2/aKtypVpAKHO8R+fVV0sNDy5i+gR0
+mqu34ZoN5wSurwARAQABiQEfBBgBAgAJBQJXI8GCAhsMAAoJEE6q+LYMHmVLNaAH
+/RJGs9gqTTArW4gSsPx3FwRSm2NyDLwFVm1Dg4pFbPG5PpKxyMTnUCRl1opR9WC6
+FFZFDnsPTSyC/5vVo/y+4GqqRJMJrGVGyogQ2HYxtHZYBlIA2h0oQFFpMHuwq5LQ
+EIvrvgOqcmbISxQJ/R0KBc96ResburE22I3Gw05x/HBBXtgolMKiqu8Z1Ndkl4vm
+3I4yvlqdx80fyx7xImFHmRH5nLgmmftlc1s53aP1mh+qpksn/rQul3YhfvnIIg8Y
+2U1YEFhUh86UCUhoZzIOounLuz889pKcNOwQXdX04MzMfGr4V1/o9TRyNXY5HaMf
+YPi9ISfsd7U8El0OiV2G0PY=
+=YRz1
+-END PGP PUBLIC KEY BLOCK-
+

Re: [VOTE] Apache OODT 1.1 Release Candidate #2

[Chris Mattmann]

Hey Team,

Why should we maintain a separate KEYS file from the one I referenced at:

https://people.apache.org/keys/group/oodt.asc

That one is maintained automatically by collecting our GPG fingerprints from
id.apache.org? 

I can see for past releases, but how much do we think people are using anything
prior to OODT e.g., 0.7 or 0.8 and I would assert that between my key and Tom’s
key there haven’t been RM’s since then…

So, thoughts? It’s one less not automatically generated thing we have to 
manage…?

Cheers,
Chris



On 7/24/17, 5:10 AM, "Tom Barber" <tom.bar...@meteorite.bi> wrote:

Good catch Sean:

bugg@tom-laptop2:~$ gpg  --verify apache-oodt-1.1-src.zip.asc
gpg: assuming signed data in `apache-oodt-1.1-src.zip'
gpg: Signature made Wed 19 Jul 2017 19:57:50 BST using RSA key ID 0C1E654B
gpg: Good signature from "Chris Mattmann (CODE SIGNING KEY - Apr 2016) <
mattm...@apache.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: F434 C970 B95A 6FCA 6FB9  0C45 4EAA F8B6 0C1E 654B
bugg@tom-laptop2:~$

The key works, but I think the KEYS file needs to be updated in the SVN
repo per: https://www.apache.org/dev/release-signing.html#keys-policy

For now I'm gonna say -1 unless updating KEYS isn't required.

Tom




On Mon, Jul 24, 2017 at 5:22 AM, Chris Mattmann <mattm...@apache.org> wrote:

> I updated it in id.apache.org, which autogenerates [1], which should be
> the
> canonical source for our KEYS file. Give it a check in ~1 hour or so
> should be
> all good.
>
> Cheers,
> Chris
>
>
>
> [1] https://people.apache.org/keys/group/oodt.asc
>
>
>
> On 7/23/17, 5:33 PM, "Sean Kelly" <ke...@apache.org> wrote:
>
> That did the trick.
>
> I'll be +1 if you also update the KEYS file.
>
> Transcript:
>
> fatalii 298 % date -u
> Mon Jul 24 00:32:49 UTC 2017
> fatalii 299 % gpg --verify apache-oodt-1.1-src.zip.asc
    > gpg: Signature made Wed Jul 19 13:57:50 2017 CDT using RSA key ID
> 0C1E654B
> gpg: Good signature from "Chris Mattmann (CODE SIGNING KEY - Apr 2016)
> <mattm...@apache.org>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: F434 C970 B95A 6FCA 6FB9  0C45 4EAA F8B6 0C1E
> 654B
>
>
> --k
>
>
> Chris Mattmann wrote:
> > Hey Sean I think I have a new key on my Mac – can you check? I just
> submitted the new
> > key to MIT keyserver, can you re-verify and see if that fixes it?
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 7/23/17, 5:06 PM, "Sean Kelly"<ke...@apache.org>  wrote:
> >
> >  Hi folks:
> >
> >  I realize it's already 72 hours and we have the requisite 3 +1
> votes,
> >  but I'm definitely in the -1 camp if this release was signed
> with the
> >  wrong key.
> >
> >  I hope it's just user error on my end.
> >
> >  Take care
> >  --k
> >
> >  >  *From:* Sean Kelly<ke...@apache.org>
> >  >  *Date:* 2017-07-22 at 12.54 p
> >  >  *To:* dev@oodt.apache.org
> >  >  *Subject:* [VOTE] Apache OODT 1.1 Release Candidate #2
> >  >  Did anyone check the signature?
> >  >
> >  >  I'm getting an unknown RSA key 0C1E654B:
> >  >
> >  >  fatalii 278 % date -u
> >  >  Sat Jul 22 17:53:42 UTC 2017
> >  >  fatalii 279 % gpg --verify apache-oodt-1.1-src.zip.asc
> >  >  gpg: Signature made Wed Jul 19 13:57:50 2017 CDT using RSA
> key ID 0C1E654B
> >  >  gpg: Can't check signature: No public key
> >  >
> >  >  --k
> >  >
> >  >  *From:* Chris Mattmann<mattm...@apache.org>
> >  >  *Date:* 2017-07-19 at 2.01 p
> >  >  *To:* dev@oodt.apache.org
> >  >  *Subje

Re: [VOTE] Apache OODT 1.1 Release Candidate #2

[Chris Mattmann]

I updated it in id.apache.org, which autogenerates [1], which should be the 
canonical source for our KEYS file. Give it a check in ~1 hour or so should be
all good.

Cheers,
Chris



[1] https://people.apache.org/keys/group/oodt.asc



On 7/23/17, 5:33 PM, "Sean Kelly" <ke...@apache.org> wrote:

That did the trick.

I'll be +1 if you also update the KEYS file.

Transcript:

fatalii 298 % date -u
Mon Jul 24 00:32:49 UTC 2017
fatalii 299 % gpg --verify apache-oodt-1.1-src.zip.asc
gpg: Signature made Wed Jul 19 13:57:50 2017 CDT using RSA key ID 0C1E654B
gpg: Good signature from "Chris Mattmann (CODE SIGNING KEY - Apr 2016) 
<mattm...@apache.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the 
owner.
Primary key fingerprint: F434 C970 B95A 6FCA 6FB9  0C45 4EAA F8B6 0C1E 654B

    
--k


Chris Mattmann wrote:
> Hey Sean I think I have a new key on my Mac – can you check? I just 
submitted the new
> key to MIT keyserver, can you re-verify and see if that fixes it?
>
> Cheers,
> Chris
>
>
>
>
> On 7/23/17, 5:06 PM, "Sean Kelly"<ke...@apache.org>  wrote:
>
>  Hi folks:
>
>  I realize it's already 72 hours and we have the requisite 3 +1 votes,
>  but I'm definitely in the -1 camp if this release was signed with the
>  wrong key.
>
>  I hope it's just user error on my end.
>
>  Take care
>  --k
>
>  >  *From:* Sean Kelly<ke...@apache.org>
>  >  *Date:* 2017-07-22 at 12.54 p
>  >  *To:* dev@oodt.apache.org
>  >  *Subject:* [VOTE] Apache OODT 1.1 Release Candidate #2
>  >  Did anyone check the signature?
>  >
>  >  I'm getting an unknown RSA key 0C1E654B:
>  >
>  >  fatalii 278 % date -u
>  >  Sat Jul 22 17:53:42 UTC 2017
>  >  fatalii 279 % gpg --verify apache-oodt-1.1-src.zip.asc
>  >  gpg: Signature made Wed Jul 19 13:57:50 2017 CDT using RSA key ID 
0C1E654B
>  >  gpg: Can't check signature: No public key
>  >
>  >  --k
>  >
>  >  *From:* Chris Mattmann<mattm...@apache.org>
>  >  *Date:* 2017-07-19 at 2.01 p
>  >  *To:* dev@oodt.apache.org
>  >  *Subject:* [VOTE] Apache OODT 1.1 Release Candidate #2
>  >  Hi Folks,
>  >
>  >  I have posted a 2nd 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:
>  >
>  >  https://cwiki.apache.org/confluence/display/OODT/Release+Process
>  >
>  >  The release was made from the OODT 1.1 tag at:
>  >
>  >  https://github.com/apache/oodt/tree/1.1/
>  >
>  >  A staged Maven repository is available at:
>  >
>  >  
https://repository.apache.org/content/repositories/orgapacheoodt-1013/
>  >
>  >  Please vote on releasing these packages as Apache OODT 1.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.1
>  >
>  >  [ ] -1 Do not release the packages because...
>  >
>  >  Thanks!
>  >
>  >  Chris Mattmann
>  >
>  >  P.S. Here is my +1.
>  >
>  >
>  >
>
>
>
>

Re: [VOTE] Apache OODT 1.1 Release Candidate #2

[Chris Mattmann]

Hey Sean I think I have a new key on my Mac – can you check? I just submitted 
the new
key to MIT keyserver, can you re-verify and see if that fixes it?

Cheers,
Chris




On 7/23/17, 5:06 PM, "Sean Kelly" <ke...@apache.org> wrote:

Hi folks:

I realize it's already 72 hours and we have the requisite 3 +1 votes, 
but I'm definitely in the -1 camp if this release was signed with the 
wrong key.

I hope it's just user error on my end.

Take care
--k

> *From:* Sean Kelly <ke...@apache.org>
> *Date:* 2017-07-22 at 12.54 p
> *To:* dev@oodt.apache.org
> *Subject:* [VOTE] Apache OODT 1.1 Release Candidate #2
> Did anyone check the signature?
>
> I'm getting an unknown RSA key 0C1E654B:
>
> fatalii 278 % date -u
> Sat Jul 22 17:53:42 UTC 2017
> fatalii 279 % gpg --verify apache-oodt-1.1-src.zip.asc
> gpg: Signature made Wed Jul 19 13:57:50 2017 CDT using RSA key ID 0C1E654B
> gpg: Can't check signature: No public key
>
> --k
>
> *From:* Chris Mattmann <mattm...@apache.org>
> *Date:* 2017-07-19 at 2.01 p
> *To:* dev@oodt.apache.org
> *Subject:* [VOTE] Apache OODT 1.1 Release Candidate #2
> Hi Folks,
>
> I have posted a 2nd 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:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT 1.1 tag at:
>
> https://github.com/apache/oodt/tree/1.1/
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1013/
>
> Please vote on releasing these packages as Apache OODT 1.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.1
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> Chris Mattmann
>
> P.S. Here is my +1.
>
>
>