Re: [VOTE] Move OODT to Attic?

[Sean Kelly]

+1 move to the attic!

And if may be allowed a little bit of intellectual conceit: this is in no way a 
"failure" of the project. 

Software lifecycles tend to follow progressions like these. I'm proud to have 
been a part of OODT, from its auspicious beginnings as NASA's first open source 
effort. to its ascendancy. to where it is now: and I am elated to help to put 
it to bed too. 

Sincere gratitude to everyone who's been a part of it.

And sincere gratitude to Imesha who's at the helm now, piloting this ship 
towards her final mooring.

Best,
-SK


> On Apr 2, 2023, at 8:02 PM, Imesha Sudasingha  wrote:
> 
> Hello everyone:
> 
> Due to inactivity, Apache OODT is considering moving to the Attic [1]. This
> email serves as a call to all PMC members to vote whether to retire OODT to
> the attic, or not.  Note that three -1 votes will be sufficient to cancel
> retirement to the attic no matter how many +1 votes there are.
> 
> PMC members, please reply to this email with your vote:
> 
> +1 [ ] I wish for Apache OODT to be retired to the Apache Attic
> +0 [ ] I do not care
> -1 [ ] Apache OODT should not be retired to the Attic
> 
> Here's my +1.
> 
> Thanks,
> Imesha
> 
> [1] https://attic.apache.org/

Re: OODT 2.0 planning

[Sean Kelly]

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: VOTE Apache OODT 1.2.2 release

[Sean Kelly]

ZIP signature: Good signature from "Tom Barber " ✅
POM signature: Good signature from "Tom Barber " ✅
MD5: ✅
SHA1: ✅
Python build: Ran 34 tests in 0.015s ✅
Java build: Total time: 04:03 min*

*I did have to do "-Dmaven.javadoc.skip=true" to get it to build. 
There's some bad HTML in the Javadocs.


[✘] +1 Release the packages as Apache OODT 1.2.2

Thanks for cutting the release!
--k


Tom Barber 
2018-02-7 at 3.04 p
Hi Folks,

I have posted a 1st release candidate for the Apache OODT 1.2.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.2 tag (commit: 
6597a782d2f36e03b05be79c26cca0e861e28f52)


A staged Maven repository is available at:

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

Please vote on releasing these packages as Apache OODT 1.2.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.2.2

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

Thanks!

Magicaltrout

P.S. Here is my +1.

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

[Sean Kelly]

BW is too fast for me! ^_^

Take care
--k

Sean Kelly wrote:

Chris:

This time I get:

gpg: Good signature from "Chris Mattmann <mattm...@apache.org>"

So I am now +1 to release!

Thanks Chris!
--k

PS: You might want to revoke your two older keys and make FD01FEDB the
go-to.


Chris Mattmann wrote:

Can you try now – I updated with the KEYS file from Master that has my
new KEY. For whatever
reason it didn’t make it into the tag, which I think is fine, since
master always has the latest
and greatest.



On 12/20/17, 8:58 AM, "Sean Kelly"<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

[Sean Kelly]

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

[Sean Kelly]

Strangely this (and the release announcement) ended up in my spam folder.

Here goes:

MD5: ✓
SHA1: ✓
Python tests: ✓
Java tests: ✓
Signature: gpg: Can't check signature: No public key

Don't we also put a convenience copy of the KEYS file in the release dir?

Take care
--k

