chore: bump mc-observability to 0.6.1 and sync agent ansible files - #195
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the mc-observability images to 0.6.1 (m-cmp/mc-observability#356, tag v0.6.1).
The image bump alone is not enough for this release.
mc-observability-infrabind-mounts
conf/mc-observability/mc-observability-infra/ansibleover/ansible,so the agent install files come from this repository, not from the image. v0.6.1
replaces DCGM Exporter with telegraf's nvidia_smi input, which changes exactly
those files, so the ansible tree is synced here as well:
roles/dcgmis removed (576 MB of vendored NVIDIA container toolkit .deb/.rpmarchives and the dcgm-exporter image). GPU nodes no longer need podman or the
exporter; nvidia-smi ships with the NVIDIA driver.
playbook.yamldrops the DCGM role invocation and the toolkit version variable.enable_gpunow only tells the manager whether to put the GPU input into thetelegraf config.
which changes the number of split parts, so the stale
_02chunks are deleted.Verified against a CB-Tumblebug 0.13.2 stack running these images: a VM was
provisioned through Tumblebug, the monitoring agent installed from this ansible
tree, and its metrics arrived in InfluxDB tagged with ns_id/infra_id/node_id.
Repeated on an NVIDIA Tesla T4 instance with
gpuenabled, which produced thedcgmmeasurement with the DCGM field names the backend reads. Both instancesand every resource they created were deleted afterwards.