2017-09-05 Meeting notes

Date

7am PST


https://meetings.webex.com/collabs/#/meetings/detail?uuid=M16YTR77R8TCQ43VT8N97WG006-3O29&rnd=113092.13628

Toll: +1-415-655-0001

Number:  197 398 008


Attendees

Goals

  • Followup on OpenLMIS v3.2 release - bug OLMIS-3130?
  • Q&A session on Performance Tips document
  • UI Extensible patterns

Discussion items

TimeItemWhoNotes
5mOpenLMIS Ref Distro 3.2 release

Josh

  • Thanks all
  • OLMIS-3130 bug
  • Any other notable bugs in release?
    • Currently starting up with the refresh db profile takes 2 hours for Malawi. First hour is the permission string generation ( OLMIS-3131 - Getting issue details... STATUS ), the second one is Javers initialization ( OLMIS-3078 - Getting issue details... STATUS ), Javers goes through all of the 110k right assignments created. (Sebastian Brudziński: Do we need Javers on RightAssignment entity? Is this something that can change and should be tracked?)
    • The migration for permission strings requires the admin user, which Malawi deleted. What is our approach towards the admin user? Do we block deleting him or do we not use him directly in migrations? Malawi worked around this migration failure. - need to check
25mQ&A Session on Performance Tips documentJoshPlease read and come prepared to ask questions and have a discussion on the recent Performance documents, especially the Performance Tips document.
25mUI Extension Patterns followupNick Reid (Deactivated)

Notes


HTTP Caching

A question was raised on how to support etags on the frontend.  At a high level this support is:

  • Store a returned etag with the resource that's returned
  • Forward that etag in an if-none-match request header
  • Be cognizant of the cache-control response headers - though this support is still in progress.

How that's enabled in our UI framework needs guidance.


As of this writing, there are 3 resources that support etags:



OpenLMIS: the global initiative for powerful LMIS software