VM storage cluster #3234
Replies: 2 comments 18 replies
-
I have a small proxmox cluster and have mounted seaweedfs via weed mount onto the servers, then added the directory within the proxmox web interface. You can happily deploy a new VM or container onto the mount point and it will run, migration etc will all work. I did start writing a proxmox plugin to wrap seaweedfs, but I've not finished it yet as earlier versions of seaweedfs failed with qcow2 and large raw files, it has only been the last 2 or 3 versions of seaweedfs that will work correctly with virtual machine images. I'd say the performance isn't the best for VMs but at the same time I've not really done a lot of testing around using it for VMs, I'm guessing that playing with chunk sizes will yield varying results. I've been trying seaweedfs in various situations to see if I can break it so as to gain confidence in it before deploying it to a production environment. I use 3 x master, 3 x filers using leveldb2 and 3 or 4 volume servers which are a mix of hdds and ssds. Replication is either 001 or 000, both work fine. I have also tried using juicefs connected to seaweedfs via the s3 interface, install of the vms is faster but the running of them is slower, again I've only done minimal experiments with this so playing with chunk sizes could yield vastly different results. Ultimately I would like to be able to use seaweedfs for both file storage within a nomad cluster and also for vm / lxc storage. |
Beta Was this translation helpful? Give feedback.
-
Having similar query regarding seaweedfs support of large vm files like qcow2. Are above issues resolved or is much larger disks in the tune of TBs been used/TBs being tested? |
Beta Was this translation helpful? Give feedback.
-
Has anyone successfully deployed seaweedfs as a virtual machine storage pool? I.e. run virtual machine disk image files from
weed mount
or other method?Beta Was this translation helpful? Give feedback.
All reactions