Chris Mattmann 
2017-12-19 at 8.50 p
Ping (

Can I get 2 more VOTEs here so I can push this release out? It’s kind 
of needed for DRAT.
We can release a 1.2.2 with Tom’s patch later, but would really love 
to release this. Thanks.


Cheers,
Chris




On 11/12/17, 9:53 AM, "Chris Mattmann"  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: Docker and Oracle License Agreement

[Sean Kelly]

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 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



Sean Kelly <mailto:ke...@apache.org>
2017-11-8 at 1.33 p
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

Re: Docker and Oracle License Agreement

[Sean Kelly]

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   76da55c8019d8 weeks 
ago 3.97MB
nutjob4life/catpics  latest   de30a9f847966 weeks 
ago 57.4MB
lwieske/java-8   jdk-8u131-slim   326f0b00e4194 months 
ago164MB
python   2.7-slim 451c85955bc23 months 
ago182MB
plonelatest   e9918460c2e89 months 
ago424MB
oodthub/oodt-nodelatest   cac1bf988d5d3 months 
ago1.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> 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



Sean Kelly <mailto:ke...@apache.org>
2017-11-8 at 1.33 p
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

Docker and Oracle License Agreement

[Sean Kelly]

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: CVEs etc

[Sean Kelly]

Huh. That's a nifty tool.

A little frightening.

--k

Tom Barber 
2017-09-9 at 8.03 a
Hi folks

This isn't supposed to be an alarmist email, but quite enlightening 
all the

same.

I saw a link to a plugin on the Drill mailing list called Dependency Check
Report so I wired it into my OODT repo amongst others to see what was
flagged up since the Struts fallout.

Anyway, of course its unlikely but not out of the question to run OODT
fronting on to the interwebs so I think this is decent food for thought as
to why its useful to keep dependencies up to date as much as possible.

Here's a selection of the output:

https://www.dropbox.com/s/2ida8dk54yleedo/curator-webapp.html?dl=0
https://www.dropbox.com/s/wgt1facgjhqiqkq/fmbrowser.html?dl=0
https://www.dropbox.com/s/o8kqcaktplzjy4y/metadata.html?dl=0
https://www.dropbox.com/s/cli4pj4jc564f16/pge.html?dl=0

Of course there is a bunch of repetition in there and plenty that aren't
over the top severe, some may also be false positives, but as we work
through to OODT 2.0 with the new stuff and chopping out the old stuff,
reducing these as much as possible I would posture.

Tom

Re: [VOTE] Apache OODT 1.2 release

[Sean Kelly]

Hi folks:

Signature on zip ✓
Signature on pom ✓
MD5 ✓
SHA1 ✓
Java tests ✓
Python tests ✓

[✘] +1 Release the packages as Apache OODT 1.2

Take care
--Sean

PS: Shouldn't there be a KEYS file at 
https://dist.apache.org/repos/dist/dev/oodt/ as well?



Tom Barber 
2017-08-15 at 2.27 p
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.

Re: Website update blocked on: https://issues.apache.org/jira/browse/INFRA-14725

[Sean Kelly]

Thank you Dr Mattmann! 

--k


Chris Mattmann 
2017-07-28 at 9.13 a
OK addressed and website updated, release complete! (

Cheers,
Chris




On 7/27/17, 8:10 PM, "Chris Mattmann"  wrote:

Git Pub Sub not working and Git mirroring for asf-site/site-dev not 
working…









Chris Mattmann 
2017-07-27 at 10.10 p
Git Pub Sub not working and Git mirroring for asf-site/site-dev not 
working…

Re: FW: oodt git commit: add mattmann's new key

[Sean Kelly]

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 
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"  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 
Authored: Mon Jul 24 16:51:10 2017 -0700
Committer: Chris Mattmann 
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) 
+sig 3 0C1E654B 2016-04-29 Chris Mattmann (CODE SIGNING KEY - Apr 
2016) 

+sub 2048R/FFD0461C 2016-04-29
+sig 0C1E654B 2016-04-29 Chris Mattmann (CODE SIGNING KEY - Apr 2016) 


+
+-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 
2017-07-24 at 6.51 p
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 
Authored: Mon Jul 24 16:51:10 2017 -0700
Committer: Chris Mattmann 
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 

Re: [VOTE] Apache OODT 1.1 Release Candidate #2

[Sean Kelly]

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.
 >
 >
 >

Fwd: Re: [VOTE] Apache OODT 1.1 Release Candidate #2

[Sean Kelly]

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

[Sean Kelly]

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


Chris Mattmann 
2017-07-19 at 2.01 p
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: Welcome Imesha

[Sean Kelly]

Welcome Imesha! Thanks for helping out.

--k


Tom Barber 
2017-05-4 at 1.00 p
I'd like to say an official Hi to Imesha who is our 2017 GSOC student for
OODT.

Imesha will be working on adding Zookeeper support to the OODT
configuration codebase.


Tom

Re: Sujen += OODT PMC

[Sean Kelly]

Most wootly.

--k


Tom Barber 
2017-04-5 at 5.05 p
Good news oh great ones!

Sujen has also accepted his PMC invite. All hail Sujen!

Cheers

Tom

Re: OODT website instructions

[Sean Kelly]

Thanks Tom! Well done.

--k


Tom Barber 
2016-12-25 at 4.31 p
Hey folks,

Happy Christmas!

I've taken the downtime to write a wiki page for the OODT website should
anyone want to edit it:
https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site

Its pretty straightforward as its a simple jekyll site, there is a bit 
of a

hop to get it into production and just covers how to add a new release
download because thats all automatically generated from a config file to
make it dead simple.

Tom

Re: New Website

[Sean Kelly]

Beautiful.

I'll dig deeper into it, but first impression: beautiful!

Take care
--k


Tom Barber 
2016-10-18 at 10.06 a
Hello folks

As ever my bandwidth shrunk and I didn't get through to completion on the
website, but I have got some time again not sure I should write that
when the boss is watching. I would like to get this new website
finished, but in parallel I'd like to kick off the changes required in
infra to move away from the OODT CMS

So with the site I worked on: http://buggtb.github.io/oodt-website/

Here is my todo:

Add some usecase content to links on homepage
Add some Vagrant content to vagrant tab
Fix component docs so the front page links actually link somewhere

Except those items does anyone have any objection to opening a vote to 
move

the website from Apache CMS to the Jekyll design hosted either in ASF
infrastructure using git-pub-sub or github pages if the ASF supports that
these days. The site is static so nothing database wise is required.

Thanks

Tom

Re: Blog post

[Sean Kelly]

This picture would've been much better:


https://www.facebook.com/photo.php?fbid=5182250249=t.536185249=3=500%2C280



Tom Barber 
2016-July-19 at 1:51 PM
Not sure where they got this dodgy picture of me from but here's the OODT
blog post:

https://jaxenter.com/tom-barber-nasa-interview-apache-oodt-127821.html

Tom

Re: Jenkins build is back to stable : oodt-trunk #2119

[Sean Kelly]

Thank you Tom!

--k


Tom Barber 
2016-July-7 at 4:46 AM
Ta da.

On Thu, Jul 7, 2016 at 10:45 AM, Apache Jenkins Server <

Apache Jenkins Server 
2016-July-7 at 4:45 AM
See 

Apache Jenkins Server 
2016-July-7 at 4:17 AM
See 

Re: VOTE Apache OODT 1.0 release

[Sean Kelly]

MD5: matches
SHA1: matches
Signature: Tom Barber (CODE SIGNING KEY) 
Python (2.7) tests: Ran 34 tests in 0.017s
Java (1.7) tests: Total time: 03:13 min

Looks great to me!


Tom Barber wrote:

[✓]+1  Release the packages as Apache OODT1.0

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

Re: VOTE Apache OODT 0.11-rc1 release

[Sean Kelly]

Working, but un-installable due to OODT-921.

Stick with 0.9; it installs fine and there have been no changes to the 
Python component in years.


--k


Lewis John Mcgibbney <mailto:lewis.mcgibb...@gmail.com>
2016-January-2 at 10:08 AM
Nice folks.
Sorry for not getting around to RC.
Nice work Tom getting this out.
Is the Python artifact working OK?




Tom Barber <mailto:tom.bar...@meteorite.bi>
2016-January-2 at 9:03 AM
Alrighty then,

72+ hours is up.

+1 4, from:
webb
kelly
mattmann
magicaltrout


-1: 0

So with the VOTE passing, I'll get on with shipping OODT 0.11.

Thanks a lot.

Tom


Tom Barber <mailto:tom.bar...@meteorite.bi>
2015-December-30 at 3:57 PM
Whoop, i'm on a roll..

On Wed, Dec 30, 2015 at 5:46 PM, Mattmann, Chris A (3980) <

Mattmann, Chris A (3980) <mailto:chris.a.mattm...@jpl.nasa.gov>
2015-December-30 at 11:46 AM
+1 from me:

[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% $HOME/bin/stage_apache_rc
apache-oodt 0.11-rc1-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 19.1M 100 19.1M 0 0 332k 0 0:00:58 0:00:58 --:--:--
347k
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 819 100 819 0 0 3774 0 --:--:-- --:--:-- --:--:--
3791
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 68 100 68 0 0 322 0 --:--:-- --:--:-- --:--:--
320
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 77 100 77 0 0 369 0 --:--:-- --:--:-- --:--:--
370
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% $HOME/bin/verify_gpg_sigs
Verifying Signature for file apache-oodt-0.11-rc1-src.zip.asc
gpg: Signature made Tue Dec 29 14:56:00 2015 PST using RSA key ID 783CE7BB
gpg: Can't check signature: public key not found
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% ls
apache-oodt-0.11-rc1-src.zip apache-oodt-0.11-rc1-src.zip.asc
apache-oodt-0.11-rc1-src.zip.md5 apache-oodt-0.11-rc1-src.zip.sha1
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% curl -O
"https://git-wip-us.apache.org/repos/asf?p=oodt.git;a=blob_plain;f=KEYS;hb=
052c87b72320b8015136d107acc2290fe32863c1"
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 19728 0 19728 0 0 36779 0 --:--:-- --:--:-- --:--:--
36805
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% ls
apache-oodt-0.11-rc1-src.zip
apache-oodt-0.11-rc1-src.zip.sha1
apache-oodt-0.11-rc1-src.zip.asc

asf?p=oodt.git;a=blob_plain;f=KEYS;hb=052c87b72320b8015136d107acc2290fe3286
3c1
apache-oodt-0.11-rc1-src.zip.md5
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% mv
asf\?p=oodt.git\;a=blob_plain\;f=KEYS\;hb=052c87b72320b8015136d107acc2290fe
32863c1 KEYS
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% gpg --import < KEYS
gpg: key B876884A: "Chris Mattmann (CODE SIGNING KEY)
<mattm...@apache.org>" not changed
gpg: key F9D98BFA: "Sean Colin-Patrick Kelly (CODE SIGNING KEY)
<ke...@apache.org>" not changed
gpg: key FF5B0BD5: "David Woollard (CODE SIGNING KEY)
<wooll...@apache.org>" not changed
gpg: key 2C47D568: "Paul Michael Ramirez (CODE SIGNING KEY)
<prami...@apache.org>" not changed
gpg: key 80EF652D: public key "Andrew Hart (CODE SIGNING KEY)
<ah...@apache.org>" imported
gpg: key 783CE7BB: public key "Tom Barber (CODE SIGNING KEY)
<magicaltr...@apache.org>" imported
gpg: Total number processed: 6
gpg: imported: 2 (RSA: 2)
gpg: unchanged: 4
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann% $HOME/bin/verify_gpg_sigs

Verifying Signature for file
apache-oodt-0.11-rc1-src.zip.asc
gpg: Signature made Tue Dec 29 14:56:00 2015 PST using RSA key ID 783CE7BB
gpg: Good signature from "Tom Barber (CODE SIGNING KEY)
<magicaltr...@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: 3D5D FAD6 FF26 7542 3168 B150 D816 7171 783C E7BB
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann%
$HOME/bin/verify_md5_checksums
md5sum: stat '*.tar.gz': No such file or directory
md5sum: stat '*.bz2': No such file or directory
md5sum: stat '*.tgz': No such file or directory
apache-oodt-0.11-rc1-src.zip: OK
[chipotle:~/tmp/apache-oodt-0.11-rc1] mattmann%



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

Re: VOTE Apache OODT 0.11-rc1 release

[Sean Kelly]

SHA1: matches
MD5: matches
Signature: Tom Barber (CODE SIGNING KEY) 
Java tests: Success, [INFO] Total time: 05:36 min
Python tests: Success, Ran 34 tests in 0.017s

[✓] +1 Release the packages as Apache OODT 0.11

--k

Re: VOTE Apache OODT 0.11-rc1 release

[Sean Kelly]

Is there a signed zip file of the release candidate, plus its 
accompanying hashes?


--k


Tom Barber 
2015-December-29 at 5:08 PM
Hi Folks,

I have posted the 1st release candidate for the Apache OODT 0.11 release.


Trying to switch from SVN to Git, hopefully its not gone too wrong!


The source code is at:
https://dist.apache.org/repos/dist/dev/oodt/

For more detailed information, see the included CHANGES.txt file for
details on release contents and latest changes. The release was made
using the OODT release process, documented on the Wiki here:
https://cwiki.apache.org/confluence/display/OODT/Release+Process

The release was made from the OODT 0.11 tag
(052c87b72320b8015136d107acc2290fe32863c1) at:
https://git-wip-us.apache.org/repos/asf/oodt.git

A staged Maven repository is available at:
https://repository.apache.org/content/repositories/orgapacheoodt-1008/

Please vote on releasing these packages as Apache OODT . The 
vote is

open for at least the next 72 hours.

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

[ ] +1 Release the packages as Apache OODT 

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

Thanks!

Tom

P.S. Here is my +1.

Re: VOTE Apache OODT 0.11-rc1 release

[Sean Kelly]

That is weird.

I swear when I visited that with my browser I got only the ".." link to 
the parent directory.


Sorry about that!

--k

Tom Barber wrote:

Isn't that whats here? https://dist.apache.org/repos/dist/dev/oodt/ ?

On Wed, Dec 30, 2015 at 3:30 PM, Sean Kelly<ke...@apache.org>  wrote:


Is there a signed zip file of the release candidate, plus its accompanying
hashes?

--k

Tom Barber<mailto:magicaltr...@apache.org>

2015-December-29 at 5:08 PM

Hi Folks,

I have posted the 1st release candidate for the Apache OODT 0.11 release.


Trying to switch from SVN to Git, hopefully its not gone too wrong!


The source code is at:
https://dist.apache.org/repos/dist/dev/oodt/

For more detailed information, see the included CHANGES.txt file for
details on release contents and latest changes. The release was made
using the OODT release process, documented on the Wiki here:
https://cwiki.apache.org/confluence/display/OODT/Release+Process

The release was made from the OODT 0.11 tag
(052c87b72320b8015136d107acc2290fe32863c1) at:
https://git-wip-us.apache.org/repos/asf/oodt.git

A staged Maven repository is available at:
https://repository.apache.org/content/repositories/orgapacheoodt-1008/

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

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

[ ] +1 Release the packages as Apache OODT

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

Thanks!

Tom

P.S. Here is my +1.

Re: [DISCUSS] Release OODT 0.11

[Sean Kelly]

Appreciated.

--k


Lewis John Mcgibbney 
2015-December-16 at 6:37 PM
Sounds dynamite.
I marked Nutjob's issue for inclusion in 0.11 as well as it seems the Pypi
packaging is buggered.





Tom Barber 
2015-December-16 at 8:40 AM
OODT-781

Thanks


On Wed, Dec 16, 2015 at 2:14 PM, Lewis John Mcgibbney <

Lewis John Mcgibbney 
2015-December-16 at 8:14 AM
Ok do you have a JIRA ticket Tom? I'll set it as blocker and shift
everything else to 0.12 version.



Tom Barber 
2015-December-16 at 3:57 AM
Yes, but the delete issue needs fixing first, not being able to delete
products is pretty high on the bad stakes. I've been dealing with sick 
kids

all week but if no one else fixes it by the end of the week I'll take a
look when I get 30 minutes.

Tom

On Wed, Dec 16, 2015 at 7:26 AM, Lewis John Mcgibbney <

Lewis John Mcgibbney 
2015-December-16 at 1:26 AM
Hi Folks,
We've addressed 87 issues since 0.10.
I think a 0.11 release would be good. I would like to revisit the Avro RPC
work again after that with the aim of merging in to or even into a > 1.0.
What does everyone think?
Lewis

Re: [RESULT] WAS Re: [VOTE] Move Apache OODT SCM to Apache Git

[kelly]

> Can as many people as possible please check out the read only .git repos at
> https://git-wip-us.apache.org/repos/asf/oodt.git
> We need to verify that it looks as expected, we have not lost any branches,
> trunk is up-to-date, etc.

Looks good to me.

--k

Re: [VOTE] Apache OODT 0.10 RC #2

[kelly]

MD5: matches
SHA1: matches
Signature: Good signature from "Chris Mattmann (CODE SIGNING KEY) 
"
Python tests: Ran 34 tests in 0.014s, OK
Java tests: maven-3.2.1, jdk 1.7.0_25, OK

> [✓] +1 Release the packages as Apache OODT 0.10

Make it so.

--k

Re: [DISCUSS] Moving to Git (was Re: Moving repository to git)

[kelly]

+1 to Apache Git.

--k

 On 2015-08-21, at 2:50 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 I would be fully supportive of this.
 
 What do others in the community think? If there are no objections
 over the next week I’d like to call a VOTE.
 
 Note, Radu, that this wouldn’t mean “moving to Github”. Github !=
 Git != Apache. Apache has writeable Git repos (that run on ASF
 hardware) and separately, Git mirrors that mirror and interact with
 Github from the Apache gold source. Everyone should check out:
 http://git.apache.org for more detail.
 
 Thoughts, please?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 -Original Message-
 From: Radu Manole manole.v.r...@gmail.com
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Friday, August 21, 2015 at 11:51 AM
 To: oodt dev@oodt.apache.org
 Subject: Moving repository to git
 
 Hello,
 
 Did you consider moving to git from svn as the main repository for the
 project?
 Especially since most of the pull requests are done from github,
 converting
 a diff to svn feels a bit unnecessary.
 
 It woul have made my life easier certainly. Especially if I didn't have to
 convert from git to svn diffs in order to post reviews on review board.
 
 Thanks,
 Radu.
 

Re: [VOTE] Apache OODT 0.9 RC #1

[kelly]

MD5: matches
SHA1: matches
Signature: Chris Mattmann (CODE SIGNING KEY) mattm...@apache.org 
mailto:mattm...@apache.org
Python: Ran 34 tests in 0.018s
Java: Total time: 2 minutes 50 seconds (And that was with 1.8.0_05! It all 
worked!)

 [✓] +1 Release the packages as Apache OODT 0.9

Re: Permission for create page

[kelly]

Anytime!

--Sean nutjob Kelly

 On 2015-05-18, at 2:38 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
 wrote:
 
 DONE.
 Thank you nutjob ;)
 Lewis
 
 
 On Mon, May 18, 2015 at 12:08 PM, Radu Manole manole.v.r...@gmail.com
 wrote:
 
 Hi Lewis,
 My user name is manole.v.radu
 Thanks.
 Radu
 
 2015-05-18 17:43 GMT+03:00 Lewis John Mcgibbney lewis.mcgibb...@gmail.com
 :
 
 Hi Radu,
 What is your wiki username please?
 Thank you
 Lewis
 
 On Sat, May 16, 2015 at 12:47 AM, Radu Manole manole.v.r...@gmail.com
 wrote:
 
 Hi,
 I need access to make a wiki page. Can you give it to me ?
 https://cwiki.apache.org/confluence/display/OODT/Home
 
 
 
 
 --
 *Lewis*
 
 
 
 
 
 -- 
 *Lewis*

Re: Python Standard

[kelly]

I would hope that we'd be compatible with 2.7 and any of the 3+ versions.

Let's see if that's the case!

--k

 On 2015-04-15, at 11:57 AM, Michael Starch starc...@umich.edu wrote:
 
 Dev,
 
 Have we standardized on a python version for OODT python code?
 
 Specifically, do we use Python 3.x or Python 2.x? From a brief search
 Agile OODT uses 2.x.  Is this the recommendation?
 
 -Michael

Re: [ANNOUNCE] Apache OODT 0.8.1 release

[kelly]

 The Apache OODT website will be updated shortly to reflect the
 releases. As always if you find anything that you'd like to report
 (including praise!) please do so on our u...@oodt.apache.org (use
 of OODT) or dev@oodt.apache.org (architecture/design of OODT) mailing
 lists. Also please visit our website:

Quick reminder: u...@oodt.apache.org is shut down [1].

--k

[1] https://issues.apache.org/jira/browse/INFRA-9074

Re: [RESULT] [VOTE] Apache OODT 0.8.1 RC #2

[kelly]

 I am going to push the release to the mirrors, and
 push out the new website. Thanks folks.

Thank YOU for rolling up our release!

Happy OODT Day!

--k

Re: [ANNOUNCE] Apache OODT 0.8.1 release

[kelly]

Seems legit.

 On 2015-02-13, at 11:56 AM, Ramirez, Paul M (398M) 
 paul.m.rami...@jpl.nasa.gov wrote:
 
 Bold prediction here but next time I'm a release manager on OODT I will make 
 the same mistake.
 
 --Paul

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

[kelly]

 WDYT?

+1 to CMS

--k

Re: [VOTE] Apache OODT 0.8.1 RC #2

[kelly]

MD5: matches
SHA1: matches
Signature: Chris Mattmann (CODE SIGNING KEY) mattm...@apache.org
Python tests: pass
Java tests: pass

 [✗] +1 Release the packages as Apache OODT 0.8.1

+1! Do it!! 

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

[kelly]

 On 2015-02-08, at 5:23 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 So on Wednesday I will ask infra to switch over the site please get updates 
 in by then and if there are updates to be made we can always do so after as 
 frequently as folks and their commit but desire.

The CMS is the way to go. Editing through-the-web is immediate and effective, 
and everyone can do it. I just put in a bunch myself.

Let's make it live!

--k

Re: NASA Soil Moisture Active Passive (SMAP) mission: Tika + OODT!

[kelly]

 As promised: https://twitter.com/TheASF/status/561603593024061441

Thanks for posting that Sally! I am so proud of my baby OODT. It's all grown up 
and working ... in SPACE!

Cheers
--k


-- 
Sean Kelly
Vice President, Apache OODT
Member, Apache Software Foundation

Re: 0.8 jira release

[kelly]

Sorry Magicaltrout. I set 0.8 to released as of 2014-12-15. (Which is nice as 
that was the release of 0.6!)

Thanks for your patience
--k


 On 2015-01-09, at 6:22 PM, Tom Barber tom.bar...@meteorite.bi wrote:
 
 Chris, Kelly, can someone do this or do I need to raise a jira to alter jira? 
 ;)
 
 On 30/12/14 12:25, Tom Barber wrote:
 can someone with jira admin rights set 0.8 as released on jira please.
 
 Tom
 -- 
 *Tom Barber* | Technical Director
 
 meteorite bi
 *T:* +44 20 8133 3730
 *W:* www.meteorite.bi | *Skype:* meteorite.consulting
 *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK
 
 
 -- 
 *Tom Barber* | Technical Director
 
 meteorite bi
 *T:* +44 20 8133 3730
 *W:* www.meteorite.bi | *Skype:* meteorite.consulting
 *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK

