Page History

• Working on templating starting
  • Doing phase 1 - moved to Stage
    • Stage EVS Rest API - fixed
    • Cloud team addressing the issue
      • Held working session with systems but unsuccessful
    • Comparing tomcat 9 with tomcat 8 to find differences
    • Working on Dev and QA
  • In progress: implement file-based template storage
    • Code completed - responding to Unit tests

Tomcat 8.5 is EOL - risk if new vulnerability discovered

• Oracle Java 8 - still being used complete on DataQAStill present on other servers, in $PATH
  
  • Java 17 being added next week
  • Current proposal is to not push to DataQA, let it retire
• Need to check on Processing Server - check with Chao
  • libraries still Java 8 based - Corretto?
  • Need Java 17 installed on the server?
• FTP1 has .bash_history issue - file removed but recreated itself; working with Brian Gurganus
  • Deadline of one month from now to resolve.
  • Not a real .bash_history - was originally created in 2016. Zombie

OBJECTIVE 

• Build scheduled report or export to document - Discovered not available on gov cloud. Will need to come up with operational procedure
  • Manish will follow up with DataDog
• Data dropping off after 30 days. Contract adjustment being pursued that will store 45 days of data.  This will allow us to run our monthly reports without having to dive into the archive.

• Documentation is in SharePoint: EVS Documentation > LexEVS Documentation > Sunsetting LexEVS (link)
• Setting up Jira tracker for retirement work - SUNSET https://tracker.nci.nih.gov/projects/SUNSET/issues/SUNSET-4?filter=allopenissues
• Spreadsheet Sharepoint Task Spreadsheet

We have an initial work breakdown structure (WBS) as follows

ORGANIZATION 

• Checklist:responsible: Mark 
• Scheduleresponsible: Mark 
• Documentation:responsible: Tracy 
• Training and Hand-off:responsible: Mark 
  

COMMUNICATION 

• Communication Planresponsible: Mark 
• Link Migration, Redirectionresponsible: Tracy 
• Banners:responsible: Scott (will be used closer to Sept) 
• Announcementsresponsible: Mark (Lori, Liz) 
  

OPERATIONS 

• Data Processing  responsible: Tracy -> Mark, Chao, Eric 
• Metrics, Stats Dashboardresponsible: Tracy -> Mark 
• Resources (github, maven)responsible: Tracy 
• Data Deploymentsresponsible: Tracy 
• Infrastructure, Jenkins, etcresponsible: Tracy 
  

CODE 

• Dependency idresponsible: Scott, Tracy, Andrew 
• Code Reviewresponsible: Scott, Tracy, Andrew 
• Stable Java 17 baseresponsible: Scott, Tracy 
• Report Exporterresponsible: Andrew -> Scott 
• CTS2responsible: Tracy 

1. A detailed checklist and plan will be sent out on Friday. It use the above WBS, with additional details/actions, etc.
2. We will have a meeting scheduled for next Tuesday (once Chao gets back to review) - will work on the detailed checklist as a group (add corrections, updates, suggestions, etc).