-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Podman] Supports SQLite containers database back-end to support newer versions (4.8+) #24373
[Podman] Supports SQLite containers database back-end to support newer versions (4.8+) #24373
Conversation
Go Package Import DifferencesBaseline: 5c66b7c
|
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=31645091 --os-family=ubuntu |
Regression DetectorRegression Detector ResultsRun ID: 51dcfc62-12d5-4542-bda1-bde48a790d45 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_to_blackhole | % cpu utilization | +2.23 | [-4.02, +8.48] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_tree | memory utilization | +2.23 | [+2.11, +2.36] |
➖ | file_to_blackhole | % cpu utilization | +2.23 | [-4.02, +8.48] |
➖ | idle | memory utilization | +1.08 | [+1.03, +1.12] |
➖ | process_agent_standard_check | memory utilization | +0.88 | [+0.81, +0.94] |
➖ | process_agent_real_time_mode | memory utilization | +0.85 | [+0.80, +0.90] |
➖ | basic_py_check | % cpu utilization | +0.78 | [-1.74, +3.30] |
➖ | process_agent_standard_check_with_stats | memory utilization | +0.61 | [+0.55, +0.67] |
➖ | otel_to_otel_logs | ingress throughput | +0.07 | [-0.39, +0.52] |
➖ | trace_agent_json | ingress throughput | +0.01 | [-0.02, +0.03] |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.20, +0.20] |
➖ | trace_agent_msgpack | ingress throughput | -0.00 | [-0.00, +0.00] |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.02 | [-0.07, +0.02] |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.15 | [-0.24, -0.06] |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.30 | [-3.17, +2.58] |
➖ | pycheck_1000_100byte_tags | % cpu utilization | -2.00 | [-6.85, +2.85] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small suggestion to add thew word Note in bold, but approved, also your discretion if you prefer to have that entire line italicized instead.
releasenotes/notes/podman-sqlite-backend-support-8437c6d5254b39ef.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to bump the DogStatsD binary size check to 42 Mb
/merge |
🚂 MergeQueue This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals. Use |
🚂 MergeQueue Pull request added to the queue. This build is going to start soon! (estimated merge in less than 24m) Use |
…r versions (4.8+) (#24373) * go import + licenses + release note * sqlite client + modifies wlm podman init * new podman detection and config * Doc suggestion on release note formatting Co-authored-by: Alicia Scott <[email protected]> * Use pure-go SQLite driver instead of CGo implementatioon * Increase max_dsd binary size to 42 MB --------- Co-authored-by: Alicia Scott <[email protected]>
…r versions (4.8+) (#24373) * go import + licenses + release note * sqlite client + modifies wlm podman init * new podman detection and config * Doc suggestion on release note formatting Co-authored-by: Alicia Scott <[email protected]> * Use pure-go SQLite driver instead of CGo implementatioon * Increase max_dsd binary size to 42 MB --------- Co-authored-by: Alicia Scott <[email protected]>
What does this PR do?
sqlite_db_client.go
forpodman
having exact parity with the current BoltDB clientdb_client.go
to support newer Podman versionspodman
feature :podman_db_path
is provided by the user OR/var/lib/containers/storage
exists (previously, only if/var/lib/containers
exists)config.go
to defaultpodman_db_path
to an empty string instead of/var/lib/containers/storage/libpod/bolt_state.db
podman
workloadmeta collector behaviour :/var/lib/containers
exists on the system : this could cause a loop of logs about/var/lib/containers/storage/libpod/bolt_state.db
not being accessible to the host Agent (running underdd-agent
).sql
or.db
to select the client to useMotivation
podman
to newer versions that default to the SQLite backend (with the BoltDB backend being deprecated in 5.0+)Additional Notes
AllContainers
function from the podman Go package returning the same type, an array of containers with their configuration and their state.Possible Drawbacks / Trade-offs
Introduces a new Go dependencypodman
, we use a pure-Go SQLite implementation (modernc.org/sqlite
) as the CGo implementation (github.com/mattn/go-sqlite3
) breaks a test (inv -e integration-tests --race --remote-docker
) as this test environment is based ondocker/compose:debian-1.29.2
which uses an old glibc version. Per the library author, this implementation is a bit slower (16% in their benchmark) but this should be acceptable considering the low podman usage out-there, nor do we rely much on it as we only open a connection to run a single querydogstatsd
stand-alone binary which uses thepodman
build tag :38338.890625 kB
on 182707b to41726.609375 kB
on 5b73966.inv -e agent.build
) where the increase is only half a MB : this affects the DSD binary as it has a very limited amount of build tags, and thus imports.Describe how to test/QA your changes
2 environments/versions of podman will be needed :
sudo apt-get install podman -yq
(.deb releases are very far behindmain
)sudo yum -y install podman
(4.8.x+)podman
containers can be run both in rootless and rootfull mode : both behaviours should be tested.Rootfull :
Rootless (e.g. run by the
ubuntu
user) :podman
workloadmeta collector is working in both rootfull and rootless by runningagent workload-list -v
: assess containers with runtimepodman
are present matching ids from the(sudo) podman ps
commandpodman
feature is automatically detected as/var/lib/containers/storage
is mounted inside your Agentpodman_db_path
, e.g. using-v /var/lib/containers/storage:/abc:ro
(mounting the storage file in/abc
) and-e DD_PODMAN_DB_PATH=/abc/libpod/bolt_state.db
(providing the path to the DB location inside the Agent)podman
support) (depends on the cgroups version on the VM) :