CEPH filesystem development
 help / color / mirror / Atom feed
From: Dan Mick <dmick@redhat.com>
To: "Igor.Podoski@ts.fujitsu.com" <Igor.Podoski@ts.fujitsu.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: tool for applying 'ceph daemon <osd>' command to all OSDs
Date: Tue, 22 Dec 2015 15:46:22 -0800	[thread overview]
Message-ID: <5679E0CE.7020401@redhat.com> (raw)
In-Reply-To: <5265afb0293f4ecbb0a5506a912d943c@R01UKEXCASM222.r01.fujitsu.local>

On 12/22/2015 12:21 AM, Igor.Podoski@ts.fujitsu.com wrote:
>> -----Original Message-----
>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
>> owner@vger.kernel.org] On Behalf Of Dan Mick
>> Sent: Tuesday, December 22, 2015 7:00 AM
>> To: ceph-devel
>> Subject: RFC: tool for applying 'ceph daemon <osd>' command to all OSDs
>>
>> I needed something to fetch current config values from all OSDs (sorta the
>> opposite of 'injectargs --key value), so I hacked it, and then spiffed it up a bit.
>> Does this seem like something that would be useful in this form in the
>> upstream Ceph, or does anyone have any thoughts on its design or
>> structure?
>>
> 
> You could do it using socat too:

Quite true.  That opens the permissions even more, but it works.
Maintaining a couple hundred x2 processes might be a little bit of a pain..

      reply	other threads:[~2015-12-22 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  5:59 RFC: tool for applying 'ceph daemon <osd>' command to all OSDs Dan Mick
2015-12-22  7:29 ` Gregory Farnum
2015-12-22 23:44   ` Dan Mick
2015-12-22  8:21 ` Igor.Podoski
2015-12-22 23:46   ` 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=5679E0CE.7020401@redhat.com \
    --to=dmick@redhat.com \
    --cc=Igor.Podoski@ts.fujitsu.com \
    --cc=ceph-devel@vger.kernel.org \
    /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