wso2 / wso2/open-cloud-datacenter

Add a restic VM-data backup guide for the tenancy/vm module

Open
#231 0 comments 0 reactions 1 assignee View on GitHub

@Akini98 is already working on this.

Since Jul 20, 2026.

Dominant language
HCL
Stars
19
Forks
15
Avg merge
2d 2h
Merged PRs (30d)
4

Description

Description

The tenancy/vm examples document how to provision a standalone Harvester VM, but not how to back up its data. Product teams own their VM-data backups to their own S3 buckets and currently have no guide for it.

This is the general-VM counterpart to the cluster backups guide (#218 / #219, etcd + Velero): that covers RKE2 clusters; this covers plain VMs.

Proposal

Add modules/tenancy/vm/examples/BACKUPS.md — a self-service restic guide, matching the style of the existing k8s-cluster/examples/BACKUPS.md:

  • Bucket + least-privilege IAM user (policy JSON including multipart actions) plus a repository password.
  • The in-guest install: cloud-init (base64-embedded scripts) that installs restic and runs a systemd backup timer, passed via the vm module's user_data.
  • Verify, and restore — into a fresh VM (same DC), a single file / subtree (file-level), and cross-DC DR.
  • A scheduling/retention reference and a production-hardening checklist.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.