5/16/24 CELR/DEX Prod Migration Planning Discussion

Date

May 16, 2024

Attendees:

 

 

APHL/AIMS

Peraton

CDC/MVPS

APHL/AIMS

Peraton

CDC/MVPS

Geo Miller: X

Erroll Rosser: X

Anthony Kimbo: X

Gretl Glick: X

 

Loretta Foster: X

 

 

Cosmin: X

 

 

Chase Farmer: X

 

 

Beth Wingerd: X

 

 

 

Goals

Discussion topics

Item

Notes

Item

Notes

 

Dev Updates:

  • Current DEX>STG workstream will be retired, migrated to Meta Data V2 and verify end point 5/22

    • 5/22-5/29: Testing of meta data v2, end point in STG, then

    • Remaining AIMS development: Cloudwatch monitoring and alert creation: Target: 5/24/24

    • 5/28/24: AIMS will be submitting CR/CAB, then migrate CELR Reporting to DEX Prod on 5/29 (or date to be chosen)

    • Would be migrated to PRD by last week of May

    • Could also potentially migrate Rabies to STG for UAT

    • Production Ops Team:

      • If DEX sees data related issues, would open HD ticket, for triaging, can pull into integration teams

      • Send email to support@aimsplatform.org (@Gretl Glick to send this over to Anthony)

        • Geo: For Instance, known issues seen--send email to DEX listserve [dexuploadapi@cdc.gov], but will also open a ticket on AIMS for tracking/time spent

        • Chase: If a file was sent to the wrong location, that might not be an issue

        • General communications/non-incident tickets--can be sent to Geo directly/emailed to team

        • If issue is with DEX, issues will be submitted to dexuploadapi@cdc.gov to communicate with DEX team and associated service desk/ticketing system

Production Readiness Review and Migration Steps

  • ER: Parallel processing to CELR and DEX/CDC; Existing pipeline will continue to be maintained (CELR on AIMS will continue to be supported)

    • Only dependency is to receive data from DEX on CDC

    • CELR on CDC--data will not be sent initially to HHS; HHS will only initially receive AIMS CELR data

      • Program outstanding decision: Need to decide if they want to receive 2022 data or 2023 data

  • General timeline for high-level timeline--there is a upload release on the DEX side which will need to implemented which will take ~1 day

    • Consensus Production Cutover Date: 6/3/24!

  • REVISION 3TIMELINE

    • - 5/15 - v2 CELR Routing updates to staging

    • - 5/15 - CELR ready for v2 in staging

    • - 5/22 - APHL deploys /info endpoint check and v2 to staging

    • - 5/22 - 5/28 - APHL | DEX | CELR End to End verification in staging

    • - 5/28 - DEX outage comms - w/o - v2.0.X CR Approval

    • - 5/28 - APHL change control request

    • - 5/28 - v2 CELR Routing updates to production

    • - 5/28 - CELR ready for v2 in production

    • - 5/30 - proposed Upload v2.0.x production release

    • - 5/31 - GO/NO GO DECISION

    • - 6/3 - pre-cutover meeting

    • - 6/3 - APHL proposed cutover

    • - Production monitoring - APHL | DEX

  • Checkpoints during the production migration

    • Go/no go Meeting : 5/31 [Anthony to schedule]

    • Production Migration Working Session: 6/3 (Geo OOO--wouter can join) [Anthony to schedule]

      • Tuesday, 6/4: 10:30am ET DL O&M Meeting [Gretl will forward meeting invite]

      • Wednesday 6/5: 11am ET CELR>DEX Meeting

      • Thursday 6/6: 8:30am ET DL O&M Meeting [Gretl will forward meeting invite]

      • Friday 6/7: To be Scheduled [Anthony will send meeting invite

Next Steps/Action Items

Schedule Production Migration Meeting Series:

  • Checkpoints during the production migration

    • Go/no go Meeting : 5/31 [Anthony to schedule]

    • Production Migration Working Session: 6/3 (Geo OOO--wouter can join) [Anthony to schedule]

      • Tuesday, 6/4: 10:30am ET DL O&M Meeting [Gretl will forward meeting invite]

      • Wednesday 6/5: 11am ET CELR>DEX Meeting

      • Thursday 6/6: 8:30am ET DL O&M Meeting [Gretl will forward meeting invite]

      • Friday 6/7: To be Scheduled [Anthony will send meeting invite

 

 

Action items

Quick decisions not requiring context or tracking

For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.

Decisions requiring context or tracking

For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.