NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Sharma, DeepakMayo x
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C] Sarah ElkinsNIH/NCI [C] x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
Rob

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
Craig

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

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open

Progress

  
Scott
  • Sprint 28
  • On going Support
Cory
  • Sprint 28
  • On going Support
Deepak
  • Sprint 28
Craig
  • Sprint 28
  • Agile Admin

...

Sprint Status

Current Sprint -  Sprint 28 (April 14, 2016 – April 27, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint Status

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.

Status#SprintStatus-Sprint28

LexEVS LexEVS Compatibility

  • Remote service and client jar migration
Cory will add notes to the wiki that describes the changes.

LexEVS 6.4 Remote Service and Client Updates

caCore legacy code was mentioned and it was suggested that we should remove any caCore code.

Mayo will need to prioritize this work to determine where it will fit into our schedule. 

TODO:  Craig to create a JIRA item to track the removal of the caCore code

Feature request to get qualifiers on properties (Metathesaurus)

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

  • 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. 
    • CI Server
    • DEV Server

    CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB.  This is being investigated by Mayo to see if we can get this working locally.

    Scott noted that our Mayo Jenkins server is running on a system that has 8 cores with 32 GB of memory.

     

    DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.

    There is a new 6.4 DEV container that Jacob is working on getting deployed.

     

    NCI testing - NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.

    NCI will also test the runtime API and Tin will look at performance to compare

  • 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

    .

     

    Jason asked when the remote API will be available.  We suggested that it should be delivered by the end of sprint 29.  We will need to verify performance is still acceptable prior to releasing it to NCI.

    CTS2 and jQuery Example Follow upKim was running into a cross site scripting issue.  Scott suggested using a JSONP call to resolve this issue
  • 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.
    LexEVS External UsersNothing to note.

    ...

    Jira
    serverNCI Tracker
    columnskey,summary,type,created,reporter,priority,status,versions,fixversions
    maximumIssues20
    jqlQueryproject = LEXEVS AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >=2016-0304-30 13 AND created <= 2016-04-06 20
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    ...

    Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryproject = LEXEVSCTS2 AND created >= 2016-0304-30 13 AND created <= 2016-04-06 20
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    ...