feat(blockstorage): Cinder volume resource and volume/snapshot data sources - #7
Merged
Conversation
…a sources
Cinder v3. Code-complete; the volume create/status-waiter/error-detection path is
verified against the lab (the waiter correctly catches the backend ERROR). The full
acceptance test can't pass on the CE lab because it has no storage backend configured
(storageBackends={}), so volumes go creating -> error. It will pass on a cloud with a
working Cinder backend. Tracked in DECISIONS.md.
- pcd_blockstorage_volume: create (wait available), in-place extend on size increase,
name/description/metadata update, import.
- pcd_blockstorage_volume / pcd_blockstorage_snapshot data sources.
- clients: BlockStorageV3Client (Cinder).
PF9-pushkar
added a commit
that referenced
this pull request
Jul 14, 2026
feat(blockstorage): Cinder volume resource and volume/snapshot data sources
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 — block storage (Cinder v3)
Final Phase 1 family. Code-complete; acceptance is gated by a lab limitation (below), the same way
pcd_compute_instance's boot is.Resource
pcd_blockstorage_volume— create (waits foravailable), in-place extend whensizeincreases (shrink is rejected), name/description/metadata update, delete (waits), import. Sourceable from snapshot / source volume / image.Data sources
pcd_blockstorage_volume,pcd_blockstorage_snapshot(by id or filters).Lab caveat (not a provider issue)
The CE lab has no Cinder storage backend (
storageBackends={}in the blueprint; only a__DEFAULT__volume type with nothing behind it), so a created volume goescreating → error. The resource's create + status-waiter + error-detection path is verified — the waiter correctly reports the ERROR state.TestAccBlockStorageVolume_basicflips green on any cloud with a working storage backend.Follow-ups
blockstorage_volume_type,blockstorage_qos, quotas (Phase 3);blockstorage_snapshotresource;compute_volume_attach(needs a booted instance + a real volume).