2019-05-31 - System Operations and Management SIG Agenda and Notes

Owned by Ingolf Kuss
Last updated: Nov 20, 2020 by jroot
3 min read

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
5WelcomeIngolf

Upgrade of Database Schemasall

FOLIO-2046 - Getting issue details... STATUS

Does this epic correctly and adequately represent the issue or can we make it more clear and accurate ?  The SIG seems t think this is a good description of the problem.

This might end up becoming a set of standards or requirements that become part of the definition of "done" since this most likely becomes a feature for each app. 

Apps should also be able to respond to requests from Okapi and other apps with "I'm currently undergoing an upgrade". 

***Tod has taking on updating the Epic with this information.

***Harry to see if older similar features can be found and added to this epic.

This includes changes to RMB, Okapi, Apps, etc.  Scope is expected to be large.


Backlog cleanupIngolf + all

Finish combination of our two Backlogs, Meeting Topic and Action Item Backlog - SysOps and Action Items for Development . Get rid of the latter one.

Reviewed items on the backlogs to identify which are done and which are not.


 FOLIO WorkflowsIngolf, allWorkflow Proposal presented by Mike Gorell in the PC meeting.
  • Feedback from the SIGs is requested by June 13th
  • What are use cases of workflows in our SIG ?
  • What priority does having a Workflow System in FOLIO (consisting of a Workflow engine, a workflow editor, a console, the To-Do App and software methods) have for our SIG ?
  • comments on the technical realization (plan) of workflows in FOLIO


Notes by Ingolf:

We wrapped up an old action list. Anton works with the Kubernetes subgroup on continuous deployment and release management using a Jenkins server. - Tod and Harry put together a JIRA issue about database schema upgrading which had been identified an item of technical debt by the PC. The group adds requirements. -  The rest of the session was dedicated to a discussion about the Workflow proposal. The group doubts that alternatives to using Camunda as the workflow engine have been thoroughly investigated. Camunda is a very complicated piece of software. One reason for Camunda is that it is easy to implement and that it is well established in industry, so that it will have support. But we think that It would be wiser to build FOLIO in a way that the workflow engine will be replaceable. In fact, we see this latter as a key requirement for implementing workflows in FOLIO. The group considers the effort to solve problems with a workflow engine fairly similar to an actual software development effort and thus questions the need of a workflow engine at all. - What libraries will really need is the To-Do App. The group finds that it didn’t see enough use-cases for a workflow engine, on which a proposal for building one could rely. We know of no document that defines the problem that is being solved. The group will therefore invite experts to the next group meeting to explain some workflows which they need. - The group can think of some use-cases which require automatic interactions with the modules : batch processes and the re-implementation of LS-Tools.

 

Action items