![]() |
Page History
Sprint Dates
-
Sprint Goals
- Transition the production tier to Fargate
- Deploy release candidate to production
- Resolve data discrepancies between environments
- Various data hot fixes
- Load new study files for PRECINCT01
- Address 2023 Q3 Final Design QA
Sprint Jira Issue Types
Jira Charts | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Completed in Sprint
Jira Charts | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sprint Schedule
Date | Scrum Ceremony | Purpose |
---|---|---|
Sprint Kickoff | Initiate new sprint | |
| Sprint Pre-planning | Review tasks targeted for next sprint and identify clarifications needed, apply initial story point estimations and initial projected assignees |
| Sprint Planning | Review prioritized tasks, assert assigned stories, assert final story point estimations, review story points by assignee |
| Sprint Review & Retrospective | Demo work completed, discuss what went well and what can be improved |
Software Release Information
Date | Build Type | Front-End Version | Back-End Version | File System Version |
---|---|---|---|---|
| Internal Beta Release | 4.0.0.197 | 14.8.1.143 | 2.3.1.74 |
| Internal Beta Release | 4.0.0.202 | 14.8.1.143 | 2.3.1.74 |
Sprint Retrospective
DevOps Post-Mortem (High impact to release schedule)
All of the other ICDC environments have been migrated to Fargate, but because prod is still running on EC2 we are seeing a kernel mismatch preventing the BE docker container from loading up successfully. We can not fix this unless we change the version of the Ubuntu operating system (centos 7) on the EC2 instance, which may or may not fix the issue. Alternatively, we can run the command in privilege mode, which introduces high risk from a security perspective.The recommended solution (by our DevOps team) is to instead complete the migration of production to Fargate, which means we have to work with the CloudOne team to change the ALB and the DNS and update all of the Terraform scripts, but this approach will require a full testing of the deployment first at a dummy url (icdc.test.gov) and lockstep support from the CBIIT CloudOne team. This is all to say that worst case scenario the release could be delayed another 2-3 weeks.