32119415969
79%

Ran 18 Aug 2026 09:02AM UTC

Jobs 1

Files 36

Run time 1min

Badge

Embed ▾

Committed 18 Aug 2026 08:51AM UTC coverage: 78.996%. Remained the same

Build # 32119415969

Build Type

push

github

Committed by

web-flow

Commit Message

Preserve VDI tags on migration (#7080)

XCP-ng has a need for persistent VDI metadata (metadata that's preserved
across snapshots/migrations). Currently none of the VDI fields
(`other_config`, `sm_config`, `tags`, etc.) persist across a migration.
This is because the destination VDI is created by storage backends and
then db-introduce'd into XAPI. Storage backends in turn consult only
some of the `vdi_info` fields of the original VDI, preserving
`name_label`, `name_description` and some other fields, but not the
fields that allow flexible metadata to be stored by clients.

This PR allows storage backends to 1) consult `vdi.tags` 2) modify
`vdi.tags`. It then modifies the SMAPIv1 migrate code to copy over the
tags from the source VDI to the destination after a migration.

---

I've tested that this code preserves vdi tags after a migration, and
this satisfies our need for persistent metadata. Opening as a draft,
however, because I'm not sure if `tags` are the right place to store
such metadata, and if the approach is the right one - thoughts?

Coverage Stats

3667 of 4642 relevant lines covered (79.0%)

0.79 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	python3.11 - 32119415969.1	18 Aug 2026 09:02AM UTC	36	79.0	GitHub Action Run

xapi-project / xen-api / 32119415969
79%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32119415969

xapi-project / xen-api / 32119415969 79%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32119415969

xapi-project / xen-api / 32119415969
79%

README BADGES
x