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

Goal: Add lines to FOLIO Feature Backlog and prioritize - above the line (v1) or below.

Integration / Interoperability with Automated Storage and Retrieval systems (ASR).

Maybe combine List of Integrations with Consortial Systems Interoperation Needs List from Consortia SIG ?

Build a Subgroup that will meet once or twice and will generate the lines.

• Ingolf on holiday next week
• Discussion of LS-Tools and requirements for FOLIO on April 12th
• Discussing orchestration tools

Orchestration Model: Wayne: We don't have a model for deployment not based on Okapi. This may something that our group needs to agree upon rather than Index Data. Work on this needs to be done for WolfCon.

Integration issues that have arisen in Resource Acess. Tanyia: Resource access is working on remote access issues. ASRs like GSA and Dematic have to send and receive info to Folio, and she wants to find out if we will be covering that issue. Consoritia will also need integrations, such as resource sharing and Union Catalog-type functionality. These are interoperation needs which service providers will have to taylor for each institutions. Resource sharing tends to be standards based. Remote storage is not. Adapters to provide integration with remote storage systems may need to have hooks inside of folio to provide access. Discussion about whether custom programming for this kinds of integrations would be attractive to vendors or not. Cornell and Duke uses GFA, and Chicago uses Dematic, and they  can serve as resources. Tanyia will find out what other vendors are out there. Ingolf wants to create a subgroup to discuss consortial integrations.

WolfCon: Ingolf won't be able to go. ingolf has created a spreadsheet of topic proposals. Wayne forward information about topics proposed by Sysops, and they have been integrated into the agenda. Discussion of who should be moderators for different sessions. (See spreadsheet for notes.) For the Data Migration session, Wayne would like to see a discussion of the Extract, Transform, Load model (ETL). Can we use existing tools or do we need to do our own work. Discussion of who should attend what session. Deployment and Orchestration of Production. What should it cover? The landscape of tools that are out there. Useful patterns of orchestration. TAMU is doing local cloud model using ESXI enterprise Plus with Containers. Cornell is using AWS. Wayne: some structure is necessary, so that we can get the most work done in a short amount of time. Who wants to be the moderator for Data Cleanup (probably Patti). The was reviewed and completed.