2020-10-30 - Sys Ops & Management SIG Agenda and Notes
- Ingolf Kuss
Date
Attendees
- Ingolf Kuss
- Philip Robinson
- Axel Dörrer
- Catherine Smith
- Tod Olson
- Florian Gleixner
- Johannes Drexl
- Brandon Tharp
- Chris Rutledge
- jroot
- Stanislav Miroshnichenko
- Darsi Rueda
- Michelle Suranofsky
- Aaron Trehub
Meeting Link
- https://zoom.us/j/591934220
- Password: folio-lsp
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 10 | Welcome | Ingolf | Welcome new member Florian Gleixner from LRZ in Munich! |
| 20 | Helm Charts | Ingolf |
Notes: Stanislav shows how to deploy for a second tenant, using a Helm chart. In the Helm chart, you can only use one tenant. To administer 100 or so tenants, Stanislav wouldn't use Helm charts, but use a script or other kind of programming tool. |
| 15 | Open Topics Session | all | Jason: TAMU has successfully upgraded their fresh Folio Q2-2020 hotfix 3 instance with Tamu data to hotfix 4 + patches. Patches are supplement to hotfixes; they are like hotfixes that haven't been released, yet. Q3 TAMU has been involved in the Bugfest for Q3. They also did upgrades from Q2 → Q3. Even more, they are going to test the whole update chain Q1 (latest) → Q2 (latest) → Q3 with TAMU data. List of Jiras related to recent upgrade testing: https://folio-org.atlassian.net/browse/RMB-744 Keep in mind, the idea here is to test upgrades from various starting points - and to also prove a continuous living instance of Folio being upgraded with data from Q1 -> Q2 -> Q3. Jason: Folio behaves differently in on-premise deployment vs. in a hosting environment. This will be addressed. Some features of Folio seem to be optimized for Amazon RDS Webservices. |
| 15 | Action Items | Ingolf | Many Action Items could be closed, as they related to preparing WolfCon sessions. SysOps Wiki pages need to be re-organized, as there are many many meeting notes by now. Ingolf will separate the Data Migration meetings from the SysOps SIG meetings and store older meetings in folders (by year). Progress on database communication encryption (JIRA ticket of 2019-06-28):
Some consider the feature of JIRA, that others than the author can edit the ticket description, contra-productive. The author (and other readers) don't know anymore, what the author originally intended. Maybe one can block editing permissions of the description (unless for the author) ? For others, it should be sufficient to write comments. |
| 5 | Topics for next sessions | Ingolf | Ingolf proposes to meet bi-weekly, as long as there have no agenda items piled up which will take more than half an hour. Generally agreed. Next regular meeting will be Nov 13th. |