2023-07-14 Sys Ops & Management SIG Agenda and Meeting notes

Owned by Ingolf Kuss
Jul 14, 2023
3 min read

Date and time

10-11 EST

https://openlibraryfoundation.zoom.us/j/591934220?pwd=dXhuVFZoSllHU09qamZoZzZiTWhmQT09

Topics

Attendees

TimeItemWhoNotes



Discussion 1

Data Migration with FSE Migration Tools and Apache Airflow

  Ingolf: I observe long times when I post to SRS. The steps "post_srs_bibs" and "post_srs_mfhds". They take 1h 15 minutes for 13,000 records, each. Would be 36 days for 9 million records !
   Jeremy:

   Database : Using pg+pool. 1 master and 2 or 3 replicas.
   Multiple submission steps to FSE migration tools in parellel, 4 steps, through airflow.
   Airflow: 4 Dags; each dag runs an instance of FSE migration tools. 2-5 seconds per 250 records; 48,000 records in 10 minutes.
   9 million records took 30 hours.
   There are 2 or 3 Okapi instances
   Jeremy: I would check Kafka; it fills up the Kafka cue, it ran out of space.
    electronic holdings have specific data; these are requirements that we specificly have.
   

Ingolf: I am running on a single VM (40 GB RAM) on a VMWare cluster. The database is on a separate machine (24 GB), not clustered. Not running submission steps in parallel, 1 instance of Okapi.





Discussion 2

Ingolf: Creation of Stripes in a Docker container fails in platform-complete Nolana HF#1; can't figure out why. See my posting in #sys-ops. Error message is 

cd platform-complete
git log 
commit 6f07e13809763c1947bc735b6caf3b4f8c8bc9d3 (HEAD, tag: R3-2022-hotfix-1)
Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Date:   Mon Apr 17 14:31:58 2023 +0200

    Update folioorg/mod-invoice Docker tag to v5.5.1 (R3-2022) (#2405)

    * Update folioorg/mod-invoice Docker tag to v5.5.1

    * [CI SKIP] Updating install files on branch

    ---------

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: jenkins <folio-jenkins@indexdata.com>

commit fe7e90d04571475d48e5ae9394bfa4b1a520b4b2

docker build -f docker/Dockerfile --no-cache=true --build-arg OKAPI_URL=https://mig-demo.folio.hbz-nrw.de --build-arg TENANT_ID=mig -t stripes .
...
Step 10/21 : RUN yarn build-module-descriptors
 ---> Running in e2112ae9d89f
yarn run v1.22.19
$ stripes mod descriptor stripes.config.js --output ./ModuleDescriptors
StripesCliError: Unable to load stripes.config.js
    at loadStripesConfig (/etc/folio/stripes/node_modules/@folio/stripes-cli/lib/cli/stripes-config-middleware.js:13:11)
    at middleware (/etc/folio/stripes/node_modules/@folio/stripes-cli/lib/cli/stripes-config-middleware.js:35:23)
    at /etc/folio/stripes/node_modules/@folio/stripes-cli/node_modules/yargs/build/index.cjs:1:4722
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command '/bin/sh -c yarn build-module-descriptors' returned a non-zero code: 1

I only made changes to stripes.config.js, Dockerfile and nginx.conf.  I only changed the OKAPI_URL, tenant_id, server_name and costumization (welcome message, branding).

Steffen: I will try to reproduce.





Call for Dev Ops  (From TC, Dev Teams)Ingolf

Please consider having someone from your institution work in the hosted reference environment team. This could be part of a contract between your institution and FOLIO. It will definitely help that person getting into the details of FOLIO hosting and build up DevOps and system operations skills. This will certainly be of benefit to your institution, especially if you plan to be self-hosting. It could be on a part-time basis. Required skills are a knowledge of  Ansible scripts and with building up Vagrant machines.
Here is a detailed "job" description:
Required skills: Ansible, Jenkins, GitHub Actions, AWS, Vagrant, Okapi/FOLIO
Tasks:

  • monitoring of #hosted-ref-envs Slack channel and addressing env build failure and helping to troubleshoot problems raised by developers
  • maintenance of the snapshot branch of the platform-complete repo: adding new modules, upgrading existing ones, removing deprecated ones
  • support and maintenance of module deployment pipelines in Jenkins and GitHub Actions
  • support and maintenance of environment deployment pipelines in Ansible and Jenkins
  • creation of release reference environments
  • creation of release Vagarant images

I could be the contact person if your institution is interested. Thank you for taking this into account.



WolfCon regsitrationIngolf 

Please register for WolfCon if you have not already done so.

Admission for virtual attendance is free!

Register here: 

https://openlibraryfoundation.org/about/wolfcon/upcoming/





WolfCon Session ConfirmationIngolf

 Our session has been confirmed by the WolfCon planning team:
ID 18
Title Platform Decisions for FOLIO Self-Deployment on Kubernetes
Start Date & Time
8/24/2023 1:30:00 PM
End Date & Time
8/24/2023 3:00:00 PM
Type/Track
FOLIO
Description
This session is meant for systems administrators who plan to self-deploy FOLIO in a general Kubernetes environment (private cloud or public cloud). We will share experiences and give recommendations and insights for self-hosting FOLIO. We will address aspects of needed infrastructure and a usable common repository for Helm Charts.
Organizer Ingolf Kuss
Speakers
jroot@library.tamu.edu, florian.kreft@lrz.de, tobias.stumpp@uni-tuebingen.de
Room
Room 701
Audience
Adopters, Potential adopters, Developers, Sys Admins, Dev Ops
Session Type
Working Meeting


WolfCon 2023 Schedule is out :

https://wolfcon2023.sched.com/





Next meetingIngolf

Ingolf will be out on leave of absence until and including Aug 1st.

Next meeting will be Friday, Aug 4th.






Topics for future meetings:






Status of Integrations



Action items

  • Type your task here, using "@" to assign to a user and "//" to select a due date