From: Dan Mick <dan.mick@inktank.com>
To: Xing Lin <xinglin@cs.utah.edu>
Cc: Neil Levine <neil.levine@inktank.com>,
Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: ssh passwords
Date: Tue, 22 Jan 2013 13:11:30 -0800 [thread overview]
Message-ID: <50FF0082.6020400@inktank.com> (raw)
In-Reply-To: <50FEFE26.2000003@cs.utah.edu>
The '-a/--allhosts' parameter is to spread the command across the
cluster...that is, service ceph -a start will start across the cluster.
On 01/22/2013 01:01 PM, Xing Lin wrote:
> I like the current approach. I think it is more convenient to run
> commands once at one host to do all the setup work. When the first time
> I deployed a ceph cluster with 4 hosts, I thought 'service ceph start'
> would start the whole ceph cluster. But as it turns out, it only starts
> local osd, mon processes. So, currently, I am using polysh to run the
> same commands at all hosts (mostly, to restart ceph service before every
> measurement.). Thanks.
>
> Xing
>
> On 01/22/2013 12:35 PM, Neil Levine wrote:
>> Out of interest, would people prefer that the Ceph deployment script
>> didn't try to handle server-server file copy and just did the local
>> setup only, or is it useful that it tries to be a mini-config
>> management tool at the same time?
>>
>> Neil
>
> --
> 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
next prev parent reply other threads:[~2013-01-22 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 18:24 ssh passwords Gandalf Corvotempesta
2013-01-22 18:45 ` Gregory Farnum
2013-01-22 20:44 ` Gandalf Corvotempesta
2013-01-22 18:46 ` Xing Lin
2013-01-22 19:35 ` Neil Levine
2013-01-22 21:01 ` Xing Lin
2013-01-22 21:11 ` Dan Mick [this message]
2013-01-22 21:16 ` Xing Lin
2013-01-22 23:14 ` Sage Weil
2013-01-22 23:57 ` Travis Rhoden
2013-01-23 0:09 ` Neil Levine
2013-01-23 3:43 ` Travis Rhoden
2013-01-23 4:06 ` Neil Levine
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=50FF0082.6020400@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--cc=neil.levine@inktank.com \
--cc=xinglin@cs.utah.edu \
/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.