You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by Tom Barber <to...@spicule.co.uk> on 2019/10/05 09:43:18 UTC
OODT 2.0 planning
Alrighty with 1.9 shipped we can now look at 2.0 with all new fun stuff.
I’ve probably forgotten some bits and pieces but here’s my wish list:
React components and Breno’s wrapper for OpsUI and improved custom web app
embedding
Updating lots of old dependencies to more current stuff.
Newer JDK support.
Test and document and demo the docker builds.
ZK stuff for distributed Filemanager deployments or scaled up docker
deployments
What have I forgotten?
Tom
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Gimhana Nadeeshan <gi...@cse.mrt.ac.lk>.
Hi All,
As per our offline conversation, I started testing with JDK11 migration. As
the first step just updated some of the project dependencies and fixed some
unit tests.
Please have a look at the PR [1]. There are few more critical dependency
updates like Solr and I hope to do it in the next few days.
[1] https://github.com/apache/oodt/pull/118
Thanks and regards,
Gimhana
On Wed, 6 Jan 2021 at 12:32, Imesha Sudasingha <im...@apache.org> wrote:
> Seems like it was due to JDK 11. Got through using JDK 8.
>
> On Wed, 6 Jan 2021 at 12:28, Imesha Sudasingha <im...@apache.org> wrote:
>
> > Hi Gimhana,
> >
> > Thanks for the details. As per our offline conversation, did you manage
> to
> > get the JDK 11 testing ongoing?
> > Because I tried to build this on JDK 11 today and it failed with:
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc
> > (attach-javadocs) on project oodt-core: Execution attach-javadocs of goal
> > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc failed: An
> API
> > incompatibility was encountered while executing
> > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc:
> > java.lang.ExceptionInInitializerError: null
> > [ERROR] -----------------------------------------------------
> > [ERROR] realm =
> > plugin>org.apache.maven.plugins:maven-javadoc-plugin:2.10.3
> > [ERROR] strategy =
> > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> > [ERROR] urls[0] =
> >
> file:/home/imesha/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.10.3/maven-javadoc-plugin-2.10.3.jar
> >
> > Not sure if this was entirely due to JDK 11.
> >
> > Imesha
> >
> > On Tue, 17 Nov 2020 at 07:59, Gimhana Nadeeshan <
> > gimhanadesilva.15@cse.mrt.ac.lk> wrote:
> >
> >> Hi all,
> >>
> >> 2. About JDK 11 support, does anybody have any idea on how we can test
> >> that
> >> > or what issues do we have when running with JDK 11? I remember Lewis
> >> trying
> >> > to run OODT with JDK 10 sometime back [3] [4]
> >> >
> >>
> >> As we discussed offline, here I'll put my suggestion regarding OpenJDK
> 11
> >> migration.
> >>
> >> When migrating basically what we have to have to do is
> >>
> >> - Update all dependencies to the latest versions.
> >> - Compile the project and resolve all issues related to unofficial
> >> access, split packages and deprecated/removed Java EE modules.
> >>
> >> We use the official Oracle JDK 11 migration guide[1] as a head start.
> >> However, we cannot guarantee that we will be able to update all the
> >> dependencies without breaking stuff. Have to try and see!
> >>
> >> [1]
> https://docs.oracle.com/en/java/javase/11/migrate/migration-guide.pdf
> >>
> >> Thanks and Regards,
> >> Gimhana
> >>
> >> On Thu, 12 Nov 2020 at 13:32, Imesha Sudasingha <im...@apache.org>
> >> wrote:
> >>
> >> > Great! We have 2 action items then:
> >> >
> >> > 1. Making Avro RPC the default. We once did this for the 1.9 release
> and
> >> > later reverted due to 1.x backward compatibility issues [1].
> Therefore,
> >> > this task can reuse some commits we had there (simply revert [2]).
> >> >
> >> > 2. About JDK 11 support, does anybody have any idea on how we can test
> >> that
> >> > or what issues do we have when running with JDK 11? I remember Lewis
> >> trying
> >> > to run OODT with JDK 10 sometime back [3] [4]
> >> >
> >> > [1] https://issues.apache.org/jira/browse/OODT-1031
> >> > [2] https://github.com/apache/oodt/pull/116
> >> > [3] https://github.com/apache/oodt/pull/71
> >> > [4] https://issues.apache.org/jira/browse/OODT-990
> >> >
> >> >
> >> > On Wed, 11 Nov 2020 at 22:20, Tom Barber <to...@spicule.co.uk> wrote:
> >> >
> >> > > I've officially marked all my email as read, so thats 3000 emails
> gone
> >> > > forever... on the plus side, I should have some time now. I've got a
> >> > couple
> >> > > of projects I need to get off my plate so I shall setup my new
> laptop
> >> > next
> >> > > week and sort them out, then I'll get this code base stood back up
> and
> >> > > figure out the best place to start.
> >> > >
> >> > > Tom
> >> > >
> >> > > On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <mattmann@apache.org
> >
> >> > > wrote:
> >> > >
> >> > > > +1 from me Imesha!
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > From: Imesha Sudasingha <im...@apache.org>
> >> > > > Reply-To: <de...@oodt.apache.org>
> >> > > > Date: Wednesday, November 11, 2020 at 7:49 AM
> >> > > > To: dev <de...@oodt.apache.org>
> >> > > > Subject: Re: OODT 2.0 planning
> >> > > >
> >> > > >
> >> > > >
> >> > > > Hi All,
> >> > > >
> >> > > >
> >> > > >
> >> > > > This is my suggestion, what if we include both Avro default
> support
> >> and
> >> > > JDK
> >> > > >
> >> > > > 11 support for OODT 2.0 as JDK 11 support seems to be critical as
> >> well.
> >> > > >
> >> > > >
> >> > > >
> >> > > > What do you think?
> >> > > >
> >> > > >
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Imesha
> >> > > >
> >> > > >
> >> > > >
> >> > > > <
> >> > > >
> >> > >
> >> >
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> >> > > > >
> >> > > >
> >> > > > Virus-free.
> >> > > >
> >> > > > www.avast.com
> >> > > >
> >> > > > <
> >> > > >
> >> > >
> >> >
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> >> > > > >
> >> > > >
> >> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <imesha@apache.org
> >
> >> > > wrote:
> >> > > >
> >> > > >
> >> > > >
> >> > > > Hi Sean,
> >> > > >
> >> > > >
> >> > > >
> >> > > > Regarding docker images, we haven't decided where to push them
> yet.
> >> > > Yasith
> >> > > >
> >> > > > was the person who contributed to them for his GSoC.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Hi Yasith,
> >> > > >
> >> > > >
> >> > > >
> >> > > > Your help is much appreciated and we will definitely need your
> help
> >> > > there.
> >> > > >
> >> > > > Keep in touch with the mails in this list.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > Imesha
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <
> yasith@cs.odu.edu
> >> >
> >> > > >
> >> > > > wrote:
> >> > > >
> >> > > >
> >> > > >
> >> > > > Hello all,
> >> > > >
> >> > > >
> >> > > >
> >> > > > I can make some time to help with the 2.3 release as well.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Best Regards,
> >> > > >
> >> > > > Yasith
> >> > > >
> >> > > >
> >> > > >
> >> > > > > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org>
> wrote:
> >> > > >
> >> > > > >
> >> > > >
> >> > > > >
> >> > > >
> >> > > > >> 2.0 – first release where we remove all the Xml-RPC and we
> change
> >> > > >
> >> > > > nothing
> >> > > >
> >> > > > >> else. Avro is the default, and only
> >> > > >
> >> > > > >> comm option – though interface exists for anyone that wants to
> >> roll
> >> > > >
> >> > > > their
> >> > > >
> >> > > > >> own. We change nothing else*
> >> > > >
> >> > > > >
> >> > > >
> >> > > > > Sounds fine by me. XML-RPC was "fun while it lasted".
> >> > > >
> >> > > > >
> >> > > >
> >> > > > >>
> >> > > >
> >> > > > >> 2.1 – first release with newer JDK support (everyone is asking
> >> for
> >> > > >
> >> > > > this,
> >> > > >
> >> > > > >> and it screws up people like me with
> >> > > >
> >> > > > >> new Macs, or computers and newer JDKs by default). We also
> begin
> >> > > >
> >> > > > cleaning
> >> > > >
> >> > > > >> up dependencies and removing
> >> > > >
> >> > > > >> old ones, and pointing at new stuff.
> >> > > >
> >> > > > >
> >> > > >
> >> > > > > Oh my glob yes, yes, yes!
> >> > > >
> >> > > > >>
> >> > > >
> >> > > > >> 2.2 – OpsUi React with GSoC 2019 output.
> >> > > >
> >> > > > >
> >> > > >
> >> > > > > I can't comment on 2.2 since I've never used it.
> >> > > >
> >> > > > >>
> >> > > >
> >> > > > >> 2.3 – We integrate, test and demo the Docker builds. We also
> test
> >> > and
> >> > > >
> >> > > > fully
> >> > > >
> >> > > > >> bake the ZK deployments and
> >> > > >
> >> > > > >> scaled up Docker.
> >> > > >
> >> > > > >
> >> > > >
> >> > > > > Are these the images owned by "oodthub" on hub.docker.com?
> >> > > >
> >> > > > >
> >> > > >
> >> > > > > Take care,
> >> > > >
> >> > > > > -SK
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > >
> >> > > --
> >> > >
> >> > >
> >> > > Spicule Limited is registered in England & Wales. Company Number:
> >> > > 09954122. Registered office: First Floor, Telecom House, 125-135
> >> Preston
> >> > > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > All engagements
> >> > > are subject to Spicule Terms and Conditions of Business. This email
> >> and
> >> > > its
> >> > > contents are intended solely for the individual to whom it is
> >> addressed
> >> > > and
> >> > > may contain information that is confidential, privileged or
> otherwise
> >> > > protected from disclosure, distributing or copying. Any views or
> >> opinions
> >> > > presented in this email are solely those of the author and do not
> >> > > necessarily represent those of Spicule Limited. The company accepts
> no
> >> > > liability for any damage caused by any virus transmitted by this
> >> email.
> >> > If
> >> > > you have received this message in error, please notify us
> immediately
> >> by
> >> > > reply email before deleting it from your system. Service of legal
> >> notice
> >> > > cannot be effected on Spicule Limited by email.
> >> > >
> >> >
> >>
> >>
> >>
> >>
> >> * <http://www.linkedin.com/in/nadeeshangimhana/>*
> >>
> >>
> >> * <http://www.linkedin.com/in/nadeeshangimhana/>*
> >>
> >
>
* <http://www.linkedin.com/in/nadeeshangimhana/>*
* <http://www.linkedin.com/in/nadeeshangimhana/>*
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Seems like it was due to JDK 11. Got through using JDK 8.
On Wed, 6 Jan 2021 at 12:28, Imesha Sudasingha <im...@apache.org> wrote:
> Hi Gimhana,
>
> Thanks for the details. As per our offline conversation, did you manage to
> get the JDK 11 testing ongoing?
> Because I tried to build this on JDK 11 today and it failed with:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc
> (attach-javadocs) on project oodt-core: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -----------------------------------------------------
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-javadoc-plugin:2.10.3
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/imesha/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.10.3/maven-javadoc-plugin-2.10.3.jar
>
> Not sure if this was entirely due to JDK 11.
>
> Imesha
>
> On Tue, 17 Nov 2020 at 07:59, Gimhana Nadeeshan <
> gimhanadesilva.15@cse.mrt.ac.lk> wrote:
>
>> Hi all,
>>
>> 2. About JDK 11 support, does anybody have any idea on how we can test
>> that
>> > or what issues do we have when running with JDK 11? I remember Lewis
>> trying
>> > to run OODT with JDK 10 sometime back [3] [4]
>> >
>>
>> As we discussed offline, here I'll put my suggestion regarding OpenJDK 11
>> migration.
>>
>> When migrating basically what we have to have to do is
>>
>> - Update all dependencies to the latest versions.
>> - Compile the project and resolve all issues related to unofficial
>> access, split packages and deprecated/removed Java EE modules.
>>
>> We use the official Oracle JDK 11 migration guide[1] as a head start.
>> However, we cannot guarantee that we will be able to update all the
>> dependencies without breaking stuff. Have to try and see!
>>
>> [1] https://docs.oracle.com/en/java/javase/11/migrate/migration-guide.pdf
>>
>> Thanks and Regards,
>> Gimhana
>>
>> On Thu, 12 Nov 2020 at 13:32, Imesha Sudasingha <im...@apache.org>
>> wrote:
>>
>> > Great! We have 2 action items then:
>> >
>> > 1. Making Avro RPC the default. We once did this for the 1.9 release and
>> > later reverted due to 1.x backward compatibility issues [1]. Therefore,
>> > this task can reuse some commits we had there (simply revert [2]).
>> >
>> > 2. About JDK 11 support, does anybody have any idea on how we can test
>> that
>> > or what issues do we have when running with JDK 11? I remember Lewis
>> trying
>> > to run OODT with JDK 10 sometime back [3] [4]
>> >
>> > [1] https://issues.apache.org/jira/browse/OODT-1031
>> > [2] https://github.com/apache/oodt/pull/116
>> > [3] https://github.com/apache/oodt/pull/71
>> > [4] https://issues.apache.org/jira/browse/OODT-990
>> >
>> >
>> > On Wed, 11 Nov 2020 at 22:20, Tom Barber <to...@spicule.co.uk> wrote:
>> >
>> > > I've officially marked all my email as read, so thats 3000 emails gone
>> > > forever... on the plus side, I should have some time now. I've got a
>> > couple
>> > > of projects I need to get off my plate so I shall setup my new laptop
>> > next
>> > > week and sort them out, then I'll get this code base stood back up and
>> > > figure out the best place to start.
>> > >
>> > > Tom
>> > >
>> > > On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <ma...@apache.org>
>> > > wrote:
>> > >
>> > > > +1 from me Imesha!
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > From: Imesha Sudasingha <im...@apache.org>
>> > > > Reply-To: <de...@oodt.apache.org>
>> > > > Date: Wednesday, November 11, 2020 at 7:49 AM
>> > > > To: dev <de...@oodt.apache.org>
>> > > > Subject: Re: OODT 2.0 planning
>> > > >
>> > > >
>> > > >
>> > > > Hi All,
>> > > >
>> > > >
>> > > >
>> > > > This is my suggestion, what if we include both Avro default support
>> and
>> > > JDK
>> > > >
>> > > > 11 support for OODT 2.0 as JDK 11 support seems to be critical as
>> well.
>> > > >
>> > > >
>> > > >
>> > > > What do you think?
>> > > >
>> > > >
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Imesha
>> > > >
>> > > >
>> > > >
>> > > > <
>> > > >
>> > >
>> >
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
>> > > > >
>> > > >
>> > > > Virus-free.
>> > > >
>> > > > www.avast.com
>> > > >
>> > > > <
>> > > >
>> > >
>> >
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
>> > > > >
>> > > >
>> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> > > >
>> > > >
>> > > >
>> > > > On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org>
>> > > wrote:
>> > > >
>> > > >
>> > > >
>> > > > Hi Sean,
>> > > >
>> > > >
>> > > >
>> > > > Regarding docker images, we haven't decided where to push them yet.
>> > > Yasith
>> > > >
>> > > > was the person who contributed to them for his GSoC.
>> > > >
>> > > >
>> > > >
>> > > > Hi Yasith,
>> > > >
>> > > >
>> > > >
>> > > > Your help is much appreciated and we will definitely need your help
>> > > there.
>> > > >
>> > > > Keep in touch with the mails in this list.
>> > > >
>> > > >
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Imesha
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <yasith@cs.odu.edu
>> >
>> > > >
>> > > > wrote:
>> > > >
>> > > >
>> > > >
>> > > > Hello all,
>> > > >
>> > > >
>> > > >
>> > > > I can make some time to help with the 2.3 release as well.
>> > > >
>> > > >
>> > > >
>> > > > Best Regards,
>> > > >
>> > > > Yasith
>> > > >
>> > > >
>> > > >
>> > > > > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
>> > > >
>> > > > >
>> > > >
>> > > > >
>> > > >
>> > > > >> 2.0 – first release where we remove all the Xml-RPC and we change
>> > > >
>> > > > nothing
>> > > >
>> > > > >> else. Avro is the default, and only
>> > > >
>> > > > >> comm option – though interface exists for anyone that wants to
>> roll
>> > > >
>> > > > their
>> > > >
>> > > > >> own. We change nothing else*
>> > > >
>> > > > >
>> > > >
>> > > > > Sounds fine by me. XML-RPC was "fun while it lasted".
>> > > >
>> > > > >
>> > > >
>> > > > >>
>> > > >
>> > > > >> 2.1 – first release with newer JDK support (everyone is asking
>> for
>> > > >
>> > > > this,
>> > > >
>> > > > >> and it screws up people like me with
>> > > >
>> > > > >> new Macs, or computers and newer JDKs by default). We also begin
>> > > >
>> > > > cleaning
>> > > >
>> > > > >> up dependencies and removing
>> > > >
>> > > > >> old ones, and pointing at new stuff.
>> > > >
>> > > > >
>> > > >
>> > > > > Oh my glob yes, yes, yes!
>> > > >
>> > > > >>
>> > > >
>> > > > >> 2.2 – OpsUi React with GSoC 2019 output.
>> > > >
>> > > > >
>> > > >
>> > > > > I can't comment on 2.2 since I've never used it.
>> > > >
>> > > > >>
>> > > >
>> > > > >> 2.3 – We integrate, test and demo the Docker builds. We also test
>> > and
>> > > >
>> > > > fully
>> > > >
>> > > > >> bake the ZK deployments and
>> > > >
>> > > > >> scaled up Docker.
>> > > >
>> > > > >
>> > > >
>> > > > > Are these the images owned by "oodthub" on hub.docker.com?
>> > > >
>> > > > >
>> > > >
>> > > > > Take care,
>> > > >
>> > > > > -SK
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > > --
>> > >
>> > >
>> > > Spicule Limited is registered in England & Wales. Company Number:
>> > > 09954122. Registered office: First Floor, Telecom House, 125-135
>> Preston
>> > > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>> > >
>> > >
>> > >
>> > >
>> > > All engagements
>> > > are subject to Spicule Terms and Conditions of Business. This email
>> and
>> > > its
>> > > contents are intended solely for the individual to whom it is
>> addressed
>> > > and
>> > > may contain information that is confidential, privileged or otherwise
>> > > protected from disclosure, distributing or copying. Any views or
>> opinions
>> > > presented in this email are solely those of the author and do not
>> > > necessarily represent those of Spicule Limited. The company accepts no
>> > > liability for any damage caused by any virus transmitted by this
>> email.
>> > If
>> > > you have received this message in error, please notify us immediately
>> by
>> > > reply email before deleting it from your system. Service of legal
>> notice
>> > > cannot be effected on Spicule Limited by email.
>> > >
>> >
>>
>>
>>
>>
>> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>>
>>
>> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>>
>
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Hi Gimhana,
Thanks for the details. As per our offline conversation, did you manage to
get the JDK 11 testing ongoing?
Because I tried to build this on JDK 11 today and it failed with:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc
(attach-javadocs) on project oodt-core: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc:
java.lang.ExceptionInInitializerError: null
[ERROR] -----------------------------------------------------
[ERROR] realm =
plugin>org.apache.maven.plugins:maven-javadoc-plugin:2.10.3
[ERROR] strategy =
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/home/imesha/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.10.3/maven-javadoc-plugin-2.10.3.jar
Not sure if this was entirely due to JDK 11.
Imesha
On Tue, 17 Nov 2020 at 07:59, Gimhana Nadeeshan <
gimhanadesilva.15@cse.mrt.ac.lk> wrote:
> Hi all,
>
> 2. About JDK 11 support, does anybody have any idea on how we can test that
> > or what issues do we have when running with JDK 11? I remember Lewis
> trying
> > to run OODT with JDK 10 sometime back [3] [4]
> >
>
> As we discussed offline, here I'll put my suggestion regarding OpenJDK 11
> migration.
>
> When migrating basically what we have to have to do is
>
> - Update all dependencies to the latest versions.
> - Compile the project and resolve all issues related to unofficial
> access, split packages and deprecated/removed Java EE modules.
>
> We use the official Oracle JDK 11 migration guide[1] as a head start.
> However, we cannot guarantee that we will be able to update all the
> dependencies without breaking stuff. Have to try and see!
>
> [1] https://docs.oracle.com/en/java/javase/11/migrate/migration-guide.pdf
>
> Thanks and Regards,
> Gimhana
>
> On Thu, 12 Nov 2020 at 13:32, Imesha Sudasingha <im...@apache.org> wrote:
>
> > Great! We have 2 action items then:
> >
> > 1. Making Avro RPC the default. We once did this for the 1.9 release and
> > later reverted due to 1.x backward compatibility issues [1]. Therefore,
> > this task can reuse some commits we had there (simply revert [2]).
> >
> > 2. About JDK 11 support, does anybody have any idea on how we can test
> that
> > or what issues do we have when running with JDK 11? I remember Lewis
> trying
> > to run OODT with JDK 10 sometime back [3] [4]
> >
> > [1] https://issues.apache.org/jira/browse/OODT-1031
> > [2] https://github.com/apache/oodt/pull/116
> > [3] https://github.com/apache/oodt/pull/71
> > [4] https://issues.apache.org/jira/browse/OODT-990
> >
> >
> > On Wed, 11 Nov 2020 at 22:20, Tom Barber <to...@spicule.co.uk> wrote:
> >
> > > I've officially marked all my email as read, so thats 3000 emails gone
> > > forever... on the plus side, I should have some time now. I've got a
> > couple
> > > of projects I need to get off my plate so I shall setup my new laptop
> > next
> > > week and sort them out, then I'll get this code base stood back up and
> > > figure out the best place to start.
> > >
> > > Tom
> > >
> > > On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <ma...@apache.org>
> > > wrote:
> > >
> > > > +1 from me Imesha!
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Imesha Sudasingha <im...@apache.org>
> > > > Reply-To: <de...@oodt.apache.org>
> > > > Date: Wednesday, November 11, 2020 at 7:49 AM
> > > > To: dev <de...@oodt.apache.org>
> > > > Subject: Re: OODT 2.0 planning
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > >
> > > >
> > > > This is my suggestion, what if we include both Avro default support
> and
> > > JDK
> > > >
> > > > 11 support for OODT 2.0 as JDK 11 support seems to be critical as
> well.
> > > >
> > > >
> > > >
> > > > What do you think?
> > > >
> > > >
> > > >
> > > > Cheers,
> > > >
> > > > Imesha
> > > >
> > > >
> > > >
> > > > <
> > > >
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> > > > >
> > > >
> > > > Virus-free.
> > > >
> > > > www.avast.com
> > > >
> > > > <
> > > >
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> > > > >
> > > >
> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >
> > > >
> > > >
> > > > On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org>
> > > wrote:
> > > >
> > > >
> > > >
> > > > Hi Sean,
> > > >
> > > >
> > > >
> > > > Regarding docker images, we haven't decided where to push them yet.
> > > Yasith
> > > >
> > > > was the person who contributed to them for his GSoC.
> > > >
> > > >
> > > >
> > > > Hi Yasith,
> > > >
> > > >
> > > >
> > > > Your help is much appreciated and we will definitely need your help
> > > there.
> > > >
> > > > Keep in touch with the mails in this list.
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Imesha
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
> > > >
> > > > wrote:
> > > >
> > > >
> > > >
> > > > Hello all,
> > > >
> > > >
> > > >
> > > > I can make some time to help with the 2.3 release as well.
> > > >
> > > >
> > > >
> > > > Best Regards,
> > > >
> > > > Yasith
> > > >
> > > >
> > > >
> > > > > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
> > > >
> > > > >
> > > >
> > > > >
> > > >
> > > > >> 2.0 – first release where we remove all the Xml-RPC and we change
> > > >
> > > > nothing
> > > >
> > > > >> else. Avro is the default, and only
> > > >
> > > > >> comm option – though interface exists for anyone that wants to
> roll
> > > >
> > > > their
> > > >
> > > > >> own. We change nothing else*
> > > >
> > > > >
> > > >
> > > > > Sounds fine by me. XML-RPC was "fun while it lasted".
> > > >
> > > > >
> > > >
> > > > >>
> > > >
> > > > >> 2.1 – first release with newer JDK support (everyone is asking for
> > > >
> > > > this,
> > > >
> > > > >> and it screws up people like me with
> > > >
> > > > >> new Macs, or computers and newer JDKs by default). We also begin
> > > >
> > > > cleaning
> > > >
> > > > >> up dependencies and removing
> > > >
> > > > >> old ones, and pointing at new stuff.
> > > >
> > > > >
> > > >
> > > > > Oh my glob yes, yes, yes!
> > > >
> > > > >>
> > > >
> > > > >> 2.2 – OpsUi React with GSoC 2019 output.
> > > >
> > > > >
> > > >
> > > > > I can't comment on 2.2 since I've never used it.
> > > >
> > > > >>
> > > >
> > > > >> 2.3 – We integrate, test and demo the Docker builds. We also test
> > and
> > > >
> > > > fully
> > > >
> > > > >> bake the ZK deployments and
> > > >
> > > > >> scaled up Docker.
> > > >
> > > > >
> > > >
> > > > > Are these the images owned by "oodthub" on hub.docker.com?
> > > >
> > > > >
> > > >
> > > > > Take care,
> > > >
> > > > > -SK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > >
> > >
> > > Spicule Limited is registered in England & Wales. Company Number:
> > > 09954122. Registered office: First Floor, Telecom House, 125-135
> Preston
> > > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
> > >
> > >
> > >
> > >
> > > All engagements
> > > are subject to Spicule Terms and Conditions of Business. This email and
> > > its
> > > contents are intended solely for the individual to whom it is addressed
> > > and
> > > may contain information that is confidential, privileged or otherwise
> > > protected from disclosure, distributing or copying. Any views or
> opinions
> > > presented in this email are solely those of the author and do not
> > > necessarily represent those of Spicule Limited. The company accepts no
> > > liability for any damage caused by any virus transmitted by this email.
> > If
> > > you have received this message in error, please notify us immediately
> by
> > > reply email before deleting it from your system. Service of legal
> notice
> > > cannot be effected on Spicule Limited by email.
> > >
> >
>
>
>
>
> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>
>
> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>
Re: OODT 2.0 planning
Posted by Gimhana Nadeeshan <gi...@cse.mrt.ac.lk>.
Hi all,
2. About JDK 11 support, does anybody have any idea on how we can test that
> or what issues do we have when running with JDK 11? I remember Lewis trying
> to run OODT with JDK 10 sometime back [3] [4]
>
As we discussed offline, here I'll put my suggestion regarding OpenJDK 11
migration.
When migrating basically what we have to have to do is
- Update all dependencies to the latest versions.
- Compile the project and resolve all issues related to unofficial
access, split packages and deprecated/removed Java EE modules.
We use the official Oracle JDK 11 migration guide[1] as a head start.
However, we cannot guarantee that we will be able to update all the
dependencies without breaking stuff. Have to try and see!
[1] https://docs.oracle.com/en/java/javase/11/migrate/migration-guide.pdf
Thanks and Regards,
Gimhana
On Thu, 12 Nov 2020 at 13:32, Imesha Sudasingha <im...@apache.org> wrote:
> Great! We have 2 action items then:
>
> 1. Making Avro RPC the default. We once did this for the 1.9 release and
> later reverted due to 1.x backward compatibility issues [1]. Therefore,
> this task can reuse some commits we had there (simply revert [2]).
>
> 2. About JDK 11 support, does anybody have any idea on how we can test that
> or what issues do we have when running with JDK 11? I remember Lewis trying
> to run OODT with JDK 10 sometime back [3] [4]
>
> [1] https://issues.apache.org/jira/browse/OODT-1031
> [2] https://github.com/apache/oodt/pull/116
> [3] https://github.com/apache/oodt/pull/71
> [4] https://issues.apache.org/jira/browse/OODT-990
>
>
> On Wed, 11 Nov 2020 at 22:20, Tom Barber <to...@spicule.co.uk> wrote:
>
> > I've officially marked all my email as read, so thats 3000 emails gone
> > forever... on the plus side, I should have some time now. I've got a
> couple
> > of projects I need to get off my plate so I shall setup my new laptop
> next
> > week and sort them out, then I'll get this code base stood back up and
> > figure out the best place to start.
> >
> > Tom
> >
> > On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <ma...@apache.org>
> > wrote:
> >
> > > +1 from me Imesha!
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Imesha Sudasingha <im...@apache.org>
> > > Reply-To: <de...@oodt.apache.org>
> > > Date: Wednesday, November 11, 2020 at 7:49 AM
> > > To: dev <de...@oodt.apache.org>
> > > Subject: Re: OODT 2.0 planning
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > This is my suggestion, what if we include both Avro default support and
> > JDK
> > >
> > > 11 support for OODT 2.0 as JDK 11 support seems to be critical as well.
> > >
> > >
> > >
> > > What do you think?
> > >
> > >
> > >
> > > Cheers,
> > >
> > > Imesha
> > >
> > >
> > >
> > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> > > >
> > >
> > > Virus-free.
> > >
> > > www.avast.com
> > >
> > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> > > >
> > >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > >
> > >
> > > On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org>
> > wrote:
> > >
> > >
> > >
> > > Hi Sean,
> > >
> > >
> > >
> > > Regarding docker images, we haven't decided where to push them yet.
> > Yasith
> > >
> > > was the person who contributed to them for his GSoC.
> > >
> > >
> > >
> > > Hi Yasith,
> > >
> > >
> > >
> > > Your help is much appreciated and we will definitely need your help
> > there.
> > >
> > > Keep in touch with the mails in this list.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Imesha
> > >
> > >
> > >
> > >
> > >
> > > On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
> > >
> > > wrote:
> > >
> > >
> > >
> > > Hello all,
> > >
> > >
> > >
> > > I can make some time to help with the 2.3 release as well.
> > >
> > >
> > >
> > > Best Regards,
> > >
> > > Yasith
> > >
> > >
> > >
> > > > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
> > >
> > > >
> > >
> > > >
> > >
> > > >> 2.0 – first release where we remove all the Xml-RPC and we change
> > >
> > > nothing
> > >
> > > >> else. Avro is the default, and only
> > >
> > > >> comm option – though interface exists for anyone that wants to roll
> > >
> > > their
> > >
> > > >> own. We change nothing else*
> > >
> > > >
> > >
> > > > Sounds fine by me. XML-RPC was "fun while it lasted".
> > >
> > > >
> > >
> > > >>
> > >
> > > >> 2.1 – first release with newer JDK support (everyone is asking for
> > >
> > > this,
> > >
> > > >> and it screws up people like me with
> > >
> > > >> new Macs, or computers and newer JDKs by default). We also begin
> > >
> > > cleaning
> > >
> > > >> up dependencies and removing
> > >
> > > >> old ones, and pointing at new stuff.
> > >
> > > >
> > >
> > > > Oh my glob yes, yes, yes!
> > >
> > > >>
> > >
> > > >> 2.2 – OpsUi React with GSoC 2019 output.
> > >
> > > >
> > >
> > > > I can't comment on 2.2 since I've never used it.
> > >
> > > >>
> > >
> > > >> 2.3 – We integrate, test and demo the Docker builds. We also test
> and
> > >
> > > fully
> > >
> > > >> bake the ZK deployments and
> > >
> > > >> scaled up Docker.
> > >
> > > >
> > >
> > > > Are these the images owned by "oodthub" on hub.docker.com?
> > >
> > > >
> > >
> > > > Take care,
> > >
> > > > -SK
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> >
> >
> > Spicule Limited is registered in England & Wales. Company Number:
> > 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
> >
> >
> >
> >
> > All engagements
> > are subject to Spicule Terms and Conditions of Business. This email and
> > its
> > contents are intended solely for the individual to whom it is addressed
> > and
> > may contain information that is confidential, privileged or otherwise
> > protected from disclosure, distributing or copying. Any views or opinions
> > presented in this email are solely those of the author and do not
> > necessarily represent those of Spicule Limited. The company accepts no
> > liability for any damage caused by any virus transmitted by this email.
> If
> > you have received this message in error, please notify us immediately by
> > reply email before deleting it from your system. Service of legal notice
> > cannot be effected on Spicule Limited by email.
> >
>
* <http://www.linkedin.com/in/nadeeshangimhana/>*
* <http://www.linkedin.com/in/nadeeshangimhana/>*
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Great! We have 2 action items then:
1. Making Avro RPC the default. We once did this for the 1.9 release and
later reverted due to 1.x backward compatibility issues [1]. Therefore,
this task can reuse some commits we had there (simply revert [2]).
2. About JDK 11 support, does anybody have any idea on how we can test that
or what issues do we have when running with JDK 11? I remember Lewis trying
to run OODT with JDK 10 sometime back [3] [4]
[1] https://issues.apache.org/jira/browse/OODT-1031
[2] https://github.com/apache/oodt/pull/116
[3] https://github.com/apache/oodt/pull/71
[4] https://issues.apache.org/jira/browse/OODT-990
On Wed, 11 Nov 2020 at 22:20, Tom Barber <to...@spicule.co.uk> wrote:
> I've officially marked all my email as read, so thats 3000 emails gone
> forever... on the plus side, I should have some time now. I've got a couple
> of projects I need to get off my plate so I shall setup my new laptop next
> week and sort them out, then I'll get this code base stood back up and
> figure out the best place to start.
>
> Tom
>
> On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <ma...@apache.org>
> wrote:
>
> > +1 from me Imesha!
> >
> >
> >
> >
> >
> >
> >
> > From: Imesha Sudasingha <im...@apache.org>
> > Reply-To: <de...@oodt.apache.org>
> > Date: Wednesday, November 11, 2020 at 7:49 AM
> > To: dev <de...@oodt.apache.org>
> > Subject: Re: OODT 2.0 planning
> >
> >
> >
> > Hi All,
> >
> >
> >
> > This is my suggestion, what if we include both Avro default support and
> JDK
> >
> > 11 support for OODT 2.0 as JDK 11 support seems to be critical as well.
> >
> >
> >
> > What do you think?
> >
> >
> >
> > Cheers,
> >
> > Imesha
> >
> >
> >
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> > >
> >
> > Virus-free.
> >
> > www.avast.com
> >
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> > >
> >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> >
> >
> > On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org>
> wrote:
> >
> >
> >
> > Hi Sean,
> >
> >
> >
> > Regarding docker images, we haven't decided where to push them yet.
> Yasith
> >
> > was the person who contributed to them for his GSoC.
> >
> >
> >
> > Hi Yasith,
> >
> >
> >
> > Your help is much appreciated and we will definitely need your help
> there.
> >
> > Keep in touch with the mails in this list.
> >
> >
> >
> > Thanks,
> >
> > Imesha
> >
> >
> >
> >
> >
> > On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
> >
> > wrote:
> >
> >
> >
> > Hello all,
> >
> >
> >
> > I can make some time to help with the 2.3 release as well.
> >
> >
> >
> > Best Regards,
> >
> > Yasith
> >
> >
> >
> > > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
> >
> > >
> >
> > >
> >
> > >> 2.0 – first release where we remove all the Xml-RPC and we change
> >
> > nothing
> >
> > >> else. Avro is the default, and only
> >
> > >> comm option – though interface exists for anyone that wants to roll
> >
> > their
> >
> > >> own. We change nothing else*
> >
> > >
> >
> > > Sounds fine by me. XML-RPC was "fun while it lasted".
> >
> > >
> >
> > >>
> >
> > >> 2.1 – first release with newer JDK support (everyone is asking for
> >
> > this,
> >
> > >> and it screws up people like me with
> >
> > >> new Macs, or computers and newer JDKs by default). We also begin
> >
> > cleaning
> >
> > >> up dependencies and removing
> >
> > >> old ones, and pointing at new stuff.
> >
> > >
> >
> > > Oh my glob yes, yes, yes!
> >
> > >>
> >
> > >> 2.2 – OpsUi React with GSoC 2019 output.
> >
> > >
> >
> > > I can't comment on 2.2 since I've never used it.
> >
> > >>
> >
> > >> 2.3 – We integrate, test and demo the Docker builds. We also test and
> >
> > fully
> >
> > >> bake the ZK deployments and
> >
> > >> scaled up Docker.
> >
> > >
> >
> > > Are these the images owned by "oodthub" on hub.docker.com?
> >
> > >
> >
> > > Take care,
> >
> > > -SK
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>
Re: OODT 2.0 planning
Posted by Tom Barber <to...@spicule.co.uk>.
I've officially marked all my email as read, so thats 3000 emails gone
forever... on the plus side, I should have some time now. I've got a couple
of projects I need to get off my plate so I shall setup my new laptop next
week and sort them out, then I'll get this code base stood back up and
figure out the best place to start.
Tom
On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann <ma...@apache.org> wrote:
> +1 from me Imesha!
>
>
>
>
>
>
>
> From: Imesha Sudasingha <im...@apache.org>
> Reply-To: <de...@oodt.apache.org>
> Date: Wednesday, November 11, 2020 at 7:49 AM
> To: dev <de...@oodt.apache.org>
> Subject: Re: OODT 2.0 planning
>
>
>
> Hi All,
>
>
>
> This is my suggestion, what if we include both Avro default support and JDK
>
> 11 support for OODT 2.0 as JDK 11 support seems to be critical as well.
>
>
>
> What do you think?
>
>
>
> Cheers,
>
> Imesha
>
>
>
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> >
>
> Virus-free.
>
> www.avast.com
>
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> >
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
>
> On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org> wrote:
>
>
>
> Hi Sean,
>
>
>
> Regarding docker images, we haven't decided where to push them yet. Yasith
>
> was the person who contributed to them for his GSoC.
>
>
>
> Hi Yasith,
>
>
>
> Your help is much appreciated and we will definitely need your help there.
>
> Keep in touch with the mails in this list.
>
>
>
> Thanks,
>
> Imesha
>
>
>
>
>
> On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
>
> wrote:
>
>
>
> Hello all,
>
>
>
> I can make some time to help with the 2.3 release as well.
>
>
>
> Best Regards,
>
> Yasith
>
>
>
> > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
>
> >
>
> >
>
> >> 2.0 – first release where we remove all the Xml-RPC and we change
>
> nothing
>
> >> else. Avro is the default, and only
>
> >> comm option – though interface exists for anyone that wants to roll
>
> their
>
> >> own. We change nothing else*
>
> >
>
> > Sounds fine by me. XML-RPC was "fun while it lasted".
>
> >
>
> >>
>
> >> 2.1 – first release with newer JDK support (everyone is asking for
>
> this,
>
> >> and it screws up people like me with
>
> >> new Macs, or computers and newer JDKs by default). We also begin
>
> cleaning
>
> >> up dependencies and removing
>
> >> old ones, and pointing at new stuff.
>
> >
>
> > Oh my glob yes, yes, yes!
>
> >>
>
> >> 2.2 – OpsUi React with GSoC 2019 output.
>
> >
>
> > I can't comment on 2.2 since I've never used it.
>
> >>
>
> >> 2.3 – We integrate, test and demo the Docker builds. We also test and
>
> fully
>
> >> bake the ZK deployments and
>
> >> scaled up Docker.
>
> >
>
> > Are these the images owned by "oodthub" on hub.docker.com?
>
> >
>
> > Take care,
>
> > -SK
>
>
>
>
>
>
>
>
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Chris Mattmann <ma...@apache.org>.
+1 from me Imesha!
From: Imesha Sudasingha <im...@apache.org>
Reply-To: <de...@oodt.apache.org>
Date: Wednesday, November 11, 2020 at 7:49 AM
To: dev <de...@oodt.apache.org>
Subject: Re: OODT 2.0 planning
Hi All,
This is my suggestion, what if we include both Avro default support and JDK
11 support for OODT 2.0 as JDK 11 support seems to be critical as well.
What do you think?
Cheers,
Imesha
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org> wrote:
Hi Sean,
Regarding docker images, we haven't decided where to push them yet. Yasith
was the person who contributed to them for his GSoC.
Hi Yasith,
Your help is much appreciated and we will definitely need your help there.
Keep in touch with the mails in this list.
Thanks,
Imesha
On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
wrote:
Hello all,
I can make some time to help with the 2.3 release as well.
Best Regards,
Yasith
> On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
>
>
>> 2.0 – first release where we remove all the Xml-RPC and we change
nothing
>> else. Avro is the default, and only
>> comm option – though interface exists for anyone that wants to roll
their
>> own. We change nothing else*
>
> Sounds fine by me. XML-RPC was "fun while it lasted".
>
>>
>> 2.1 – first release with newer JDK support (everyone is asking for
this,
>> and it screws up people like me with
>> new Macs, or computers and newer JDKs by default). We also begin
cleaning
>> up dependencies and removing
>> old ones, and pointing at new stuff.
>
> Oh my glob yes, yes, yes!
>>
>> 2.2 – OpsUi React with GSoC 2019 output.
>
> I can't comment on 2.2 since I've never used it.
>>
>> 2.3 – We integrate, test and demo the Docker builds. We also test and
fully
>> bake the ZK deployments and
>> scaled up Docker.
>
> Are these the images owned by "oodthub" on hub.docker.com?
>
> Take care,
> -SK
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Hi All,
This is my suggestion, what if we include both Avro default support and JDK
11 support for OODT 2.0 as JDK 11 support seems to be critical as well.
What do you think?
Cheers,
Imesha
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, 5 Nov 2020 at 14:42, Imesha Sudasingha <im...@apache.org> wrote:
> Hi Sean,
>
> Regarding docker images, we haven't decided where to push them yet. Yasith
> was the person who contributed to them for his GSoC.
>
> Hi Yasith,
>
> Your help is much appreciated and we will definitely need your help there.
> Keep in touch with the mails in this list.
>
> Thanks,
> Imesha
>
>
> On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu>
> wrote:
>
>> Hello all,
>>
>> I can make some time to help with the 2.3 release as well.
>>
>> Best Regards,
>> Yasith
>>
>> > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
>> >
>> >
>> >> 2.0 – first release where we remove all the Xml-RPC and we change
>> nothing
>> >> else. Avro is the default, and only
>> >> comm option – though interface exists for anyone that wants to roll
>> their
>> >> own. We change nothing else*
>> >
>> > Sounds fine by me. XML-RPC was "fun while it lasted".
>> >
>> >>
>> >> 2.1 – first release with newer JDK support (everyone is asking for
>> this,
>> >> and it screws up people like me with
>> >> new Macs, or computers and newer JDKs by default). We also begin
>> cleaning
>> >> up dependencies and removing
>> >> old ones, and pointing at new stuff.
>> >
>> > Oh my glob yes, yes, yes!
>> >>
>> >> 2.2 – OpsUi React with GSoC 2019 output.
>> >
>> > I can't comment on 2.2 since I've never used it.
>> >>
>> >> 2.3 – We integrate, test and demo the Docker builds. We also test and
>> fully
>> >> bake the ZK deployments and
>> >> scaled up Docker.
>> >
>> > Are these the images owned by "oodthub" on hub.docker.com?
>> >
>> > Take care,
>> > -SK
>>
>
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Hi Sean,
Regarding docker images, we haven't decided where to push them yet. Yasith
was the person who contributed to them for his GSoC.
Hi Yasith,
Your help is much appreciated and we will definitely need your help there.
Keep in touch with the mails in this list.
Thanks,
Imesha
On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith <ya...@cs.odu.edu> wrote:
> Hello all,
>
> I can make some time to help with the 2.3 release as well.
>
> Best Regards,
> Yasith
>
> > On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
> >
> >
> >> 2.0 – first release where we remove all the Xml-RPC and we change
> nothing
> >> else. Avro is the default, and only
> >> comm option – though interface exists for anyone that wants to roll
> their
> >> own. We change nothing else*
> >
> > Sounds fine by me. XML-RPC was "fun while it lasted".
> >
> >>
> >> 2.1 – first release with newer JDK support (everyone is asking for this,
> >> and it screws up people like me with
> >> new Macs, or computers and newer JDKs by default). We also begin
> cleaning
> >> up dependencies and removing
> >> old ones, and pointing at new stuff.
> >
> > Oh my glob yes, yes, yes!
> >>
> >> 2.2 – OpsUi React with GSoC 2019 output.
> >
> > I can't comment on 2.2 since I've never used it.
> >>
> >> 2.3 – We integrate, test and demo the Docker builds. We also test and
> fully
> >> bake the ZK deployments and
> >> scaled up Docker.
> >
> > Are these the images owned by "oodthub" on hub.docker.com?
> >
> > Take care,
> > -SK
>
Re: OODT 2.0 planning
Posted by "Jayawardana, Yasith" <ya...@cs.odu.edu>.
Hello all,
I can make some time to help with the 2.3 release as well.
Best Regards,
Yasith
> On Nov 3, 2020, at 10:23 AM, Sean Kelly <ke...@apache.org> wrote:
>
>
>> 2.0 – first release where we remove all the Xml-RPC and we change nothing
>> else. Avro is the default, and only
>> comm option – though interface exists for anyone that wants to roll their
>> own. We change nothing else*
>
> Sounds fine by me. XML-RPC was "fun while it lasted".
>
>>
>> 2.1 – first release with newer JDK support (everyone is asking for this,
>> and it screws up people like me with
>> new Macs, or computers and newer JDKs by default). We also begin cleaning
>> up dependencies and removing
>> old ones, and pointing at new stuff.
>
> Oh my glob yes, yes, yes!
>>
>> 2.2 – OpsUi React with GSoC 2019 output.
>
> I can't comment on 2.2 since I've never used it.
>>
>> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
>> bake the ZK deployments and
>> scaled up Docker.
>
> Are these the images owned by "oodthub" on hub.docker.com?
>
> Take care,
> -SK
Re: OODT 2.0 planning
Posted by Sean Kelly <ke...@apache.org>.
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
> else. Avro is the default, and only
> comm option – though interface exists for anyone that wants to roll their
> own. We change nothing else*
Sounds fine by me. XML-RPC was "fun while it lasted".
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
> and it screws up people like me with
> new Macs, or computers and newer JDKs by default). We also begin cleaning
> up dependencies and removing
> old ones, and pointing at new stuff.
Oh my glob yes, yes, yes!
>
> 2.2 – OpsUi React with GSoC 2019 output.
I can't comment on 2.2 since I've never used it.
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and
> fully
> bake the ZK deployments and
> scaled up Docker.
Are these the images owned by "oodthub" on hub.docker.com?
Take care,
-SK
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Great. I had a discussion with Gimhana, who was the GSoC 2019 student and
contributed to developing the React based new OpsUI. He will also be able
to help us with this.
On Mon, 2 Nov 2020 at 07:06, Chris Mattmann <ma...@apache.org> wrote:
> +1 from me
>
>
>
>
>
>
>
> From: Imesha Sudasingha <im...@apache.org>
> Reply-To: <de...@oodt.apache.org>
> Date: Thursday, October 29, 2020 at 6:56 PM
> To: dev <de...@oodt.apache.org>
> Subject: Re: OODT 2.0 planning
>
>
>
> Hi All,
>
>
>
> This is an old thread where we discussed the plan for next releases. In
>
> summary, following was the plan:
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
>
> else. Avro is the default, and only
>
> comm option – though interface exists for anyone that wants to roll their
>
> own. We change nothing else*
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
>
> and it screws up people like me with
>
> new Macs, or computers and newer JDKs by default). We also begin cleaning
>
> up dependencies and removing
>
> old ones, and pointing at new stuff.
>
>
>
> 2.2 – OpsUi React with GSoC 2019 output.
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
>
> bake the ZK deployments and
>
> scaled up Docker.
>
>
>
> Any changes/suggestions to the above plan?
>
> What if we release the OpsUI ahead of others?
>
>
>
> Thanks,
>
> Imesha
>
>
>
> On Sun, 6 Oct 2019 at 06:20, Tom Barber <to...@spicule.co.uk> wrote:
>
>
>
> Sounds good to me. Should also increase the release cadence as well.
>
>
>
>
>
> On 5 October 2019 at 09:06:35, Chris Mattmann (mattmann@apache.org) wrote:
>
>
>
> Here is my suggested Roadmap here:
>
>
>
>
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
>
> else. Avro is the default, and only
>
> comm option – though interface exists for anyone that wants to roll their
>
> own. We change nothing else*
>
>
>
>
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
>
> and it screws up people like me with
>
> new Macs, or computers and newer JDKs by default). We also begin cleaning
>
> up dependencies and removing
>
> old ones, and pointing at new stuff.
>
>
>
>
>
>
>
> 2.2 – OpsUi React with Breno’s stuff.
>
>
>
>
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
>
> bake the ZK deployments and
>
> scaled up Docker.
>
>
>
>
>
>
>
> 2.4+ … who knows
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Tom Barber <to...@spicule.co.uk>
>
> Reply-To: <de...@oodt.apache.org>
>
> Date: Saturday, October 5, 2019 at 3:31 AM
>
> To: <de...@oodt.apache.org>, Imesha Sudasingha <im...@apache.org>
>
> Subject: Re: OODT 2.0 planning
>
>
>
>
>
>
>
> On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org)
>
> wrote:
>
>
>
>
>
>
>
> I think there was a plan to
>
>
>
> remove XML rpc support completely and use avro only in 2.0.
>
>
>
>
>
>
>
>
>
>
>
> That is true. XMLRPC needs to die.
>
>
>
>
>
>
>
> Not sure about Knative, but certainly a Kubernetes operator would be
>
>
>
> something interesting to look at if we could.
>
>
>
>
>
>
>
> --
>
>
>
>
>
>
>
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
>
>
>
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
>
>
>
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> All engagements
>
>
>
> are subject to Spicule Terms and Conditions of Business. This email and its
>
>
>
> contents are intended solely for the individual to whom it is addressed and
>
>
>
> may contain information that is confidential, privileged or otherwise
>
>
>
> protected from disclosure, distributing or copying. Any views or opinions
>
>
>
> presented in this email are solely those of the author and do not
>
>
>
> necessarily represent those of Spicule Limited. The company accepts no
>
>
>
> liability for any damage caused by any virus transmitted by this email. If
>
>
>
> you have received this message in error, please notify us immediately by
>
>
>
> reply email before deleting it from your system. Service of legal notice
>
>
>
> cannot be effected on Spicule Limited by email.
>
>
>
> --
>
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
>
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
>
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
>
>
>
>
>
> All engagements
>
> are subject to Spicule Terms and Conditions of Business. This email and
>
> its
>
> contents are intended solely for the individual to whom it is addressed
>
> and
>
> may contain information that is confidential, privileged or otherwise
>
> protected from disclosure, distributing or copying. Any views or opinions
>
> presented in this email are solely those of the author and do not
>
> necessarily represent those of Spicule Limited. The company accepts no
>
> liability for any damage caused by any virus transmitted by this email. If
>
> you have received this message in error, please notify us immediately by
>
> reply email before deleting it from your system. Service of legal notice
>
> cannot be effected on Spicule Limited by email.
>
>
>
>
>
>
Re: OODT 2.0 planning
Posted by Chris Mattmann <ma...@apache.org>.
+1 from me
From: Imesha Sudasingha <im...@apache.org>
Reply-To: <de...@oodt.apache.org>
Date: Thursday, October 29, 2020 at 6:56 PM
To: dev <de...@oodt.apache.org>
Subject: Re: OODT 2.0 planning
Hi All,
This is an old thread where we discussed the plan for next releases. In
summary, following was the plan:
2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their
own. We change nothing else*
2.1 – first release with newer JDK support (everyone is asking for this,
and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning
up dependencies and removing
old ones, and pointing at new stuff.
2.2 – OpsUi React with GSoC 2019 output.
2.3 – We integrate, test and demo the Docker builds. We also test and fully
bake the ZK deployments and
scaled up Docker.
Any changes/suggestions to the above plan?
What if we release the OpsUI ahead of others?
Thanks,
Imesha
On Sun, 6 Oct 2019 at 06:20, Tom Barber <to...@spicule.co.uk> wrote:
Sounds good to me. Should also increase the release cadence as well.
On 5 October 2019 at 09:06:35, Chris Mattmann (mattmann@apache.org) wrote:
Here is my suggested Roadmap here:
2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their
own. We change nothing else*
2.1 – first release with newer JDK support (everyone is asking for this,
and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning
up dependencies and removing
old ones, and pointing at new stuff.
2.2 – OpsUi React with Breno’s stuff.
2.3 – We integrate, test and demo the Docker builds. We also test and fully
bake the ZK deployments and
scaled up Docker.
2.4+ … who knows
From: Tom Barber <to...@spicule.co.uk>
Reply-To: <de...@oodt.apache.org>
Date: Saturday, October 5, 2019 at 3:31 AM
To: <de...@oodt.apache.org>, Imesha Sudasingha <im...@apache.org>
Subject: Re: OODT 2.0 planning
On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org)
wrote:
I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
That is true. XMLRPC needs to die.
Not sure about Knative, but certainly a Kubernetes operator would be
something interesting to look at if we could.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and
its
contents are intended solely for the individual to whom it is addressed
and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Hi All,
This is an old thread where we discussed the plan for next releases. In
summary, following was the plan:
2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their
own. We change nothing else*
2.1 – first release with newer JDK support (everyone is asking for this,
and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning
up dependencies and removing
old ones, and pointing at new stuff.
2.2 – OpsUi React with GSoC 2019 output.
2.3 – We integrate, test and demo the Docker builds. We also test and fully
bake the ZK deployments and
scaled up Docker.
Any changes/suggestions to the above plan?
What if we release the OpsUI ahead of others?
Thanks,
Imesha
On Sun, 6 Oct 2019 at 06:20, Tom Barber <to...@spicule.co.uk> wrote:
> Sounds good to me. Should also increase the release cadence as well.
>
>
> On 5 October 2019 at 09:06:35, Chris Mattmann (mattmann@apache.org) wrote:
>
> Here is my suggested Roadmap here:
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
> else. Avro is the default, and only
> comm option – though interface exists for anyone that wants to roll their
> own. We change nothing else*
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
> and it screws up people like me with
> new Macs, or computers and newer JDKs by default). We also begin cleaning
> up dependencies and removing
> old ones, and pointing at new stuff.
>
>
>
> 2.2 – OpsUi React with Breno’s stuff.
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
> bake the ZK deployments and
> scaled up Docker.
>
>
>
> 2.4+ … who knows
>
>
>
>
>
>
>
> From: Tom Barber <to...@spicule.co.uk>
> Reply-To: <de...@oodt.apache.org>
> Date: Saturday, October 5, 2019 at 3:31 AM
> To: <de...@oodt.apache.org>, Imesha Sudasingha <im...@apache.org>
> Subject: Re: OODT 2.0 planning
>
>
>
> On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org)
> wrote:
>
>
>
> I think there was a plan to
>
> remove XML rpc support completely and use avro only in 2.0.
>
>
>
>
>
> That is true. XMLRPC needs to die.
>
>
>
> Not sure about Knative, but certainly a Kubernetes operator would be
>
> something interesting to look at if we could.
>
>
>
> --
>
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
>
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
>
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
>
>
>
>
>
> All engagements
>
> are subject to Spicule Terms and Conditions of Business. This email and its
>
> contents are intended solely for the individual to whom it is addressed and
>
> may contain information that is confidential, privileged or otherwise
>
> protected from disclosure, distributing or copying. Any views or opinions
>
> presented in this email are solely those of the author and do not
>
> necessarily represent those of Spicule Limited. The company accepts no
>
> liability for any damage caused by any virus transmitted by this email. If
>
> you have received this message in error, please notify us immediately by
>
> reply email before deleting it from your system. Service of legal notice
>
> cannot be effected on Spicule Limited by email.
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>
Re: OODT 2.0 planning
Posted by Tom Barber <to...@spicule.co.uk>.
Sounds good to me. Should also increase the release cadence as well.
On 5 October 2019 at 09:06:35, Chris Mattmann (mattmann@apache.org) wrote:
Here is my suggested Roadmap here:
2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their
own. We change nothing else*
2.1 – first release with newer JDK support (everyone is asking for this,
and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning
up dependencies and removing
old ones, and pointing at new stuff.
2.2 – OpsUi React with Breno’s stuff.
2.3 – We integrate, test and demo the Docker builds. We also test and fully
bake the ZK deployments and
scaled up Docker.
2.4+ … who knows
From: Tom Barber <to...@spicule.co.uk>
Reply-To: <de...@oodt.apache.org>
Date: Saturday, October 5, 2019 at 3:31 AM
To: <de...@oodt.apache.org>, Imesha Sudasingha <im...@apache.org>
Subject: Re: OODT 2.0 planning
On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org) wrote:
I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
That is true. XMLRPC needs to die.
Not sure about Knative, but certainly a Kubernetes operator would be
something interesting to look at if we could.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Chris Mattmann <ma...@apache.org>.
Here is my suggested Roadmap here:
2.0 – first release where we remove all the Xml-RPC and we change nothing else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their own. We change nothing else*
2.1 – first release with newer JDK support (everyone is asking for this, and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning up dependencies and removing
old ones, and pointing at new stuff.
2.2 – OpsUi React with Breno’s stuff.
2.3 – We integrate, test and demo the Docker builds. We also test and fully bake the ZK deployments and
scaled up Docker.
2.4+ … who knows
From: Tom Barber <to...@spicule.co.uk>
Reply-To: <de...@oodt.apache.org>
Date: Saturday, October 5, 2019 at 3:31 AM
To: <de...@oodt.apache.org>, Imesha Sudasingha <im...@apache.org>
Subject: Re: OODT 2.0 planning
On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org) wrote:
I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
That is true. XMLRPC needs to die.
Not sure about Knative, but certainly a Kubernetes operator would be
something interesting to look at if we could.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Tom Barber <to...@spicule.co.uk>.
On 5 October 2019 at 11:25:41, Imesha Sudasingha (imesha@apache.org) wrote:
I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
That is true. XMLRPC needs to die.
Not sure about Knative, but certainly a Kubernetes operator would be
something interesting to look at if we could.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Posted by Imesha Sudasingha <im...@apache.org>.
Hi Tom,
Yes. That's pretty much all we planned for 2.0. I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
May be in 2.x something, we can see the possibility of your knative
suggestion and a more advanced kubernetes support?
Imesha
On Sat, 5 Oct 2019 at 15:13, Tom Barber <to...@spicule.co.uk> wrote:
> Alrighty with 1.9 shipped we can now look at 2.0 with all new fun stuff.
> I’ve probably forgotten some bits and pieces but here’s my wish list:
>
> React components and Breno’s wrapper for OpsUI and improved custom web app
> embedding
> Updating lots of old dependencies to more current stuff.
> Newer JDK support.
> Test and document and demo the docker builds.
> ZK stuff for distributed Filemanager deployments or scaled up docker
> deployments
>
> What have I forgotten?
>
> Tom
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>