[ZOO-PSC] ZOO-Project 2.0.0 release

Tue Feb 13 09:43:57 PST 2024

+1
Maria

Inviato da Outlook per Android<https://aka.ms/AAb9ysg>
________________________________
From: ZOO-PSC <zoo-psc-bounces at lists.osgeo.org> on behalf of Angelos Tzotsos via ZOO-PSC <zoo-psc at lists.osgeo.org>
Sent: Tuesday, February 13, 2024 6:09:27 PM
To: Gérald Fenoy <gerald.fenoy at geolabs.fr>
Cc: zoo-psc <zoo-psc at lists.osgeo.org>
Subject: Re: [ZOO-PSC] ZOO-Project 2.0.0 release

+1
Angelos

On Tue, Feb 13, 2024 at 7:08 PM Gérald Fenoy via ZOO-PSC <zoo-psc at lists.osgeo.org<mailto:zoo-psc at lists.osgeo.org>> wrote:
Dear PSC members,
I intend to request your support in voting to release the ZOO-Project's 2.0.0 release candidate version.

There were some years since the last release.
Also, we need to renew the OGC-certified compliance license(s) for the ZOO-Project product on February 19.

So, I think it is perfect timing to release a new version and get it certified.

We tested on a local setup and the ZOO-Project passed 100% of the tests for both OGC API - Processes - Part 1: Core and synchronous WPS 2.0.

Below, you can see a list of significant modifications:

  * Update relation type to monitor for the status location.
  * Add support for the conformance class remote processes from the
  OGC API - Processes - Part 3: Workflow & chaining. Execution of
  remote processes are automatically run asynchronously in case the
  root process was invoked asynchronously.
  * Parse the Location header from ulinet and the cookie if any.
  * Add schemas to the components and support description stored in the file.
  * Add a trivial DeployOnHpc service for automating the installation
  and the deployment of a singularity container using the image
  parameter provided in the executionUnit used when deploying the
  process.
  * Set the key json_response_object with the JSON response that the
  ZOO-Kernel produced for the request, it can be updated from a
  filter_out process.
  * Update filter_in to support returning a response directly by
  adding a response key in the lenv section (binary is supported for
  this response)
  * Provide an initial Dockefile dedicated to the DRU support with
  remote HPC execution support
  * Add a USE_HPC_NESTEDOUTPUTS build option to activate the nested
  inputs and outputs addition (not supported with OGC API - Processes
  - Part 1: Core)
  * Update C-API errorException and printExceptionResponse* signatures
  to handle the main configuration maps memory properly
  *  Build Docker image with DRU supporting OpenEO UDP encoding
  * Add support for deploying and executing OpenEO User Defined
  Processes by using an OpenEO graph for the executionUnit
  * Add support for schema type string for request body, providing a
  way to include CWL example files in the published OpenAPI
  * Integrate the OGC API - Processes - Part 2: Deploy, Replace,
  Undeploy optional support.
  * Build Docker image based on MDL4EO/OTBTF and the onnx runtime for
  models sharing
  * Integrate the TeamEngine and ETS for OGC API - Processes
  * Add JWT parser in security_service.py as filter_in to allocate
  resources per authenticated user
  * Integrate the work done during GSoC 2022 to support Node.js
  ZOO-Services (cf. updated documentation for NodeJS)
  * Update support to filter the jobs list using the user_id
  * Add support for nested processes n OGC API - Processes - Part 3:
  Workflows & Chaining
  * Add filter_in and filter_out service array to be invoked previously
  of and after the service run
  * Add trivial support for OpenAPI security, basicAuth / openId, and add
  sample services implementation
  * Add support for MapServer 8.0 (actually 7.7-dev), including
  returning result as OGC API -Features
  * Integrate downloading MapServer 8.0 and building from the
  dedicated Dockerfile-MS8
  * Include basicAuth build instructions in the Dockefile
  * Add basicAuth service illustrating how to secure access to OGC API
  - Processes using Basic Authentication
  * Use the osecurity section to detect secured path, request method
  from the published OpenAPI
  * Update the printHeaders function to allow Status definition at runtime
  * Add a [osecurity] section to secure access to path, method couple
  from the published OpenAPI
  * Update the database connection handling to make it independent from
  instantiation order
  * Use the RabbitMQ also for OGC API - Processes
  * Pass the subscriber if any is passed from the original request
  * Make C OGR base-vect-ops compatible with memory=protect
  * Add volumes to be shared by the ZOO-Kernel and the ZOO-FPM
  * Add a RabbitMQ and a ZOO-FPM container to docker-compose
  * Add documentation for RabbitMQ support and ZOO Fast Process
  Manager (ZOO-FPM)
  * Optional use of ZOO-Kernel Fast Process Manager backends to handle
  asynchronous execution
  * Partial integration of the code from the
  Publicamundi_David_integration01-devel branch

I propose myself as a release manager, and the release is to occur this coming Saturday (2024/02/17).

My vote is +1 for this release to happen as proposed.

Best regards,

Gerald Fenoy
gerald.fenoy at geolabs.fr<mailto:gerald.fenoy at geolabs.fr>
Chair, ZOO-Project PSC

_______________________________________________
ZOO-PSC mailing list
ZOO-PSC at lists.osgeo.org<mailto:ZOO-PSC at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/zoo-psc

--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-psc/attachments/20240213/188fe451/attachment-0001.htm>