Hello Paolo!

We had libvirt driver for CTs some time ago.
Its functionality was not on par with prlctl/vzctl and it was dropped from 
provided binary releases.

Best regards,
Konstantin

From: users-boun...@openvz.org <users-boun...@openvz.org> On Behalf Of Paulo 
Coghi - Coghi IT
Sent: Monday, December 23, 2019 7:07 PM
To: OpenVZ users <users@openvz.org>
Subject: [Users] Question about libvirt and prlctl

Hello OpenVZ community,


Short question
Is libvirt as complete as prlctl regarding OpenVZ/Virtuozzo containers 
management? Can we change resources independently and without reboot using 
libvirt instead of prlctl? Can we manage every aspect of a container on libvirt 
as we can on prlctl?
-

Full question
I am developing a new open source OpenVZ control panel, as previously discussed 
here on the list, based on NodeJS to the back-end API and a modern front-end 
framework to the UI.
The only challenge for me is the communication between NodeJS and OpenVZ and,
after asking for suggestions about this on the openvz-dev list, the most 
prominent suggestion I received was to use the Virtuozzo SDK and node-gyp.

The first problem that I faced on this approach was that Google is moving to 
gn, which means that the gyp's days of support are counted.

Researching for an alternative for node-gyp, I found cmake-js, that works 
exactly like node-gyp, but instead of gyp, it is based on CMake build system.

But it can't use C sources, but only compiled C libraries, and this approach 
started to get a little complex for me to follow alone.

For this reason, I am currently considering to use libvirt and I would like to 
know if it has feature-parity with prlctl, when managing OpenVZ/Virtuozzo 
containers.



Thanks again!
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Reply via email to