nes though.
> -Original Message-
> From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
> si...@turka.nl
> Sent: Thursday, 19 October 2017 6:41 AM
> To: Samuel Soulard
> Cc: ceph-users
> Subject: Re: [ceph-users] Thick provisioning
>
> Hi all,
>
Hi all,
Thanks for the replies.
The main reason why I was looking for the thin/thick provisioning setting
is that I want to be sure that provisioned space should not exceed the
cluster capacity.
With thin provisioning there is a risk that more space is provisioned than
the cluster capacity. When
I can only speak for some environments, but sometimes, you would want to
make sure that a cluster cannot fill up until you can add more capacity.
Some organizations are unable to purchase new capacity rapidly and making
sure you cannot exceed your current capacity, then you can't run into
problems
> Op 17 oktober 2017 om 19:38 schreef Jason Dillaman :
>
>
> There is no existing option to thick provision images within RBD. When
> an image is created or cloned, the only actions that occur are some
> small metadata updates to describe the image. This allows image
> creation to be a quick, co
There is no existing option to thick provision images within RBD. When
an image is created or cloned, the only actions that occur are some
small metadata updates to describe the image. This allows image
creation to be a quick, constant time operation regardless of the
image size. To thick provision
Hi,
I have deployed a Ceph cluster (Jewel). By default all block devices that
are created are thin provisioned.
Is it possible to change this setting? I would like to have that all
created block devices are thick provisioned.
In front of the Ceph cluster, I am running Openstack.
Thanks!
Sinan
