[Users] Manage KVM/Qemu and OpenVZ the same way

[Bosson VZ]

Hi,

the problem with the VNC helper is that it uses the internal libvirt API heavily and thus it would be very difficult to make it completely stand-alone. Apart from that, it is a pretty generic code, so it could be used by e.g. the LXC libvirt driver.

-- 
David Fabian
Cluster Design, s.r.o.

Dne St 2. července 2014 17:23:39, Pavel Odintsov napsal(a):
> Oh, vnc for vzctl! It's amazing! Maybe you can contribute this helper to OpenVZ?
> 
> On Wed, Jul 2, 2014 at 5:20 PM, Pavel Odintsov <pavel.odintsov at gmail.com> wrote:
> > 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 <bossonvz at 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 at openvz.org
> >> https://lists.openvz.org/mailman/listinfo/users
> >>
> >
> >
> >
> > --
> > Sincerely yours, Pavel Odintsov
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20140703/0895560c/attachment-0001.html>