Open Stack

On Tue, Jan 22, 2013 at 1:10 AM, Daniel P. Berrange <berrange at redhat.com> wrote:
[...]
> That isn't the libvirt python module. That is Nova's libvirt integration
> driver code.

That is to say, libvirt.so is from standard libvirt code itself and libvirt
python module is from libvirt.so. They(libvirt.so and libvirt python module)
are part of libvirt. And Nova just uses libvirt integration driver codes.
But i wonder if they(libvirt integration codes and libvirt python module)
have any relationships? What and how do they have? Nova's libvirt integration
codes call libvirt python module, right?

-- 
Thanks
Harry Wei