General
Escalation
General
Escalation
Description
How to test
Check all three
deb // can be tested only after merge
RPM // can be tested only after merge
tarball // can be tested in FB
Check that PMM Client package includes nomad binary
Check that pmm-agent contains path to installed nomad binary.
PMM Client removal should remove also Nomad
Upgrade - PMM Client repo contains Nomad pkg
How to document
None
has to be done before
Activity
Show:
Nailya Kutlubaeva November 13, 2024 at 11:56 AM
we need to add this check to autotests @Peter Sirotnak
Nailya Kutlubaeva November 13, 2024 at 11:55 AM
verified, upgrade will be checked later
Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Priority
Medium
Needs QA
Yes
Needs Doc
No
Planned Version/s
Fix versions
Story Points
5
Lead time
36
In progress time
22
Smart Checklist
Open Smart Checklist
Open Smart Checklist
Created September 30, 2024 at 9:45 AM
Updated last week
Resolved last week
ℹ️ What should be done:
Nomad binary should be included to PMM Client package. pmm-agent should contain path to nomad agent in it’s config.
Added value:
We want to provide forward-compatability for PMM Client, so when we will implement SEP on PMM Server it will support PMM Clients starting PMM 3.0.0 version.
Suggested implementation / options:
Include nomads binary to PMM Client package the same way as we do with vmagent.
Update pmm-agent config to contain path to nomad binary.
Update codebase if required to be able to run nomad agent.
Check that nomad binary has correct ownership and mode.
Out of scope:
Configuration of nomad agent
Running nomad agent from PMM Server
Details: