CEPH filesystem development
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: 袁冬 <yuandong1222@gmail.com>, "Gregory Farnum" <greg@inktank.com>,
	ceph-devel@vger.kernel.org
Subject: Re: production ready?
Date: Tue, 30 Oct 2012 14:06:28 -0700	[thread overview]
Message-ID: <50904154.7080004@inktank.com> (raw)
In-Reply-To: <CAJH6TXg=DpmE8O24TPtQwPL3MsEaqqdxBsnhS1zAFmjgRbUYrQ@mail.gmail.com>



On 10/30/2012 07:59 AM, Gandalf Corvotempesta wrote:
> 2012/10/30 袁冬 <yuandong1222@gmail.com>:
>> Yes, but network (and many other isssues) must be considered.
>
> Obviously
>
>> 3 is suggested.
>
> Any contraindication running mon in the same OSD server?
>

Generally that's considered OK.  ceph-mon doesn't use very much disk or 
CPU or network bandwidth.
--
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:[~2012-10-30 21:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 21:52 production ready? Gandalf Corvotempesta
2012-10-29 20:21 ` Dan Mick
2012-10-30 11:35   ` Gandalf Corvotempesta
2012-10-30 13:15     ` Gregory Farnum
2012-10-30 13:36       ` Gandalf Corvotempesta
2012-10-30 13:38         ` Stefan Priebe - Profihost AG
2012-10-30 13:45           ` Gregory Farnum
2012-10-30 20:32             ` Stefan Priebe
2012-10-30 13:40         ` Gregory Farnum
2012-10-30 13:57           ` Gandalf Corvotempesta
2012-10-30 14:17             ` 袁冬
2012-10-30 14:31               ` Gandalf Corvotempesta
2012-10-30 14:38                 ` 袁冬
2012-10-30 14:59                   ` Gandalf Corvotempesta
2012-10-30 21:06                     ` Dan Mick [this message]
2012-10-30 21:17                       ` Gandalf Corvotempesta
2012-10-30 21:21                         ` Sage Weil

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=50904154.7080004@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=greg@inktank.com \
    --cc=yuandong1222@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox