[GeoNetwork-devel] GeoNetwork codespint on UI and microservices

GeoNetwork GeoNetwork Developer
1

Dear all,

Next week (12th to 16th October), we are organizing a GeoNetwork codesprint about UI and microservices. See
https://github.com/geonetwork/core-geonetwork/wiki/GeoNetwork-UI-and-microservices-codesprint-October-2020 for details.

Do not hesitate to join us to contribute to this topic.

Kind regards.

Francois

2

That sounds great, it may be too short notice for me to attend.

···

–
Jody Garnett

3

Dear all, a quick summary of last week sprint
https://github.com/geonetwork/core-geonetwork/wiki/GeoNetwork-UI-and-microservices-codesprint-October-2020

This sprint was the opportunity to jump in 2 new major topics for the future of GeoNetwork.

Half of the team concentrated on microservices. With the help of Gabriel Roldan who designed the GeoServer architecture based on Spring Cloud (see https://github.com/camptocamp/geoserver-microservices), Jose, Christophe and Francois managed to:

  • Move the search proxy from GeoNetwork 4 to a dedicated service which does not take into account yet user privileges
  • Validated the option that Spring Cloud Event bus (using RabbitMQ or Kafka) can be used to communicate between GeoNetwork4, microservices and Camel routes
  • A microservice dedicated to indexing has been designed in order to focus on performances - based on events, streaming, multithread, XSLT3 and bulk operations (see https://github.com/geonetwork/geonetwork-microservices/blob/main/modules/services/indexing/README.md). The indexing chain has been set up using Apache Camel project providing metrics using micrometer library to monitor the progress of tasks. The approach sounds efficient and reliable.
  • Docker images are built with maven build to make startup of GeoNetwork4, Elasticsearch and microservices easy (see https://github.com/geonetwork/geonetwork-microservices/pull/16)
  • A gateway application can take care of routing incoming requests to both GeoNetwork4 and microservices. As things progress, the routes can be adapted to redirect API calls from the legacy app to the corresponding microservices.
  • Authentication using Oauth and JWT was analyzed but is a challenging tasks. We have to be able to setup authentication at the gateway level, share user information across microservices using JWT and also be in capacity to authenticate in GeoNetwork4 at the same time. This topics needs more investigation.
  • An OGC API Records server was generated from the OpenAPI specification provided by https://github.com/opengeospatial/ogcapi-records/. The specification is a draft and we are checking which the standardization team which documents is best to use and how to help on the standardization efforts.

A number of issues/questions have been added to the roadmap including some about templating which interacts with the GeoNetwork UI project which was the 2nd topic.

Michel, Olivier and Florent made progress on the https://github.com/geonetwork/geonetwork-ui project focusing on:

Thanks to all contributors and to EEA & Ifremer sponsoring the event.

Francois

Le sam. 10 oct. 2020 à 02:07, Jody Garnett <jody.garnett@anonymised.com> a écrit :

That sounds great, it may be too short notice for me to attend.

–
Jody Garnett

On Wed, 7 Oct 2020 at 05:27, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Dear all,

Next week (12th to 16th October), we are organizing a GeoNetwork codesprint about UI and microservices. See
https://github.com/geonetwork/core-geonetwork/wiki/GeoNetwork-UI-and-microservices-codesprint-October-2020 for details.

Do not hesitate to join us to contribute to this topic.

Kind regards.

Francois

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork