2016-04-19 Meeting notes
Date
Apr 19, 2016 PDT & EDT
4-4:50pm PDT
7-7:50pm EDT
20 Apr 2016 7-7:50am Beijing / CST
Attendees
@Josh Zamor (Deactivated)
@Elias Muluneh
@Jeff Xiong (Unlicensed)
@Rich Magnuson (Deactivated)
@Jake Watson (Deactivated) - N/A
@Chris George (Unlicensed) - N/A
@Ben Leibert - N/A
@Chongsun Ahn (Unlicensed)
Pengfei
Meeting Link
Join by phone:
Dial phone number and enter the Meeting ID (30957362) when prompted
- Toll: +1 201-479-4595
Goals
Recap architecture workshop
Share technical spike findings
Discussion items
Previous meeting: https://openlmis.atlassian.net/wiki/x/F4C-Ag
Time | Item | Who | Notes |
|---|---|---|---|
5min | Call setup & agenda review | Josh |
|
| share spike findings from Seattle | Josh? |
|
| share spike findings from Wuhan: infrastructure (docker) | Pengfei |
|
| Possible: community updates? ...
|
|
|
Meeting Notes
Shared details on spikes:
spring boot + data REST: https://github.com/chunky56/ol-rearch-poc
Web Modularity: https://openlmis.atlassian.net/wiki/x/DgDpAg
Docker for Services: https://github.com/cuipengfei/Spikes/blob/master/docker/workflow_plan.md
Some questions were discussed:
What's a good way to handle credentials across docker images?
environment variables and docker compose file
host mount the secrets in
part of the provisioning with Chef / Ansible
more?
How do we wire the UI together? e.g. if someone wants to add a new attribute to a facility, how would that be added to the administration screen?
could do more CMS type system, however it may not keep our look and feel / be clunky
It seems like a real common use case, but we've also said the UI is a reference UI. seems like a question we need to work on more.
Action items
OpenLMIS: the global initiative for powerful LMIS software