All of lore.kernel.org
 help / color / mirror / Atom feed
* Using different storage types on same osd hosts?
@ 2013-03-05 20:48 Stefan Priebe
  2013-03-06  8:58 ` [ceph-users] " Martin B Nielsen
  0 siblings, 1 reply; 3+ messages in thread
From: Stefan Priebe @ 2013-03-05 20:48 UTC (permalink / raw)
  To: ceph-users, ceph-devel@vger.kernel.org

Hi,

right now i have a bunch of OSD hosts (servers) which have just 4 disks 
each. All of them use SSDs right now.

So i have a lot of free harddisk slots in the chassis. So my idea was to 
create a second ceph system using these free slots. Is this possible? Or 
should i just the first one with different rules? Any hints?

Greets,
Stefan


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ceph-users] Using different storage types on same osd hosts?
  2013-03-05 20:48 Using different storage types on same osd hosts? Stefan Priebe
@ 2013-03-06  8:58 ` Martin B Nielsen
       [not found]   ` <CAD3n6hFUg0ks-V=XVTA+u+NLcM_ADEqhD7Nk_rx-A3FrWqLBuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Martin B Nielsen @ 2013-03-06  8:58 UTC (permalink / raw)
  To: Stefan Priebe; +Cc: ceph-users, ceph-devel@vger.kernel.org

Hi,

We did the opposite here; adding some SSD in free slots after having a
normal cluster running with SATA.

We just created a new pool for them and separated the two types. I
used this as a template:
http://ceph.com/docs/master/rados/operations/crush-map/?highlight=ssd#placing-different-pools-on-different-osds
and left out the part with placing a master copy on each ssd.

I had to create the pool, rack and host in the crush rules for the
first server (wouldn't let me from the command line using 'ceph osd
crush set ...'), after that I could just add servers/osd to it like
normal.

I think unless you really need two separate clusters, I'd go with just
having different pools for it; you'll need a copy of every service
(mons, storagenodes etc) with two clusters.

More info on running multiple clusters here:
http://ceph.com/docs/master/rados/configuration/ceph-conf/#running-multiple-clusters

Cheers,
Martin

On Tue, Mar 5, 2013 at 9:48 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> Hi,
>
> right now i have a bunch of OSD hosts (servers) which have just 4 disks
> each. All of them use SSDs right now.
>
> So i have a lot of free harddisk slots in the chassis. So my idea was to
> create a second ceph system using these free slots. Is this possible? Or
> should i just the first one with different rules? Any hints?
>
> Greets,
> Stefan
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Using different storage types on same osd hosts?
       [not found]   ` <CAD3n6hFUg0ks-V=XVTA+u+NLcM_ADEqhD7Nk_rx-A3FrWqLBuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2013-03-07 20:27     ` Stefan Priebe
  0 siblings, 0 replies; 3+ messages in thread
From: Stefan Priebe @ 2013-03-07 20:27 UTC (permalink / raw)
  To: Martin B Nielsen
  Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, ceph-users

Am 06.03.2013 09:58, schrieb Martin B Nielsen:
> Hi,
>
> We did the opposite here; adding some SSD in free slots after having a
> normal cluster running with SATA.
Thanks for your answer. Why did you do this? Was it to slow with SATA?

Stefan

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-03-07 20:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-05 20:48 Using different storage types on same osd hosts? Stefan Priebe
2013-03-06  8:58 ` [ceph-users] " Martin B Nielsen
     [not found]   ` <CAD3n6hFUg0ks-V=XVTA+u+NLcM_ADEqhD7Nk_rx-A3FrWqLBuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-07 20:27     ` Stefan Priebe

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.