From: Wido den Hollander <wido@42on.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: QCOW2 to RBD format 2 in one step
Date: Tue, 14 May 2013 12:16:32 +0200 [thread overview]
Message-ID: <51920F00.406@42on.com> (raw)
Hi,
While working on the CloudStack code for 4.2 I'm running into some
problems with QCOW2 and RBD format 2.
A quick cap of the problem:
CloudStack stores all the templates on "Secondary Storage" as QCOW2 files.
When a VM is deployed, this image will be copied (once) from Secondary
Storage to Primary Storage, this is done by qemu-img which does the
conversion.
When the image is on Primary Storage it will be copied to the
destination volume and the Instance/VM is started.
In that last step I want to use layering, but the problem is that my
image is RBD format 1 due to the qemu-img copy.
I can skip the qemu-img copy, but I have to find a way to go from QCOW2
to RBD format 2 in preferably one step. There is a issue about this in
the tracker [0], but that won't be finished on time.
Another idea would be to do QCOW2 -> RAW -> RBD format 2, but that extra
step will take a lot of time. It would also require some temporary
storage on the hypervisor.
I also thought of creating the RBD image prior to converting to it, but
that fails, since qemu-img won't let you convert to a already existing
image.
Any brights ideas? Maybe even doing the QCOW2 -> RAW format in memory?
In Java?
The goal is to go from QCOW2 to RBD format 2 in one step.
[0]: http://tracker.ceph.com/issues/4897
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
next reply other threads:[~2013-05-14 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 10:16 Wido den Hollander [this message]
2013-05-14 10:34 ` QCOW2 to RBD format 2 in one step Leen Besselink
2013-05-14 11:52 ` Wido den Hollander
2013-05-14 12:11 ` Damien Churchill
2013-05-14 12:15 ` Leen Besselink
2013-05-14 14:36 ` Alexandre DERUMIER
2013-05-14 20:10 ` Josh Durgin
2013-05-14 19:57 ` Josh Durgin
2013-05-14 20:37 ` Wido den Hollander
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=51920F00.406@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.