multiple path for volume

[fahimeh2010]

Hello all First thanks for your opensource project. How can I run convoy vfs/nfs daemon with multiple specified path for saving volumus? thanks a lot

[yasker]

What do you mean by multiple specified path? Currently one Convoy daemon only support one vfs.path a.k.a. one specific path.

[Ramblurr]

@yasker I think the original reporter was asking if it is possible to have multiple convoy daemons running, each with its own storage location.

For example, we have 2 local storage pools, one backed by fast SSDs and the other by slower HDDs. Ideally we could use multiple instance of the convoy daemon (or a single instance configured to support backends) to store some volumes in one pool and some volumes in another.

Something like:

--volume-driver=convoy-pool1
--volume-driver=convoy-pool2

[yasker]

@Ramblurr I think the multiple instance usage is more doable, and different locations can be referred as different driver names. Though it won't work for device mapper at least for now because IIRC the name of the storage pool is fixed.

It should be possible to get it done without modifying the core code, by using different directories as the configuration root and different name in the volume plugin spec provides to the Docker.