mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 20:23:39 +09:00
The disabled hack/e2e-chainsaw/backup/ suite was a Chainsaw port of the retired
backup.bats, written against the old backup API, so the VMInstance and standalone
VMDisk Velero paths had no e2e coverage. Replace it with two round-trips in the
vminstance suite that drive the validated examples/backups/{vmi,vmdisk} scripts,
so the documented demo and the automated test stay in step.
Both run un-gated in CI:
- vminstance-2-backup-roundtrip boots a tiny cirros VM (u1.nano, 2Gi), backs it
up via BackupClass + BackupJob, restores in place, and asserts the VM returns
Running off a disk PVC the restore created: a new uid, Velero's restore-name
label and the -orig- PVC keepOriginalPVC leaves behind. The label alone is not
enough, because existingResourcePolicy: update also stamps it on a PVC Velero
only patched, which moves no data. A guest-side boot proof is unavailable: the
KubeVirt CR disables serial-console logging and cirros ships no guest-agent.
- vmdisk-2-backup-roundtrip imports a 5Gi disk, backs it up, and restores it in
place with the same three assertions. The controller prepares the target
(suspend HelmRelease, delete DataVolume, rename PVC). On a WaitForFirstConsumer
class the Velero data mover waits for a Pod to select a node for the restored
PVC, which a detached disk never gets, so the script starts a pause Pod on the
new PVC, standing in for the VM that would attach it.
The disk storageClass is an override (default replicated; the CI steps pass the
lane's COZY_E2E_STORAGE_CLASS, 'local' on the DRBD-off gate) and the script waits
are bounded so their worst case stays under the 40m op timeout, sized to keep the
whole parallel:1 suite inside the 215m job cap. On failure the catch also dumps
the Velero Restore, DataDownload and DataUpload objects. Each harness stands up a
throwaway in-cluster BSL (the platform cozy-default BSL derives the external S3
endpoint, unroutable in kind); its finally resumes the suspended HelmReleases,
reclaims the keepOriginalPVC orig PVC and its LINSTOR volume, and drains the
Velero backups before deleting the BSL. The example scripts are non-interactive
so the harness can drive them.
Assisted-by: LLM
Signed-off-by: Andrey Kolkov <androndo@gmail.com>
64 lines
2.4 KiB
Bash
Executable File
64 lines
2.4 KiB
Bash
Executable File
#!/bin/bash
|
|
# Step 01: Create the Velero backup/restore strategy for a standalone VMDisk.
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
source "$SCRIPT_DIR/00-helpers.sh"
|
|
|
|
print_header "Step 1: Create VMDisk Velero strategy"
|
|
|
|
log_step "Creating Velero strategy 'vmdisk-backup-strategy'..."
|
|
log_command "kubectl apply -f - (Velero strategy: vmdisk-backup-strategy)"
|
|
|
|
# A standalone VMDisk is just an HelmRelease + a DataVolume-backed PVC (+ its
|
|
# configmaps), all labelled app.kubernetes.io/instance: vm-disk-<name>. Unlike a
|
|
# VMInstance there is no VirtualMachine / VMI / launcher pod to capture. With
|
|
# snapshotMoveData the CSI data mover streams the volume through the
|
|
# BackupStorageLocation, so no VolumeSnapshotLocation is required (matching the
|
|
# platform's own cozy-default-velero-vmdisk strategy).
|
|
kubectl apply -f - <<'EOF'
|
|
apiVersion: strategy.backups.cozystack.io/v1alpha1
|
|
kind: Velero
|
|
metadata:
|
|
name: vmdisk-backup-strategy
|
|
spec:
|
|
template:
|
|
restoreSpec:
|
|
existingResourcePolicy: update
|
|
includedNamespaces:
|
|
- '{{ .Application.metadata.namespace }}'
|
|
orLabelSelectors:
|
|
- matchLabels:
|
|
app.kubernetes.io/instance: 'vm-disk-{{ .Application.metadata.name }}'
|
|
- matchLabels:
|
|
apps.cozystack.io/application.kind: '{{ .Application.kind }}'
|
|
apps.cozystack.io/application.name: '{{ .Application.metadata.name }}'
|
|
includedResources:
|
|
- helmreleases.helm.toolkit.fluxcd.io
|
|
- persistentvolumeclaims
|
|
- configmaps
|
|
includeClusterResources: false
|
|
spec:
|
|
includedNamespaces:
|
|
- '{{ .Application.metadata.namespace }}'
|
|
orLabelSelectors:
|
|
- matchLabels:
|
|
app.kubernetes.io/instance: 'vm-disk-{{ .Application.metadata.name }}'
|
|
- matchLabels:
|
|
apps.cozystack.io/application.kind: '{{ .Application.kind }}'
|
|
apps.cozystack.io/application.name: '{{ .Application.metadata.name }}'
|
|
includedResources:
|
|
- helmreleases.helm.toolkit.fluxcd.io
|
|
- persistentvolumeclaims
|
|
- configmaps
|
|
includeClusterResources: false
|
|
storageLocation: '{{ .Parameters.backupStorageLocationName }}'
|
|
snapshotVolumes: true
|
|
snapshotMoveData: true
|
|
ttl: 720h0m0s
|
|
itemOperationTimeout: 24h0m0s
|
|
EOF
|
|
|
|
log_success "Velero strategy created"
|
|
echo -e "\n${GREEN}${BOLD}Next step:${NC} ./02-create-backupclass.sh" >&2
|