2022-12-16 - Sys Ops & Management SIG Agenda and Meeting notes
Date
Topics
Attendees
Time | Item | Who | Notes |
---|---|---|---|
5 | Welcome | Ingolf | |
Documentation topic |
Single Server fresh install: Ingolf updated single server MG documentation : Single server or PC: fresh install | FOLIO Documentation. It didn't change much from Lotus. Single Server upgrade: This needs to be written for MG; usually Ingolf does this. But: Do upgrade prescriptions necessarily be a part of the "Getting Started" documentation ? Kubernetes example: Jeremy will update Production System to Nolana in 2023 and commits to updating the K8s documentation ; Jason also commits to update the relevant files in the K8s documentation The K8s files need updating to Lotus/Morning Glory. The procedure is the same, just the yaml and json has changed for versions. Vagrant boxes: The link therein points to https://github.com/folio-org/folio-ansible/blob/r3-2021-release/doc/index.md and this also needs an update. Who maintains github.com/folio-org/folio-ansible ? Last update is from Feb. 2022. Customizations: This probably doesn't need much of an upgrade. "Settings" section: Many sub-topics. Some of it is SysOps-stuff: It's part of the platform. At some institutions, librarians configure this. At TAMU it's been a mix of system operators and librarians. They do stuff in the Folio UI or "curl" it in. At TAMU, after the reference data has been put it, it is being largely handled by Jason. Jason: At a certain point it will stabilize as the platform does. And it will just need to be updated sparingly. But I will work on my K8s stuff and input things needed for the Settings/customizations part. Ingolf: If SysOps find errors in API documentation dev.folio.org or want to propose different parameters in https://hub.docker.com/u/folioci/, they should also contribute. Tipps & Tricks section: Individual Apps - Information, Tips, and Tricks some of it is in docs.folio.org, some is not. Potentially less related to Sys Ops. Release Notes: Sys Ops might engage earlier in the Release Process and contribute to the Release Notes. Question of time and availability. | ||
miscellaneous | Nils: Deployment of modules without using Okapi: docker run -d -p <PICK-A-PORT>:8080 -e DB_PORT='5432' -e KAFKA_PORT='9092' -e KAFKA_HOST=<YOUR-KAFKA-HOST> -e DB_HOST=<YOUR-DATABASE-HOST> -e DB_PASSWORD=<FOLIOS-DB-PASSWD> -e ELASTICSEARCH_URL=<YOUR-ELASTIC-SEARCH:9200> -e DB_DATABASE='folio' -e OKAPI_URL=<GUESS-WHAT> -e DB_USERNAME='folio' -e JAVA_OPTIONS="-server -XX:+UseContainerSupport -XX:MaxRAMPercentage=55.0 -XX:+PrintFlagsFinal" -e DB_MAXPOOLSIZE="50" folioorg/mod-agreements:5.1.1 (see the discussion in the support channel).
Deployment of mod-agreements and mod-licenses failed when deploying with the okapi endpoint (see the discussion in #support). Jason: They use a lot of memory, and do take a hot minute to start up. They use spring boot -------------------------------------------------------------------------------------------------------------------------------------- Nils: SIP2 - Integration edge-sip2 fails when loading a template: FTL stack trace ("~" means nesting-related): Fails Here: This is the content of /mnt/sip2-tenants.conf : { a database record which it seems to not pick up: | ||
Happy Holidays and a Happy New Year ! Enjoy your holidays. To a better 2023. |
Action items
- Type your task here, using "@" to assign to a user and "//" to select a due date