Hey Val, Yep it’s already there hidden away in the client layers and server layers. You won’t have to change your server or client apps. One thing though is that you can’t use a pre 2.x server with a client, and vice versa. 1.9 will still support both.
I’ll make sure to test/work on docs, etc. I am using OODT with DRAT (now a top level Apache project, check it out: http://github.com/apache/drat) and so will be motivated to make this all work and document it. Help in doing so is welcomed ( Cheers, Chris On 10/12/17, 10:52 AM, "Mallder, Valerie" <valerie.mall...@jhuapl.edu> wrote: Hey Folks, Will you be providing new workflow, filemgr, resource, etc applications that are all avro-based? Val -----Original Message----- From: Chris Mattmann [mailto:mattm...@apache.org] Sent: Thursday, October 12, 2017 1:33 PM To: dev@oodt.apache.org Subject: Stable Development/2.0 branch and Plan Hey Folks, Thanks to the amazing work from Imesha and some of my own work on the development: branch, we now have a merged ZK feature and Avro RPC feature branch stabilized, and building fine: [INFO] OODT Core .......................................... SUCCESS [ 2.089 s] [INFO] Common Utilities ................................... SUCCESS [ 23.410 s] [INFO] CAS Command Line Interface ......................... SUCCESS [ 8.908 s] [INFO] OODT - Configuration Management .................... SUCCESS [ 24.494 s] [INFO] Process Control System Input Data Package .......... SUCCESS [ 1.604 s] [INFO] Catalog and Archive Service Generic Multi-valued Metadata Container SUCCESS [ 2.893 s] [INFO] Catalog and Archive File Management Component ...... SUCCESS [03:17 min] [INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 19.712 s] [INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 34.483 s] [INFO] Catalog and Archive Crawling Framework ............. SUCCESS [ 28.783 s] [INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [ 1.913 s] [INFO] CAS Curation Web Services .......................... SUCCESS [ 10.401 s] [INFO] Process Control System Core Package ................ SUCCESS [ 19.273 s] [INFO] OODT Wicket Web Components ......................... SUCCESS [ 4.770 s] [INFO] CAS Curation Interface ............................. SUCCESS [ 10.254 s] [INFO] CAS PGE Adaptor Framework .......................... SUCCESS [ 22.754 s] [INFO] CAS Installer Maven Mojo ........................... SUCCESS [ 3.097 s] [INFO] OODT :: Archetypes :: OpsUI ........................ SUCCESS [ 1.194 s] [INFO] OODT :: Archetypes :: RADiX ........................ SUCCESS [ 1.341 s] [INFO] OODT :: Archetypes ................................. SUCCESS [ 0.033 s] [INFO] CAS File Manager Browser Web App ................... SUCCESS [ 8.492 s] [INFO] CAS Workflow Manager Monitor Web App ............... SUCCESS [ 5.006 s] [INFO] CAS Product Server Web Application ................. SUCCESS [ 13.420 s] [INFO] CAS Workflow REST Services ......................... SUCCESS [ 4.638 s] [INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 19.873 s] [INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [ 8.082 s] [INFO] Apache OODT ........................................ SUCCESS [ 0.040 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 07:58 min [INFO] Finished at: 2017-10-12T10:28:04-07:00 [INFO] Final Memory: 123M/1584M [INFO] ------------------------------------------------------------------------ nonas:oodt mattmann$ git push -u origin development Great work in OODT-963 and OODT-964 wrapped this up. My proposal: 1. I am going to merge development into master: 2. Let’s make an OODT 1.9 release that will be the last release in the 1.x series, which includes XML-RPC (optionally), but also gives you the AvroRPC the recommended solution (along with ZK and distributed config) 3. After 1.9, we change the version in master: to 2.0-dev, and then in 2.0-dev we remove XML-RPC, and fix any breaks. Then we release 2.0 with only AvroRPC as the default. I will execute step one of this plan in the next few minutes. Feedback is welcomed! Cheers Chris