Shutdown of the OODT Apache User Mailing List

[kelly]

Folks:

We have two public mailing lists:

- dev@oodt.apache.org mailto:dev@oodt.apache.org, ostensibly for discussion 
of the development of Apache OODT
- u...@oodt.apache.org mailto:u...@oodt.apache.org, allegedly for end users 
to ask questions and find answers about Apache OODT

Greg Stein noted during the last Apache board meeting that since the user@ 
traffic is so low that we're needlessly segmenting our community.  OODT itself 
is software that's more for developers than end users since it requires such 
high levels of integration into existing architectures.

Following the K.I.S.S. Principle [2], I'd like to call for a community vote to 
shut down the u...@oodt.apache.org mailto:u...@oodt.apache.org mailing list:

[ ] +1, shut down u...@oodt.apache.org mailto:u...@oodt.apache.org
[ ] ±0, don't care about user@oodt.apache mailto:user@oodt.apache.org's fate
[ ] -1, do NOT shut down u...@oodt.apache.org mailto:u...@oodt.apache.org, 
because …

I'll leave the vote open at least 72 hours. And here's my +1.

Best wishes
--k

[1] 
https://svn.apache.org/repos/private/foundation/board/board_agenda_2014_12_17.txt
 
https://svn.apache.org/repos/private/foundation/board/board_agenda_2014_12_17.txt
[2] http://en.wikipedia.org/wiki/KISS_principle

Re: VOTE Apache OODT 0.8 release

[kelly]

 I have posted a first release candidate for the Apache OODT 0.8 release. The
 source code is at:
 
 https://dist.apache.org/repos/dist/dev/oodt/ 
 https://dist.apache.org/repos/dist/dev/oodt/

Thanks, Tom. Checking:

✓ Signature: Tom Barber (CODE SIGNING KEY) magicaltr...@apache.org
✓ SHA1: matches
✓ MD5: matches
✓ Python tests: pass
✓ Java tests: pass

 [✗] +1 Release the packages as Apache OODT 0.8

D eeet!

And Tom, thanks for volunteering to roll this release! 

--k

Re: OODT 0.8 release

[kelly]

 Either way, I think a Jan release would be sensible after our meeting earlier 
 in the year.
 
 Let me know what you think.

Yes, yes, yes!

--k

Re: Confluence Wiki Edit Permissions

[kelly]

 How do I get edit permissions to the OODT Confluence WIKI hosted at Apache?

Got you covered. Added starchmd with appropriate permissions to the OODT 
space.

--k

Re: oodt release process

[kelly]

 Or just write it somewhere :)

You doubt Chris?!?

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

--k

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

[kelly]

Fairly thorough Lewis. Next time, ensure the Python tests run as well:

cd agility; python setup.py test

--k

On 2014-09-17, at 1:45 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Chris,
 
 lmcgibbn@LMC-032857 /usr/local/oodt/release/apache-oodt-0.7-src(master) $ 
 java -version
 java version 1.7.0_55
 Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
 Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
 
 On Mon, Sep 15, 2014 at 9:50 AM, Chris Mattmann mattm...@apache.org wrote:
 Hi Folks,
 
 I have posted a 1st release candidate for the Apache OODT 0.7 release. The
 source code is at:
 
 https://dist.apache.org/repos/dist/dev/oodt/
 
 Sigs good
 
 lmcgibbn@LMC-032857 /usr/local/oodt/release(master) $ gpg --import 
 KEYS-0.7.txt
 gpg: key B876884A: Chris Mattmann (CODE SIGNING KEY) mattm...@apache.org 
 not changed
 gpg: key F9D98BFA: public key Sean Colin-Patrick Kelly (CODE SIGNING KEY) 
 ke...@apache.org imported
 gpg: key FF5B0BD5: public key David Woollard (CODE SIGNING KEY) 
 wooll...@apache.org imported
 gpg: key 2C47D568: Paul Michael Ramirez (CODE SIGNING KEY) 
 prami...@apache.org not changed
 gpg: key 80EF652D: public key Andrew Hart (CODE SIGNING KEY) 
 ah...@apache.org imported
 gpg: Total number processed: 5
 gpg:   imported: 3  (RSA: 3)
 gpg:  unchanged: 2
 lmcgibbn@LMC-032857 /usr/local/oodt/release(master) $ gpg --verify 
 apache-oodt-0.7-src.zip.asc
 gpg: Signature made Mon Sep 15 01:43:58 2014 EDT using DSA key ID B876884A
 gpg: Good signature from Chris Mattmann (CODE SIGNING KEY) 
 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: 03CC 5FFA 61AA AD3C 8FF2  5E92 70F0 9CC6 B876 884A
 lmcgibbn@LMC-032857 /usr/local/oodt/release(master) $ md5 
 apache-oodt-0.7-src.zip
 MD5 (apache-oodt-0.7-src.zip) = 18fe10547d0ca91e6b6337d45ba98521
 lmcgibbn@LMC-032857 /usr/local/oodt/release(master) $ openssl sha1 
 apache-oodt-0.7-src.zip
 SHA1(apache-oodt-0.7-src.zip)= c7c2854017246106d9fcdd31b3ba3dc892fb231a
  
 
 The release was made from the OODT 0.7 tag (r1624941) at:
 
 http://svn.apache.org/repos/asf/oodt/tags/0.7/
 
 Check over top level files and pom.xml's within tags look good.
  
 
 
 A staged Maven repository is available at:
 
 https://repository.apache.org/content/repositories/orgapacheoodt-1000/
 
 Maven artifacts all look good as well. Metadata files look accurate.
  
 
 
 Please vote on releasing these packages as Apache OODT version. The vote
 is
 open for the next 72 hours.
 
 The VOTE is of course for 0.7... we can let you away with this haha
  
 
 [X] +1 Release the packages as Apache OODT 0.7
 
 
 +1 from me.
 
 One note here is that I logged https://issues.apache.org/jira/browse/OODT-749 
 and will fix this port release.
 Great to see 0.7 moving closer to release.
 Thanks
 Lewis
 
  

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

[kelly]

Apache OODT 0.7 RC 1:

Signature: confirmed
SHA1: matches
MD5: matches
Python tests: pass
Java tests: intermittent failures
Also, let's change oodt/agility/setup.py's description to Apache OODT.

The failure seems to be an ordering issue:

---
Test set: org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.249 sec  
FAILURE!
testMapping(org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository)  
Time elapsed: 0.224 sec   FAILURE!
junit.framework.AssertionFailedError: expected:[test-queue-1, quick] but 
was:[quick, test-queue-1]
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:280)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:71)
at 
org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository.testMapping(TestXmlQueueRepository.java:64)

Probably a quick fix. This is with Java 1.8.0_05.





On 2014-09-15, at 8:50 AM, Chris Mattmann mattm...@apache.org wrote:

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

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

[kelly]

Java 7 is A-O-K. No problems there.

If we release with that caveat, then I'm +1.

--k


