2022-05-20 - Sys Ops & Management Agenda and Meeting notes

Date

Attendees

  • Help TC to define / review Technical Pain Points 

Discussion items

TimeItemWhoNotes
5WelcomeIngolf
55FOLIO Technical Pain Points

FOLIO Technical Pain Points - DRAFT - Google Docs

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

SysOps SIG to answer these questions:

  • Is this the right set of pain points ?
  • Why and how is something painful ?
  • What negative impact does it have  ?
  • How do we prioritize it ? 

Note: Detailed notes are linked in the Draft FOLIO Technical Pain Points document.

  • Conflation of gateway and discovery of modules
  • Reliance on HTTP as primary communication
  • Microservice complexity, message queueing, dependency among modules

  • Performance Issues
    • JSONB storage
    • Over-reliance on synchronous updates
    • Version upgrades and required downtime
    • Observability: need appropriate visibility into the code/operation
    • OKAPI inconsistencies and opaqueness

FOLIO Technical Pain Points  - Conclusions

There has been some mis-understanding about the ownership of this document. The ownership is TC, not SysOps SIG.

We think the sections in this document need to re-grouped and re-written. We could not make any prioritizations at this state of the work.

  • Ingolf will re-wind the document to pre-meeting , thus restore changes that have been (accidentally) lost during the meeting. Then he will re-insert the changes / comments made during the meeting.
  • Wayne will take that document and compile a SysOps-Version of the document; with pain points from the system administrators perspective
  • A core group of Wayne, Jakub, Jason, Ingolf, maybe others (Marc) will meet on Wednesday 12 EST (noon; 6 PM central European time).

Action items


  • Ingolf Kuss Plan Operational Needs session for WOLFCon 2022