2019-04-26 Team Lead Meeting

Date

Apr 26, 2019

Participants

  • @Ashraf

  • @Clay Crosby (Unlicensed)

  • @Josh Zamor

  • @Wesley Brown

  • @Craig Appl (Unlicensed)

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

15 min

General Discussion

Wes

https://openlmis.atlassian.net/wiki/spaces/OP/pages/501580018/The+3.6+Regression+and+Release+Candidate+Test+Plan+work+in+progress

Reporting capacity trip:

  • May 6, 7

  • Loose Agenda:

    • Supserset

    • Deployment

    • Ingesting Data into Nifi

    • Mapping between OpenLMIS database and reporting database and walkthrough of the KPI indicators available on the reporting stack

    • Hands on exercise on how to develop a new report/dashlet for ad hoc requests received from MoH

  • Plan:

    • 9-5 with an hour lunch break starting at 12:30 or 1PM

    • Day 1:

      • Morning: Level Setting and Dev-ops

        • Deploying and setting up the reporting stack on their local machines as well as on a dedicated server)

        • Hand-on exercise

        • Review docker containers

        • Define each service, their roles and starting each service

      • Afternoon: Nifi

        • Overview

        • Requisition connectors/flows

        • Scenario:

          • Deploy reporting stack and setup reports

          • How would you take what was done for requisitions and port it over to stock management

        • Discuss common errors, troubleshooting and addressing them

    • Day 2:

      • Morning: Superset

        • Overview

        • Interactions between Postgres and Superset

        • Review the process of setting up connections to the database, queries and getting information into charts

      • Afternoon: Review of FHIR integrations

        • Review the process of creating measures, the thinking behind it and showing the information

        • Identify how information gets pulled in from OpenLMIS Requisitions and measure reports get generated

  • Questions:

    • Dedicated instance of the reporting stack (nifi, nifi registry, superset, etc) to play with?

      • We don’t want to affect uat or other shared OLMIS instances

      • OpenLMIS may need to spin up a new instance (AWS) and setup Nifi and (maybe) Regsitry via terraform in preparation for the training

  • Comments:

    • FHIR may be too specific for the audience - We should expect to have to spend significant time on Nifi and Superset.

    • We should level set at the beginning of the workshop each day.

 

10 min

Ona

Clay

Working on fixing issues with the docker container setup and integration

Have been testing the updates to the FHIR server (in isolation)

Will start the end-to-end tests early next week - Monday!

Clay - Phasing out at Ona during May, requests should go to Craig alongside Clay. Clay moving on in June

10 min

JSI

Ashraf

 

10 min

MtG

Sam

Had the last retrospective… the team is no more

10 min

(Mind the) Parrot

Sebastian

Regression testing and releasing

Also working on several code freeze tasks

Closed on functional test and one contract test

Working on some tests that have been randomly failing

Could also help with testing the reporting stack

Action items

@Wesley Brown to instruct attendees of the reporting training to download the docker images beforehand, if possible
@Clay Crosby (Unlicensed) to provide names (or whatever) to the docker images that are required
@Josh Zamor To help set up of the shared Nifi and Nifi Registry instance
@Wesley Brown Cancel meeting next week

Decisions

OpenLMIS: the global initiative for powerful LMIS software