On 2014-09-15, at 1:01 PM, Chris Mattmann mattm...@apache.org wrote:

 Hey Sean,
 
 Weird on the test - can you try with Java7? I ran and built
 with Java7 and am not sure the tests pass with Java8?
 
 Cheers,
 Chris
 
 
 -Original Message-
 From: ke...@apache.org
 Reply-To: u...@oodt.apache.org
 Date: Monday, September 15, 2014 8:00 AM
 To: dev@oodt.apache.org
 Cc: u...@oodt.apache.org
 Subject: Re: [VOTE] Apache OODT 0.7 release candidate #1
 
 Apache OODT 0.7 RC 1:
 
 Signature: confirmed
 SHA1: matches
 MD5: matches
 Python tests: pass
 Java tests: intermittent failures
 Also, let's change oodt/agility/setup.py's description to Apache OODT.
 
 The failure seems to be an ordering issue:
 
 --
 -
 Test set: org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository
 --
 -
 Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.249 sec
  FAILURE!
 testMapping(org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository)
 Time elapsed: 0.224 sec   FAILURE!
 junit.framework.AssertionFailedError: expected:[test-queue-1, quick]
 but was:[quick, test-queue-1]
   at junit.framework.Assert.fail(Assert.java:47)
   at junit.framework.Assert.failNotEquals(Assert.java:280)
   at junit.framework.Assert.assertEquals(Assert.java:64)
   at junit.framework.Assert.assertEquals(Assert.java:71)
   at 
 org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository.testMapping(
 TestXmlQueueRepository.java:64)
 
 Probably a quick fix. This is with Java 1.8.0_05.
 
 
 
 
 
 On 2014-09-15, at 8:50 AM, Chris Mattmann mattm...@apache.org wrote:
 
 Hi Folks,
 
 I have posted a 1st release candidate for the Apache OODT 0.7 release.
 The
 source code is at:
 
 https://dist.apache.org/repos/dist/dev/oodt/
 
 For more detailed information, see the included CHANGES.txt file for
 details on
 release contents and latest changes. The release was made using the OODT
 release process, documented on the Wiki here:
 
 https://cwiki.apache.org/confluence/display/OODT/Release+Process
 
 The release was made from the OODT 0.7 tag (r1624941) at:
 
 http://svn.apache.org/repos/asf/oodt/tags/0.7/
 
 
 A staged Maven repository is available at:
 
 https://repository.apache.org/content/repositories/orgapacheoodt-1000/
 
 
 Please vote on releasing these packages as Apache OODT version. The
 vote
 is
 open for the next 72 hours.
 
 Only votes from OODT PMC are binding, but folks are welcome to check the
 release candidate and voice their approval or disapproval. The vote
 passes
 if at least three binding +1 votes are cast.
 
 [ ] +1 Release the packages as Apache OODT version
 
 [ ] -1 Do not release the packages because...
 
 Thanks!
 
 Chris
 
 P.S. Here is my +1.
 
 
 
 
 
 
 

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

[kelly]

Most wootly! 

--k

On 2014-09-15, at 3:28 PM, Tyler Palsulich tpalsul...@gmail.com wrote:

 Did the Python tests run too?
 
 Just ran them. Everything looks good!

Re: OODT 0.7 status

[kelly]

Good excuse!

--k

On 2014-09-12, at 2:49 AM, Tom Barber tom.bar...@meteorite.bi wrote:

 Cool. I'll be happy to help with the 0.8 release to learn the Apache
 release process. Paternity leave will get in the way of 0.7 sadly.
 
 Tom
 
 On Fri, Sep 12, 2014 at 7:07 AM, Ramirez, Paul M (398J) 
 paul.m.rami...@jpl.nasa.gov wrote:
 
 +1. I'm ready to check the RC as it comes off the presses.
 
 --Paul
 
 Sent from my iPhone
 
 On Sep 11, 2014, at 11:20 AM, ke...@apache.org ke...@apache.org
 wrote:
 
 Chris, thanks for stepping up as usual. Although it might be nice to
 have a new blood tackle it for the learning experience, this release is so
 long overdue I don't mind have experienced hands at the helm.
 
 Let's get 'er done.
 
 --k
 
 
 
 
 On 2014-09-11, at 12:07 AM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Hey Tom,
 
 Once I fix the Resource Manager, I would like to volunteer to
 be the RM for 0.7 and push!
 
 That sound OK?
 
 So maybe RC tomorrow or latest Friday and 0.7 release next week
 if VOTE'ing goes well?
 
 Cheers,
 Chris
 
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi
 Date: Thursday, September 4, 2014 8:35 AM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: OODT 0.7 status
 
 
 
 
 Hello folks,
 
 I dunno if I've just missed an email or what but whats the 0.7
 status? Code freeze? still open? packaged and ready to roll?
 
 Thanks
 
 Tom
 --
  Tom Barber | Technical Director
 
  meteorite bi
  T: +44 20 8133 3730
  W: www.meteorite.bi http://www.meteorite.bi | Skype:
 meteorite.consulting
  A: Surrey Technology Centre, Surrey Research Park,
  Guildford, GU2 7YG, UK
 
 

Re: Review Request 22791: Streaming OODT Changes

[Sean Kelly]

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


Do the supporting scripts have to be BASH-specific? We'd show better 
compatibility with a wider range of Unix systems if we could stick with pure 
/bin/sh.

- Sean Kelly


On Aug. 13, 2014, 10:56 p.m., Michael Starch wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/22791/
 ---
 
 (Updated Aug. 13, 2014, 10:56 p.m.)
 
 
 Review request for oodt.
 
 
 Repository: oodt
 
 
 Description
 ---
 
 This patch contains all the changes needed to add in streaming oodt into 
 the oodt svn repository.
 
 There are four main portions:
-Mesos Framework for Resource Manager (Prototype working)
-Spark Runner for Workflow Manager (Prototype working)
-Filemanager streaming type (In development)
-Deployment and cluster management scripts (In development)
 
 Where can this stuff be put so that it is available to use, even while it is 
 in development?
 
 
 Diffs
 -
 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/shutdown.sh 
 PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/start-up.sh 
 PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/start-up/mesos-master.bash
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/start-up/mesos-slave.bash
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/start-up/resource.bash
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/scripts/utilites.sh 
 PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/setup/env-vars.sh.tmpl
  PRE-CREATION 
   http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/setup/hosts 
 PRE-CREATION 
   http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/setup/install.sh 
 PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/cluster-tools/setup/required-software.txt
  PRE-CREATION 
   http://svn.apache.org/repos/asf/oodt/trunk/core/pom.xml 1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/cli/action/IngestProductCliAction.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/datatransfer/LocalDataTransferer.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/metadata/extractors/CoreMetExtractor.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/metadata/extractors/examples/MimeTypeExtractor.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/structs/Product.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/structs/Reference.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManager.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/versioning/BasicVersioner.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/versioning/DateTimeVersioner.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/versioning/SingleFileBasicVersioner.java
  1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/versioning/VersioningUtils.java
  1617800 
   http://svn.apache.org/repos/asf/oodt/trunk/resource/pom.xml 1617800 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/batchmgr/MesosBatchManager.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/batchmgr/MesosBatchManagerFactory.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/mesos/MesosUtilities.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/mesos/OODTExecutor.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/mesos/ResourceMesosFrameworkFactory.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache/oodt/cas/resource/mesos/ResourceMesosScheduler.java
  PRE-CREATION 
   
 http://svn.apache.org/repos/asf/oodt/trunk/resource/src/main/java/org/apache

Re: svn commit: r1617138 - /oodt/trunk/

[kelly]

Mad props, Mattmann.

--k

On 2014-08-10, at 12:53 PM, mattm...@apache.org wrote:

 Author: mattmann
 Date: Sun Aug 10 17:53:57 2014
 New Revision: 1617138
 
 URL: http://svn.apache.org/r1617138
 Log:
 - update props
 
 Modified:
oodt/trunk/   (props changed)
 
 Propchange: oodt/trunk/
 --
 --- svn:ignore (original)
 +++ svn:ignore Sun Aug 10 17:53:57 2014
 @@ -14,3 +14,4 @@ maven-eclipse.xml
 .externalToolBuilders
 .idea
 *.iml
 +.pydevproject
 
 

Re: OODT Officially Stable - Hats off to Ross Laidlaw

[kelly]

What a Friday.

Thanks Lewis, Ross, and everyone.

--k

