2026-02-18 Sys Ops & Management SIG Agenda and Meeting Notes

Flux CD
Argo CD
Flo: Rolling out Developer Enviroment; One Repository for each Developer
YAML Files hosted on Repositories
Florian: Presentation to Developers (2,5 h) ; a prototype of how to use Argo CD

Florian offers to do the presentation in English in one of the next sessions here!

BiblioCon vs. Bib Commons Conference
Eureka Deployments
Argo CD

WolfCon
More structured - short talks
depict infrastructure requirements

Local installation strategy:
3 or 4 installations dev - prod - demo - test
multi-tenancy on the installations
split up installations by Name space;
Jason host single Name spaces (liable to pay costs)
others share 1 Namespace with 10 tenants
each Namespace has their own infrastructure (postgres, elastic, kafka, okapi / Kong)
2 versions of FOLIO deployed in each Namespace
in Okapi you can use the same Gateway for tenant X and Y ; Kafka needs to be a different Installation / In Eureka, you would use different Gateways (Kong) for each tenant.
Kafka has a different Name for each version: kafka-ramsons, kafka-sunflower
different secrects that have KAFKA_HOST

Ingolf (permission upgrade issue):
the admin user needs a freshly generated list of permissions after each release upgrade ; can still use bootstrap-user.pl

You have to add new permissions after the fact.

Better would be global permission sets (admin, circ desk, order etc.) which would be maintained by FOLIO and updated for each release.

The situation will get even more complicated in Eureka. Permissons will be replaced by Capabilities and Roles.

Josh: an issue in mod-source-record-storage partitions "give it 12 partitions"
in Quesnelia we had more Problems with data Import

Jason: an issue in EDI Imports

Chat Log

Topics for next meetings

Ingolf

Using FOLIO as a local system in a library union environnement

FOLIO to interact with a union catalogue, which is NOT FOLIO

1. Use case: Download: Creation and Updating of bib records in the union catalog, then import/update to FOLIO SRS (Format: MARC-XML)

   1. Requirements for FOLIO: Import interface. Merging external records to existing records in SRS (matching via external id). Subsequently updating the FOLIO inventory records accordingly.

2. Use case: Location Upload: When FOLIO creates a location (Holding) for a bib record, the union catalogue needs to get knowledge of the new Holding (because the holdings will be listed in the union catalog).

   1. Requirements on FOLIO: Export of the whole record, bib + holdings, in a single MARC-XML record.

   2. Requirements on union catalog: Import facility, Match & Merge of Holings records.

3. Use case (optional) : Creating new bib records in FOLIO (quick marc) and exporting them to the union catalogue.

   1. Requirements: FOLIO bib export inteface

   2. Requirements on union catalog: Import facility for new records !