Skip to end of banner
Go to start of banner

2020-12-11 - Sys Ops & Management SIG Agenda and Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Attendees

Discussion items

TimeItemWhoNotes
5WelcomeIngolf
10Review Action ItemsIngolf

Q3 Installation experiences




Support SIG representative

Action items

  • Jason/Ingolf : invite Lucy Liu to one of the next SysOps meetings.

Q3 Installation experiences

Ingolf:

  • Updated single server from Q2 but all data were gone
  • Problems with (missing?) pg_trm

Jason:

  • Has not yet migrated to Q3 but tested the prereleased Q3's
  • Rather migrate on fresh builds
  • Planning to move from Chef to Ansible

Dale raises the issue where customized reference data are overwritten by updates.

Jason agree there is still a lot of handwork to do when migrating

Common topics

Deployments single server vs rancher/kubernetes
  • Single server based on Vagrant mostly supposed to be for module developers who also uses the CI/CD deployments
  • Rancher/Kubernetes
    • High entrance but once set up it is very easy to manage and handle since FOLIO instances can easy
      newly setup, cloned or teared down, which is a huge benefit while testing migrations

What kind of the deployments in the Single server vs rancher/kubernetes?

  • TAMU: rancher/kubernetes
  • Chicago: has both
  • LZ Munich: single server on openstack
  • HBZ & Mainz: single server
About Postgres
  • Officially supported postgres is version 9-10
  • Jason is currently using postgres 11 and ran into no issues so far.
  • Dale suggested using Postgres 12 since moving to Java 11 this should be possible
About Documentation
  • Where is the best place to have this documentation?
    → should ask Marcia next week
  • Documentation should distinguish between a common single server and a kubernetes setup
  • Also destinction between local and cloud services
  • Rancher/Kubernetes documentation should be rather on a on premise setup than on AWS
  • Rancher/Kubernetes and AWS documentation is very outdated but steps didn't changed too much
  • DevOps and SysOps should write on the documentation together


Most Institutions implementing 2021 plan to go live on Iris release









  • No labels