kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-05 09:55:44 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: describe the need for dmidecode in docs (#19348)

Browse Source
This commit is contained in:
Seth Hoenig
2023-12-08 10:45:37 -06:00
committed by GitHub
parent f3cbe2e29a
commit 39eb17f3ec
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/concepts/cpu.mdx
View File

@@ -320,6 +320,12 @@ resources {
}
```
## Virtual CPU Fingerprinting
When running on a virtualized host such as Amazon EC2 Nomad makes use of the
`dmidecode` tool to detect CPU performance data. Some Linux distributions will
require installing the `dmidecode` package manually.
[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
[cpushares]: https://www.redhat.com/sysadmin/cgroups-part-two
[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access

8
website/content/docs/upgrade/upgrade-specific.mdx
View File

@@ -88,6 +88,14 @@ upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
meets expectations before upgrading. The [cpu concepts][cpu] documentation
contains guidance in understanding how Nomad detects CPU metrics.
#### CPU EC2 Detection Changes
Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
performance data for every EC2 instance type. In 1.7 and later Nomad instead
gathers this data by executing the `dmidecode` command. The `dmidecode` package
must be installed manually on some Linux distributions before the Nomad agent
is started.
#### CPU Core Isolation
Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`