2023-08-11 Sys Ops & Management SIG Agenda and Meeting notes

Looking at Platform Minimal, wondering about some of the third party dependencies like MinIO and OpenSearch

Lack of definition for what constitutes a FOLIO Application,  from the document:

"It is proposed that an Application be defined as the minimal but complete set of elements which together are intended to deliver a specific solution to Folio. " we like the proposal for a separate versioning scheme for the Application while the individual modules and interfaces maintain their own versions. Discuss what it means by interface version, same inputs produces the same outputs regardless of how the interface is implemented. Module descriptors what dependencies on the interfaces for other modules.  Application would provide it's own interface versioning independent of its modules versions. Bug fixes should not change interface version, larger flower release would be changes in the interface.

• If you update core, all Applications would need updating. If an Application change, could be updated without updating other applications? Can depend on each other?
  
• Question about dependencies between Applications? Would make sense if Applications depend on range of versions for other Applications?
• What happens if interface updates to a complete new endpoint/interface? Would older Applications still work? Interface version is an API contract, doesn't matter how module is implemented?
• Interface version and module version doesn't haven't to be one-to-one? More of coincidence and not by design
• All modules in the flower release will be tested together?
• Would Applications change the scope of a flower release? Conern that "flower releases could be reduced in scope" (as the document says) and "minority" modules might fall out of the bugfest testing. 
• Do core developers test every module or leave it to the module developers? Does this codify what is already FOLIO practice?

Please register for WolfCon if you have not already done so.

Admission for virtual attendance is free!

Register here: 

https://openlibraryfoundation.org/about/wolfcon/upcoming/

Registration is open until August 19.

 Our session has been confirmed by the WolfCon planning team:
ID 18
Title Platform Decisions for FOLIO Self-Deployment on Kubernetes
Start Date & Time
8/24/2023 1:30:00 PM
End Date & Time
8/24/2023 3:00:00 PM
Type/Track
FOLIO
Description
This session is meant for systems administrators who plan to self-deploy FOLIO in a general Kubernetes environment (private cloud or public cloud). We will share experiences and give recommendations and insights for self-hosting FOLIO. We will address aspects of needed infrastructure and a usable common repository for Helm Charts.
Organizer Ingolf Kuss
Speakers
jroot@library.tamu.edu, florian.kreft@lrz.de, tobias.stumpp@uni-tuebingen.de
Room
Room 701
Audience
Adopters, Potential adopters, Developers, Sys Admins, Dev Ops
Session Type
Working Meeting

Link https://wolfcon2023.sched.com/event/1Olfo/platform-decisions-for-folio-self-deployment-on-kubernetes

WolfCon 2023 Schedule is out :

https://wolfcon2023.sched.com/

• Dry run of SysOps Session next week
• no meeting in two weeks (08/25 - Friday after WolfCon)
• Big changes from WolfCon
• What is a Platform?
• Application store or marketplace?

• Overview: List of Integrations - System Operations and Management SIG - FOLIO Wik