On 2014-08-08, at 3:05 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Folks,
 The OODT trunk (0.7-SNAPSHOT) codebase is stable [0] now for the first time 
 in a while which is extremely good news.
 I personally (and I'm sure I speak on behalf of many of us) am extremely 
 appreciative of the work Ross has recently put in to ensuring the codebase is 
 stabalized.
 Hats off Ross. The drinks are on me... and make sure to remind me about it.
 Have a great weekend folks.
 Lewis
 
 [0] https://builds.apache.org/job/oodt-trunk/1438/
 
 
 -- 
 Lewis 

[REMINDER] OODT Roadmap Telecon in 60 minutes

[kelly]

T minus 60 minutes and counting . . .

To dial in:

International: +1-650-479-3208
US Toll-Free: +1-877-668-4493
Other Toll-Free: http://s.apache.org/globalcallin
Access Code: 2329 5771

--k

NEW TELECON LINE! OODT Roadmap telecon

[kelly]

Folks:

I cannot get the Apache telecon line to accept the host access code.

I've set up a telecon line at NASA JPL:

US Toll free phone: +1 866 328 8761
Regular phone: +1 818 354 3434
Meeting ID: 4321

Please dial in!

--k

OODT Roadmap Telecon: summary of the event

[kelly]

Folks:

Thanks for dialing into the OODT Roadmap Telecon.

The attendees were:

- Tom Barber, UK business intelligence consultant
- Roger Carter, JPL intern
- Cameron Goodale, JPL
- Michael Joyce, JPL
- Sean Kelly, consultant
- Ross Laidlaw, JPL intern
- Lewis John McGibbney, JPL
- Tyler Palsulich, JPL intern
- Rishi Verma, JPL


Here are the milestones that I recorded from the telecon, presented in no 
particular order:

A. Stability to the codebase.  Tests must pass before we can reliably move 
forward.  This is especially troublesome since there are new features we do 
want to implement, yet our confidence level of not breaking existing function 
is low since the tests just don't work.

B. Upgrade OODT's outdated components.  A number of parts within OODT has 
ossified and become brittle (XML parsing, for example).  As the (mainly Java) 
ecosystem has matured, these components have not, and they continue to be 
software hangnails.

C. End-to-end story-driven testing.  While we'd love to see more and more unit 
testing, complete integration testing is also vital.  OODT is a large and 
complex system, and ensuring all the parts work in a story-driven manner is 
important.

D. Changing 5 to 10 config files to get OODT just to work is terrible.  And 
worse, they're largely XML configuration files.  OODT needs to get-up-and-go 
out-of-the-box.

E. Documentation and website movement to Apache CMS-based tech.  The static 
nature of the OODT website is a barrier to updates.  We'd like for updates to 
frequent and timely.

F. Make OODT more of a product, less of an architecture.  It's difficult for 
new users to approach OODT since it's presented mainly as a software 
architecture that has some software.  If we could change it into a product (by 
providing sensible defaults, IoC, etc.) it could have a lower barrier of entry.

G. Remove PHP. OODT requires a Java servlet container for its core function, so 
why bring in yet another technology for the Balance components?  This increases 
the exploitable surface of an OODT server as well as making adoption of OODT 
trickier.

H. XML specification and/or schema so you can know what can be where.  For 
these XML configuration files, the lack of a schema means it's difficult to 
tell what elements and attributes go where, which are required, which are 
optional, etc.  With a schema (and an XML-aware editor) this becomes easier to 
do—and gives validation-before-run as a bonus.

I. Where and what are the extension points?  This needs to be clearly 
documented and highlighted.

J. Tutorials are static and don't allow for community updates.  We need them on 
the wiki instead so everyone can help.  Leave a getting started tutorial on 
the main website, but move everything else to the Apache Confluence wiki.

K. Put Jenkins build status on the OODT website!

L. Videos (screencasts).  But keep them upbeat.  Edit them carefully so users 
aren't watching slow typists backspacing over mistakes repeatedly.

M. Regular release cycle.  Four times a year.  This gives liveness to the 
project, but also gives confidence to new users knowing that a certain bug or 
new feature will be addressed in an upcoming release.

O. Report list subscription numbers in board reports, not # of messages.  This 
is a more interesting metric since it demonstrates the breadth of OODT 
adoption, which is orthogonal to the amount of discussion which can be 
dominated by one or two members.

What milestones did I miss?  Do these sound correct?  Please reply to the list 
and let's discuss further.  Once we've hammered out this list, we should then 
priortize them.

Thanks again for your participation,
--k

-- 
Sean Kelly
Vice President, Apache OODT
Member, Apache Software Foundation

OODT Roadmap Teleconference: line details

[kelly]

OODT folk:

Our roadmap telecon is scheduled for Thursday, 2014-08-07, at 17:00 UTC.

Time conversions (and iCal/vCal links): http://s.apache.org/00S

To dial in:

International: +1-650-479-3208
US Toll-Free: +1-877-668-4493
Other Toll-Free: http://s.apache.org/globalcallin
Access Code: 2329 5771

I hope as many of us as possible join in the discussion!

--k

OODT Roadmap Telecon

[kelly]

Folks:

Thanks for everyone for signing up at http://doodle.com/bi6g5rr8hukziqga to 
pick a time for an OODT Roadmap Teleconference.

Unfortunately, I've just received a reminder that discussion outside our 
mailing lists is frowned upon as not being part of the Apache Way 
(accountability and all that).

We could flaunt the policy and hold it anyway, but it might be better if we 
were good Apache citizens and stick to this mailing list.

Comments?
--k

Re: OODT Roadmap Telecon

[kelly]

Thanks for that Chris. We'll go ahead and move forward with a roadmap telecon.

Based on the Doodle poll, then, the best time is Thursday, 2014-08-07 at 17:00 
UTC (12:00 eastern, 11:00 central, 09:00 pacific, 01:00 Japan).

PLEASE MARK YOUR CALENDARS!

I'll ask if we can use the board's line. If not, perhaps an employer or another 
can volunteer one.

Take care.
--k




On 2014-07-31, at 12:43 PM, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Everyone,
 
 I don't think there is a problem with having discussions on a telecon.
 The key distinction is to NOT make decisions on those telecons. Decisions
 are made on the ASF mailing lists. However, people talk outside of the list
 all of the time and it's not our goal to thwart all of those opportunities.
 We also here at the ASF are all about trust and caring behind people's
 intentions. Sean Kelly and Tom Barber have made every effort as far as I
 can
 tell to hold a Doodle poll, include people in multiple time zones, and have
 a chance for a discussion in real time that is often not possible. I say,
 have
 the discussion. Decisions are made/recorded, and *acted on* via our ASF
 mailing
 lists. So, I would say, do so.
 
 And if you do all those things, and then just follow up, I personally trust
 that you guys are doing the right thing and no one is doing anything
 nefarious here.
 Heck you have done a ton of things to discuss this telecon on the list,
 there are
 already several announcements of it, etc.
 
 I would for sure NOT get into the habit of doing this as the only modis
 operandi for
 communication but of course, no one is suggesting that.
 
 So, I would say, move forward, nothing much to see here. I will try my
 best to attend it
 but if I can't I trust you guys are doing the right thing and will take
 care of stuff
 on list as it should be.
 
 Thanks.
 
 Cheers,
 Chris
 
 
 
 -Original Message-
 From: ke...@apache.org ke...@apache.org
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Thursday, July 31, 2014 8:33 AM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: OODT Roadmap Telecon
 
 Folks:
 
 Thanks for everyone for signing up at http://doodle.com/bi6g5rr8hukziqga
 to pick a time for an OODT Roadmap Teleconference.
 
 Unfortunately, I've just received a reminder that discussion outside our
 mailing lists is frowned upon as not being part of the Apache Way
 (accountability and all that).
 
 We could flaunt the policy and hold it anyway, but it might be better if
 we were good Apache citizens and stick to this mailing list.
 
 Comments?
 --k
 
 
 
 

Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

[kelly]

Give it a shot with Maven-2.2.1.  (I don't think we're ready for Maven 3, which 
itself is another issue that needs addressing.)

--k

On 2014-07-23, at 10:49 AM, Tyler Palsulich tpalsul...@gmail.com wrote:

 Thanks all! I'm looking forward to the roadmap call.
 
 Before then, I'm having issues even passing the Commons tests on a clean 
 install... Here is the output of `mvn test -X`: https://paste.apache.org/75u9.
 
 ➜  mvn --version
 Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 
 2014-02-14T09:37:52-08:00)
 Maven home: /usr/local/Cellar/maven/3.2.1/libexec
 Java version: 1.7.0_60, vendor: Oracle Corporation
 Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: mac os x, version: 10.9.3, arch: x86_64, family: mac
 
 TL;DR: I don't see any failed tests. -DfailIfNoTests=false doesn't help. My 
 surefire directory doesn't have any failures.
 
 Is there any config that needs to be set up before install? Or, am I missing 
 something in the output above?
 
 Thank for any help,
 Tyler
 
 
 On Tue, Jul 22, 2014 at 8:43 PM, Rajith Siriwardana 
 rajithsiriward...@gmail.com wrote:
 Welcome Tyler..!!!
 
 
 Cheers,
 --Rajith
 
 
 On Wed, Jul 23, 2014 at 1:06 AM, Michael Starch starc...@umich.edu wrote:
 Great!  Welcome, Tyler.
 
 As another new PMC I aggree that we should discuss a roadmap.
 
 -Michael
 
 On Jul 22, 2014 11:58 AM, Michael Joyce jo...@apache.org wrote:
 Yay! Welcome Tyler!!!
 
 
 -- Joyce
 
 
 On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber tom.bar...@meteorite.bi wrote:
 Aye I'll +1 that, and move this over to dev@ 
 
 We have an ever expanding PMC, so lets do some Project Managing! ;)
 
 I think we need to come up with some roadmap goals, both regarding features, 
 and also the existing code base, build systems and delivery.
 
 Personally I think it would be benificial to get a bunch of us on the phone 
 and discuss it in real time (I'm GMT based which does make it a little 
 tricker) rather than hash it out over a 6 month chain of emails. Like I said 
 the other day, I don't really know how other projects manage this type of 
 thing so those with more experience may want to chime in here.
 
 Regards
 
 Tom
 
 
 
 On 22/07/14 18:33, Lewis John Mcgibbney wrote:
 Hi Tyler,
 Please see Tom's thread from before the weekend.
 I say we have a full on discussion on establishing a roadmap.
 For us to establish and agree on this will be extremely beneficial for the 
 project.
 Lewis
 
 
 On Tue, Jul 22, 2014 at 10:29 AM, Tyler Palsulich tpalsul...@gmail.com 
 wrote:
 Hi All,
 
 Thanks for inviting me to join as a committer and PMC member! I'm happy to 
 be part of the project. Any tips on where to dive in?
 
 Tyler
 
 
 
 

OODT Roadmap Teleconference

[kelly]

TL;DR:

Go to http://doodle.com/bi6g5rr8hukziqga

Full:

We'd like to get folks together on a teleconference to discuss OODT's future 
roadmap, including features, releases, low-hanging fruit, packaging, and other 
goals. The telecon should last about an hour, probably less.

Visit this Doodle poll and select time slots you could attend:

http://doodle.com/bi6g5rr8hukziqga

Default times are eastern; use Doodle's control to change it to something 
convenient to you. Call it a quorum if say 5 of us can attend?

Thanks
--k

Re: Activity Logger in Commons

[kelly]

My pleasure, doctor.

The use case for the o.a.oodt.commons.activity package was to enable 
distributed logging mostly for ascertaining performance of the OODT grid code.

For example, suppose we had an activity like make some stew and we suspected 
a bottleneck in it somewhere, or we wanted to see what steps occurred; moreover 
making stew turned out to be a distributed activity, involving CookTop, Oven, 
Fridge, etc., all running on different hosts. The effort to make stew involves 
several incidents.

Make some classes:

import o.a.oodt.commons.activity.Incident;
public class BaconRenderedIncident extends Incident { ... }
public class ChickenBrownedIncident extends Incident { ... }
public class VegetablesChoppedIncident extends Incident { ... }
public class WineBottleOppenedIncident extends Incident { ... }
...

Set some properties:

activity.host=some.host.over.there
activity.port=4556

Create an activity factory:

import o.a.oodt.commons.activity.DatagramLoggingActivityFactory;
import o.a.oodt.commons.activity.ActivityStopped;
...
public class Kitchen {
private factory = new DatagramLoggingActivityFactory():
public void makeStew() {
Activity activity = factory.createActivity();
remoteCookTop.makeStew(activity.getID());
remoteChoppingBlock.makeStew(activity.getID());
activity.log(new ActivityStopped());
}
}
pubic class CookTop {
private factory = new DatagramLoggingActivityFactory():
...
public void makePasta() { ... }
public void makeStew(String id) {
Activity activity = factory.createActivity();
activity.setID(id);
renderBacon();
activity.log(new BaconRenderedIncident());
brownChicken();
activity.log(new ChickenBrownedIncident());
...
}
}
public class ChoppingBlock {
private factory = new DatagramLoggingActivityFactory():
...
public void chopFingers() { ... }
public void makeStew(String id) {
Activity activity = factory.createActivity();
activity.setID(id);
chopCarrots();
activity.log(new CarrotsChoppedIncident());
diceOnions();
activity.log(new OnionsDicedIncident());
...
}
}

Somewhere on the local network, start this:

java -Dactivity.port=4556 
-Dactivity.storage=o.a.oodt.commons.activity.StandardOutputStorage 
o.a.oodt.commons.activity.DatagramLogger

Then when you make stew, you'll see on the standard output of the above process 
all of the incidents that happened when you made stew.

You like XML, use XMLStandardOutputStorage. You want a database? Use 
SQLDatabaseStorage. Hosts aren't all on a local network? Define your own 
ActivityFactory. Go wild.

Enjoy
--k




On 2014-07-18, at 3:06 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Folks (specifically kelly),
 As part of our involvement with the DARPA XDATA [0] program of work, we are
 working with Draper Labs [1] on their Activity Logger (User-ALE) [2].
 We're in the process of porting the native JavaScript API to Java and
 embedding it within OODT for XDATA specific experiments.
 I wonder if someone (NutJob) could possibly descrbe what the /activity
 package in commons [3] does?
 Thanks in advance and BTW have a great weekend folks.
 Lewis
 
 [0] http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx
 [1] http://www.draper.com/
 [2] http://draperlaboratory.github.io/user-ale/
 [3]
 https://svn.apache.org/repos/asf/oodt/trunk/commons/src/main/java/org/apache/oodt/commons/activity/
 
 -- 
 *Lewis*

Re: Commits to oodt.staging.apache.org

[kelly]

Needs more short ribs.

--k

