Data Protection in OpenStack: More than just the Data
summary
Trilio argues that protecting OpenStack requires more than VM backups: legacy agent-plus-media-server setups are costly, hard to scale and can consume an entire compute node, so Trilio adds a lightweight service to each compute node to capture data plus OpenStack metadata (flavor, placement groups, networking) and enable automated restores. Required properties listed are self-service, agentless, multi-tenancy and non-disruptive upgrades; the claimed result is linear scaling with cloud size and restores that need no manual metadata reconstruction.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:58Every sheep brings value
- 1:56Isn't it all stateless in the cloud?
- 4:39Okay, let's implement the old trustworthy Backup solution!
- 5:57Managing backups - a nightmare
- 7:08Backup needs to be self-service
- 8:19The cost of the media server
- 11:51Multi-Tenancy - Ownership of backups
- 13:56Every OpenStack project adds information to the VM
- 16:01Okay, solution found, where is my maintenance window?
- 18:16Summary: data protection requirements for OpenStack clouds
related talks
36mAdventures in Running a Private Cloud
28mWhat is OpenStack and what services do I need?
27mHow to get rich with cloud!
40mCoriolis How to easily migrate your IT workloads to Charmed OpenStack
45mOpenstack-on-OpenStack Overview
17mLessons learned: scaling confidential clusters on OpenStack
23mThe Fifth Open Paradigm: Open Operations
26mEnsuring data protection readiness across hybrid environments