Close issue
Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
- Created issue:
Create JIRA issue to remove caCore legacy code
- Created issue:
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
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, Cory | Mayo | x |
| Sharma, Deepak | Mayo | x |
| Wynne, Robert | NIH/NCI [C] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | NIH/NCI [C] | x |
| Wong, Joanne | NIH/NCI [C] | |
Kuntipuram, Kumar | NIH/NCI [C] | x |
| Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|
| Rob | Close issue | 2016.02.09 | 2016.04.10 | Open | |
| Cory | Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
| 2016.03.09 | 2016.08.30 | 2016.07.28 | Done |
| Cory | Create JIRA issue to remove caCore legacy code
| 2016.04.20 | 2016.08.30 | 2016.07.28 | Done |
| Scott |
|
| Cory |
|
| Deepak |
|
| Craig |
|
LexEVS External Users
Sprint Status
| Current Sprint - Sprint 35 (July 21, 2016 – August 3, 2016) LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint35 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
| 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
| 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.4 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 Prod | This has been discussed and there is a plan is in place. |
| 6.5 Planning | Craig 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. |
| Team Absences | Mayo Team
|
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
| None | ||||||
| Area of Interest | Details |
|---|---|
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
| Opened Date | Description | Assigned |
|---|---|---|
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 64 | Scott | To follow up on URI's on OWL2 with Harold. | on hold | |||
| 164 | Cory | Cory to add implementation to CTS2 implementations page. | 2014.04.30 | on hold | ||
| 197 | Scott | Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs | 2014.6.18 | on hold | ||
| 200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | on hold | ||
| 207 | Cory | Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only. | 2014.07.30 | on hold | ||
| 210 | Larry/Gilberto | Determine if there is a need to meet with the CTRP | 2014.07.30 | on hold | ||
| 212 | Larry | Include LexGrid XML Export as part of the 5.1 retirement notice. | 2014.07.30 | on hold | ||
| 224 | Scott | URI Resolver - Provide overview of how to access the URI Resolver | 2014.09.03 | on hold | ||
| 225 | Scott | URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver | 2014.09.03 | on hold | ||
| 244 | Craig | Plan meeting with Tracy to discuss collaborative LexEVS development process | 2014.12.03 | on hold | ||
| 281 | Scott | Try to replicate what CTRP did to break our service (retrieve a tree through CTS2). | 2015.03.25 | on hold | ||
| 282 | Mayo Team | Look into implementing graph node in CTS2 for the path to root method (and path to leaf). | 2015.03.25 | on hold |