![]() |
Page History
...
Description | Actions, Update | ||||
---|---|---|---|---|---|
NCI-SCTASK0750465 | Security team has flagged EVS stage host( nciws-p803) for JQuery vulnerability with full details as per below. | Eric asked us to remove it from lower tiers but we found no evidence of it there. It should be removed from Stage Jason sent email message to remove the jar from Stage. Appears that Systems was asking security team about location of file; sec team
ACTION: - wait till next week for update | |||
NCI-RITM0473138 | Discuss DOS strategy, tactics with Systems | Waiting on appt time for mtg/call||||
NCI-INC0779210 | NCIterms outage | Wait to watch status; ticket probably | |||
INC0779210 | OUTAGE: NCIterms outage - Wed 9/27 → Thu 9/28 | Wait to watch status; ticket probably will be closed soon | |||
OUTAGE: Outage continues: Tue 10/3 evening , Wed 10/4 | Note: there was an attack last night, Tue Oct 3 from 4:48 pm -> 5:10 pm. | Outage continues for Term Form | Note: there was an attack last night, Tue Oct 3 from 4:48 pm -> 5:10 pm. ACTION: wait and watch? |
STATUS: As decided from last week, we will wait to switch STAGE from on prem to VM once PROD VM is ready; so we can switch both PROD and STAGE at same time .
BACKGROUND:
On Friday Sept 29th, we were asked to deploy a banner on public-facing websites if the government was shutdown. There was confusion about who was reponsible for which pages - and how to do it quickly (especially if systems groups goes to bare-bones support level. While the government was not shut down, we still want the ability to handle it better in the future.
OBJECTIVE:
to be able to update public-facing pages with banners quickly and efficiently, with Consistent styling desired for all sites - in case the need ever arises again (in case of another shutdown/emergency/etc)
ACTION:
- Build responsibility list for public facing pages (Jason Lucas compiled the list)
Application | URL | Developer/POC |
Term Browser | Guidehouse/Kim Ong | |
Metathesaurus Browser | Guidehouse/Kim Ong | |
Term Suggestion Application | Guidehouse/Kim Ong | |
EVS Explore | WCI/Brian Carlsen | |
EVSRESTAPI (Swagger Page) | WCI/Brian Carlsen | |
EVS website | Clint Malone? | |
Report Exporter | Mayo/Andrew Moore | |
LexEVS CTS2 docs | Mayo/Tracy Safran | |
LexEVS CTS2 Landing Page | Mayo/Tracy Safran | |
EVS Semantic Integration Platform | ESI/Ye Wu |
ACTION:
- Benson, Mark (NIH/NCI) [C] to schedule a mtg/ discuss a possible CSS file/ENV variable for banner message and report on
Planning and Focus
Completed Sprint - Sprint 212 (Sept 4 - Sept 29) – Burndown Report
Current Sprint - Sprint 213 (Oct 2 - Oct 27) LINK TO Jira Sprint 213
(see EVSREPEXP-475 -> 483)
RMI Retirement - in progress
Unfortunately, I do not have a detailed update at this time, other than there are efforts to update the test script. I believe that the the RMI is turned off on STAGE, and the test script would test other components to verity that there are no unseen side-effects.
- Improvements, Refactoring Code Debt, Feature development:
- LEXEVS-5341 Update Spring to Spring 6
- LEXEVSCTS2-453 Update CTS2 welcome with digital sytle requirements (header, footer, etc)
- 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-5361- Investigate Java 17
- Miscellaneous bug fixes (several small bugs that have been identified over time and need to be addressed)
- EVSREPEXP-491 resolve branch-download list not being displayed on chrome browser (now FIXED)
- EVSREPEXP-433 Security issue: set-value vulnerability (in progress)
- LEXEVSCTS2-452 test_associations_subject_of call revealed hierarchy bug
- EVSREPEXP-478 Feedback form is not coming up
- LEXEVS-5252 Read an Entity by URI throwing a 302 error
- LEXEVSCTS2-431 Service resource does not populate Service name/version
- Investigate ERROR messages (both reported by Jason Lucas, and in
catalina.out
)
ACTIONS
- Benson, Mark (NIH/NCI) [C] to add JIRA ticket to debug error messages found during outage to Sprint 213
- Coding complete on lexevs services - except for isolated dependencies
- The isolated dependencies largely depend on using an updated version of Java (e.g. they are using more current Java versions. Java 21 LTS is the current version. The more popular non-LTS Java version is Java 14)
- Scott is investigating costs and feasibility of Java 17 (see LEXEVS-5361 above)
- LEXEVSCTS2-447 javax-servlet - on hold, until we update Java 17
- LEXEVSCTS2-446 spring-boot - on hold, until we update Java 17
- Work on NCIt Browser - ehcache beta on dev. Kim approves promotion (Scott)
- Vulnerable dependencies - in progress
- Red Herring: while Andrew was debugging, was getting "no results" for Concept codes – turns out it was service problems ?
- Improving unit testing remaining
- Red Herring: while Andrew was debugging, was getting "no results" for Concept codes – turns out it was service problems ?
- Ticket 487 - on Prod
- Feedback form
- Need to research approval procedure, Mark was asked to reach out to OCPL
- Andrew to supply copy of survey form from RE
- Vulnerable dependencies - in progress
ACTIONS
- Moore, Andrew (NIH/NCI) [C] to kindly explain more about the red herring, and to please demo the fix for Concept Codes
- Benson, Mark (NIH/NCI) [C] to report on info found out from OCPL on
Statistics Dashboard
OBJECTIVE
Complete Migration of Statistics Dashboard from SumoLogic to DataDog by March 2024
STATUS
The queries used in the Statistics Dashboard have been shared with < someone on migration team > (as of Sept 2023).
They are working on migrating from "SumoLogic" format to DataDog format
- SumoLogic Query:
- Data Dog Query
<note: removed images of DataDog vs SumoLogic queries, as they didn't add much to the discussion anyway >
ACTIONS
- Safran, Tracy (NIH/NCI) [C] ask how migration is going (show # of queries, # migrated, etc)
- On Hold
Waiting on AWS team
Team Absences
Mayo Team - Tracy off Oct 12, 13. In training Wed, Fri. Andrew off Oct 27
MSC -
Leidos -
QA -
Gov -
Will meet next week
23-09.d - schedule to deploy to PROD on
Will do monthly terminology week starting
Then will work on META afterwards
DECIDED: Data Deployment should continue as planned - no reason to delay.
BROWSER UPDATES
QA UPDATES
>We completed Regression Executions for the Monthly DDR for Sep '23 (23.09d) for EVS REST APIs on PRODUCTION .
>We Executed Sanity Test Sets for LexEVS Data refresh on QA Tier .
>We have executed Sanity Tests on NCIm,NCIt,TermForm for updated 23.09 Thesaurus deployment on STAGE Tier and for LexEVS Data refresh on QA Tier.
>We have completed Progression and Sanity Executions for EVS Report Exporter v1.2.0-RC3 Tag on PRODUCTION Tier (EVSREPEXP-487).
Thanks to Itendra for the helpful updates!
Terminology Updates and Schedule
Everyone is humbly asked to complete NIH Anti-Harassment training as soon.
Unless your contracting company tells you otherwise - Please check and verify your status on theNIH HHS.gov Learning Portal to confirm completion.LexEVS Technical Debt Progress
...
Technical Debt Related Update
...
Estimated Effort
...
Start Date
...
Complete Date
...
Status
...
JIRA
...
ADO Ticket
...
Technical Debt Related Update
...
Estimated Effort
...
Status
NCI-RITM0473138 | OUTAGE: Discuss DOS strategy, tactics with Systems | STATUS AWaiting on appt time for mtg/call with System Group ACTION: ask systems if it possible to have a trigger to send alert? (maybe ask systems group if this is possible) ACTION: come up with a design for message for users on how to use/access data. ACTION: brainstorm and discuss, discuss ideas and thoughts by next week. Lyuba requested that everyone to brainstorm and pool ideas and write down what we learn. We should propbably investigate what could be happening internally to the issue. (can ignore the error messages from netsparker scan)
|
NCI-INC0779039 | Hosting Application Outage - Missing or Incorrect Content for API on DEV tier. | The API on the DEV tier was having issues (not returning data) This impacted Andrew as he was working on Report Exporter; was unsure why Report Exporter was suddenly giving a blank column. (see screenshot below under "Report Exporter". Andrew filed a ticket, and the API was restarted, and Report Exporter started behaving correctly again. |
SYSTEMS | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
EVS transition to virtual machines | STATUS: As decided from last week, we will wait to switch STAGE from on prem to VM once PROD VM is ready; so we can switch both PROD and STAGE at same time . | |||||||||||||||||||||||||||||||||
Systems | BACKGROUND: On Friday Sept 29th, we were asked to deploy a banner on public-facing websites if the government was shutdown. There was confusion about who was reponsible for which pages - and how to do it quickly (especially if systems groups goes to bare-bones support level. While the government was not shut down, we still want the ability to handle it better in the future. to be able to update public-facing pages with banners quickly and efficiently, with Consistent styling desired for all sites - in case the need ever arises again (in case of another shutdown/emergency/etc) ACTION:
ACTION:
| |||||||||||||||||||||||||||||||||
LEXEVS UPDATES | ||||||||||||||||||||||||||||||||||
Monthly Planning and Focus | Completed Sprint - Sprint 212 (Sept 4 - Sept 29) – Burndown Report Current Sprint - Sprint 213 (Oct 2 - Oct 27) LINK TO Jira Sprint 213
ACTIONS
| |||||||||||||||||||||||||||||||||
Technical Debt remediation |
| |||||||||||||||||||||||||||||||||
Report Exporter | Vulnerable dependencies - in progress
EVSREPEXP-475- "Apply Digital Styling to Report Exporter" is now on PROD
Feedback form
ACTIONS
| |||||||||||||||||||||||||||||||||
Security | see JQuery issue under Systems | |||||||||||||||||||||||||||||||||
Statistics Dashboard | OBJECTIVE STATUS The queries used in the Statistics Dashboard have been shared with < someone on migration team > (as of Sept 2023). They are working on migrating from "SumoLogic" format to DataDog format
<note: removed images of DataDog vs SumoLogic queries, as they didn't add much to the discussion anyway > ACTIONS
| |||||||||||||||||||||||||||||||||
Comparison/Mapping Tool | On Hold | |||||||||||||||||||||||||||||||||
AWS Cloud to be in Separate Account | Waiting on AWS team | |||||||||||||||||||||||||||||||||
Team Absences | Mayo Team - Tracy off Oct 12, 13. In training Wed, Fri. Andrew off Oct 27 MSC - Leidos - QA - Gov - | |||||||||||||||||||||||||||||||||
EVS SERVICE AND ARCHITECTURE GROUP UPDATES | ||||||||||||||||||||||||||||||||||
EVS Service and Architecture Group | Will meet next week | |||||||||||||||||||||||||||||||||
DATA UPDATES | ||||||||||||||||||||||||||||||||||
Data | 23-09.d - schedule to deploy to PROD on Will do monthly terminology week starting Then will work on META afterwards DECIDED: Data Deployment should continue as planned - no reason to delay. | |||||||||||||||||||||||||||||||||
BROWSER UPDATES | ||||||||||||||||||||||||||||||||||
Browser | note outage discussion above | |||||||||||||||||||||||||||||||||
QA UPDATES | ||||||||||||||||||||||||||||||||||
QA | >We completed Regression Executions for the Monthly DDR for Sep '23 (23.09d) for EVS REST APIs on PRODUCTION . >We Executed Sanity Test Sets for LexEVS Data refresh on QA Tier . >We have executed Sanity Tests on NCIm,NCIt,TermForm for updated 23.09 Thesaurus deployment on STAGE Tier and for LexEVS Data refresh on QA Tier. >We have completed Progression and Sanity Executions for EVS Report Exporter v1.2.0-RC3 Tag on PRODUCTION Tier (EVSREPEXP-487). Thanks to Itendra for the helpful updates!
| |||||||||||||||||||||||||||||||||
TERMINOLOGIES LIFECYCLE REPORT | ||||||||||||||||||||||||||||||||||
Terminology Updates and Schedule | ||||||||||||||||||||||||||||||||||
Mark Benson TPM Update | Everyone is humbly asked to complete NIH Anti-Harassment training as soon.
|
LexEVS Technical Debt Progress
Technical Debt Related Update | Estimated Effort | Status |
---|---|---|
Report Exporter vulnerabilities - design | 4 days | |
Report Exporter vulnerabilities - implementation | 5 days | |
Unit testing | 2 days | |
QA | 2 days | |
Deployment | 5 days (elapsed) |
Vocabularies Slated for Production
Terminology Updates and Schedule
Vocabulary Name | Local Name | Version | Arrival Date | Loaded to data-qa DB | Date to Stage | Date to Production |
---|---|---|---|---|---|---|
Vocabulary Name in LexBIG | Short Name | Version identifier | Date the vocabulary arrived for processing | Has the vocabulary been loaded to the data-qa database? | Approximate date the vocabulary version is scheduled to move to staging | Approximate date the vocabulary version is scheduled to move to production |
NCI Thesaurus | NCIt | 23.08d |
...
Vocabularies Slated for Production
Terminology Updates and Schedule
Vocabulary Name
Local Name
Version
Arrival Date
Loaded to data-qa DB
Date to Stage
Date to Production
Vocabulary Name in LexBIG
Short Name
Version identifier
Date the vocabulary arrived for processing
Approximate date the vocabulary version is scheduled to move to staging
Approximate date the vocabulary version is scheduled to move to production
08/28/2023 | yes | 09/11/23 | 09/13/23 | |
NCIt-ChEBI | NCIt-ChEBI |
AUg2023 |
08/ |
28/ |
2023 | yes | 09/ |
11/23 | 09/ |
13/23 | |
NCIt-HGNC | NCIt-HGNC |
Aug2023 |
08/ |
28/ |
2023 | yes | 09/ |
11/23 | 09/ |
13/23 |
QA Schedule and Status
SECTION FOR FUNCTIONAL SYSTEM TESTING STATUS ::
SwissProt | SwissProt | Aug2023 | 08/28/2023 | yes | 09/11/23 | 09/13/23 |
ChEBI | ChEBI | v225 | 09/05/23 | yes | 09/15/23 | 09/18/23 |
HGNC | HGNC | Sept2023 | 09/05/23 | yes | 09/15/23 | 09/18/23 |
QA Schedule and Status
SECTION FOR FUNCTIONAL SYSTEM TESTING STATUS ::
Application and Version | Percentage Complete | Estimated Completion Date per Iteration | Priority Level | Type Of Testing | Current Tier for Release (DEV, QA, Stage, Prod) | Expected Production Date | ||||
EVS REST API | ||||||||||
Application and Version | Percentage Complete | Estimated Completion Date per Iteration | Priority Level | Type Of Testing | Current Tier for Release (DEV, QA, Stage, Prod) | Expected Production Date | ||||
EVS REST API (v1.6) | 100% | 5/27/2022 | High | Progression + Regression | QA | 6/6/2022 | ||||
EVS Explore (v1.6) | 100% | 5/27/2022 | High | Progression + Regression | QA | 6/6/2022 | ||||
EVS REST API(v1.6) | 100% | 6/1/2022 | High | Regression | Stage | 6/6/2022 | ||||
EVS Explore (v1.6) | 100% | 65/227/2022 | HighRegression | Progression + Regression | StageQA | 6/76/2022 | ||||
EVS REST APIExplore (22v1.05e6) - Monthly Data Deployment | 100% | 65/127/2022 | High | Progression + Regression | StageQA | 6/36/2022 | ||||
EVS REST API(22v1.05e6) - Monthly Data Deployment | 100% | 6/31/2022 | High | Regression | ProductionStage | 6/36/2022 | ||||
EVS REST APIExplore(v1.6) | 100% | 6/62/2022 | High | Regression | ProductionStage | 6/67/2022 | ||||
EVS ExploreREST API(v122.605e) - Monthly Data Deployment | 100% | 6/71/2022 | High | Regression | ProductionStage | 6/73/2022 | ||||
NCIt,NCIm,TermFormEVS REST API(22.05e + GO & HGNC Jun 2022 Deployment)) - Monthly Data Deployment | 100% | 6/3/2022 | High | Regression | StageProduction | 6/63/2022 | ||||
NCIt,NCIm,TermForm(22.05e + GO & HGNC Jun 2022 DeploymentEVS REST API(v1.6) | 100% | 6/6/2022 | High | Regression | Production | 6/86/2022 | ||||
EVS REST APIExplore(22v1.06d6) - Monthly Data Deployment | 100% | 6/307/2022 | High | Regression | Stage , Production | 6/307/2022 | ||||
NCIt,NCIm,TermForm(22.06d) - Monthly Data Deployment.05e + GO & HGNC Jun 2022 Deployment) | 100% | 76/83/2022 | High | SmokeRegression | Stage,Production | 76/86/2022 | ||||
NCIt,NCIm,TermForm(22.05e + GO & HGNC Jun 2022 Deployment) | 100% | 6/36/2022 | High | Regression | StageProduction | 6/68/2022 | ||||
NCIt,NCIm,TermForm EVS REST API(22.06d) - Monthly Data Deployment | 100% | 7 6/ 830/2022 | High | Smoke Regression | Stage , Production | 7 6/ 830/2022 | ||||
NCIt,NCIm,TermForm( ChEBI, GO & HGNC July 2022 Deployment)22.06d) - Monthly Data Deployment | 100% | 7/ 128/2022 | High | Smoke | Stage,Production | 7/ 128/2022 | ||||
NCIt,NCIm,TermForm( ChEBI,22.05e + GO & HGNC JulyJun 2022 Deployment) | 100% | 7 6/ 133/2022 | High | Smoke Regression | Production Stage | 7 6/ 136/2022EVS REST API | ||||
NCIt,NCIm,TermForm(22.07d06d) - Monthly Data Deployment | 100% | 7/278/2022 | High | RegressionSmoke | Stage,Production | 7/278/2022 | ||||
NCIt,NCIm,TermForm(22.07d) - Monthly Data DeploymentChEBI, GO & HGNC July 2022 Deployment) | 100% | 87/112/2022 | High | Smoke | Stage,Production | 87/112/2022 | ||||
NCIt,NCIm,TermForm(CanMEDChEBI, GO & HGNC AUG July 2022 Deployment) | 100% | 87/313/2022 | High | Smoke | Stage,Production | 87/313/2022 | ||||
EVS REST API - 1.6.1 (Hot Fix Deployment) | 100 % | 8/3/2022 | Highest | (22.07d) - Monthly Data Deployment | 100% | 7/27/2022 | High | Regression | Stage , Production | 7/27/2022 |
NCIt,NCIm,TermForm(22.07d) - Monthly Data Deployment | 100% | 8/1/2022 | High | SmokeProgression + Regression | Stage,Production | 8/41/2022 |
Attendees
NCIt,NCIm,TermForm(CanMED, GO & HGNC AUG 2022 Deployment) | 100% | 8/3/2022 | High | Smoke | Stage,Production | 8/3/2022 |
EVS REST API - 1.6.1 (Hot Fix Deployment) | 100 % | 8/3/2022 | Highest | Progression + Regression | Stage,Production | 8/4/2022 |
Attendees
Name | Role | Present |
---|---|---|
Remennik, Lyubov | NIH/NCI | |
Safran, Tracy |
Name
Role
Present
Safran, Tracy
NIH/NCI [C] |
Ong, |
Kim L | NIH/NCI [C] |
Lucas, |
Jason R | NIH/NCI [C] |
Bauer, Scott | NIH/NCI [C |
JIRA Issues
Recent EVS Stats Dashboard Related Bugs and Features (within last week)
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Recent Report Exporter Related Bugs and Features (within last week)
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
] | ||
Alkis, Barry | NIH/NCI [C] | <checked in> |
Solie, Chuck | NIH/NCI [C] | |
Kondareddy, Swathi | NIH/NCI [C] | |
Singh, Itendra | NIH/NCI [C] | |
Zhang, Chao | NIH/NCI [C] | |
Johnson, Connie | NIH/NCI [C] | |
Whiteman, Lori | NIH/NCI [C] | |
Benson, Mark | NIH/NCI [C] | |
Andrew Moore | NIH/NCI [C] |
JIRA Issues
Recent EVS Stats Dashboard Related Bugs and Features
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Recent
...
Report Exporter Related Bugs and Features
|
Jira | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Recent LexEVS Related
...
Bugs and Features
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Recent CTS2 Service Related
...
Issues
Jira | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
ASSIGNED ACTION ITEMS
tasks-report-macro | ||||
---|---|---|---|---|
|