Page History

Close issue 

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

• Sprint 30
• Sprint 31 PlaningPlanning
• On going Support

• Sprint 30
• Sprint 31 PlaningPlanning
• On going Support

• Sprint 30
• Sprint 31 PlaningPlanning

• Sprint 30
• Sprint 31 PlaningPlanning
• Agile Admin

Sprint Status

Current Sprint -  Sprint 30 (May 12, 2016 – May 25, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint Status

NCI has deployed LexEVS core API and LexEVS Remote API.

Tracy mentioned that she will test from her client.

Kim has been testing with the remote API. He is running into the issue related to LEXEVS-957. The Mayo team will discuss possible solutions to this issue.

Discuss Issues

• LEXEVS-1729
• LEXEVS-1730
• LEXEVS-1731
• LEXEVS-1732

Status#SprintStatus-Sprint30

Mayo team deployed sprint 29 artifacts and determined stories for sprint 31.

We are looking at moving to the next phase for documentation and tier deployment. We have planned 60 days for tier deployment.

We need to discuss the following next steps:

• Loader and tree extension

• JIRA items and if they need to be

• implemented for 6.4

• .

• Investigate if this is a bug that we can reproduce. If this is a bug, then we need to fix for 6.4

• There is a workaround. This issue can be completed after LexEVS release 6.4.

• Determine when to working on 6.5 work.
• Many issues have been de-prioritized to 6.5

Larry agreed that there are some loader issues that need to be worked on for the 6.4 release.

• We will need to go through the existing loader issues to determine which ones need to be completed in 6.4.

We all agreed to move the backlog issues (not including the loader issues) in 6.4 into 6.5.

LEXEVS-957 - Mapping iterators do not work on distributed.

This issue was closed and two new issues were created to better describe the issues (LEXEVS-960, LEXEVS-961)

Larry agreed that LEXEVS-960 and LEXEVS-961 should be looked at in 6.5

NCI DEV deployment updatesLexEVS core API 6

• CTS2 1.4

• .1 (6.3) snapshot deployment progress
• CTS2 1.5.0 (6.4) snapshot deployment

CTS2 6.3 - NCI will deploy to existing is installed on DEV. This hasn't been tested on DEV yet.

• Cory will create a FINAL tag on CTS2 6.3

• Cory to send a link to Tin for our online API.
  • https://lexevscts2.herokuapp.com/cts2
• Cory to send JIRA item that was fixed to Tin.

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

• Larry would like to move CTS2 6.3 up the tiers to PROD as soon as possible.

CTS2 6.4 - will deploy to a new container that is currently empty.

PIV card updates

No updates.

Kumar asked if Deepak filled out the form: VPN remote access user agreement. Cory will follow up with Deepak.

LexEVS External Users

• Updates

Gilberto mentioned that there was an app support question from a user at Georgetown University.

Gilberto pointed him to the LexEVS wiki about the LexEVS API and CTS2 API.

• (1.4.1) and place the artifact on the NCI SFTP site.
• Cory will also need to update the PTE to use the correct artifact naming.

CTS2 6.4 is deployed on DEV, but has not be configured yet. Mayo will work with Tracy next week to configure sprint 30 artifacts and test.

6.4 DEV Testing updates

• Lexevs API
• Lexevs Remote API

Mayo has some lexevs remote API fixes that will be in the artifacts we create from sprint 30.

Kim will be able to test these fixes next week.

6.4 Deployment strategy

Mayo's server doesn't have a public URI resolver anymore.

The lexevs CTS2 service requires to connect to a URI resolver in order perform the unit/integration tests. This forces the developers to have a local URI resolver to connect to in order to build.

We were asking if NCI has any interest in hosting a public URI resolver instance.

Larry was asking if there has been an appscan on their URI resolver. We don't recall specifically if there was one and agreed it would be good to have one done on their current instance.

LexEVS External Users

• Updates

These seem to happen when indexes are deleted and the container is still running and holds a reference to them.