Server Landscape

Current Status

Future Infrastructure (in planning)

Principles

  • consistent production lines

  • Minimize admin costs

  • optimize performance

  • data integrity

Server-Options

assumption:

  • one server = one IP, one operating system (LINUX WindowS nAP LOCAL )

  • one cell = one instance on a server

  • no distributed resources

  • Minimal Sizing:

    • WINDOWS 2 : 4core, 16GB, root server, dedicated

    • LINUX 2 : 4core, 16GB, root server, dedicated

    • Free BSD : as virtual machine on LINUX 2 (to be verified)

Application / Line

Develop
”Feature”

Integration
”Develop”

Quality Assurance
”Release”

Demo
”Demo”

Training
”Training”

Application / Line

Develop
”Feature”

Integration
”Develop”

Quality Assurance
”Release”

Demo
”Demo”

Training
”Training”

  • github branches

feature

develop

release

main

main

  • used for

developer test

integration test

user acceptance test

current stable

customized demos / trainings

openIMIS Legacy

LOCAL

Windows 2

Windows 2

Windows 2

Windows 2

openIMIS Modular

LOCAL

LINUX 2

LINUX 2 Windows 2

LINUX 2

LINUX 2

openIMIS DB

LOCAL

Windows 2

Windows 2

Windows 2

Windows 2

DHIS2 w/ oI connector

LOCAL

LINUX 2

LINUX 2

LINUX 2

LINUX 2

DHIS2 DB

LOCAL

LINUX 2

LINUX 2

LINUX 2

LINUX 2

OpenHIM

LOCAL

LINUX 2

LINUX 2

LINUX 2

LINUX 2

OpenMRS

nAP

LINUX 2

LINUX 2

nAP

optional

BAHMNI

nAP

LINUX 2

LINUX 2

nAP

optional

FHIR (HAPI FHIR)

nAP

optional

optional

nAP

optional

PFSENS (Firewall etc)

nAP

Free bsd

Website (Drupal)

 

managed Drupal server

Discussion

  • look at loads

  • Modular doesn’t need windows server

  • managed server or root server

  • lines:

    • develop: own computers, online DB for testing

    • training: several instances on one server (same IP, different ports/ subdomains)

Draft architecture

 

Timeline

Server config based on: