2018-06-12 Meeting notes

Date

Jun 12, 2018

7am PST / 4pm CET

Meeting Link

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/737202874

Or iPhone one-tap :
US: +16699006833,,737202874# or +14086380968,,737202874#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 408 638 0968 or +1 646 876 9923
Meeting ID: 737 202 874
International numbers available: https://zoom.us/zoomconference?m=F0kj5u6u0wFxr7Xfz5NKZxl0xyLhuTPF

Attendees

@Chongsun Ahn (Unlicensed)
@Craig Appl (Unlicensed)
@Elias Muluneh
@Nikodem Graczewski (Unlicensed)
@Sebastian Brudziński
@Łukasz Lewczyński (Deactivated)
@Mateusz Kwiatkowski
@Jakub Kondrat

Goals

See discussion items

Discussion items

Time	Item	Who	Notes

Time	Item	Who	Notes
10m	Agenda and action item review
(from last meeting)	Cross-service migration	@Chongsun Ahn (Unlicensed)	Re-use run-sql Bespoke Template for cross-service migration / exemplar?
(from last meeting)	Demo data - review new findings	@Chongsun Ahn (Unlicensed)	https://openlmis.atlassian.net/wiki/x/FgB0Fg docker image size concerns due to huge CSV files?
(from last meeting)	APIs Tech Debt review	@Łukasz Lewczyński (Deactivated)	Presents results of APIs tech debt review from this wiki page Hopefully we can get feedback on the dev group. If not, bring this to the next tech committee call.
(from last meeting)	Reporting Repo Template	Ona Team member
(from last meeting)	Mobile Strategy Discussion Review	@Craig Appl (Unlicensed)

Notes

Cross Service Migration

Call out to re-use https://github.com/OpenLMIS/openlmis-ref-distro/tree/master/utils/run-sql

Everytime we want to run some SQL against the services database(s)

It re-uses the ref distro settings.env file
it has some checks
Useful esp. for migrations, eg. https://github.com/OpenLMIS/openlmis-requisition-template-migration

VLDD - Very Large Demo Data

Document:

https://openlmis.atlassian.net/wiki/x/FgB0Fg

New demo data repo (has stockmanagement line item data): https://github.com/OpenLMIS/openlmis-demo-data

Demo-data Pipeline

Each service during it's build process exports it's schema and demo data.

The pipepline of demo-data takes the schema out of each service's image

How do I add to it?

Follow the pattern in stock management
- move away from JSON demo data approach - now for a service's demo data we use the same approach that performance data used
- export the schema into the service's image
- trigger the pipeline after the build of the service (manually atm, will be changed)

How do I use it?

https://github.com/OpenLMIS/openlmis-ref-distro#performance-data

Where are we using it?

Currently only in perftest: https://github.com/OpenLMIS/openlmis-deployment/tree/master/deployment/perftest_env

Outstanding question:

How do we want to version the demo-data image?
- Milestone tagging?
- Can't semantically version it...
Do we have a need for a Country specific very large demo data set?
- Should be possible to do by extending the demo-data repo/image (docker build from) with your own data files.
Is there a developer use-case for creating published images from service's branches?
- Might want it for perf data

API Review:

Please review the API review and provide any new feedback: https://groups.google.com/d/msg/openlmis-dev/EHSLclol_W0/1h9X-RLjAgAJ

Next step is to create work to address items.

Reporting folder

https://github.com/OpenLMIS/openlmis-ref-distro/tree/master/reporting

OpenSRP interop - Mobile

Decision was made to build out stock/inventory in OpenSRP
Technical dive was done on SIGLUS, however team decided it was too risky in budget and time.
OpenSRP in Modular, so the stock mgmt is independent - though you'll still need an OpenSRP server.
SIGLUS documentation is available and decision log is on the wiki: https://openlmis.atlassian.net/wiki/x/4gBMFQ
Wed this week @Craig Appl (Unlicensed) will have further requirements doc available for review.

Locales

In UI date-time components we don't have timezone capability, and in reports we need to make sure we display in the system/user profile timezone.
No one's done an audit yet.
This epic is to go through the user-facing displays and ensure that we're using dates and times correctly.
OLMIS-4834: Make OpenLMIS use a consistent locale (timezone, currency, etc.) in UI/ReportsDone
Document on business dates and instants: https://openlmis.atlassian.net/wiki/x/ZgE_Bg

Action items

@Sebastian Brudziński create tech debt ticket to add docs on cross-service migrations to developer docs -

OLMIS-4914: Cross-service migrations developer docsTo Do

Team please provide feedback to @Łukasz Lewczyński (Deactivated) and @Craig Appl (Unlicensed) on API review doc, otherwise tickets will be made to fix: https://groups.google.com/d/msg/openlmis-dev/EHSLclol_W0/1h9X-RLjAgAJ