<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Dear PSC members,<br>I intend to request your support in voting to release the ZOO-Project's 2.0.0 release candidate version.<div><br></div><div>There were some years since the last release. </div><div>Also, we need to renew the <span style="font-family: Trebuchet, sans-serif;">OGC-certified compliance license(s) for the ZOO-Project product on February 19. </span></div><div><span style="font-family: Trebuchet, sans-serif;"><br></span></div><div><span style="font-family: Trebuchet, sans-serif;">So, I think it is perfect timing to release a new version and get it certified.</span></div><div><span style="font-family: Trebuchet, sans-serif;"><br></span></div><div><span style="font-family: Trebuchet, sans-serif;">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.</span></div><div><br></div><div>Below, you can see a list of significant modifications:<br><br><div> * Update relation type to monitor for the status location.</div><div> * Add support for the conformance class remote processes from the</div><div> OGC API - Processes - Part 3: Workflow & chaining. Execution of</div><div> remote processes are automatically run asynchronously in case the</div><div> root process was invoked asynchronously.</div><div> * Parse the Location header from ulinet and the cookie if any.</div><div> * Add schemas to the components and support description stored in the file.</div><div> * Add a trivial DeployOnHpc service for automating the installation</div><div> and the deployment of a singularity container using the image</div><div> parameter provided in the executionUnit used when deploying the</div><div> process.</div><div> * Set the key json_response_object with the JSON response that the</div><div> ZOO-Kernel produced for the request, it can be updated from a</div><div> filter_out process.</div><div> * Update filter_in to support returning a response directly by</div><div> adding a response key in the lenv section (binary is supported for</div><div> this response)</div><div> * Provide an initial Dockefile dedicated to the DRU support with</div><div> remote HPC execution support</div><div> * Add a USE_HPC_NESTEDOUTPUTS build option to activate the nested</div><div> inputs and outputs addition (not supported with OGC API - Processes</div><div> - Part 1: Core)</div><div> * Update C-API errorException and printExceptionResponse* signatures</div><div> to handle the main configuration maps memory properly </div><div> * Build Docker image with DRU supporting OpenEO UDP encoding </div><div> * Add support for deploying and executing OpenEO User Defined</div><div> Processes by using an OpenEO graph for the executionUnit</div><div> * Add support for schema type string for request body, providing a</div><div> way to include CWL example files in the published OpenAPI</div><div> * Integrate the OGC API - Processes - Part 2: Deploy, Replace,</div><div> Undeploy optional support.</div><div> * Build Docker image based on MDL4EO/OTBTF and the onnx runtime for</div><div> models sharing</div><div> * Integrate the TeamEngine and ETS for OGC API - Processes</div><div> * Add JWT parser in security_service.py as filter_in to allocate</div><div> resources per authenticated user</div><div> * Integrate the work done during GSoC 2022 to support Node.js</div><div> ZOO-Services (cf. updated documentation for NodeJS)</div><div> * Update support to filter the jobs list using the user_id</div><div> * Add support for nested processes n OGC API - Processes - Part 3: </div><div> Workflows & Chaining</div><div> * Add filter_in and filter_out service array to be invoked previously</div><div> of and after the service run</div><div> * Add trivial support for OpenAPI security, basicAuth / openId, and add</div><div> sample services implementation</div><div> * Add support for MapServer 8.0 (actually 7.7-dev), including</div><div> returning result as OGC API -Features</div><div> * Integrate downloading MapServer 8.0 and building from the</div><div> dedicated Dockerfile-MS8</div><div> * Include basicAuth build instructions in the Dockefile</div><div> * Add basicAuth service illustrating how to secure access to OGC API</div><div> - Processes using Basic Authentication</div><div> * Use the osecurity section to detect secured path, request method</div><div> from the published OpenAPI</div><div> * Update the printHeaders function to allow Status definition at runtime</div><div> * Add a [osecurity] section to secure access to path, method couple</div><div> from the published OpenAPI</div><div> * Update the database connection handling to make it independent from</div><div> instantiation order</div><div> * Use the RabbitMQ also for OGC API - Processes</div><div> * Pass the subscriber if any is passed from the original request</div><div> * Make C OGR base-vect-ops compatible with memory=protect</div><div> * Add volumes to be shared by the ZOO-Kernel and the ZOO-FPM</div><div> * Add a RabbitMQ and a ZOO-FPM container to docker-compose</div><div> * Add documentation for RabbitMQ support and ZOO Fast Process</div><div> Manager (ZOO-FPM)</div><div> * Optional use of ZOO-Kernel Fast Process Manager backends to handle</div><div> asynchronous execution </div><div> * Partial integration of the code from the</div><div> Publicamundi_David_integration01-devel branch</div><br>I propose myself as a release manager, and the release is to occur this coming Saturday (2024/02/17).<br><br>My vote is +1 for this release to happen as proposed.<br><br>Best regards,<br><br><br></div><br><br><div>
<div>Gerald Fenoy<br>gerald.fenoy@geolabs.fr<br>Chair, ZOO-Project PSC</div>
</div>
<br></body></html>