OpenVZ Forum


Home » Mailing lists » Users » openvz ploop images on moosefs mount
Re: Re: openvz ploop images on moosefs mount [message #45744 is a reply to message #45741] Mon, 02 April 2012 10:54 Go to previous messageGo to previous message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
Am 02.04.2012 12:19, schrieb Aleksandar Ivanisevic:
> Out of interest, have you tried running VEs off of moosefs, directly,
> without ploop? How does that work, if at all?

Yes, but only for a quick test and not with any production data:

- setup moosefs as usual and mount it on host
- create (sparse) file for container on moosefs mount
- use this file to setup a loop device using losetup
- make fs on loop device and mount it to the container's private folder
- start the container as usual

I din't really like this approach because it involes a lot of (slow)
layers and double buffering issues and so I'd expect quite bad
performance. If you try it yourself and do some benchmarks I'd be very
happy to know the results.

I didn't try to use moosefs directly (without loop device) as a backing
storage for containers because I made very bad experience (mostly
performance and stability) with all kinds of network storages in the past.

From my past experience having a distributed block device (and not a
distributed file system) is the way to go, as the system then has almost
"native" performance due to the page cache (if not too many layers are
involved as above).

I'm currently evaluating distributed network block devices, but
unluckily there doesn't one to exist yet:
http://serverfault.com/questions/375570/distributed-fault-to lerant-network-block-device/375821#375821

Corin
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: openvz oracle linux unbreakable kernel
Next Topic: Missing changelogs in kernel.spec
Goto Forum:
  


Current Time: Thu Oct 09 12:37:45 GMT 2025

Total time taken to generate the page: 0.08110 seconds