On 2014-07-17, at 10:37 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Folks,
 We got a kick start on the above staging website.
 N.B. The original site is still very much functional at oodt.apache.org.
 Unfortunately I (or anyone else who wishes to work on the staging site)
 have no way to avoid commits coming to our lists.
 This will be like this for a while yet so I APOLOGISE in advance folks :(
 Lewis
 
 -- 
 *Lewis*

Re: Javadoc for OODT

[kelly]

We do!

Check 'em out at: http://oodt.apache.org/components/maven/apidocs/

To publish the current website, we take the Maven artifacts and run them 
through XDV to transform them to the OODT style. Those get combined with the 
static artifacts (welcome page and the like) to make a complete website.

For the revamped website, we'll need to decide if we want to continue to 
publish the Maven-generated artifacts.

FYI: https://cwiki.apache.org/OODT/how-to-publish-the-oodt-web-site.html

--k


On 2014-07-16, at 4:19 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Folks,
 Have we been releasing Javadoc for OODT?
 Thanks
 Lewis
 
 -- 
 *Lewis*

Re: Javadoc for OODT

[kelly]

#@$!@% Chris! Aren't you on a plane? You are way too fast!

--k

On 2014-07-16, at 4:29 PM, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hey Lewis,
 
 We sure have:
 
 http://oodt.apache.org/components/maven/apidocs/
 
 
 Note the process for building the current site is here:
 
 Yes, it's long, but it does a great job of combining static
 content, with dynamic Maven content (e.g., the API docs). I would
 strongly urge you guys to understand the way that the current website
 is built:
 
 https://cwiki.apache.org/OODT/how-to-publish-the-oodt-web-site.html
 
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Lewis John Mcgibbney lewis.mcgibb...@gmail.com
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Wednesday, July 16, 2014 2:19 PM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: Javadoc for OODT
 
 Hi Folks,
 Have we been releasing Javadoc for OODT?
 Thanks
 Lewis
 
 -- 
 *Lewis*
 

Re: Your project uses a possibly LGPL dependency: com.icegreen.greenmail:greenmail

[kelly]

Same with Aapche OODT. We use it soley in the test scope to ensure our IMAP 
handling works.

--k

On 2014-07-14, at 1:21 PM, Robert Kanter rkan...@cloudera.com wrote:

 Thanks for letting us know Steve.
 In Oozie, it's only included as a test scope dependency and used only for
 unit tests, so I think we're good here.
 
 
 On Sun, Jul 13, 2014 at 7:36 PM, Kevan Miller kevan.mil...@gmail.com
 wrote:
 
 Thanks Steve. For clarity:
 
 This message announces a license switch for Greenmail --
 http://sourceforge.net/p/greenmail/mailman/message/58953/
 However, some/most/all of the src license headers are still labeled as
 LGPL. There would also be general questions about the license switch --
 were all necessary copyrights properly held to make this license switch?
 And subsequent to the switch were all changes/contributions made under
 ALv2?
 
 Depending on the outcome of these questions, you may or may not want to
 treat the greenmail dependency as LGPL. Assuming it is held to be LGPL,
 then a question of how the dependency is used? Bundling an LGPL dependency
 is bad. Direct source linkage to LGPL, likewise. Simple build / test maven
 dependency would be OK from an ASF perspective...
 
 
 On Sat, Jul 12, 2014 at 12:36 PM, Steve Rowe sar...@gmail.com wrote:
 
 Hi, my name is Steve Rowe, and I'm a member of the Apache Lucene PMC.
 
 We recently discovered that the greenmail Java library, which declares
 its license as ASLv2 in its POM and elsewhere, has LGPL license headers
 in
 its source code files.  In response the Lucene project reverted a recent
 commit containing this depedency.
 
 I conducted a survey of current Apache releases and found that four
 Apache
 projects include source code that links to the greenmail library:
 Syncope, OODT, Oozie and Geronimo.  Additionally, Axis2 has a Maven POM
 that includes a greenmail dependency, though I couldn't find any
 current
 releases containing this dependency.  Details are posted on 
 https://issues.apache.org/jira/browse/LEGAL-206; I would appreciate
 your
 project's involvement.
 
 An issue was filed with the greenmail project on Sourceforge earlier this
 year asking for clarification 
 http://sourceforge.net/p/greenmail/bugs/8/,
 but there has been no response on that issue, or any other issue, for
 that
 matter - the project may be dead, as it has seen no activity for some
 time.
 
 Steve
 
 

Re: Wiki Edit Access

[kelly]

You should be all set up. If you're missing some permissions, let me know.

Also, have you considered joining OODT as a code committer and/or as an OODT 
Project Management Committee member?

Take care
--k


On 2014-06-24, at 10:35 AM, Tyler Palsulich tpalsul...@gmail.com wrote:

 Hi All,
 
 I found a few typos on the wiki and was interested in correcting them. ;)
 May I have access to edit the Apache OODT wiki? My username is tpalsulich.
 
 Thanks!
 Tyler Palsulich
 tpalsul...@gmail.com

Re: What happened to this wiki page:

[kelly]

HAX.

--k

On 2014-06-18, at 11:26 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 We can view the pages on the wiki here
 https://cwiki.apache.org/confluence/collector/pages.action?key=OODT
 This enables us to track changes right back until
 
   -
Home https://cwiki.apache.org/confluence/display/OODT/Home
   Feb 06, 2010 • created by Gavin
   https://cwiki.apache.org/confluence/display/%7Eipv6guru
 
 So basically, there is no history of the page being edited for the entire
 duration of the wiki existence!!!
 
 I am stumped on this one folks.
 Lewis
 
 
 
 On Wed, Jun 18, 2014 at 12:18 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 no worries Tom, Lewis is looking into it - I just recreated it.
 
 Just thought you may know since you reorganized the wiki
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi
 Date: Wednesday, June 18, 2014 8:46 AM
 To: dev@oodt.apache.org
 Subject: Re: What happened to this wiki page:
 
 
 
 
   Well i never deleted anything (to my
 knowledge)!
 
 On 18/06/14 17:43, Mattmann, Chris A (3980) wrote:
 
 
 Hey Guys, (Tom Barber, specifically),
 
 Does anyone know what happened to this page?
 
 https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API
 
 
 I created it a while back and I can find it in an email reference
 on the mail archives, but it's no longer on the wiki.
 
 Any ideas?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect
 Instrument Software and Science Data Systems Section (398)
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 168-519, Mailstop: 168-527
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 
 
 
   --
 Tom Barber | Technical Director
 
 meteorite bi
 T: +44 20 8133 3730
 W: www.meteorite.bi http://www.meteorite.bi | Skype:
 meteorite.consulting
 A: Surrey Technology Centre, Surrey Research Park,
 Guildford, GU2 7YG, UK
 
 
 
 
 
 
 -- 
 *Lewis*

Re: ApacheCon CFP closes June 25

[kelly]

+1.316

On 2014-06-13, at 2:54 AM, Tom Barber tom.bar...@meteorite.bi wrote:

 Dear OODT enthusiast,
 
 As you may be aware, ApacheCon will be held this year in Budapest, on
 November 17-23. (Seehttp://apachecon.eu  for more info.)
 
 The Call For Papers for that conference is still open, but will be
 closing soon. We need you talk proposals, to represent OODT at
 ApacheCon. We need all kinds of talks - deep technical talks, hands-on
 tutorials, introductions for beginners, or case studies about the
 awesome stuff you're doing with OODT.
 
 Please consider submitting a proposal, at
 http://events.linuxfoundation.org//events/apachecon-europe/program/cfp

Re: [REQUEST] Ideas for OODT Site

[kelly]

I suppose my hand-crafted HTML  CSS have served their time.

Goodbye chemical OODT!

--k

On 2014-06-10, at 12:55 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Folks,
 It is a goal to shift the OODT site over to the Apache Content Management
 System [0] by the end of this week.
 I logged a Jira issue for this here[1].
 What I am trying to get right now are ideas for the design of the new
 site...
 Have you guys seen any cool templates you would like to base the new site
 on?
 Are there any cool sites you've seen recently which you would like to
 shadow?
 
 Thanks
 Lewis
 
 [0] http://www.apache.org/dev/cms.html
 [1] https://issues.apache.org/jira/browse/OODT-678
 
 -- 
 *Lewis*

Re: Keeping CHANGES.txt in sync with actual CHANGES

[kelly]

+1.

Heck, +193.6.

Thanks for the reminder Lewis.

--k

On 2014-06-06, at 3:38 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 Hi Folks,
 Can I please ask that we keep CHANGES.txt up-to-date.
 I forget this ALL the time... so I know how easy it is.
 It is really helpful for quick provenance tracking over time.
 Right now I have a local copy of OODT, with a number of files changed
 within filemgr component and I just did a svn update... which of course led
 to conflicts. I then went to CHANGES.txt, and I am now having to sniff my
 way through through svn log and viewvc to try and piece together what has
 been committed to trunk codebase.
 /rant
 Have a great weekend folks :)
 Lewis
 
 -- 
 *Lewis*

Future Plans for OODT 2014

[kelly]

Hey folks:

Apache™ OODT has enjoyed a meteoric rise and we've leveled off, reaching our 
cruising speed and voyaging into open source deep space.

We've got a novel talk coming up at ApacheCon and a lot of fantastic recent 
development. I don't want to lose our momentum, though. In the coming months, 
I'd love to see us push on a few fronts:

== 1️⃣ Release of 0.7 ==

Do we have enough to cut a new release? By habit we do so twice a year, and I'm 
fine with that. But, should we buck our trend?

== 2️⃣ Recruitment evaluation ==

We have a really healthy group of committers/committee-members. Is there anyone 
else on the horizon we should consider? I think magicaltrout's talk might help 
attract some new talent—as well as the general fervor of ApacheCon—so let's be 
on the lookout, everyone!

== 3️⃣ OODT Drinking Game ==

Drink a shot whenever someone says any of these phrases: virtual laboratory, 
metadata middleware, catalog and archive (two shots if said separately), 
SCIENCE (must be yelled or typed in all-caps), data grid, integration.

Drink two shots for these phrases: multidimensional aggregation and allocation, 
transparent search and discovery, key performance indicators optimization, MIME 
type detection.

Down your beverage for any of these phrases: stovepipe, thought leader, unit 
tests only work in pacific time zone, failed to find available node for job 
spec: null.

Bonus: eat whatever garnish is on your beverage for these phrases: Radix, 
Agility, Balance.

== 4️⃣ New Territory ==

What other fronts do you think we should pursue? What other rules should be 
added to the drinking game?

Thanks for being a part of Apache™ OODT!

--Sean

-- 
Sean Kelly
Vice President, Apache OODT
Apache Software Foundation

Re: OODT's Git mirror at Github is borked

[kelly]

Definitely, thanks Jake. 

And thank you, Chris, for hunting this down. 

--k

