Skip to content

VAST driver: Add multitenancy support via share types#17

Open
Alex-Welsh wants to merge 1 commit into
stackhpc/2026.1from
2026.1-cherries
Open

VAST driver: Add multitenancy support via share types#17
Alex-Welsh wants to merge 1 commit into
stackhpc/2026.1from
2026.1-cherries

Conversation

@Alex-Welsh

Copy link
Copy Markdown
Member

Cherry-pick of an upstream patch we have in our 2025.1 fork. (This is a cherry-pick of the latest patchset, not the exact change we have in 2025.1)

This patch adds multitenancy support to the VAST Manila driver by allowing administrators to specify different VIP pools per share type using the namespaced extra spec 'vast:vippool_name'. This enables network isolation between different tenants or projects while sharing the same Manila backend.

Change-Id: If01c9fd888b4338a7ac5408f6a589e9bbeae8903

This patch adds multitenancy support to the VAST Manila driver by
allowing administrators to specify different VIP pools per share type
using the namespaced extra spec 'vast:vippool_name'. This enables
network isolation between different tenants or projects while sharing
the same Manila backend.

Change-Id: If01c9fd888b4338a7ac5408f6a589e9bbeae8903
Signed-off-by: Volodymyr Boiko <volodymyr.boiko@vastdata.com>
@Alex-Welsh Alex-Welsh requested a review from a team as a code owner June 12, 2026 13:33
@Alex-Welsh

Copy link
Copy Markdown
Member Author

DNM until we decide if we want to use zuul

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.

2 participants