NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint Status

Current Sprint - Sprint 23 ( February 04, 2016 – February 17, 2016 )

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint23

Craig reviewed what is needed to exit phase 4 (core Lucene development) and what will need to be worked on in phase 5.

Craig also reviewed the roadmap.  We added one more sprint to phase 4 to finish up all of the issues.  Also, deployment and documentation will happen concurrently.

Nexxus Testing

  • Delayed and rescheduled for Feb 17

We haven't heard back from Toky yet.

TODO: Craig to get the latest status from Toky on the scheduled testing.

6.4 Install on Dev

  • Update from Craig

Kim noted that testing from his term browser to DATA_QA (remote API) doesn't work.  But it does work on PROD (remote API).

NCI is considering moving from the local LexEVS to the LexEVS remote API.  They need to first evaluate performance between the local and remote API

Tin mentioned that he will do some performance testing will be done by next Monday.

6.3.0.2 RC Testing with Term Browser

  • Finding updates from Jason/Kim

Kim found an issue in view in hierarchy.  Kim will create created a JIRA issue for this.

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-1627

This is a different issue than the namespace issue that was fixed for 6.3.0.2 RC1.

Scott will look into how to create complex properties for Tracy.

VPN Testing

  • Update from Scott and Cory

LexEVS 6.4 VPN Analysis 

Based on our testing, we found that the Site-to-Site VPN was a bit slower than the software VPN. 

Additionally, the software VPN is more versatile in it's usage (don't need to be hardwired, can connect to multiple DEV servers at NCI).

LexEVS External UsersNo updates.
6.4 Deployment

How to make this more DevOPs like to streamline testing:

  • Run queries against the API ahead of time before handing it over to QA
  • Mayo to test with Junits and to run against the latest terminologies from NCI.
  • NCI to remove some of the queries against automobiles and and do testing against the live data.

TODO: Create a deployment wiki page to keep a running list of tasks we want to do for deploying 6.4.

...