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

We reviewed what was completed in sprint 23 and what we are going to work on in sprint 24.

Term Browser Performance

• Remote vs. Local Update from Tin

We reviewed the performance numbers with Kevin.  Kevin agreed that the Remote API will take additional time.

The performance numbers show that the remote API times are approximately 20% longer.

We noticed the the Hierarchy traversal shows the remote API is actually faster.

We suggested trying to break out the actual LexEVS call timings to see what time it takes for the call versus the browser rendering.

Tracy will look at changing her test calls (using remote) and convert to making local calls to get some timings.

Tin mentioned he was testing the terms browser with Load Runner test tool.

NCI will continue to use the local API and test the Remote API.

OBI Load Issues

• Update from Gilberto

RRF Load Issue

Brian agreed that the multiple relationship attributes were viewed as being correct, if there is a relationship back to the attribute.

Brian asked if these attributes are useful/being used? 

Brian suggested there are a few browser options for showing the qualifiers:

• Aggregate all the attributes
• Show the additional attribute information
• Don't show them at all

Gilberto didn't believe users would need to see all of these attributes.

Brian suggested to continue to load the data, but don't show it in the browser. (It's presence in the browser isn't useful in it's current state.)

Larry suggested that Kim update the browser to not display these attributes.

These attributes would still be available via the LexEVS API.

Nexxus Testing

• Delayed and rescheduled for Feb 17

This has been delayed to February 24th.

Craig will get additional details from Toky

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

• Update from Tracy

OBI was reloaded and the tree worked as expectedKim found an issue in view in hierarchy.  Kim created a JIRA issue for this.

NCI agreed that LEXEVS-1427 was finished and we can tag 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 Tracyas FINAL.

VPN TestingS2S Removal

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

• Gilberto

Gilberto will coordinate the shutdown of the site-2-sited VPN with Mark.

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.