-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Podman: Add SQLite support to Podman
-
False
-
None
-
False
-
Not Selected
-
To Do
-
RHELBU-2165 - SQLite as optional db backend to Podman
-
rhel-sst-container-tools
-
0% To Do, 7% In Progress, 93% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Very early renditions of Podman supported both boltdb and sqlite. The sqlite implemented was dropped before Podman 1. Our goal is to re-implement the SQLite db interface.
Why is this important?
- a customer/partner has discovered a way to corrupt the boltdb during power loss testing. this renders podman useless and requires manual setup to make almost any podman command work again.
- the above is a known bug for four years
- upstream boltdb is nearly inactive
- boltdb has no error handling; it throws a panic instead. this is bad.
- sqlite offers some possible performance opportunities
- sqlite has better r/rw locking and locking algorithms
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- sqlite3
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>