[Geoserver-devel] PSC meeting notes, Feb 1st 2022

GeoServer GeoServer Developer
,
1

GeoTools / GeoServer PMC meeting - 2022-01-18Attending

   -

   Torben Barsballe
   -

   Jukka Rahkonnen
   -

   Jody Garnet
   -

   Andrea Aime
   -

   Kevin Smith

Actions from prior meetings:

   -

   Andrea to follow up with spotless team to see how formatter handles
   switching between branches [DONE]
   -

   Andrea: Setup a maintenance page about the h2 1.x → 2.x challenges
   [started]
   -

   Jody: create log4j upgrade/replace news item inviting proposals and
   sponsors
   -

   Andrea: create sf ticket about mailing list archive [DONE]

Agenda

   1.

   Cite Workspace Cleanup / Jenkins Access
   2.

   CQL2 GeoTools community module
   3.

   Community modules, graduation targets?
   4.

   Follow up on formatter updates
   5.

   Logging proposals / decisions
   6.

   FOSS4G

Actions

   -

   action: cite-master-all is now disabled
   -

Cite Workspace Cleanup / Jenkins Access

   -

   We ran into slowdown in december, fixed in january
   -

   Alessandro and others are in position to help (confirmed access),
   although availability is limited
   -

   Juan determined the issue (a permission problem) sharing files
   (specifically, the log files of the cite job, from the docker image) –
   change to jenkins/jenkins
   -

      Jenkins was reporting these as problem; and busy waiting trying to
      remove files
      -

      Using about 50% of build machine capacity
      -

   action: turn cite tests until this is fixed?
   -

      cite-master-all is now disabled
      -

      torben may be able to look at this if alessandro cannot act quickly
      -

   windows installer non blocking issue; similar issue with rsync files
   back to jenkins

CQL2 GeoTools community module

CQL2 - limited opportunity for Andrea

   -

   Got +1 on email
   -

   good luck!

Aside: consider renaming package org.geotools.filter.text.cql2 → to
org.geotools.filter.text.cql

   -

   Sure: Deprecate and move ...

Community modules, graduation targets?

Discussion …

   -

   What is available for 2.21 release plan?
   -

   Some are staying there forever?
   -

   some modules like "feature templating" are using jira (and showing up in
   release notes) before graduating … please mark with "Community Module"
   category to save release manager time
   -

   Are their any we can declare as dead and be removed
   -

      teradata → move back to unsupported (it has not been maintained)
      -

   geojson split is working out (gt-geojson-core, gt-geojson-store)
   -

      talking with Ian about graduating? ...
      -

      gt-geojson to be removed without deprecation

Community modules ready for removal:

   -

   gs-geomesa: just pom, no release package? remove
   -

   gwc-distributed: still alive?
   -

   jdbc-metrics: probably dead? Justin are you still using it?
   -

   monitor-hibernate: ready
   -

   ows-similate: Justin are you still using it?
   -

   rest-upload: ask in GeoSolutions
   -

   wms-eo: still active? check in GeoSolutions
   -

   wps-sextante: stil active?

Follow up on formatter updates

formatter updates:

   -

   from email this appears to be testing well
   -

   slower for initial format, faster once index is created
   -

   Draft pull request, not ready, need to skip formatting on a couple of
   modules

Logging proposals / decisions

See:
https://github.com/geoserver/geoserver/wiki/Update-or-replace-Log4J-1-library

Fundraising going well: $5k+ raised

   -

   GeoCat cleaned GSIP 167 log4j2
   -

      Attitude of adding features with out review consequences seems poor
      -

      GeoCat has capacity if PSC is interested, will propose for 5k
      (suggest remaining go to cite sprint or security)
      -

   Mark started GISP-209 logback
   -

      But stalled out … but logback seems good.
      -

      Website to convert log4j1 config → logback configurati
      <https://logback.qos.ch/translator/&gt;

Action:

   -

   Jody: Attach quote for 5k to GSIP-167 and email the list

FOSS4G

   -

   Call for Papers for Feb? In person (assumed)...
   -

      State of GeoServer: andrea, jody
      -

      GeoServer Feature Frenzy: andrea, jody
      -

      GeoServer Ecosystem: if there is interest … reach out ot gabe?
      -

      State of GeoWebCache: kevin
      -

      State of GeoTools: andrea / jody / ask Ian

Chit/chat

OSGeo funding meeting last week

GDAL upgrade: testing worked, API change (for bindings to binary) is subtle!

   -

   recommend no longer bundling gdal bindings, add instructions to download
   the version you use …
   -

   Use apache bench for load testing, use more threads than cpu as, confirm
   it will not segault
   -

   Consider upgrading also:
   -

      OGR store
      <https://github.com/geotools/geotools/tree/main/modules/unsupported/ogr/ogr-jni&gt;
      -

      VSI
      <https://github.com/geotools/geotools/tree/main/modules/unsupported/vsi&gt;

2

Checked internally about the community modules we had some relation with:

  • gwc-distributed: still alive?

Can be eliminated.

  • rest-upload: ask in GeoSolutions

Same here, can go

  • wms-eo: still active? check in GeoSolutions

Still seeing a bit of usage, to be revisited next time we look at community modules cleanup

Cheers
Andrea

···

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

3

Hi All,

I’ve got a bit of an update on Jenkins.

