Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

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

LexEVS 6.4 S13-500 Agile Development - Sprint Status

• Sprint 22 is complete.
• Sprint 23 is being planned.
• Mayo to release the Sprint 22 artifacts and deploy to Dev to enable browser testing.

CTRP Planning

• Update from Larry

• Larry sent a note to request an update from the CTRP team (Jose).
  • Unlikely that CTRP will be able to deliver requirements that will impact the 6.4 release.
  • We should plan to include CTRP in 6.5 planning.

Value Set Resolution

• Review updates from Rob

• This can be closed. The issue was associated to Max value to resolve and recompilation. (via properties files)
• Changes are on stage and will be promoting to Prod.

Status#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 created a JIRA issue for this.6.4 Performance testing

Ability to get and load all of the value sets

• Scott to provide update

• Scott has been working on automation of loading value sets.
• Search extension will be tested over the resolved value sets and over the NCI Meta.
• NCI Team to provide test cases to consider when querying value sets.
• Querying is expected to behave the same way as previous release.

Nexxus Testing

• Delayed and rescheduled for Feb 17

• Toky is going to determine the final date based on Scott's availability.

6.4 Install on Dev

• Update from Cory

• Sprint 22 artifacts to be deployed to Dev this week by Cory.

6.3.0.2 RC Testing with Term Browser

• Finding updates from Jason/Kim

• Kim was to have tested to verify the namespace issue. This has not been done yet.
• Data Dev has this installed and Kim can test.

• Testing has been completed with MySQL
• Larry suggested that we should only test on those that we know are being used (Oracle and MySQL)
• Earlier versions have been tested on the other DBs, but 6.4 should be limited.

VPN Testing

• Updates from Scott and Cory
• Update from Tracy

• Scott and Cory have been testing several times a day on both s2s and software VPN and recording performance status.
• Tracy is not seeing a delay from the office or from home. So any latency would be because of the connection.
• Rob was running eclipse with some initial UI slowness, but things then started performing fine.
• Detailed report to be given on Friday.

• Nothing to note

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).

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.