[MESOS-9540] Support `DESTROY_DISK` on preprovisioned CSI volumes.

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Done
• Fix Version/s: 1.7.3, 1.8.0
• Component/s: storage
• Labels: mesosphere mesosphere-dss-ga storage
• Target Version/s: 1.7.3, 1.8.0
• Epic Link: Resource Provider and CSI Tech Debt
• Sprint: Storage R11 Sprint 40, Storage: RI-12 Sprint 43
• Story Points: 2
• Assignee: Chun-Hung Hsiao
• Reporter: Chun-Hung Hsiao
• Shepherd: Benjamin Bannier
• Created: 28/Jan/19 20:09
• Updated: 01/Apr/19 10:45
• Resolved: 29/Mar/19 23:45

Description

Currently the experimental DESTROY_DISK operation only applies to BLOCK or MOUNT disk resources. We should consider supporting DESTROY_DISK on RAW disk resources with source IDs as well. This could be handy in e.g., the following scenario:

1. The framework issued a CREATE_DISK.
2. The SLRP received CREATE_DISK and translated to a CreateVolume CSI call.
3. While the CreateVolume is ongoing, the agent was restarted with a new agent ID, causing the SLRP to lose its bookkeeping and start with a new RP ID as well, and hence the CREATE_DISK operation was lost.
4. The CreateVolume call succeeded and the new SLRP picked it up as a preprovisioned CSI volume.

In the above case, the framework should be able to choose to either "import" the CSI volume through CREATE_DISK, or directly reclaim the space through DESTROY_DISK. Currently the framework needs to always import the CSI volume before reclaiming the space.

Issue Links

• is related to: MESOS-9254 Make SLRP be able to update its volumes and storage pools.
• is related to: MESOS-9655 Improving SLRP tests for preprovisioned volumes.