Sprint 8 Showcase

Date

Sep 16, 2016

Attendees

@Josh Zamor (Deactivated), @Chongsun Ahn (Unlicensed), @Paweł Gesek, @Jake Watson (Deactivated), @Sebastian Brudziński, @Krzysztof Kaczmarczyk (Deactivated), @Mary Jo Kochendorfer (Deactivated), @Darius Jazayeri (Unlicensed), @Nick Reid (Deactivated), @Pengfei Cui (Deactivated)

Meeting Recording

Pengfei

Pengfei shared a descriptive google doc detailing what he worked on, which included OLMIS-954, OLMIS-995, and OLMIS-993. He demoed each of these, all of which are related to the "pipeline" he's been been working on. He additionally showed us the work done on the other stories within his google doc.

The openlmis-deployment repository uses ELB to wrap/wire OpenLMIS' related services for use within a particular/specific deployment (eg: UAT, Production, etc.) OpenLMIS-Blue, on the other hand, does the same via Consul. The openlmis-deployment configuration has a VIRTUAL_HOST variable which points to a single ELB. Potentially, this URL can be changed to that of eg: a Production or UAT server.

ToDo:

Determine what the next steps should be for Pengfei. (Will do so during our Spring Planning session.)

@Pengfei Cui (Deactivated) Look into how to incorporate the build-pipeline work into UAT and Production contexts. This won't necessarily be trivial, and should address how this relates to OpenLMIS-Blue and Docker Compose.

@Pengfei Cui (Deactivated) Adopt a load-balancer and obviate the long URLs we currently have.

@Pengfei Cui (Deactivated) Determine why Jenkins/the pipelines use nearly 9 gigs of memory.

@Mary Jo Kochendorfer (Deactivated) Touch base with Pengfei about marking his stories as In Review and subsequently having Soldevelo look at them.

Sebastian

As planned we're still working within a single branch (master). For requisition repository, though, there's still more work needed before merging back into master. They have to first finish updating tests before merging, and then attempt the merge on Monday. Estimate that by mid-weak they'll have finished it.

Though it's still a work in progress, Sebastian showed off the openlmis-requisition service's code. Most if not all reference-data has been moved out is out of requisition and into the reference-data service. They also use UUIDs for reference-data now.

He also showed some of their documentation-related work. The proper documentation is generated automatically, but haven’t moved story to “Done” because a couple images aren’t showing up in the HTML page. This seems like a very minor issue. They also added a “Contribute Documentation” section to the existing docs.

Regarding OLMIS-911 - They finished removing SDR from code, created the necessary endpoints in RAML, and exposed them within ReadTheDocs.

Chris

Reviewed stories 965, 401, 1006, 862 and did a helpful walkthrough of OLMIS-965 ("Configure order file template"). We also began discussing why using CascadeType.Persist was causing errors.

ToDo:

@Krzysztof Kaczmarczyk (Deactivated) Add data validation to the functionality implemented for OLMIS-965. (We tried specifying an invalid Date format within the template, and the service accepted it. The service then tried using this during the retrieval of an Order File and choked.)

@Krzysztof Kaczmarczyk (Deactivated) Post links to github in order to better highlight what the problem related to CascadeType.Persist had been.

Josh

Showed an implementation of Products by loading tradeItems, globalProducts, a program, and productCategories.

Showed how to associate a tradeItem with a globalProduct via the /globalProducts endpoint. After doing so, he was able to access them via the /orderableProducts endpoint.

This is all described in the Medical Commodities (Products) wiki entry.

ToDo:

@Paweł Gesek Ensure that Soldevelo begins ramping up on fundamental GS1 concepts.

Chongsun

Finished up Role Based Authentication by:

Creating DTOs for many of our domain objects.
Creating Importer and Exporter interfaces which provide methods for converting domain objects to/from their DTO counterparts.

Chongsun showed off these endpoints:

/rights
/roles
/users
/hasRight (which indicates whether a specified user has a given right)

Finally, he showed newly-added filters added to the existing endpoints which allow users to determine eg: all the facilities that someone supervises, or all the programs they’re associated with.

ToDo:

@Chongsun Ahn (Unlicensed) Assign the stories that Chongsun closed in this Sprint to Pawel, who will in turn assign them to a QA at Soldevelo.

Final Notes

We’ll end the next Sprint on the Tuesday the 27th, and have the showcase the following day.