2024-05-15
Performance Issues
Jan Flowers - working on finding “real-world” type data set for using in testing
other possible pathways - work with Palladium to work real time on troubleshooting together or via VPN, synthetic data (pros/cons)
Org Administrator - will follow up with Antony to determine pathway for troubleshooting their issue they reported
Tracking/Prioritizing
Can we make an Epic at least? Grace is tagging
Org Administrator making O3 chattiness Epic
How do we track the performance issues that are being reported
How do we make sure we are creating tickets for the performance issues we want to prioritize and focus on resolving; measure/track/target to resolve
E.g. Locations thread, supposedly fixed with indexing fix and closed, but with recent versions of Tomcat there is a noticeable slowness - is there a ticket for this and is it assigned to be addressed?
We are not in a situation where there is no actionable performance issues - Tomcat issue, and “chattiness” from O3 for Palladium
Paul Biondich - can Daniel be responsible to driving the troubleshooting and resolving of OpenMRS performance issues
Daniel - challenges in troubleshooting to get to the point of creating epics/tickets
When Daniel can’t move something forward, should turn to Paul/Jan/Burke to help unblock and problem solve
Create momentum through shared responsibility for solving problems - holding folks to commitments for follow up, pinging when someone doesn’t follow up, etc.
Billing/Stock Management Module
Org Administrator - working with ___(?) to generalize module that was harvested from Banda Health
Docker Images for recent JDKs
raff - JDK 11 and 17? Ready for the master build, will backport for 2.6 and 2.5 release lines
Cloud hosting architecture
Looking into cluster containers and drafting architecture and approach for cloud based deployment of OpenMRS3, started talk post - waiting for feedback; will start R&D on this approach next week
MVP definition - request for OpenMRS to be run on multi-tenant environment
multiple instances for multiple facilities in a cluster, via kubernetes with centralized platform for deployment with monitoring
advising for AWS, Azure, etc deployment
not just about scaling the API, but also about the backend db - kubernetes supports the cluster of db, instances, but more work needed on the API
Goal: get to the point that this is a “best practice” approach and is a straight forward recipe/lift for implementing
Auto de-activation of users / timeouts - isaiahmuli
Reviewing code and sorting through questions for Daniel
Need guidance on how improvements are made at code level, pointers to documentation
Org Administrator use forums (talk and slack) as much as possible in public way so that others can help support (not just daniel directly), also improves knowledge base for others to get set up; edit documentation, point out gaps and problems, as you go through things
PM support for Platform/Backend
Can jmwiinga spend some time helping here? Jeremiah and Jan to follow up to determine how he could help