2021-02-12 - Sys Ops & Management SIG Agenda and Notes
Date
Attendees
- Ingolf Kuss
- Harry Kaplanian
- Marc Johnson
- Tod Olson
- Anton Emelianov
- Catherine Smith
- Gang Zhou
- Sha Jiang
- Wayne Schneider
- Xiaoyang Chen
- CHristopher Rutledge
Meeting Link
- https://zoom.us/j/591934220
- Password: folio-lsp
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Note Taker: Harry Welcome Sha, Gang and Xiaoyang ! | |||
Proposed Short Term Approach to schedule aged to lost billing processes | Marc Johnson , all | Marc Johnson wrote in the Slack chat: "Challenge Implementing organisations need to be able to schedule aged to lost ... billing processes to run when they choose. They will often choose to run these overnight in order to avoid reduce the load on systems and impact on day to day activities. This capability is needed for the 2021 R1 release. Current Situation The current implementation of these processes uses the okapi The Okapi There are less than 3 weeks of development time remaining for the 2021 R1 release (for platform core modules) and the Core Functional team does not have capacity to make significant changes to this implementation. Proposed Short Term Approach It is believed that many organisations already have the ability to schedule processes in their operational infrastructure already. Hence it has been suggested we use the organisations chosen mechanism for doing this outside of FOLIO. I think this would involve the following development:
And configuration by the hosting provider (including the hosted reference environments) of:
Organisations will likely need to schedule these processes separately meaning two separate tasks and schedules are likely to be needed." An http request gets sent to OKAPI via Cron and OKAPI send the message to the process to execute. It might be interesting to provide an option in the future to trigger these events internally, externally or a mixture of both. Today a library does not have the ability to turn off these events. This will need to be updated in the future in Mod-Circulation-storage. Right now, we don't have the developer resources to get all this work done. Wayne, yes it would just be an http request, but it means that institutions need to develop a simple FOLIO app/client and user to set this up. Something could be built to demonstrate this (ex. cli stripes container). Would need to engage the FOLIO dev ops team. Wayne, this is an all or nothing deal for right now? Marc, we would like to make as few changes as possible. Will focus on just these two areas for circulation. Marc has started a document for how we could schedule jobs in FOLIO in the future. Marc will circulate. If this was not needed for R1, we would be focusing on the bigger larger solution. This proposal should not the the standard way for the future. | |
Engagement of SysOps SIG in docs project | Ingolf | We need to recruit a representative for the documentation working group. Ingolf has stepped up to represent the SIG The Documentation Working Group will be run by Emily Fowler. Initial meeting will be on Feb 24th or 25th. | |
Kafka integration in mod-inventory-storage | Ingolf | https://github.com/folio-org/mod-inventory-storage/commit/54dd0bb0c99639e2de64d89eee6c99935aa32607
The Answer to these questions is: YES It's for remote storage, elastic search and improvements for import. This is not a general policy, but might change in the future. |