2024-07-05 Sys Ops & Management SIG Agenda and Meeting notes

There has been a long discussion 3-4 years ago about how FOLIO should handle reference data upon upgrades. See these links for background:

• Original problem statement
• Input from SysOps SIG
• Proposals considered by Tech Council working group
• Recommendation from Tech Council working group

The recommendation has never been implemented.

Recently (and currently), there is a new discussion about reference data upgrade behaviour in specific modules, especially in mod-circulation-storage. But there are also issues with acquisition data and foreign language labels that non-English speaking universities have put up.

For mod-circulation-storage, there are currently two Jira issues which are being worked on, one for the Poppy release, the other one for the Quesnelia release: https://folio-org.atlassian.net/browse/CIRCSTORE-517
https://folio-org.atlassian.net/browse/CIRCSTORE-516

But, what is more, we think we must have a better solution for all modules. And therefore, we will propagate the worked out solution, again. Ingolf will bring this issue to the Technical Council. Wayne will provide details [I have amended the notes to add the details above – ws].

Virtually all hosting providers are affected by this issue. Most of them store their reference data locally and then need to reload it after each upgrade. This procedure is tedious, annoying and unprofessional. It definitely needs to become part of the FOLIO upgrade procedure to take care of institutional reference data and not scrape them.

Notes from April 30 meeting:

Invite someone from EBSCO
- Ingolf reaches out to Mark Weksler → Mark Veksler says he will be able to give a short presentation (10-15 minutes) from EBSCO's point of view.

Session submitted by Sys Ops SIG
Session Title
Self-Hosting FOLIO in a New Platform Architecture
Session Description
Moving the Architecture from the Okapi to the Eureka Platform. Experiences, observations and challenges.
Organizer Name
Joshua Greben
Organizer Email
jgreben@stanford.edu
Session Type
Working Meeting (could in some way turn into a Workshop)
Session Length
Extended (80 minutes)
Names of presenters (include the organizer if they are presenting) OR Name of working group/SIG
Sys Ops SIG
E-mail addresses of presenters (separated by comma)
jgreben@stanford.edu, jroot@tamu.edu, florian.kreft@lrz.de, kuss@hbz-nrw.de

(note: we can add more)
E-mail addresses of presenters (separated by comma)
Collaborative of Hybrid meeting, Recorded and shared on the WOLFcon YouTube archive
Project and Topic Track(s)
FOLIO
Sub-Track - FOLIO Councils, SIGs, other sub-groups
Technical Council, Data Migration, Sys Ops SIG
Audience
Current users, prospective users, Developers
Technology or Room requirements
a whiteboard or dashboard
Do you or any presenters require special accommodations?
No

Meeting Notes July 5th :

The group has not much experience with deploying in a Eureka environment, yet. Efforts at GBV/VZG have been paused since 4 weeks ago.

It is questionable if the group can present some experiences in that area at WolfCon, although there is still some time until then. But LRZ will be occupied with Poppy (Quesnelia?) upgrades.

We should focus on issues / problems / requests for amendments that we see in the Eureka formalism. So far have been raised:

• Problem to deploy the side cars is seen most urgently (Ghassen Tajini)
• Missing documentation in general, more particularly for Kong and Keycloak integration to FOLIO
• Has there ever been another authentification mechanism in FOLIO than what we have now ?
• Timelines. Every institution has their own set of tools for a Release Upgrade. All these tools can be scraped and written anew if the institution moves to Eureka. A lot of effort which will take a lot of time. Problem that alle institutions use different set of tools. We need to have a common way to deploy FOLIO on a Kubernetes based environment, independetly of whether one is using Rancher, AWS, plain K8s, kubespray or whatever → Kubernetes Operator (see next chapter)
• Need to be able to set up a tenant and an application in a unique way for all K8s based environments

Other Session accepted for WolfCon:  https://openlibraryfoundation.org/about/wolfcon/upcoming/agenda/

• Sparse information; Who is presenting ? What is the audience ? Will this be more a technical talk or an functional one ?
• Two sessions about Application / Platform Formalisation → connected to Eureka formalism, but not necessarily with that. Application Formalisation is also a topic without Eureka

Wayne Schneider submitted a session on the Kubernetes Operator

Proposed Session with more details, but old (April). Is there no more recent list with more details ??

2024 WOLFcon session proposals - Brainstorm

Many interesting sessions proposed:

• Application formalization workshop
• Joint presentation with someone from NLA - Eureka
• Applications and mgmt thereof. Introduce and drill into Eureka’s manager components with the focus on system administration
• LoC Case study - LoC is going live on Eureka, ...
• Eureka architectural overview - provide more details about topics such as Keycloak, Kong, Sidecars, manager components, etc. and how they interact

All propsed by EBSCO people.

How many of these sessions have been accepted ??