All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Gregory Farnum <greg@inktank.com>,
	John Nielsen <lists@jnielsen.net>,
	ceph-devel@vger.kernel.org
Subject: Re: questions on networks and hardware
Date: Tue, 22 Jan 2013 13:05:09 -0800	[thread overview]
Message-ID: <50FEFF05.1050700@inktank.com> (raw)
In-Reply-To: <CAJH6TXhxCBeB7-0vw3mbVO05zckH=F5JiVBJG7woW2SfwrBFBQ@mail.gmail.com>



On 01/21/2013 12:19 AM, Gandalf Corvotempesta wrote:
> 2013/1/21 Gregory Farnum <greg@inktank.com>:
>> I'm not quite sure what you mean…the use of the "cluster network" and "public network" are really just intended as conveniences for people with multiple NICs on their box. There's nothing preventing you from running everything on the same network…(and more specifically, from different speed grades to different boxes, but keeping them all on the same network).
>
> I mean using two cluster network and two pubic networks. 4 NICs in total.
> Our cluster network will be 10GBe or Infiniband DDR/QDR, making a
> fully redundany cluster network (two nics on each server, two
> switches) will double our costs.

Well, again, you needn't use two different networks for Ceph; that 
capability is there so that you *can* only use the faster gear for the 
cluster traffic if you want to limit costs but still segregate traffic. 
  If you're just after a fully-redundant network (by which I assume you 
also mean fully-redundant fabric, power, etc.), there's no reason it 
can't all be fast gear.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-01-22 21:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 23:34 questions on networks and hardware John Nielsen
2013-01-19 16:00 ` Holcombe, Christopher
2013-01-20 17:16 ` Wido den Hollander
2013-01-20 18:51   ` Jeff Mitchell
2013-01-20 19:05     ` Sage Weil
2013-01-20 18:52   ` Stefan Priebe
2013-01-20 19:03     ` Sage Weil
2013-01-21 23:15   ` John Nielsen
2013-01-22 13:20     ` Wido den Hollander
2013-01-22 14:58       ` Jeff Mitchell
2013-01-20 20:30 ` Gandalf Corvotempesta
2013-01-20 22:23   ` Gregory Farnum
2013-01-20 22:43     ` Gandalf Corvotempesta
2013-01-20 23:17       ` Gregory Farnum
2013-01-21  8:19         ` Gandalf Corvotempesta
2013-01-22 21:05           ` Dan Mick [this message]

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=50FEFF05.1050700@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=greg@inktank.com \
    --cc=lists@jnielsen.net \
    /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.