[one-users] OpenVZ

[knawnd at gmail.com]

Hi!

Spent some time in attempts to implement OpenVZ support in OpenNebula 
via libvirt I realized that for the moment probably it was not the most 
efficient way to do that since libvirt provides pretty poor OpenVZ 
support. In particular:
1) some of openvz specific parameters/options are missing from libvirt 
docs (e.g. [1]) despite of they are mentioned in "Example guest domain 
XML configuration" at libvirt openvz driver page [2] (I submitted a bug: 
[3] );
2) as far as I understand there is no way to specify assigned disk space 
and disk inodes by libvirt means (feature request: [4]);
3) it looks like network device veth is wrongly assigned inside openvz 
container (at least I couldn't find the proper way to do that: [5]) and 
there is no way to use another network device - venet 
(http://wiki.openvz.org/Venet).
4) total (max) and used (current) memory parameters for certain VM 
always have a zero value ([6]).
Libvirt-users mail-list doesn't help too much to clarify details;
Most of issues mentioned above as well as e.g. [7] had been discussed 
before in libvirt mail-list (some of them more than a year ago) but I 
couldn't find any submitted bugs and that and those issues still exist.

For the moment I have done not so much progress in implementing openvz 
support in ONE via libvirt:
$ git status
# On branch one-openvz
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       new file:   src/im_mad/remotes/ovz.d/architecture.sh
#       new file:   src/im_mad/remotes/ovz.d/cpu.sh
#       new file:   src/im_mad/remotes/ovz.d/name.sh
#       new file:   src/im_mad/remotes/ovz.d/ovz.rb
#       new file:   src/vmm/LibVirtDriverOVZ.cc
#       new file:   src/vmm_mad/remotes/ovz/cancel
#       new file:   src/vmm_mad/remotes/ovz/deploy
#       new file:   src/vmm_mad/remotes/ovz/migrate
#       new file:   src/vmm_mad/remotes/ovz/ovzrc
#       new file:   src/vmm_mad/remotes/ovz/restore
#       new file:   src/vmm_mad/remotes/ovz/save
#       new file:   src/vmm_mad/remotes/ovz/shutdown
#       new file:   src/vmm_mad/remotes/poll_vmm.rb
#       deleted:    src/vmm_mad/remotes/poll_xen_kvm.rb
#       new file:   src/vmm_mad/ssh/vmm_ssh_ovz.conf
#
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#
#       modified:   include/LibVirtDriver.h
#       modified:   install.sh
#       modified:   share/etc/oned.conf
#       modified:   src/vmm/LibVirtDriverOVZ.cc
#       modified:   src/vmm/SConstruct
#       modified:   src/vmm/VirtualMachineManager.cc
#       modified:   src/vmm_mad/ssh/vmm_ssh_ovz.conf

Taking all mentioned above into account I incline to an opinion it would 
be better to implement openvz support in OpenNebula by native openvz 
means like vzctl/vzlist/vzcalc/vzmigrate/vzdump commands just invoking 
those commands on remote host.

I would like to know other opinions on that.

Best regards,
Nikolay.

[1] http://libvirt.org/formatdomain.html
[2] http://libvirt.org/drvopenvz.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=683355
[4] https://bugzilla.redhat.com/show_bug.cgi?id=683512
[5] https://bugzilla.redhat.com/show_bug.cgi?id=683834
[6] https://bugzilla.redhat.com/show_bug.cgi?id=683851
[7] https://bugzilla.redhat.com/show_bug.cgi?id=683834