qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack
@ 2013-01-19  8:47 harryxiyou
  2013-01-19 14:04 ` MORITA Kazutaka
  0 siblings, 1 reply; 3+ messages in thread
From: harryxiyou @ 2013-01-19  8:47 UTC (permalink / raw)
  To: Kazutaka Morita
  Cc: openstack-dev, sheepdog, libvir-list, qemu-devel, openstack,
	cloudxy, Liu Yuan, Kang Hua

Hi all,

I wanna add a new block storage driver by Libvirt/Qemu way for Openstack, which
is as same as Sheepdog driver for Openstack. So i think the theories
are like this.

1, In the Openstack Nova branch, Openstck driver call libvirt client
and send parameters
to libvirt client.(From this point, i should modify Openstack Nova
source codes. They are
a, nova/nova/virt/libvirt/driver.py    add new driver way
b, /OpenStack/nova/nova/tests/test_libvirt.py  add new driver test)

2, According to own protocol, libvirt client in Openstack Nova branch
send parameters to
Libvirt server.(From this point, i should modify libvirt library to
let libvirt library support this
new driver like Sheepdog).

3, Libvirt server call Qemu interfaces to send parameters to
Qemu.(From this point, i should
modify Qemu source codes to let Qemu support this new driver like Sheepdog).

4, In Openstack Cinder branch, Openstack driver use Qemu commands to
create this new volumes
to Qemu.(From this point, i should modify Openstack Cinder branch
source codes like this.
a, Add new driver file
/OpenStack/cinder/cinder/volume/drivers/new_driver.py like Sheepdog.py
b, Change file /OpenStack/cinder/cinder/tests/test_drivers_compatibility.py
to test new driver).

5, At last, i should also modify
/OpenStack/manuals/doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml
to configure this new driver.

Are my theories right? Should i do any other stuffs? Could anyone give
me any other suggestions?
Thanks in advance ;-)

-- 
Thanks
Harry Wei

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack
  2013-01-19  8:47 [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack harryxiyou
@ 2013-01-19 14:04 ` MORITA Kazutaka
  2013-01-19 15:39   ` harryxiyou
  0 siblings, 1 reply; 3+ messages in thread
From: MORITA Kazutaka @ 2013-01-19 14:04 UTC (permalink / raw)
  To: harryxiyou
  Cc: openstack-dev, sheepdog, Kazutaka Morita, qemu-devel, openstack,
	libvir-list, cloudxy, Liu Yuan, Kang Hua

At Sat, 19 Jan 2013 16:47:37 +0800,
harryxiyou wrote:
> 
> Hi all,
> 
> I wanna add a new block storage driver by Libvirt/Qemu way for Openstack, which
> is as same as Sheepdog driver for Openstack. So i think the theories
> are like this.
> 
> 1, In the Openstack Nova branch, Openstck driver call libvirt client
> and send parameters
> to libvirt client.(From this point, i should modify Openstack Nova
> source codes. They are
> a, nova/nova/virt/libvirt/driver.py    add new driver way
> b, /OpenStack/nova/nova/tests/test_libvirt.py  add new driver test)
> 
> 2, According to own protocol, libvirt client in Openstack Nova branch
> send parameters to
> Libvirt server.(From this point, i should modify libvirt library to
> let libvirt library support this
> new driver like Sheepdog).
> 
> 3, Libvirt server call Qemu interfaces to send parameters to
> Qemu.(From this point, i should
> modify Qemu source codes to let Qemu support this new driver like Sheepdog).
> 
> 4, In Openstack Cinder branch, Openstack driver use Qemu commands to
> create this new volumes
> to Qemu.(From this point, i should modify Openstack Cinder branch
> source codes like this.
> a, Add new driver file
> /OpenStack/cinder/cinder/volume/drivers/new_driver.py like Sheepdog.py
> b, Change file /OpenStack/cinder/cinder/tests/test_drivers_compatibility.py
> to test new driver).
> 
> 5, At last, i should also modify
> /OpenStack/manuals/doc/src/docbkx/openstack-compute-admin/tables/hypervisors-nova-conf.xml
> to configure this new driver.
> 
> Are my theories right? Should i do any other stuffs? Could anyone give
> me any other suggestions?

If you do the above work, I think you can use your file system with
OpenStack.

But I suggest doing them step by step.  If your file system is not
supported in QEMU, I think libvirt won't support it.  If libvirt
doesn't support it, OpenStack shouldn't support it too.

Thanks,

Kazutaka

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack
  2013-01-19 14:04 ` MORITA Kazutaka
@ 2013-01-19 15:39   ` harryxiyou
  0 siblings, 0 replies; 3+ messages in thread
From: harryxiyou @ 2013-01-19 15:39 UTC (permalink / raw)
  To: MORITA Kazutaka
  Cc: openstack-dev, sheepdog, libvir-list, qemu-devel, openstack,
	cloudxy, Liu Yuan, Kang Hua

On Sat, Jan 19, 2013 at 10:04 PM, MORITA Kazutaka
<morita.kazutaka@gmail.com> wrote:
> At Sat, 19 Jan 2013 16:47:37 +0800,
[...]
> If you do the above work, I think you can use your file system with
> OpenStack.
>

Thanks for your review ;-)

> But I suggest doing them step by step.  If your file system is not
> supported in QEMU, I think libvirt won't support it.  If libvirt
> doesn't support it, OpenStack shouldn't support it too.
>

Yes, i think so. I will finish this job step by step ;-)



-- 
Thanks
Harry Wei

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-01-19 15:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-19  8:47 [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack harryxiyou
2013-01-19 14:04 ` MORITA Kazutaka
2013-01-19 15:39   ` harryxiyou

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).