LexEVS Meeting Minutes - 2016.04.13

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Close issue 

  LEXEVS-1516 - Getting issue details... STATUS

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

• Sprint 27
• Sprint 28 Planning
• On going Support

• Sprint 27
• Sprint 28 Planning
• On going Support

• Sprint 27
• Sprint 28 Planning

• Sprint 27
• Sprint 28 Planning
• Agile Admin

Current Sprint -  Sprint 27 (March 31, 2016 – April 13, 2016)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint27

We discussed Sprint 28 work that is planned.

Larry was asking when we can deliver the first release candidate for NCI DEV.

They would only need the LexEVS core API initially (no remote service).

Priority for sprint 28 will be to get LexEVS API deployed to NCI DEV.  CTS2 changes have a lower priority.

LexEVS Compatibility

• Remote service and client jar migration

Feature request to get qualifiers on properties (Metathesaurus)

LEXEVSCTS2-35 - Getting issue details... STATUS

• Discuss 6.3 related deployment
• Discuss 6.3. and 6.4 CTS2 versions running simultaneously

CTS2 needed to be upgraded (Lucene dependencies) for 6.4.  We will need CTS2 services for both LexEVS 6.4 and LexEVS 6.3.

CTS2 service for LexEVS 6.4 can be used by end users instead of the CTS2 service for LexEVS 6.3.  There are no API changes.  However, there are dependency changes for the CTS2 services.  This results in the CTS2 service being dependent on 6.4 and will not be able to talk to LexEVS 6.3.

Larry suggested getting the CTS2 service for LexEVS 6.3 up the tiers prior to CTS2 service for 6.4.

It was decided that the CTS2 service for 6.3 will be deployed up to PROD independent of the CTS2 service for 6.4.

The CTS2 service for 6.4 will be deployed with LexEVS 6.4.

PTE for CI and DEV environment discussion

• MySQL for integration tests
• MySQL plugin for Jenkins

PTE for CI server request questions

• We use Jenkins to run unit and integration tests every time there is a check in.
• This would require a separate tier (aside from DEV, QA) for CI deploys.
• Mayo would like a MySQL plugin for Jenkins for LexEVS integration testing.

Jacob will need to make a VM request for our Jenkins instance.

PTE for LexEVS

• If Mayo installs Jenkins, they may need root access during the install.
• Jacob mentioned that the new container would run Java 8 and asked if LexEVS would run on 8. 
• LexEVS hasn't been thoroughly tested on Java 8.  This could be a substantial effort.
• Jacob suggested that we can still run Java 7 for this release.
• For the LexEVS DEV environment, the current indexes are taking up approximately 60% of the drives. 
  • Jacob suggested possibly moving 6.3 to NFS drives and 6.4 would be on the fixed drives for DEV. 
  • We may need more space for the indexes if both 6.3 and 6.4 reside on the same drives.
• Jacob will have a container for 6.4 DEV by next Monday.
• Sarah suggested that we do not need a separate ARC meeting for setting up the 6.4 DEV container.  This is an existing application with software from the existing tech stack.