Description

As indicated by our roadmap, we want a better management for volumes. There has been good attempts toward this in the past but it wasn't a priority, and the volume subsystem needed a refactoring.

How to

We need a top-level volume management command which takes its inspiration from what has been done on networking to support the new CNM (Container Networking Model).

• Define and propose a new volume management UX
  • Consistent with network management
  • Taking plugins into account
  • Doesn't make it cumbersome fo create "throwawy" volumes?
• Ideally implement command-line and API endpoints inside the volumes subsystem

Questions

• How are networks internally idenfied? Do they have a randomly generated unique id? If so, should
  we do the same for volumes and should those ids be all be in the same scope?

Reference

• Proposal: Add volume ls/inspect/rm/create commands #8484: earlier implementation
• Proposal: Volume refactor and external volume plugins #13161: volume refactoring
• Experimental feedback - Volume plugins #13420: some feedback to take into account
• Volume extensions: from experimental to stable #14213: volume extensions

Ping @cpuguy83!