qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: MORITA Kazutaka <morita.kazutaka@gmail.com>
To: harryxiyou <harryxiyou@gmail.com>
Cc: openstack-dev@lists.launchpad.org,
	sheepdog <sheepdog@lists.wpkg.org>,
	Kazutaka Morita <morita.kazutaka@gmail.com>,
	qemu-devel@nongnu.org, openstack@lists.launchpad.net,
	libvir-list@redhat.com, cloudxy@googlegroups.com,
	Liu Yuan <namei.unix@gmail.com>, Kang Hua <kanghua151@gmail.com>
Subject: Re: [Qemu-devel] [Openstack][Sheepdog][Libvirt][Qemu]Add a new block storage driver by Libvirt/Qemu way for Openstack
Date: Sat, 19 Jan 2013 23:04:48 +0900	[thread overview]
Message-ID: <m21udhxo8v.wl%morita.kazutaka@gmail.com> (raw)
In-Reply-To: <CAD+1EGOnRbkHg0EAtvX7gic=bsXhKYUfUEitLcOrp5pVjXJ+PA@mail.gmail.com>

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

  reply	other threads:[~2013-01-19 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2013-01-19 15:39   ` harryxiyou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m21udhxo8v.wl%morita.kazutaka@gmail.com \
    --to=morita.kazutaka@gmail.com \
    --cc=cloudxy@googlegroups.com \
    --cc=harryxiyou@gmail.com \
    --cc=kanghua151@gmail.com \
    --cc=libvir-list@redhat.com \
    --cc=namei.unix@gmail.com \
    --cc=openstack-dev@lists.launchpad.org \
    --cc=openstack@lists.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).