[openstack-dev] [Fuel} Separating Ceph pools depending on storage type

Federico Michele Facca federico.facca at create-net.org
Fri Mar 20 06:46:30 UTC 2015


hi,
generally speaking it would be nice to have the possibility to define
availability zones. and this could be used as well to group, not only
computing resources, but also storage ones. for this if i am not wrong
there is already a discussion or blueprint on this from mirantis folks.
then i am not sure this would be exactly what you need :)

best,
federico

On Fri, Mar 20, 2015 at 3:12 AM, Rogon, Kamil <kamil.rogon at intel.com> wrote:

> Hello,
>
> I want to initiate a discussion about different backend storage types for
> Ceph. Now all types of drives (HDD, SAS, SSD) are treated the same way, so
> the performance can vary widely.
>
> It would be good to detect SSD drives and create separate Ceph pool for
> them. From the user perspective, it should be able to select pool when
> scheduling an instance (scenario for high-IOPS needed VM, like database).
>
> Regards,
> Kamil Rogon
>
> ----------------------------------------------------------------------------
> ---
> Intel Technology Poland sp. z o.o.
> KRS 101882
> ul. Slowackiego 173
> 80-298 Gdansk
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
--
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

-- 
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P  +39 0461 312471
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150320/b8076a1f/attachment.html>


More information about the OpenStack-dev mailing list