2019-05-17 - System Operations and Management SIG Agenda and Notes
- Ingolf Kuss
- Florian Ruckelshausen
Date
Attendees
- Johannes Drexl
- Florian Ruckelshausen
- patty.wanninger
- Tod Olson
- Brandon Tharp
- Christopher Creswell
- Craig Boman
- Dale Arntson
- Greg Delisle
- Ian Walls
- Jackie Gottlieb
- jroot
- Alexander Soto
- Philip Robinson
- Robert Douglas (Robbie Douglas)
- Wayne Schneider
- @Harry (-10:30)
Goals
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 | Welcome | Ingolf | Notetaker: Florian |
| 5 | Updates on June FOLIO Meeting | Ingolf | Discussion sessions scheduled Meeting Notes Both session proposals from SysOps have been accepted:
|
| Implementing a Data Warehouse | Ingolf | What does a Data Warehouse mean for SysOps ? What will be the difference to the DW built by the Reporting SIG (questions by Ingolf) ? Meeting Notes The reporting SIG is adressing a data warehouse solution for reporting (called library data plattform = LDP). It relies on an additional relational database and uses Python scripts to get the data out of FOLIO. The idea is that a data load happens on a daily basis. The SysOps group discusses several questions: Will the LDP get the data via OKAPI? Will such a daily job consume too much OKAPI ressources? Is it really necessary to get a complete refresh with only a small portion of data that changes or is it a better idea just synchronizes the changes? Is such an approach consistent with a microservice architecture? Before speculating to much it seems reasonable to invite Nacib and/or Roman to a session so that these questions can be adressed. Ingolf will ask them and also add data privacy to the list of topics. There is a new sub sig that espeacially adresses this topic for reporting. | |
| Roadmap & Backlog | all |
Here's our meeting topics backlog: Meeting Topic and Action Item Backlog - SysOps Here are the plans and Jira tickets for Folio integration with an orchestration toolset Meeting Notes From the backlog topics the upgrade problem seems to be the most crucial one. Especially for database schema changes there is no update path and in a productive system a live update of the database schemas should be possible without a manual export-import process. Anton will add existing JIRA tickets to the table at Meeting Topic and Action Item Backlog - SysOps, so that everyone can have a look what is already there and what is missing. Then tickets have to be added and ranked. Jo has posted his suggestion for Upgrading in the wiki: Upgrading & Dependency resolving Can the RAML module builder be used for database schema versioning? The documenation indicates it can be used. | |
Topics for next meeting: | Meeting Notes Topics for the next meeting
|