NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

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

...

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
RobCory

Close issue 

 

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

2016.02.092016.04.10 Open

Progress

  
Scott
  • Sprint 3536
  • LexEVS 6.5 planning
  • On going Support
Cory
  • Sprint 3536
  • LexEVS 6.5 planning
  • On going Support
Deepak
  • Sprint 3536
  • LexEVS 6.5 planning
Craig
  • Sprint 3536
  • LexEVS 6.5 planning
  • Agile Admin

...

Sprint Status

 

Current Sprint  Sprint 35 36 (July 21August 04, 2016 – August 320, 2016)

LexEVS 6.4 Agile Development - Sprint Status

Tracy is working on Data deployment to DEV and QA

The indexes were created on DEV.  These indexes will need to be propagated to QA .  Tracy will be doing this move.

We closed out Sprint 35.

Tasks associated to the 6.4 release have been closed.

We will create a build that has the OWL2 loader changes.  This will be done in the next sprint

QA Tier Status

  • Test update - Tin
  • AppScan

 

  • NCI-RITM0031271: New container on QA for the LexEVS 6.4 Remote API
  • NCI-RITM0031282: CTS2 AHP on QA
  • AppScan

LexEVS Remote API and LexEVS service (CTS2) have been deployed to QA.

Larry approved the test plan.

Tin will start the testing on QA. 

Next, the AppScan will be submitted.

LexEVS using HTTPs - Update

  • LexEVS - no impact
  • CTS2 - no impact / configuration
  • Remote API - changes needed
  • URI Resolver - no impact / configuration

Remote API - the client will need to change based on SSL changes.

Because the Remote  API client will need to change, we decided to not update LexEVS 6.3.  Instead, we will add the HTTPs  ability to LexEVS 6.4 and not LexEVS 6.3.

TODO: Cory will need to add a warning message that Remote clients will need to use SSL.  This should be added the notes about how to upgrade from LexEVS 6.3 to LexEVS 6.4.

 

Java 8 and Spring 4 update - not needed

We have found that the current versions of Java 8 and our current Spring 2.x are building and testing with one issue with CTS2.  Deepak will investigate further.

Deepak is using Java 8.92 in the Docker system test scripts.

LexEVS is running Spring 2.x.  At some point this should be updated to Spring 4.

Larry suggested the Mayo team should investigate the quickest path to getting the Remote API set up for HTTPs.

Tracy suggested that we have an HTTPs fix by the end of August.  The Mayo team will investigate to see if this is possible.

At this point we will not upgrade to Spring 4.

Priority for upgrades (in this order): HTTPs, CentOS 7, Java 8.

LexEVS 6.4.0 testing will continue and will be pushed up the tiers.

We will put the HTTPs changes only into LexEVS 6.4.1.  No Java upgrade.

Jacob/Tracy/Sarah can be contacted for configuration on DEV

TODO: We need to get an announcement on this change to users as soon as we understand the impact and the wiki updated for this.

 Data issues on ProdThis has been discussed and there is a plan is in place.
 6.5 PlanningCraig will explain the changes in detail next week when the board is completed.

LexEVS External Users

Brian added a couple comments to the issue.

Scott will follow up with some additional suggestions.

  • Configuration and test on NCI DEV
  • Lexevs Remote API
  • Lexevs Service (CTS2)

 

CTS2 Testcase update 
HL7 Content Load Issue 
 6.5 Planning 
OWL2 Loader verification 

LexEVS External Users

 

Team Absences

Mayo Team

  • Deepak - Sept 1-6?, Sept 5
  • Cory - August 5, 12, Sept 5
  • Scott - Sept 5
  • Craig - August 24 -29, Sept 5

...