1
78%
master: 80%

Ran 19 Mar 2025 01:35PM UTC

Files 33

Run time 2s

Badge

Embed ▾

Committed 19 Mar 2025 01:31PM UTC coverage: 77.703%. Remained the same

Job # 13947812695.1

Build Type

push

github

Committed by

web-flow

Commit Message

CA-408339: Respect xenopsd's NUMA-placement-policy default (#6368)

Xenopsd has an experimental feature that aims to optimise NUMA
placement. This used to be configured by adding `numa-placement=true` to
the file /etc/xenopsd.conf, which tells xenopsd to enable the feature.

Later, an actual API was added to configure this:
`host.set_numa_affinity_policy`. The expectation was that, while this
new API should be preferred, the old xenopsd.conf option would still
work for backwards compatibility reasons. This is particularly important
for hosts that are upgraded to the new version.

Unfortunately, while code exists in xenopsd to read and use the config
option when it starts up, when xapi starts up immediately after xenopsd,
it always overrides the NUMA config based its own DB field. The field
type actually has a "default" option, but this gets translated to "any"
(= no NUMA). By default, this means means that the experimental feature
is disabled, no matter what the config file says, and can only be
enabled through the API.

The fix is for xapi to not assign a default value itself, but let
xenopsd decide on the default policy. And xenopsd uses its config file
to do so, as before.

Run Details

3356 of 4319 relevant lines covered (77.7%)

0.78 hits per line

xapi-project / xen-api / 13947812695 / 1
78%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job python3.11 - 13947812695.1

xapi-project / xen-api / 13947812695 / 1 78% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job python3.11 - 13947812695.1

xapi-project / xen-api / 13947812695 / 1
78%
master: 80%

README BADGES
x