Support for locking and unlocking shares

Registered by Goutham Pacha Ravi

This specification concerns a feature discussed at the 2023.2 Bobcat PTG.

We need a mechanism in Manila to allow locking a share from deletion. Such a locking mechanism will be used by nova when mounting Manila shares to expose to guests via VirtIOFS. Without a lock, shares can be deleted while they are mounted. Deleting a mounted share that's hard mounted on a nova virtual machine host will likely bring down the host.

[1] https://etherpad.opendev.org/p/nova-bobcat-ptg#72

Blueprint information

Status:
Complete
Approver:
Carlos Eduardo
Priority:
Undefined
Drafter:
Goutham Pacha Ravi
Direction:
Needs approval
Assignee:
Goutham Pacha Ravi
Definition:
Approved
Series goal:
Accepted for bobcat
Implementation:
Implemented
Milestone target:
None
Started by
Goutham Pacha Ravi
Completed by
Goutham Pacha Ravi

Related branches

Sprints

Whiteboard

Addressed by: https://review.opendev.org/c/openstack/manila-specs/+/881894
    Allow locking shares against deletion

Gerrit topic: https://review.opendev.org/#/q/topic:bp/allow-locking-shares-against-deletion

Addressed by: https://review.opendev.org/c/openstack/manila/+/887725
    Allow restricting access rules fields and deletion

Addressed by: https://review.opendev.org/c/openstack/manila/+/887115
    Resource Locks: Support for share deletion lock

Addressed by: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/888618
    Test resource locks

Addressed by: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/889331
    Add access rules restriction tests

Addressed by: https://review.opendev.org/c/openstack/manila/+/892582
    TrivialFix: Don't warn on legitimate all_projects usage

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.