On 2014-01-31, at 10:36 AM, Chris Mattmann mattm...@apache.org wrote:

 Thank you Jake!
 
 
 -Original Message-
 From: Jake Farrell jfarr...@apache.org
 Reply-To: jfarr...@apache.org jfarr...@apache.org
 Date: Friday, January 31, 2014 8:05 AM
 To: jpluser mattm...@apache.org
 Cc: jfarr...@apache.org jfarr...@apache.org,
 infrastruct...@apache.org infrastruct...@apache.org,
 dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: OODT's Git mirror at Github is borked
 
 Hey Chris
 Looks like oodt is missing the svn mirror on git-wip, hook depends on it
 being on git-wip. its only showing on git.a.o. will get it synced shortly
 and see why it isnt in both places
 
 
 -Jake
 
 
 
 On Fri, Jan 31, 2014 at 12:13 AM, Chris Mattmann
 mattm...@apache.org wrote:
 
 Thanks Jake.
 
 I just tested this out by issuing a pull request, see:
 
 https://github.com/apache/oodt/pull/3
 
 
 I didn't see an email show up on dev@oodt and if I look at apmail:
 
 [hermes] 5:12am oodt.apache.org http://oodt.apache.org  ezmlm-list dev
 | grep git
 g...@git.apache.org
 [hermes] 5:12am oodt.apache.org http://oodt.apache.org 
 
 
 Any idea what's up? Is there some delay on the hook script?
 
 Cheers,
 Chris
 
 
 
 
 
 -Original Message-
 From: Jake Farrell jfarr...@apache.org
 Reply-To: jfarr...@apache.org jfarr...@apache.org
 Date: Wednesday, January 29, 2014 9:59 PM
 To: jpluser mattm...@apache.org
 Cc: jfarr...@apache.org jfarr...@apache.org,
 infrastruct...@apache.org infrastruct...@apache.org,
 dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: OODT's Git mirror at Github is borked
 
 Hey Chris
 Hook added
 
 
 -Jake
 
 
 
 On Thu, Jan 30, 2014 at 12:47 AM, Chris Mattmann
 mattm...@apache.org wrote:
 
 Hey Jake,
 
 Thanks. I know what the official source repository is for OODT,
 and that SVN is the canonical bits, and that the mirror at Github
 is simply a mirror. I also know that merges aren't automatic and
 that they can't automatically be integrated.
 
 My question is can you configure the pull request-to-email list
 notification? We should be able to do that without switching to
 Git, correct? I'm not proposing to move OODT to Git. Thanks.
 
 Cheers,
 Chris
 
 
 
 -Original Message-
 From: Jake Farrell jfarr...@apache.org
 Reply-To: jfarr...@apache.org jfarr...@apache.org
 Date: Wednesday, January 29, 2014 9:36 PM
 To: jpluser mattm...@apache.org
 Cc: jfarr...@apache.org jfarr...@apache.org,
 infrastruct...@apache.org infrastruct...@apache.org,
 dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: OODT's Git mirror at Github is borked
 
 Hey Chris
 The official source repository for OODT is currently in svn, and Github
 is just a mirror of that svn repository. When a pull request is issued
 against one of our mirrors on Github it can email the configured mailing
 list for that mirror that a pull request
 is available, but it can not be merged into that mirror. The Github
 notification email that is sent contains a link to the patch and the
 description or comment that was given, not the actual patch itself.
 
 
 Tika has 3 open pull requests which are 8 months old to 2 years old,
 comments can be made by anyone on them, but only Github Apache org
 admins
 can close them out.
 
 
 If OODT is interested in switching over to git and using git-wip-us.a.o
 as the primary repository I would be happy to help migrate them.
 
 
 If you have any other questions let me know
 -Jake
 
 
 
 
 
 
 On Thu, Jan 30, 2014 at 12:21 AM, Chris Mattmann
 mattm...@apache.org wrote:
 
 Thanks Jake. I guess I was under the (potentially) wrong impression
 that we could do pull requests against our Github mirrors for ASF
 projects and they would show up as emails on our
 dev@oodt.apache.org mailto:dev@oodt.apache.org
 mailing lists with emails back to the patch that the pull request
 represented. I've seen this in Tika and in a few other projects.
 
 Is that not the case anymore? I could directly commit to OODT as I'm
 a PMC member for the project, but I wanted to be cool and try Github ;)
 
 Cheers,
 Chris
 
 
 
 
 -Original Message-
 From: Jake Farrell jfarr...@apache.org
 Reply-To: jfarr...@apache.org jfarr...@apache.org
 Date: Wednesday, January 29, 2014 9:19 PM
 To: jpluser mattm...@apache.org
 Cc: infrastruct...@apache.org infrastruct...@apache.org,
 dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: OODT's Git mirror at Github is borked
 
 Hey Chris
 I have switched the default branch on the Github mirror for OODT to be
 trunk and closed out the two open pull requests that you had issued.
 Can
 you please submit the patches you have to OODT
 and not issue pull requests against the mirror as no one from OODT
 will
 be able to accept/merge them or close the pull request.
 
 
 Thanks
 -Jake
 
 
 
 
 
 
 On Wed, Jan 29, 2014 at 11:58 PM, Chris Mattmann
 mattm...@apache.org wrote:
 
 Hey Guys,
 
 
 I just tried to do some 

Re: [jira] [Resolved] (OODT-629) python wrapper for workflow xml-rpc

[kelly]

 Python wrapper for OODT's workflow manager xml-rpc interface providing quick 
 integration into a python based application.

Awesome. Thanks Arni!

--k

OODT wiki issues

[kelly]

Gavin:

Would you mind taking off your OODT hat for a sec and putting on your infra hat?

Paul Ramirez and I would like to make some updates to the OODT Confluence wiki, 
but since the new restrictions went in place, we no longer have write access.

And neither of us have access to the Space Permissions. Do you know who does? 
And should that person be someone in the OODT group, say you or the chair or 
someone?

Thanks!
--k

-- 
Sean Kelly
VP, Apache OODT
Member, Apache Software Foundation

Re: OODT wiki issues

[kelly]

Gavin:

Sorry to follow-up to my own follow-up, but after speaking with Uli- in 
#asfinfra, I filed this instead:

https://issues.apache.org/jira/browse/INFRA-6921

Anyway, sorry to bug you!

--k

On 2013.Oct.24, at 10.01a, ke...@apache.org wrote:

 Gavin:
 
 Would you mind taking off your OODT hat for a sec and putting on your infra 
 hat?
 
 Paul Ramirez and I would like to make some updates to the OODT Confluence 
 wiki, but since the new restrictions went in place, we no longer have write 
 access.
 
 And neither of us have access to the Space Permissions. Do you know who does? 
 And should that person be someone in the OODT group, say you or the chair or 
 someone?
 
 Thanks!
 --k
 
 -- 
 Sean Kelly
 VP, Apache OODT
 Member, Apache Software Foundation
 

Re: Apache OODT Wiki Space Access

[kelly]

Your name's on the ticket for access, Lewis:

https://issues.apache.org/jira/browse/INFRA-6921

Take care!
--k

On 2013.Oct.24, at 11.10a, Lewis John Mcgibbney lewis.mcgibb...@gmail.com 
wrote:

 ACK.
 I would like access.
 I'll be starting on documentation soon enough.
 Thanks
 Lewis

Re: svn commit: r2505 - /release/oodt/

[kelly]

Go Chris go! Go Chris go!

On 2013.Jul.17, at 3.30p, mattm...@apache.org wrote:

 Author: mattmann
 Date: Wed Jul 17 20:30:44 2013
 New Revision: 2505
 
 Log:
 Push Apache OODT 0.6 release.

Woot!

 Removed:
 ...
release/oodt/KEYS

Also, thanks for removing that!

--k

Re: [VOTE] Apache OODT 0.6 Release Candidate #1

[kelly]

 http://people.apache.org/~mattmann/apache-oodt-0.6/rc1/

MD5: match
SHA1: match
Signature: Chris Mattmann (CODE SIGNING KEY) mattm...@apache.org
Java tests: pass
Python tests: pass

[✗] +1 Release this package as Apache OODT 0.6

Heck yes. Thanks for rolling up the release!

--k

Re: [VOTE] Apache OODT 0.6 Release Candidate #1

[kelly]

 Also selfishly verified that all three PEAR packages (filemgr, balance, sso) 
 have version numbers bumped to 0.6 and that all packages build via `pear 
 package` and install via `(sudo) pear install pkg_name.tgz`. Looks great!

I'd say that's rather selfless! Thanks for checking that!

--k

Fwd: [SECURITY] Frame injection vulnerability in published Javadoc

[kelly]

See the forwarded message below. Yuck.

I used the patching tool mentioned to fix OODT's Javadocs online at 
http://oodt.apache.org/

Whoever cuts the next OODT website MUST use Java 1.7.0_23 or higher.

--k

Begin forwarded message:

 From: Mark Thomas ma...@apache.org
 Subject: [SECURITY] Frame injection vulnerability in published Javadoc
 Date: 2013 June 20 3.29.23a CDT
 To: committ...@apache.org
 Cc: r...@apache.org
 Reply-To: infrastruct...@apache.org infrastruct...@apache.org
 
 Hi All,
 
 Oracle has announced [1], [2] a frame injection vulnerability in Javadoc
 generated by Java 5, Java 6 and Java 7 before update 22.
 
 The infrastructure team has completed a scan of our current project
 websites and identified over 6000 instances of vulnerable Javadoc
 distributed across most TLPs. The chances are the project(s) you
 contribute to is(are) affected. A list of projects and the number of
 affected Javadoc instances per project is provided at the end of this
 e-mail.
 
 Please take the necessary steps to fix any currently published Javadoc
 and to ensure that any future Javadoc published by your project does not
 contain the vulnerability. The announcement by Oracle includes a link to
 a tool that can be used to fix Javadoc without regeneration.
 
 The infrastructure team is investigating options for preventing the
 publication of vulnerable Javadoc.
 
 The issue is public and may be discussed freely on your project's dev list.
 
 Thanks,
 
 Mark (ASF Infra)
 
 
 
 [1]
 http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html
 [2] http://www.kb.cert.org/vuls/id/225657
 
 Project   Instances
 abdera.apache.org 1
 accumulo.apache.org   2
 activemq.apache.org   105
 any23.apache.org  13
 archiva.apache.org4
 archive.apache.org13
 aries.apache.org  7
 avro.apache.org   23
 axis.apache.org   5
 beehive.apache.org16
 bval.apache.org   12
 camel.apache.org  786
 cayenne.apache.org4
 chemistry.apache.org  6
 click.apache.org  3
 cocoon.apache.org 6
 commons.apache.org34
 continuum.apache.org  9
 creadur.apache.org19
 crunch.apache.org 4
 ctakes.apache.org 2
 curator.apache.org4
 cxf.apache.org6
 db.apache.org 39
 directory.apache.org  4
 empire-db.apache.org  1
 felix.apache.org  5
 flume.apache.org  5
 geronimo.apache.org   241
 giraph.apache.org 6
 gora.apache.org   3
 hadoop.apache.org 21
 hbase.apache.org  2
 hive.apache.org   4
 hivemind.apache.org   10
 incubator.apache.org  355
 jackrabbit.apache.org 9
 jakarta.apache.org39
 james.apache.org  53
 jena.apache.org   5
 juddi.apache.org  3
 lenya.apache.org  46
 logging.apache.org111
 lucene.apache.org 713
 manifoldcf.apache.org 112
 marmotta.apache.org   1
 maven.apache.org  1623
 maventest.apache.org  1178
 mina.apache.org   2
 mrunit.apache.org 3
 myfaces.apache.org348
 nutch.apache.org  8
 oltu.apache.org   11
 oodt.apache.org   1
 ooo-site.apache.org   1
 oozie.apache.org  10
 openjpa.apache.org20
 opennlp.apache.org9
 pdfbox.apache.org 1
 pig.apache.org7
 pivot.apache.org  1
 poi.apache.org1
 portals.apache.org35
 river.apache.org  2
 santuario.apache.org  1
 shale.apache.org  55
 shiro.apache.org  3
 sling.apache.org  2
 sqoop.apache.org  4
 struts.apache.org 190
 subversion.apache.org 3
 synapse.apache.org1
 syncope.apache.org2
 tapestry.apache.org   6
 tika.apache.org   9
 tiles.apache.org  12
 turbine.apache.org100
 tuscany.apache.org4
 uima.apache.org   12
 velocity.apache.org   41
 whirr.apache.org  2
 wicket.apache.org 3
 wink.apache.org   13
 ws.apache.org 22
 xalan.apache.org  1
 xerces.apache.org 5
 xml.apache.org1
 xmlbeans.apache.org   3
 zookeeper.apache.org  18
 
 

Re: Interested in participating GSoC 2013 with OODT

[kelly]

GREAT NEWS Rajith! Thanks for sharing.

I hope you and Chris have a fun and productive summer. 

OODTly,
Sean.

