[libvirt] [Openstack][Openstack-dev]Where is libvirt library packages in Openstack Nova branch
Hi all, I read the source code of Openstack Nova branch source codes but i can not find the standard libvirt library packages, which i think Nova uses libvirt interfaces they are from standard libvirt library to attach Sheepdog(or others) volumes to QEMU. If i add a new block storage driver for standard libvirt, i have to update these libvirt library packages in Openstack Nova brahch. Cloud anyone give me some suggestions? Thanks in advance ;-) -- Thanks Harry Wei
On Sun, Jan 20, 2013 at 01:46:58PM +0800, harryxiyou wrote:
Hi all,
I read the source code of Openstack Nova branch source codes but i can not find the standard libvirt library packages, which i think Nova uses libvirt interfaces they are from standard libvirt library to attach Sheepdog(or others) volumes to QEMU. If i add a new block storage driver for standard libvirt, i have to update these libvirt library packages in Openstack Nova brahch. Cloud anyone give me some suggestions? Thanks in advance ;-)
The nova driver for talking to libvirt is in nova/virt/libvirt/ The libvirt code itself is not part of openstack, and available from our website http://libvirt.org Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On Mon, Jan 21, 2013 at 8:14 PM, Daniel P. Berrange <berrange@redhat.com> wrote: [...]
The nova driver for talking to libvirt is in nova/virt/libvirt/
Yup, i think so. Therefore, i also think nova driver in nova/virt/libvirt has some relationships with libvirt code itself, right? Nova driver send parameters to libvirt client(in Nova branch), then libvirt client send these parameters to libvirt serever(libvirt code itself). How do they(libvirt client and libvirt server) communicate with each other in details? I wonder if they(libvirt client and libvirt server) are a whole one in libvirt code itself. And Openstack just call libvirt client interfaces, which Openstack just package libvirt code itself to be a library for calling. Daniel, do you understand my meanings? Do you agree with me?
The libvirt code itself is not part of openstack, and available from our website http://libvirt.org Of course, Libvirt and Openstack are two independent and wonderful projects, i love them very much ;-)
-- Thanks Harry Wei
On Tue, Jan 22, 2013 at 12:13:57AM +0800, harryxiyou wrote:
On Mon, Jan 21, 2013 at 8:14 PM, Daniel P. Berrange <berrange@redhat.com> wrote: [...]
The nova driver for talking to libvirt is in nova/virt/libvirt/
Yup, i think so. Therefore, i also think nova driver in nova/virt/libvirt has some relationships with libvirt code itself, right? Nova driver send parameters to libvirt client(in Nova branch), then libvirt client send these parameters to libvirt serever(libvirt code itself). How do they(libvirt client and libvirt server) communicate with each other in details? I wonder if they(libvirt client and libvirt server) are a whole one in libvirt code itself. And Openstack just call libvirt client interfaces, which Openstack just package libvirt code itself to be a library for calling.
Nova simply uses the standard "libvirt" python module, which is a thin python wrapper around the libvirt.so C library. This library talks to the libvirtd server via a private RPC service. Nova only includes its own custom libvirt integration code, the libvirt python module isn't part of Nova. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On Tue, Jan 22, 2013 at 12:20 AM, Daniel P. Berrange <berrange@redhat.com> wrote: [...]
Nova simply uses the standard "libvirt" python module, which is a thin python wrapper around the libvirt.so C library.
I think so, but i wonder if the standard "libvirt" python module is nova/virt/libvirt/driver.py?
This library talks to the libvirtd server via a private RPC service. Nova only includes its own custom libvirt integration code, the libvirt python module isn't part of Nova.
But the libvirt python module is in the Nova branch. Why do you think it is not a part of Nova? Is it part of libvirt code itself? -- Thanks Harry Wei
On Tue, Jan 22, 2013 at 01:08:23AM +0800, harryxiyou wrote:
On Tue, Jan 22, 2013 at 12:20 AM, Daniel P. Berrange <berrange@redhat.com> wrote: [...]
Nova simply uses the standard "libvirt" python module, which is a thin python wrapper around the libvirt.so C library.
I think so, but i wonder if the standard "libvirt" python module is nova/virt/libvirt/driver.py?
That isn't the libvirt python module. That is Nova's libvirt integration driver code. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On Tue, Jan 22, 2013 at 1:10 AM, Daniel P. Berrange <berrange@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
participants (2)
-
Daniel P. Berrange -
harryxiyou