Shuveb Hussain wrote:
There is the same problem with the Xen libraries. Dan had to rewrite a lot of code concerning access to the hypervisor.No matter how different I think, the end result looks just like the OpenVZ library code :-P So, I'm trying to write code that looks different, but does the same thing. The OpenVZ utilities are however, scripting friendly. Their text output is consistent. How about writing a daemon for OpenVZ that "talks" to the OpenVZ utilities, rather than trying to re-write the utilities? Would this be a bad idea?
It sounds like a very good idea. There can also be no question of infringement if done this way.
The actual libvirt can then connect to this daemon to get the real stuff done. This is what I did in my EasyVZ GUI tool for OpenVZ.
Why is the daemon needed though? The libvirt calls can just launch the OpenVZ command line tools as necessary. We got into daemons with QEMU, and it's nothing but trouble.
Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Description: S/MIME Cryptographic Signature