On 2013.May.27, at 7.55p, Rajith Siriwardana rajithsiriward...@ieee.org wrote:

 Hi all,
 
 I have been notified that my proposal was accepted for GSOC 2013. Thank you
 so much to everybody in the OODT community for your encouragements, kind
 words and welcoming me to your community. Most importantly thank you very
 much Chris for deciding my proposal is worth sharing your valuable time
 during the summer. I'm very happy to have this opportunity to work with you.
 
 I'm hoping to have a very productive summer and make this project a
 success.
 
 Thanks
 Rajith
 
 
 T.W.R.O. Siriwardana
 StMIEEE
 Undergraduate
 Department of Computer Science  Engineering
 Faculty of Engineering
 University of Moratuwa
 Sri Lanka.
 
 
 On Tue, Apr 23, 2013 at 9:23 PM, Mattmann, Chris A (398J) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Awesome work!
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Rajith Siriwardana rajithsiriward...@ieee.org
 Date: Tuesday, April 23, 2013 8:38 AM
 To: dev dev@oodt.apache.org, jpluser chris.a.mattm...@jpl.nasa.gov
 Subject: Re: Interested in participating GSoC 2013 with OODT
 
 Hi Chris,
 
 I've submitted a first draft of my GSoC 2013 proposal. Here's a link to
 the proposal:[1]
 If you'd like me to make any amendments or additions,
 please let me know and I'll update it.
 Many thanks for your valuable time spent on reviewing my proposal in the
 first place.[1]
 
 https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/ra
 jithsiriwardana/1Cheers,
 Rajith
 ---
 T.W.R.O. Siriwardana
 StMIEEE
 Undergraduate
 Department of Computer Science  Engineering
 Faculty of Engineering
 University of Moratuwa
 Sri Lanka.
 
 
 
 
 
 
 On Sat, Apr 20, 2013 at 11:59 AM, Mattmann, Chris A (398J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Thanks Rajith!
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 
 -Original Message-
 From: Rajith Siriwardana rajithsiriward...@gmail.com
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 
 Date: Friday, April 12, 2013 10:38 AM
 To: dev dev@oodt.apache.org
 Subject: Re: Interested in participating GSoC 2013 with OODT
 
 On Fri, Apr 12, 2013 at 10:54 PM, Mattmann, Chris A (398J) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Hi Rajith,
 
 Thanks, replies below!
 
 
 
 -Original Message-
 From: Rajith Siriwardana rajithsiriward...@ieee.org
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Friday, April 12, 2013 10:17 AM
 To: dev dev@oodt.apache.org
 Subject: Re: Interested in participating GSoC 2013 with OODT
 
 Hi Chris,
 please find the comments inline.
 [..snip..]
 
 
 Do you know of one? I looked way back in 2005 but there wasn't one
 back
 then.
 
 
 Still I haven't found a parser compatible with the Apache license
 v2.0,
 but
 I found some parsers to get the idea of how it should be. I guess it
 won't
 be hard.
 
 +1, great.
 
 
 
 
 
  - In job status monitoring it will involve jvm monitoring (that
 is
 not
  related to the plugin as it just polling gmetad) correct me if
 i¹m
  misunderstood the job concept.
 
 Job status is resource manager job status polling. Have you seen the
 Job class in resource manager?
 
 
 yep I did that, gmetad has nothing to do with polling job status
 information. Should GangliaAssignmentMonitor worry about obtaining job
 status information then? am I missing something here?
 
 I'm not sure what you mean about it not having anything to do with job
 polling?
 gmetad collects metrics published by gmond. Some of those metrics are
 related to
 CPU load, disk space, etc. I guess that's what I meant, more than job
 status.
 
 
 No Chris I guess the confusion caused by this
 
 In the issue OODT-219 it says Write a GangliaAssignmentMonitor and
 
 
 GangliaAssignmentMonitorFactory that plug in to Ganglia to   obtain *Job
 status information*. hence I thought it should also 

[ANNOUNCE] Welcome Varun Ratnakar as an OODT PMC member!

[kelly]

Folks:

I'm happy to report that Varun Ratnakar has accepted our invitation to become 
not just a committer on Apache OODT but to also join the OODT Project 
Management Committee. WOOT!

Welcome, Varun. Feel free to introduce yourself.

--k

Re: New list ?

[kelly]

Progress on OODT is strongly driven by JIRA issues, so my only concern would be 
that folks might forget to subscribe and miss out on what initiates progress on 
the codebase.

--k

On 2013.Apr.30, at 5.04a, Gavin McDonald ga...@16degrees.com.au wrote:

 A personal peeve of mine, all the jira notifications going to the commits
 list, makes it hard to see whats going on.
 
 (Yes I could filter but..)
 
 How about an issues@ list where we can send the jira stuff ?
 
 Gav...
 
 

[ANNOUNCE] Welcome Gavin McDonald as an OODT PMC member and committer!

[Sean Kelly]

Folks:

I'm happy to report that Gavin McDonald has accepted our invitation to become a 
committer on Apache OODT and to join the OODT Project Management Committee. 
WOOT!

Welcome, Gav. Please feel free to introduce yourself.

--k

[REPORT] Apache OODT

[Sean Kelly]

DESCRIPTION

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.

RELEASES/DEVELOPMENT

For our Christmas-day gift of 2012, we released version 0.5 of OODT [1], which
closed out 61 issues in JIRA [2] and provided improvements to:

* OODT File Manager, and Lucene- and Solr-based catalog indexing
* Curator JAX-RS web application
* PushPull remote file retrieval
* WEngine workflow system

Future work in the next quarter will focus on cross-fertilization projects
with Apache Airavata and Apache Tika, as well as fleshing out our Python APIs.

OODT Jenkins jobs are now prominently featured from our project home page [3].

Our development mailing lists remain quite popular, while the user list shows
less activity.  The table below lists the number of postings by list, by
month, in 2013:

List Jan Feb Mar
 --- --- ---
dev   57  75  12
user  12  16   0

COMMUNITY

The North American ApacheCon 2013 conspicuously featured Apache OODT.  Seven
speakers gave eight presentations about OODT in the Apache in Science track at
the conference [4].

We established a third social media base at Google Plus [5], complementing our
existing Facebook [6] and Twitter [7] presence.  We also created a read-only
mirror of OODT at Github [8], enabling a wider base of code contributions and
future participants.

BRANDING

There are no outstanding branding issues since our last report. All's good.

PRESS

Apache OODT received noteworthy attention in two articles penned by our
eminent member Chris A. Mattmann:

* Nature published Computing: A Vision for Data Science [9] in volume 493
  (p. 474) featuring Apache OODT, Hadoop, and Tika in the face of big data.

* Software Development Times published Apache Does Science [10], discussing
  OODT's and Apache Airavata's places in scientific endeavors.

ISSUES

There are no issues requiring board attention at this time.

[1] http://s.apache.org/gm
[2] http://issues.apache.org/jira/browse/OODT
[3] http://oodt.apache.org/
[4] http://s.apache.org/c8C
[5] http://s.apache.org/8vM
[6] http://s.apache.org/M5x
[7] http://s.apache.org/PYt
[8] http://s.apache.org/cNy
[9] http://s.apache.org/eS
[10] http://s.apache.org/Yeg

Re: Requested Read-only Git Mirror for Apache OODT

[Sean Kelly]

Given how much time I spend on Github these days, this is especially convenient.

Thanks a lot, Chris!
--k




On 2013.Jan.21, at 11.08a, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Dear all,
 
 This is now complete:
 
 https://github.com/apache/oodt
 
 
 Apache OODT is available on Github. If you make a pull request over there
 too I *think* that we'll get an email here on the dev@oodt list to
 integrate it. Yay!
 
 Cheers,
 Chris
 
 On 1/12/13 10:04 AM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Hey Guys,
 
 FYI https://issues.apache.org/jira/browse/INFRA-5759
 
 I requested a GitHub read-only Git mirror for Apache OODT. Yay!
 
 I'm not proposing we move to Git for our CM system :) I just wanted folks
 on Github to be able to send us pull requests with improvements if they
 have any.
 
 Cheers,
 Chris
 
 

Re: [NOTICE] Added a ton of new material on the Apache OODT Web Page

[Sean Kelly]

Wooo! Looks fantastic Chris. Thanks for adding those links to the doormat and 
fixing up the other broken links and typos.

Happy new year!
--Sean


On 2012.Dec.26, at 11.45p, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Guys FYI I added a ton of new material on the Home Page, as you can
 probably tell. Including:
 
 1. Links to Jenkins in the Bottom Footer
 2. Links to PEAR channel in Bottom Footer
 3. Links to PyPI in Bottom Footer
 4. Links to Gplus sites
 5. News and announcements for 0.5 release and for ApacheCon NA 2011 and
 2013
 6. Link to Jenkins on testing page
 7. Various link fixes and typo fixes throughout
 
 Yay!
 
 Cheers,
 Chris
 

Re: [RESULT] [VOTE] Apache OODT 0.5 RC #1

[Sean Kelly]

Along with snow keeping my in-laws at bay, another Xmas miracle has occurred!

Congratulations to us all for another Apache™ OODT release!

Thanks again for rolling it up, Chris.
--k


On 2012.Dec.25, at 4.24p, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Merry Christmas Apache OODT users and devs!
 
 The VOTE to release 0.5 has passed with the following tallies:
 
 +1 PMC
 
 Chris Mattmann
 Sean Kelly
 Luca Cinquini
 Mike Joyce
 
 I'll push the release out to the mirrors and send an ANNOUNCE very soon.
 I'll also update the website shortly.
 
 Merry Christmas!
 
 Cheers,
 Chris
 

Re: [VOTE] Apache OODT 0.5 RC #1

[Sean Kelly]

MD5: matches!
SHA1: matches!
Signature: verified!
Python tests: pass!
Java tests: pass!

My vote:

 [✗] +1 Release the packages as Apache OODT 0.5

Thanks for rolling the release, Chris!
--k

Re: [VOTE] Apache OODT 0.5 RC #1

[Sean Kelly]

 Will do thanks dude. Are you +1 on the release?

See: http://s.apache.org/WQC

--k

Re: Problems committing an OODT patch

[Sean Kelly]

Rishi, you can report trouble with SVN access; see 
http://www.apache.org/dev/reporting-issues.html#svn-access

I also checked the oodt group to ensure you have access; and I see riverma 
as an active account, so it might some other issue.

Good luck!

--
Sean Kelly
Apache Software Foundation

On 2012.Jul.20, at 6.45p, Verma, Rishi (388J) wrote:

 Hi all,
 
 I'm getting svn access problems committing a patch to the OODT trunk.
 i.e.
 bash-3.2$ svn commit -m OODT-466 resolution: Allow MIME type (HTTP 
 content-type) configurability for product handlers' generated content
 svn: Commit failed (details follow):
 svn: access to '/repos/asf/!svn/act/a9oo3d5c-1156-5a89-adf5-1sgh13c53eb' 
 forbidden
 
 Could someone please provide e-mail contacts for Apache admins who may be 
 able to look into this?
 
 Thanks!
 rishi

Re: OODT XML Namespace URI

[Sean Kelly]

 One thing that we should think about too is how to bake these schemas
 into the OODT jar files.

These aren't schemata, just namespaces. There doesn't need to be anything 
resolvable by the URI.

--k

OODT XML Namespace URI

[Sean Kelly]

Hey folks:

What is the official XML namespace URI for Apache™ OODT?

--k

Re: Google Summer of Code 2012

[Sean Kelly]

 http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/rlaidlaw/1

Argh.  When I try to view it, I get:

This proposal is not made public, and you are not the student who submitted the 
proposal, nor are you a mentor for the organization it was submitted to.








Maybe another OODT'er can see it?

--k

Re: Build failed in Jenkins: oodt-trunk #378

[Sean Kelly]

Quite! #TDD: it must break first, then work second!

On 2012.Mar.28, at 10.50p, Mattmann, Chris A (388J) wrote:

 hahah #TDD dude, you aren't retarded!

Re: Heads up: OODT-396 and OODT-397

[Sean Kelly]

  -- I'm trying to do #TDD to wrap up OODT-215 :)

I ♥ #TDD.

--k

Re: build fail ?

[Sean Kelly]

 [INFO] Failed to create assembly: Failed to retrieve OS environment 
 variables. Reason: Cannot run program env: java.io.IOException: error=24, 
 Too many open files
 ...
 Did I do something wrong, or is there something that needs fixing on the 
 server ?

Sounds like a server issue.

Jenkins may need to be restarted on the server, or perhaps the server itself 
needs a reboot.

Or, optimistically, you might just try re-kicking the build off manually and 
see if it works.

--k