All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dmick@redhat.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: RFC: tool for applying 'ceph daemon <osd>' command to all OSDs
Date: Mon, 21 Dec 2015 21:59:30 -0800	[thread overview]
Message-ID: <5678E6C2.40007@redhat.com> (raw)

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?

It requires a locally-installed ceph CLI and a ceph.conf that points to
the cluster and any required keyrings.  You can also provide it with
a YAML file mapping host to osds if you want to save time collecting
that info for a statically-defined cluster, or if you want just a subset
of OSDs.

https://github.com/dmick/tools/blob/master/osd_daemon_cmd.py

Excerpt from usage:

Execute a Ceph osd daemon command on every OSD in a cluster with
one connection to each OSD host.

Usage:
    osd_daemon_cmd [-c CONF] [-u USER] [-f FILE] (COMMAND | -k KEY)

Options:
   -c CONF   ceph.conf file to use [default: ./ceph.conf]
   -u USER   user to connect with ssh
   -f FILE   get names and osds from yaml
   COMMAND   command other than "config get" to execute
   -k KEY    config key to retrieve with config get <key>

-- 
Dan Mick
Red Hat, Inc.
Ceph docs: http://ceph.com/docs

             reply	other threads:[~2015-12-22  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  5:59 Dan Mick [this message]
2015-12-22  7:29 ` RFC: tool for applying 'ceph daemon <osd>' command to all OSDs Gregory Farnum
2015-12-22 23:44   ` Dan Mick
2015-12-22  8:21 ` Igor.Podoski
2015-12-22 23:46   ` Dan Mick

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=5678E6C2.40007@redhat.com \
    --to=dmick@redhat.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 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.