Ask Your Question

Revision history [back]

A volume is a disk. You can attach it to an instance, put a file system on it and create a file on that file system that is then persistent. To the instance, a volume looks like a block device, which you may call drive, or disk, or LUN etc. It may well be implemented as something else than a disk, e.g. a logical volume or a Ceph device, but I believe your question is not about the implementation. In short, if I understand your question correctly, the answer is no.

Apart from Cinder, you can use Swift or Manila for persistent storage. Manila manages remote filesystems, not disks, which reside on Windows or NFS shares. Perhaps this is what you are looking for? Swift is an altogether different beast. A Swift object neither looks like a disk, nor a filesystem, nor a file, and is accessed using HTTP.

Admittedly, it’s not clear to me what exactly you want to achieve and why volumes are not a solution to your problem.

A volume is a disk. You can attach it to an instance, put a file system on it and create a file on that file system that is then persistent. To the instance, a volume looks like a block device, which you may call drive, or disk, or LUN etc. It may well be implemented as something else than a disk, e.g. a logical volume or a Ceph device, but I believe your question is not about the implementation. In short, if I understand your question correctly, the answer is no.

Apart from Cinder, you can use Swift or Manila for persistent storage. Manila manages remote filesystems, not disks, which reside on Windows or NFS shares. shares and many other backends. Perhaps this is what you are looking for? Swift is an altogether different beast. A Swift object neither looks like a disk, nor a filesystem, nor a file, and is accessed using HTTP.

Admittedly, it’s not clear to me what exactly you want to achieve and why volumes are not a solution to your problem.