Page History

Sprint Status

Current Sprint -  Sprint 37 (August 18, 2016 – August 31, 2016)

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

6.4.1 Testing on Dev and QA

• QA Verification Process

Discussion Points:

• 6.4.1 is deployed on QA.
• 6.4.1 was not deployed/tested on DEV.
• QA tier is configured for HTTPS
• HTTP requests against the remote API are working.

Decision Points:

6.4.1 Lexevs remote API HTTPS discussion

• Discuss NCI QA setup on Apache

Discussion Points:

• HTTP requests against the remote API are working
• HTTPS requests against the remote API are throwing exceptions.
• The remote API service accepts a valid, signed certificate, not a self signed one.
• At the morning meeting, NCI suggested that we could remove our HTTPS security in the remote API.
• Mayo team suggested we dig into this a bit more to see what the problem is.
• Larry/Jacob suggested that Apache should handle the security rather than the remote API.
• Scott is wondering if the certificate on QA is a valid, signed certificate. If it is, then the remote API should work fine.

Decision Points:

• Mayo team will work with Jacob to understand the root problem and determine if our HTTPS fix is the cause of the issue.
• Scott/Cory will deploy 6.4.1 lexevs-remote API to DEV to see if DEV behaves similar to what the problems are on QA.
  • Tin is deploying 6.4.1 to DEV now. (No need for Mayo to install now).
• Mayo team will discuss the 6.4.1 QA deployment with Jacob to better understand the HTTPS issue.

OWL2 Loader Discussion

• Jira
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2245

Discussion Points:

• Mayo team asked what NCI's priority is on implementing a fix for this issue.
• This issue is seen in our 6.4.1 codebase.
• A fix would be created and released as 6.4.1.1 and could be pushed up the tiers similar to all of the other loader fixes we have done.

Decision Points:

• We will work on this issue after the 6.4.1 HTTPS issue is resolved.

HTTPS document review

• End user communication update

Discussion Points:

• Remote Client HTTPS Requirements
• We will need to understand the current HTTPS issues and then this document may need to be updated to reflect any changes.

Decision Points:

Discussion Points:

• Toky had configured Jenkins at NCI for LexEVS.
• No one has continued this work.

Decision Points:

• Mayo team will contact Sarah Elkins to work with Jenkins set up at NCI

CTS2 over RMI

• Future Need

Discussion Points:

• It was mentioned that some clients at NCI may be using CTS2 over RMI.
• The Mayo team has updated the code to make this work.
• Gilberto/Tracy suggested we disable this feature and see if anyone is using it.

Decision Points:

• Mayo will create a JIRA item to remove/hide this feature.

NCI Nexus Server

• Mayo to migrate to NCI's server

Discussion Points:

• Cory/Deepak met with Sarah Elkins and she discussed options on how to move the lexevs jars to NCI's maven repository.
• Craig mentioned that the Mayo team has until the end of September to move from our Nexus server to NCI's.

Decision Points:

• Cory will work with Sarah in the next Sprint to start moving jars to NCI's Maven repository

LexEVS External Users

• Alexander
  

https://github.com/cts2/lexevs-service/issues/2#issuecomment-240205829

• Our fix worked for Alexander.
• Scott is working with him on his coding scheme mapping issues.

Multiple Loads at the same time

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2253

• This is a feature request.

Discussion Points:

• Rob/Tracy are requesting the GUI to do multiple loads of different coding schemes at the same time.
• Scott mentioned there are some restrictions with multiple JVMs and locks on the file system.

Mayo Team

Deepak - Sept 2-5

• Cory - Sept 5, Sept 8-9
• Scott -Sept 5
• Craig - Sept 5

NCI

• Rob Wynne - Sept. 1-5