2021-08-18 Meeting notes

2021-08-18 Meeting notes

Date

Aug 18, 2021

Attendees

  • @Craig McNally (Convener, Scribe)

  • @Julian Ladisch

  • @Philip Robinson

  • @Raman Auramau

  • @Zak Burke

  • @Marc Johnson

  • @Tod Olson

  • @Chulin Meng

  • @Steffen Köhler

  • @VBar

  • @Jeremy Huff

  • @Jakub Skoczen

  • @Mark Veksler

  • @Dennis Benndorf

  • @jroot (Unlicensed)

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

5 min

Review outstanding action items

All

  • @Craig McNally updated the wiki to reflect membership changes

  • Still outstanding items for @Mark Veksler and @Zak Burke

5 min

External Code Submissions

@Jeremy Huff @Zak Burke @Marc Johnson @Raman Auramau @Ian Walls @Craig McNally

@Jakub Skoczen

Some initial progress was made, but has since grinded to a halt... 

  • We need a volunteer to "own" this and drive the process.

    • @Jeremy Huff to reach out to @Ian Walls to see if he wants to be the champion.  If not, he will take it.

  • Subgroup has agreed to find a time to meet this week.  @Jeremy Huff to organize.

5 min

WOLFcon 2022

@Philip Robinson @Tod Olson

Quick follow-up → have you connected with @Mike Gorrell

  • Yes, the ball is rolling - slack channel, google doc, etc. exist

    • WOLFcon 2022 brainstorming document: 

    • WOLFcon needs for FOLIO - 2022

  • @Philip Robinson to organize a list of questions for the TC. 

    • Topics that are relevant now may not be when WOLFcon actually happens

      • Possibly defer the topic discussion until ~6mo prior to Sept. 2022 

    • @Tod Olson /@Philip Robinson will let us know when they are ready for feedback/input and we'll get it on the agenda.

<= 45 min

module storage, S3/min.io 

All

Proposal (@Marc Johnson/ @VBar / @Jakub Skoczen ):

  • The S3 API is the protocol for external (non-Postgres) object storage in FOLIO and standard environment variables/configuration of an S3 server on a per module basis.

  • The module implementation of object storage must conform to the FOLIO standards for tenant separation

    • The recommended standards will be referenced/pointed out by the tech leads.

      • e.g. how tenant separation should be handled, etc.

      • @Jakub Skoczen will raise the topic with the tech leads

  • Should the min.io client library be the recommended client as object storage choice agnostic library, but modules could also choose the native S3 implementation?

    • Yes.

  • Should teams be allowed to store binary data in Postgres?  In some cases (amount of data is small, etc.)?

    • Yes.  If external object storage (not Postgres) is required, it must be S3.

    • Regardless of which is used, tenant separation still must be done. (x3)

Time permitting

TC charter review

All

 

Action items

@Jakub Skoczen to raise the topic of tenant separation in object storage with the tech leads group.
@Philip Robinson to organize a list of questions for the TC (wrt WOLFcon 22) and let us know when they're ready for feedback/input.
@Jeremy Huff to organize a meeting of the "external code contributions" subgroup
@Jeremy Huff to ask @Ian Walls if he's interested/willing to drive the "external code contributions" subgroup/effort.