Child pages
  • 2016-01-21 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

In person

Courtesy, please

If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.

Interactive meeting - Adobe Connect

  • We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at http://connect.iu.edu/omrsdf. For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.

By telephone

  • US telephone number: +1-888-510-4073
  • Access code: 24222#

By Browser

Chat/IRC

  • Chat is available in the Adobe Connect meeting room (see above).
  • A backchannel meta-discussion during the meeting also occurs on IRC.

 

Agenda

  • Quickly review previous meeting minutes (5 min)
  • ThoughtWorks Update
  • Review next meeting agenda

Minutes

 

Attendees
  • Jamie Thomas
  • Bharat Akkinepalli
  • Tim
  • Daniel Kayiwa
  • Burke Mamlin
  • Darius Jazayeri
  • Wyclif Luyima
  • Karl Wurst
  • Gurpreet Luthra
Agenda/Notes
ThoughtWorks Update
  • Bharat presetned on Bahmni
  • Using CentOS and yum to install
  • yum install openmrs
  • yum insatll bahmni-emr
  • yum install bahmni-lab
  • yum install bahmni-erp
  • Ansible
  • All install locations are in /opt folder.
  • And each component has its own embedded tomcat service.
  • Daniel: what are the advantages/disadvantages of this?
  • Bharat:
  • isolation is a big advantage
  • enables easier one-click installation, given different possible configurations
  • splitting up the logs
  • has made it easier to connect to tomcat via JPDA for debugging
  • disadvantage is that the RPMs are bigger
  • Apache is used with letsencrypt for automatic SSL config and openmrs/bahmni are reverse proxied through httpd
  • Added "Program Enrollment Attributes"
  • also built a web service for thi
  • will be moved to openmrs-core (when release timeline allows)
  • Bahmni blog
  • Soon we'll be publishing the Bahmni roadmap (publicly so everyone can have visibility)
Questions
Is there common code with the multiple embedded tomcats which could be separated into a separate rpm and so the total package size would be smaller.?
  • Neflix nebula plugin
  • In theory, if someone wanted to have the "smallest possible install for their chosen configuration" then they could splice together different commands from the bahmni ansible playboods, and build their own custom RPM, right? (but this is not recommended)
  • True
Are the modules bundled in the war file?
  • Module omods are available at /opt/openmrs/module
  • and they are bundled in the bahmni-emr RPM
How do you do upgrades?
  • one version of each RPM for each release
  • so you would do "yum remove" and "yum install"
  • yum update does not work at this time (because of a limitation in the nebula plugin, or yum-gradle)
What about config files?
  • Config files are removed if you yum remove
  • Config file & database backups can be provided as inputs
  • The database stays around (during upgrade) because you haven't removed mysql/pgsql?
  • True. The database stays if you yum remove & yum install
Why CentOS (and not Ubuntu)
  • CentOS was being used by Bahmni when we started
  • Could support deb packages as well, so could support apt-get as well in the future

 

TODOs

Outstanding TODOs  (${entries.size()} issues)

Summary Assignee Created Due
Loading...
Refresh

Create a TODO: http://go.openmrs.org/todo

Transcripts

  • Audio recording of the call: Listen online or download (available after the meeting)