On 07/03/2014 05:19 AM, Bosson VZ wrote: > > Hi, > > > > the driver supports vSwap AFAIK. You can set RAM limits (soft, hard) > and SWAP hard limit (soft is always 0). Could you explain to me what > you mean by vRaw? > > > > I understand that vzctl provides a lot of knobs to play with but since > libvirt is supposed to be a common management interface, I had to play > by the libvirt rules. I extended the libvirt XML syntax only as much > as was needed for supporting the amount of features that we use at the > company. I also didn't want break too many things and sticked with the > semantics that was already in libvirt for LXC. > > > > UBC settings is currently reduces to only manage RAM and SWAP. All > other UBC limits are set as unrestricted. >
You'd better also set some secondary UBCs (if those are not set explicitly), same as vzctl does and as described at http://openvz.org/VSwap#Implicit_UBC_parameters Those are lockedpages, oomguarpages, vmguarpages, and optionally privvmpages. > Technically, it is not hard to extend the driver to support all the > UBC limits but I don't want to divert from the upstream libvirt domain > file syntax too much. > > > > Ploop is not supported as we don't use it in the company. Most of the > features that ploop provides can be easily achieved with LVM/drbd. > I tend to disagree here. First, ploop works on top of ext4 filesystem, so it's way more flexible. You just can't move an LVM partition to a different server (in ploop case it's just scp). There is no online snapshot merging in LVM as far as I know. Finally, I can't see how DRBD can be a replacement for ploop copy. This is just from the top of my head, maybe there's something else as well (say I'm not sure how good is LVM online grow/shrink). > However, unlike the UBC limits, there is already a syntax for > "mounting a file as a file system" in libvirt, so implementing ploop > might be possible. > > > > -- > > David Fabian > > Cluster Design, s.r.o. > > > > Dne St 2. c(ervence 2014 17:20:19, Pavel Odintsov napsal(a): > > > Hello! > > > > > > Very nice! But what about vRaw/vSwap/non standard UBC management and > > > ploop support? I'm used libvirt for kvm few years but it's really ugly > > > for OpenVZ in upstream repository from RH. > > > > > > On Wed, Jul 2, 2014 at 4:26 PM, Bosson VZ <bosso...@bosson.eu> wrote: > > > > Helo, > > > > > > > > > > > > > > > > for everyone who would like to manage their Qemu/KVM and OpenVZ > virtuals in > > > > the same fashion, I am presenting a new libvirt driver, bossonvz, > which will > > > > allow you to manage OpenVZ containers with libvirt. To name a > couple of > > > > features: > > > > > > > > > > > > > > > > - complete control over the container > > > > > > > > - live migration via libvirtd > > > > > > > > - remote VNC console > > > > > > > > - fs mounts management > > > > > > > > > > > > > > > > Just check this web page out to find out more. > > > > > > > > > > > > > > > > http://bossonvz.bosson.eu/ > > > > > > > > > > > > > > > > The driver is provided as a separate patch to libvirt and as RPM > packages > > > > for CentOS/SL 6.5. > > > > > > > > > > > > > > > > -- > > > > > > > > David Fabian > > > > > > > > Cluster Design, s.r.o. > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users@openvz.org > > > > https://lists.openvz.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
