> -----Original Message-----
> From: ceph-devel-ow...@vger.kernel.org [mailto:ceph-devel-
> ow...@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:

Node1 has osd.0

cd /var/run/ceph
sudo socat TCP-LISTEN:60100,fork unix-connect:ceph-osd.0.asok

cd /var/run/ceph
sudo  socat unix-listen:ceph-osd.0.asok,fork TCP:Node1:60100

sudo ceph daemon osd.0 help | head
    "config diff": "dump diff of current config and default config",
    "config get": "config get <field>: get the config value",

This is more for development/test setup.


> 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
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the
> body of a message to majord...@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

Reply via email to