NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 7

changes.mady.by.user Benson, Mark (NIH/NCI) [C]

Saved on

compared with

New Version Current

changes.mady.by.user Benson, Mark (NIH/NCI) [C]

Saved on

Key

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

...


SYSTEMS
EVS transition to virtual machines

STATUS: We are waiting to switch STAGE from on prem to VM once PROD server is ready; so we can switch both PROD and STAGE at same time . 

Systems

 BANNER

  • There is a request by CBIIT to do a test run of putting a banner across all applications, including EVS. Would happen within firewall first. 
    • Injection approach
    • Waiting to hear back from Systems regarding info for scheduling


CONTACT FORM SPAM

Contact Us page is being spammed

  • Possibly drop form and provide email to systems for forwarding ?
  • Server was scanned, and is not infected.
  • Any additional work is on us.
  • (we're not going to be shut down)
  • Ticket closed this morning


JAVA 17

Explore Java 17 update on servers

We had a meeting last Fri (Jan 5) (NCI-RITM0497500)  with Systems.

ACTION: Will be meeting with Systems to decide next action for testing, and to get estimated costs, etc.

ACTION: which jdk, notably for windows, reply to Kim. Answer: Corretto Java 17.


CENTOS 7 RETIREMENT

Our servers are running CentOS 7, which is being retired by Systems in June 24.

We need to develop a plan to address the issue.

  1. I'm talking with Amit Mukherjee about how they are addressing this
  2. I'll be getting more information from Systems after the next meeting.



LEXEVS UPDATES

Monthly Planning and Focus

Completed Sprint - Sprint 215 (Dec 8- Jan 2) - LINK TO Jira Spring 2165

Current Sprint  - Sprint 216 (

For the month of December 2023, the Mayo group is planning to:

  • Complete Report Exporter banner


  • Improvements, Refactoring Code Debt, Feature development:
  • Examine feasibility of Java 17
    • BACKGROUND: a small number of LexEVS components (aka dependencies) are being phased off of java 8 (or are no longer being supported on java 8).  We ideally want to use a current version of those components (dependencies). IF the current version of that component is only supported on Java 14 or later (just as an example), then we would have to migrate the ENTIRE LexEVS stack to Java 14 or later. (Note that the current Java version is Java 21 LTS, and the most popular non-LTS version is Java 14). So there is a risk that a vulnerability is found in the older version of the component/dependency and we would have to either migrate everything quickly to a new version, or not use that component (which might not be possible), or shutdown LexEVS entirely. Note that there are certain versions of Java which are "long-term support" versions - meaning that they will be supported for several years beyond non-LTS versions. LTS versions are Java 8,  Java 11, Java 17, and Java 21.
    • OBJECTIVE: find out what would it be like to upgrade from Java 8 LTS to Java 17 LTS.  How hard would it be? How long might it take?
    • LEXEVS-5373Investigate Upgrade of NCIt Browser to Java 17
  • DataDog

ACTIONS

  •   


Technical Debt remediation

LexEVS Code Debt Refactoring

  • Coding complete on lexevs services - except for isolated dependencies
    • Java 17 work ready for NCit Browser 
  • CTS2 - Working to update Jakarta - linked to Java17
  • Dependabot notice to update jQuery - ready for Dev


Report Exporter
  • Banner changes being implemented  - in progress
    • May be moot with centralized approach
    • Systems did implement config change - currently being tested on Dev
  • Working on templating - Need user feedback for phase 2
    • Demo feedback implemented
    • Need to make more dynamic - load values from external source
    • Will need feedback from users to provide template requirements
  •  Work with Mark to setup communications with Lori

Andrew discussed banner progress with Systems group configuration change (however the fix needs to be finalized). However, this is very low priority.

Feedback form

  • Need to research approval procedure, Mark was asked to reach out to OCPL
  • Andrew supplied copy of survey form from RE

ACTION: (from Lyuba) We don't have any indication that the tool is working? Like . Can we get an indicator, like a spinning circle, etc.


Security


Statistics Dashboard

OBJECTIVE 
Complete Migration of Statistics Dashboard from SumoLogic to DataDog by March 2024.

STATUS

Status meeting has been scheduled for every Friday

ACTIONS

  •  Check on status of collectors on other servers than evsexplore - Tracy


Comparison/Mapping Tool

On Hold

AWS Cloud to be in Separate Account

Waiting on AWS team

Team Absences


Mayo Team - 

MSC - 

Leidos - MLB out next Wed (Jan 17) morning

QA - 

Gov - 



EVS SERVICE AND ARCHITECTURE GROUP UPDATES
EVS Service and Architecture Group
  • Looked at logging on upper tiers;
  • fixes are in next release


DATA UPDATES
Data
23.12d - ; and working on monthly vocabs

BROWSER UPDATES

Browser

2 tags went to production today

  • Some ehcache work needs to be implemented
  • Consider changing browser behaviors to limit abusive searching
    • Updating/adding/changing cookies might require security review

Note to QA: EVS Explorer and API are higher priority over the tags.



QA UPDATES

QA

Completed sanity testing for Dec 23 data deployment, all browsers, on QA and lower tiers.

Currently working on EVS Explorer and API, target is to finish first iteration this week, next iteration next week. Final target is Jan 26th for PROD deployment.
Thanks for clarifying priorities.


TERMINOLOGIES LIFECYCLE REPORT

Terminology Updates and Schedule 


Mark Benson TPM Update
  • No issues

...