FW: [EXTERNAL] DRAT 1.0 RC2 warnings
So I think this is actually an OODT bug, sending to OODT and CC to DRAT.
so @imesha i think the issue is here
9:55 PM
you actually don’t allow override of the client factory at runtime since at
this line in RpcCommFactory for workflow
9:55 PM
https://github.com/apache/oodt/blob/master/workflow/src/main/java/org/apache/oodt/cas/workflow/system/rpc/RpcCommunicationFactory.java#L41
workflow/src/main/java/org/apache/oodt/cas/workflow/system/rpc/RpcCommunicationFactory.java:41
InputStream prpFileStream =
RpcCommunicationFactory.class.getResourceAsStream("/workflow.properties");
apache/oodt | Added by GitHub
9:55 PM
you force it to load /workflow.properties which is shipped with the JAR
9:55 PM
you can’t override it
9:57 PM
same goes for resource
9:58 PM
you can’t actually override it b/c you load and force the one shipped with the
JAR
Let me know what you think. I think we need to make the client code in OODT
workflow and resmgr look like the filemgr
client code so that we can actually override it at runtime and not just pick
the version that shipped with the JAR.
Thoughts?
I think we may need a 1.9.1 for this…
Cheers,
Chris
From: Chris Mattmann
Reply-To: "d...@drat.apache.org"
Date: Saturday, October 5, 2019 at 9:45 PM
To: "d...@drat.apache.org"
Subject: [EXTERNAL] DRAT 1.0 RC2 warnings
Team,
One thing I noticed about DRAT 1.0 RC2 after upgrading to OODT 1.9. By default
XmlRpc is
available, but the behavior of certain functions have changed where we were
creating the
clients for FM and WM and RM – by default we get Avro ones back now. We should
be able
to control this via system properties, for example the following 3 properties
should fix this
problem in $TOMCAT/conf/catalina.properties (but they only fix it for FM
client). Any ideas,
Imesha?
# OODT Avro stuff
filemgr.client=org.apache.oodt.cas.filemgr.system.rpc.XmlRpcFileManagerClientFactory
workflow.client.factory=org.apache.oodt.cas.workflow.system.rpc.XmlRpcWorkflowManagerFactory
resmgr.manager.client=org.apache.oodt.cas.resource.system.XmlRpcResourceManagerClient
That fixes the FM client, but the web apps in DRAT’s OPSUI are still creating
the Avro versions of
workflow manager client and resource client. What am I doing wrong here?
Cheers,
Chris
Re: OODT 2.0 planning
Sounds good to me. Should also increase the release cadence as well. On 5 October 2019 at 09:06:35, Chris Mattmann (mattm...@apache.org) wrote: Here is my suggested Roadmap here: 2.0 – first release where we remove all the Xml-RPC and we change nothing else. Avro is the default, and only comm option – though interface exists for anyone that wants to roll their own. We change nothing else* 2.1 – first release with newer JDK support (everyone is asking for this, and it screws up people like me with new Macs, or computers and newer JDKs by default). We also begin cleaning up dependencies and removing old ones, and pointing at new stuff. 2.2 – OpsUi React with Breno’s stuff. 2.3 – We integrate, test and demo the Docker builds. We also test and fully bake the ZK deployments and scaled up Docker. 2.4+ … who knows From: Tom Barber Reply-To: Date: Saturday, October 5, 2019 at 3:31 AM To: , Imesha Sudasingha Subject: Re: OODT 2.0 planning On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org) wrote: I think there was a plan to remove XML rpc support completely and use avro only in 2.0. That is true. XMLRPC needs to die. Not sure about Knative, but certainly a Kubernetes operator would be something interesting to look at if we could. -- Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891. All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email. -- Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891. All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.
Re: OODT 2.0 planning
Here is my suggested Roadmap here: 2.0 – first release where we remove all the Xml-RPC and we change nothing else. Avro is the default, and only comm option – though interface exists for anyone that wants to roll their own. We change nothing else* 2.1 – first release with newer JDK support (everyone is asking for this, and it screws up people like me with new Macs, or computers and newer JDKs by default). We also begin cleaning up dependencies and removing old ones, and pointing at new stuff. 2.2 – OpsUi React with Breno’s stuff. 2.3 – We integrate, test and demo the Docker builds. We also test and fully bake the ZK deployments and scaled up Docker. 2.4+ … who knows From: Tom Barber Reply-To: Date: Saturday, October 5, 2019 at 3:31 AM To: , Imesha Sudasingha Subject: Re: OODT 2.0 planning On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org) wrote: I think there was a plan to remove XML rpc support completely and use avro only in 2.0. That is true. XMLRPC needs to die. Not sure about Knative, but certainly a Kubernetes operator would be something interesting to look at if we could. -- Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891. All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.