First of all, I did find out why we were still getting undeleteable build artifacts - cite-runner was disabled, but cite-master-all_makefile was not. Could someone please clarify which does what (or at least add a description to the jobs in jenkins)? They both seem to run all the cite tests. Both are affected by the issue. I have now disabled the latter, and deleted any lingering cleanup workspaces, so at least we should no longer be getting the unremovable files until the issue is fixed.

Seemed to have worked, but apparently not;

Following on from Juan’s discoveries as to how the issue is being caused by the UID docker runs as I found that, when using docker-compose, you can change the UID docker uses.

I added a step to each of the cite jenkins builds that adds UID and GID of jenkins to the .env file, right after:

echo “### Build docker images”
echo “” >> .env
echo “UID=$(id -u)” >> .env
echo “GID=$(id -g)” >> .env

This initially seemed to work, but subsequent automatic runs of the jobs indicate it didn’t - troubleshooting has been complicated by the instability of the cite builds, in particular their tendency to time out when downloading docker images.
Given this attempted fix didn’t work, I think it will be necessary to modify the cite docker configuration itself (the docker-compose file or the dockerfiles themselves) to run as the jenkins user. It’s also possible that the docker file needs to have its own internal jenkins user (with a matching UID and GID - the user name doesn’t really matter here) in order to be able to run as it. It would be best if someone who is familiar with the cite docker configuration (and who has access to the appropriate repository) tries to get that working.

Cheers,
Torben

On Tue, Feb 1, 2022 at 10:32 AM Andrea Aime <andrea.aime@anonymised.com> wrote:

GeoTools / GeoServer PMC meeting - 2022-01-18### Attending- Torben Barsballe

  • Jukka Rahkonnen

  • Jody Garnet

  • Andrea Aime

  • Kevin Smith

Actions from prior meetings:- Andrea to follow up with spotless team to see how formatter handles switching between branches [DONE]

  • Andrea: Setup a maintenance page about the h2 1.x → 2.x challenges [started]

  • Jody: create log4j upgrade/replace news item inviting proposals and sponsors

  • Andrea: create sf ticket about mailing list archive [DONE]

Agenda1. Cite Workspace Cleanup / Jenkins Access

  1. CQL2 GeoTools community module

  2. Community modules, graduation targets?

  3. Follow up on formatter updates

  4. Logging proposals / decisions

  5. FOSS4G

Actions- action: cite-master-all is now disabled

Cite Workspace Cleanup / Jenkins Access- We ran into slowdown in december, fixed in january

  • Alessandro and others are in position to help (confirmed access), although availability is limited

  • Juan determined the issue (a permission problem) sharing files (specifically, the log files of the cite job, from the docker image) – change to jenkins/jenkins

  • Jenkins was reporting these as problem; and busy waiting trying to remove files

  • Using about 50% of build machine capacity

  • action: turn cite tests until this is fixed?

  • cite-master-all is now disabled

  • torben may be able to look at this if alessandro cannot act quickly

  • windows installer non blocking issue; similar issue with rsync files back to jenkins

CQL2 GeoTools community module

CQL2 - limited opportunity for Andrea

  • Got +1 on email

  • good luck!

Aside: consider renaming package org.geotools.filter.text.cql2 → to org.geotools.filter.text.cql

  • Sure: Deprecate and move …

Community modules, graduation targets?

Discussion …

  • What is available for 2.21 release plan?

  • Some are staying there forever?

  • some modules like “feature templating” are using jira (and showing up in release notes) before graduating … please mark with “Community Module” category to save release manager time

  • Are their any we can declare as dead and be removed

  • teradata → move back to unsupported (it has not been maintained)

  • geojson split is working out (gt-geojson-core, gt-geojson-store)

  • talking with Ian about graduating? …

  • gt-geojson to be removed without deprecation

Community modules ready for removal:

  • gs-geomesa: just pom, no release package? remove

  • gwc-distributed: still alive?

  • jdbc-metrics: probably dead? Justin are you still using it?

  • monitor-hibernate: ready

  • ows-similate: Justin are you still using it?

  • rest-upload: ask in GeoSolutions

  • wms-eo: still active? check in GeoSolutions

  • wps-sextante: stil active?

Follow up on formatter updates

formatter updates:

  • from email this appears to be testing well

  • slower for initial format, faster once index is created

  • Draft pull request, not ready, need to skip formatting on a couple of modules

Logging proposals / decisions

See: https://github.com/geoserver/geoserver/wiki/Update-or-replace-Log4J-1-library

Fundraising going well: $5k+ raised

  • GeoCat cleaned GSIP 167 log4j2

  • Attitude of adding features with out review consequences seems poor

  • GeoCat has capacity if PSC is interested, will propose for 5k (suggest remaining go to cite sprint or security)

  • Mark started GISP-209 logback

  • But stalled out … but logback seems good.

  • Website to convert log4j1 config → logback configurati

Action:

  • Jody: Attach quote for 5k to GSIP-167 and email the list

FOSS4G- Call for Papers for Feb? In person (assumed)…

  • State of GeoServer: andrea, jody

  • GeoServer Feature Frenzy: andrea, jody

  • GeoServer Ecosystem: if there is interest … reach out ot gabe?

  • State of GeoWebCache: kevin

  • State of GeoTools: andrea / jody / ask Ian

Chit/chat

OSGeo funding meeting last week

GDAL upgrade: testing worked, API change (for bindings to binary) is subtle!

  • recommend no longer bundling gdal bindings, add instructions to download the version you use …

  • Use apache bench for load testing, use more threads than cpu as, confirm it will not segault

  • Consider upgrading also:

  • OGR store

  • VSI

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel