fuel-dev team mailing list archive

[Miroslav Anashkin <manashkin@xxxxxxxxxxxx>]

Hi Dmitry,

A1 - A2) Yes. It is greatly recommended to use RAW images for CEPH. CEPH
has own copy-on-write mechanism.
For qcow2 ones Ceph has to expand and convert the image to full size, since
it does not support images with on-demand space reservation.
BTW, it is in our docs:
http://docs.mirantis.com/openstack/fuel/fuel-5.0/reference-architecture.html?highlight=raw#object-storage-for-images

Kind regards,
Miroslav


On Wed, Jun 25, 2014 at 7:08 PM, Dmitriy Novakovskiy <
dnovakovskiy@xxxxxxxxxxxx> wrote:

> Hi Fuelers,
>
> One of my customers is testing Fuel 5.0 w/ Ceph. He's trying to boot a VM
> from a volume, using qcow2 image as a source for volume creation. What
> we're seeing (Nikita in CC was helping w/ troubleshooting) is:
> - image is copied from Glance (which uses Ceph as backend)
> - image is converted from qcow2 to raw
> - new RBD volume is created from raw image
>
> Looks kinda suboptimal - given both image and boot volume being hosted on
> Ceph I'd expect copy-on-write cloning to work.
>
> Q1) Are there some limitations here, like images stored on Ceph should be
> in RAW initially?
> Q2) Would the same (images should be in raw) apply to boot from image
> scenario, when VM's ephemeral disk is stored on Ceph?
>
> Thoughts much appreciated. If necessary I can arrange for someone to take
> a look at customer's pod
>
> ---
> Regards,
> Dmitriy
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 

*Kind Regards*

*Miroslav Anashkin**L2 support engineer**,*
*Mirantis Inc.*
*+7(495)640-4944 (office receptionist)*
*+1(650)587-5200 (office receptionist, call from US)*
*35b, Bld. 3, Vorontsovskaya St.*
*Moscow**, Russia, 109147.*

www.mirantis.com

manashkin@xxxxxxxxxxxx