2025-07-15 Maintenance Handing Over

2025-07-15 Maintenance Handing Over

Introduction

  •  


Proposed handing over topics

 

  • 2025-07-15 - Infrastructure:

    • 2 bare metal servers from Hetzner

      • S1 should be managed by Maintenance team

      • S2 is managed by the Interoperability Sandbox team

    • Main server is the Ubuntu server / Docker host

      • We have plenty of services running on docker

        • Some docker services are not started automatically, so if there is a case of a server reboot - these have to be checked and started.

      • There are a few cron jobs that need to be aware of on the host machine.

        • Reset admin for demo; Resets database credentials for admin password for demo instance, it runs frequently 

        • One to pull the Docker Images everyday for the different services 

          • There is an enterprise account for GitHub and we use the GitHub Container Registry

        • Docker system prune task - done everyday to clean up docker images to maintain space on the host

      • Services running on the docker server

        • See list below under [s1 HOME directory] for folders - take note of the [deprecated] services 

      • Every time we need a new configuration for docker, we create a new directory

      • Quick note: Sometimes implementors may ask for a Demo instance on the server to show the capabilities of openIMIS (which may get created on the S1)

      • For the AI directories there were to test the AI developments 

      • One of the most important directories is the: testlink

        • testlink - is the actual DEMO instance. Hosted at qa.openimis.org and has the most valuable data on the server

        • The QA data is used in the UAT for the release and user automating

      • Question: if there is a script that automates the testing on the testlink

        • There are  backend tests for graphql and about ~900 tests for CI/CD

        • No tests for frontend yet, but planned to use Cypress via World Bank project

      • Question: on whether there is a backup of the testlink database

        • We can export test data in Excel format for a backup.

        • Currently no automated backup for the testlink

    • Network and firewall: Server Landscape

    • s1

    • reverse proxy: opnsense haproxy + Traefik

      • NGINX used to serve the static frontend React application

      • There is a docker network called proxy - it was manually created network, it is persistent and used for each docker service configuration

    • services:

      • ousehold Data,

      • reset-admin-mssql.sh [script to reset Admin password]

      • docker-bench-security

      • traefik [reverse proxing]

    • public facing

    • openIMIS Instances (to be documented in Sandbox Landscape )

    • services [deprected]

      • ai

      • database_ms_sqlserver (GIT clone of database_ms_sqlserver)

      • dev-psql-old [deprecated]

      • mwi [deprecated]

      • release-old [deprecated]

      • ai-v2 [deprecated]

      • dhis2 [deprecated]

      • healthix [deprecated]

      • nhib [deprecated]

      • bahmni-integration [deprecated]

      • meshagent [deprecated]

      • openhim [deprecated]

      • tools [deprecated]

      • cdkeys [deprecated]

      • demo2 [deprecated]

      • demo2-bk [deprecated]

      • e0_demo [deprecated]

      • dev [mssql dev, deprecated]

      • forum-discourse [deprecated]

      • mifos [deprecated]

      • coreMIS [deprecated]

      • fs [deprecated]

      • moja [deprecated]

      • release_coremis [deprecated]

      • uzbekistan[deprecated]

    • password reset scripts, daily deployments, 

 

  • Release

    • scripts 

    • check list

    • UAT testing process and support 

    • IT test

    • docker deployment

    • doc updates

 

  • Source management

    • git teams

    • git flow

    • CI

    • base concept

      • Versioned model / historyModel

      • ORM

      • cache

      • settings and security 

      • FE/BE interaction

      • FHIR facades and IG

  • business process ? (theoretically it should be done by someone else)

 

 

  • Support

    • Service Desk process

    • Jira Project and ticket

    •  

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/