/
2018-03-08 - System Operations and Management SIG Agenda and Notes

2018-03-08 - System Operations and Management SIG Agenda and Notes

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
5WelcomeIngolf

Determine note taker: Steve

Review last week's action items (=action items on the wiki pages). Action items from previous sessions are addressed in the agenda items below.

5 Review status of Action Items for Development (action items that we compiled from our discussions and want to take to the developers)Ingolf, Wayne 
5Add new lines to FOLIO Feature BacklogIngolf

These were two action items of 2018/01/04 .

Add items below the line or create separate spreadsheet.

The action items were only about the List of Integrations .

It will take some time to discuss this list ==> have a small Subgroup that will meet once or twice and that will generate lines in the FOLIO Feature Backlog ?

10SysOps related sessions on the WOLF Con (= World Open Library Foundation F2F meeting (conference), tentatively scheduled for May 2018, to be hosted by Duke University)IngolfWhich sessions do we need and what topics do we want to have addressed on the WOLF conference ? Concerning Implementation and Migration strategies - SIG Conveners have been asked to bring up their ideas in the Product Council.
30Discussion of experiences in putting up local FOLIO instancesGroup

Continue with point 7. in Deployment at TAMU .

Other questions or comments


API-ConsistencyIngolf, group

Martina Tumulla talked to Nassib Nassar about this in Madrid. Result:

  • the developers need more specifications, what exactly shall be standardized

Send specifications to Cate, Jakub, Nassib

 
5Topics for the next meetingIngolf

Notes

Action Item review:

  1. Making dependency resolution easier
  • Wayne - Jira issue

https://folio-org.atlassian.net/browse/FOLIO-1111

Add launch descriptors to module descriptors.

Result would be OKAPI handling dependency resolution/deployment vs. the manual process of doing the simulate=true step.

Doesn’t solve the problem of people deploying modules without OKAPI doing the docker work for back end modules.

Discussion of OKAPI’s role in deploying modules and resolving dependencies.

Wayne is going to take this discussion back to the core FOLIO group to see what they can do.


Discussion of integrations for FOLIO backlog

Take the list we have and create something that can be put into the FOLIO backlog

Convening a sub-group to finalize this list and submit to development team.


WOLF con

Pushed back to June

Suggestions for sessions

OKAPI dependency resolution, face to face with developers. (see above action item)

Walkthrough of installation/architectural diagram presentation

Tabling this discussion for next time


TAMU experiences discussion

Pretty much covered concerns in discussion on action items.  TAMU deferred to group to discuss any experiences they have had in their deployments.


For next time:

Possibility of bulk-load API

API consistency a concern for the bulk-loader.

Action items

Related content