Skip to content

docs: propose thin-pool data isolation - #605

Open
ganesan23 wants to merge 1 commit into
mainfrom
docs/thin-pool-data-isolation
Open

ganesan23 wants to merge 1 commit into
mainfrom
docs/thin-pool-data-isolation

Conversation

@ganesan23

Copy link
Copy Markdown
Collaborator

Summary

  • document the cross-tenant stale-data risk when thick LVM extents are reused, particularly for raw-block PVCs
  • propose one explicitly zero-enabled thin pool per CSI-managed VG
  • require full virtual-capacity reservations so thin provisioning can never overcommit physical capacity
  • describe how to preserve multi-NVMe striping in the pool data LV
  • identify required provisioning, capacity, expansion, GC, cleanup, monitoring, migration, and validation changes

Motivation

The current driver removes ordinary thick LVs without sanitizing all released extents. A later raw-block volume can receive those extents and potentially observe data written by a previous tenant. Thin-pool allocation-time zeroing can provide logical reuse isolation, but adopting it safely requires more than changing the lvcreate command.

Review focus

  • whether a zero-enabled thin pool is the preferred isolation boundary
  • permanent prohibition of thin-pool overcommit
  • pool data/metadata sizing and reserved VG headroom
  • preserving the current multi-NVMe RAID0-style distribution
  • GC and lifecycle treatment of pool infrastructure LVs
  • rollout and migration of existing thick LVs

Testing

Documentation-only change; no runtime behavior changed.

Document the stale extent exposure in the current thick-LV design and propose a zero-enabled, non-overcommitted thin-pool architecture with preserved NVMe striping.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant