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

Owned by Ingolf Kuss
Last updated: Aug 18, 2023

Date and time

10-11 EST

https://openlibraryfoundation.zoom.us/j/591934220?pwd=dXhuVFZoSllHU09qamZoZzZiTWhmQT09

Topics

Attendees

TimeItemWhoNotes



Meeting Notes:

Dry Run of our WolfCon sessionIngolf, Jason, Florian Kreft, Tonias

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/

-----------------------------------------------------------

Meeting Notes

  • Jason: I will show our folio code repo / scaling out
  • Florian: we have test systems since two years now. Where will be the real bottle necks ? Interesting to know which modules must be scaled in what way. We will go live next year. Go live October with ERM.
  • Jason: We did fiscal year rollover on Tuesday. It took ca. 15 minutes total. Infrastructure deployment environment. Backup strategies. The sustainability part is important. We have been running the system live for two years.
  • Tod: This is some old deployment info from TAMU, 2018: Deployment at TAMU
  • Florian: We have an elasticsearch engine which is fed by the logs.
  • Jason: 100,000nds of logs per minute is a pain point.
  • Tod: Let's have some specific requirements for logs. That will be useful. 
  • Tod: Please give a window into your backup strategy. Do you have a retention policy (yes). Do you test your recovery process ? (yes) - Database dumps. Jason; We have 3 different levels of backups:; 1. VM 2. nightly pg-backrest server. A point-in-time backup 3. weekly full backup . On top: Replication of the db to two other nodes. Florian: Very similar to our plans. Kubernetes manifests are backed-up. Zalando postgres 
  • Jason : Databases run on CentOS VMs (not in Kubernetes). We run crunchy postgres.
  • Florian: It might be harder to optimize stuff like Storage.
  • Jason: Our Storage are netapp clusters presented as nfs volumes. All backend storage is presented as nfs.


Application Formalization

Application Formalization - Google Docs

These ideas have been recently presented on a summit meeting in Chicago. We might think of them as technical proposals right now. They are currently the subject of dedicated discussions of the Technical Council. Several WolfCon sessions will also touch on these topics. It is the intention of the author to share these ideas with a wider audience. 

I think it makes sense to present and discuss these ideas in SysOps SIG, as well. Many of those technical changes proposed there will induce changes in the deployment and maintenance procedure.

Please watch recordings of FOLIO Technical Council's dedicated discussions on Mondays. First Meeting about the Application Formalization was on July 17th, recording is here: https://recordings.openlibraryfoundation.org/folio/tech-council/2023-07-17T11:00/  (Passwort= folio-lsp)

Next Meeting about Platform & Application Formalization was on July 31st: https://recordings.openlibraryfoundation.org/folio/tech-council/2023-07-31T11:00/

Next meeting with Vince: "Extending FOLIO's authorization model": https://recordings.openlibraryfoundation.org/folio/tech-council/2023-08-07T11:00/

And you might also want to watch the recording of the regular TC meeting on August 9th. The sections in the 2nd half of the meeting: "Questions from Monday's presentation" and "Process Concerns in the wake of Vince's presentations" : https://recordings.openlibraryfoundation.org/folio/tech-council/2023-08-09T11:00/  

... I know, it's a lot to watch (wink)

-------------------------------------------------------------------------------------------------------------------------

Meeting Notes:

Application Boundaries: Interface Versions need to include a range of versions, must be backwards compatible. Application versioning not much different than modules versioning + flower release bundles ?

Ingolf: A concern about the (proposed) changing notion of a Platform. If there will be not just one big platform (platform-complete), as it is now, but several smaller platforms, maybe specialized to ERM, circulation, other specific purposes:  All modules which one might possible install must go through thorough buckfest testing (or some QA testing of similar quality). Having just a smaller set of modules undergo the QA testing workflows does not seem acceptable.



WolfCon regsitrationIngolf 

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.






Topics for future meetings:


  • no meeting on August 25th - Friday after WolfCon (Shoulder sessions are ongoing)
  • Big changes from WolfCon

Need to pick up topics from the Application Formalization proposal in further sessions:

  • What is a Platform?
  • Application store or marketplace?
  • Microservice boundaries

(basically, we have so far only discussed the Folio Applications section)



Status of Integrations

Action items

  • Type your task here, using "@" to assign to a user and "//" to select a due date