Kubevirt: move containerd-user root to persist

[andrewd-zededa]

New kubevirt storage layout has /var/lib slimmed
down to 10GB only for k3s.
containerd-user root requires a move to persist.

Part 1 of the breakup of now-draft PR: #3838.

[eriknordmark]

LGTM.

Will this require a flag day reinstall for all existing devices running kubevirt due to the path name change? If so can you prepare a message for LF-Edge slack and email.

[andrewd-zededa]

@eriknordmark yes this would require a fresh usb reinstall to move forward from a build with the previous path . I can prepare a message

[andrewd-zededa]

@eriknordmark

I don't currently have an account with access to the lf edge slack. I'll try to request access. For now here is a potential draft message for the community:

Storage layout change to kubevirt EVE-OS containerd images.

This is an announcement to any users of the kubevirt build of EVE-OS. This prerelease image is seeing a change to the storage layout
which moves user containerd images from its default inside k3s subpath /var/lib/rancher/k3s/agent/containerd/ to the standard EVE path
of /persist/vault/containerd. This change will be included as a part of PR3877.

The change will impact any currently installed kubevirt image and require those nodes to be reinstalled. Upgrades are not supported from a build before this change to a build after this change.

[eriknordmark]

@eriknordmark

I don't currently have an account with access to the lf edge slack. I'll try to request access.

I emailed you an invite. (I don't recall whether you have to create a login on the LF-Edge webpages/wikis to be able to join slack.)

For now here is a potential draft message for the community:

Storage layout change to kubevirt EVE-OS containerd images.
This is an announcement to any users of the kubevirt build of EVE-OS.

It would make sense to specify who should worry (developers) and how to tell you are running kubevirt (the EVE release string contains "kubevirt" as opposed to "kvm" or "xen").

This prerelease image is seeing a change to the storage layout

which moves user containerd images from its default inside k3s subpath /var/lib/rancher/k3s/agent/containerd/ to the standard EVE path
of /persist/vault/containerd. This change will be included as a part of PR3877.
The change will impact any currently installed kubevirt image and require those nodes to be reinstalled. Upgrades are not supported from a build before this change to a build after this change.

[andrewd-zededa]

Thanks @eriknordmark. Here is my latest draft. If this looks alright should I post it to the eve channel on lf-edge slack?

Storage layout change to kubevirt EVE-OS containerd images.

This is an announcement to any developers of the kubevirt build of EVE-OS. This prerelease image is seeing a change to the storage layout which moves user containerd images from its default inside k3s subpath /var/lib/rancher/k3s/agent/containerd/ to the standard EVE path of /persist/vault/containerd. This change will be included as a part of PR3877. The kubevirt build are only those identified by presence of the string "kubevirt" in the version string which can be found either from the output of the "eve version" command or through the contents of the /hostfs/etc/eve-release and /run/eve-hv-type files.

The change will impact any currently installed kubevirt image and require those nodes to be reinstalled. Upgrades are not supported from a build before this change to a build after this change.

[eriknordmark]

Kick eden

[andrewd-zededa]

@eriknordmark @rouming Looks like the latest failed CI checks are due to build-jet comms issues and are on the kvm build anyways which this PR did not change.

Otherwise, is this go for merging?