All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Oliveira <doliveira@suse.com>
To: Sebastien Han <shan@redhat.com>, Jesse Williamson <jwilliamson@suse.de>
Cc: Squid Cybernetic <ceph-devel@vger.kernel.org>
Subject: Re: [Feature request] config diff on a single option with the admin socket
Date: Mon, 08 Aug 2016 20:38:55 -0600	[thread overview]
Message-ID: <1470710335.14948.10.camel@suse.com> (raw)
In-Reply-To: <1470691964.14948.2.camel@suse.com>

Sebastien, 

For now, We have something like this (which follows the same standard
as 'config diff' and 'config get' : 

#1:
./ceph --admin-daemon out/osd.1.asok config diff get
mon_data_avail_crit 
{
    "diff": {
        "current": {
            "mon_data_avail_crit": "1"
        },
        "defaults": {
            "mon_data_avail_crit": "5"
        }
    },
    "unknown": []
}

./ceph --admin-daemon out/osd.1.asok config diff get
mon_data_avail_warn
{
    "diff": {
        "current": {
            "mon_data_avail_warn": "10"
        },
        "defaults": {
            "mon_data_avail_warn": "30"
        }
    },
    "unknown": []
}

What would be the proper way to display a setting that *was not*
changed from its default?, for example: 
./ceph --admin-daemon out/osd.1.asok config diff get num_client
{
    "diff": {
        "current": {},
        "defaults": {}
    },
    "unknown": []
}

Or only the "current" value? 

Thanks,
-Daniel 


On Mon, 2016-08-08 at 15:32 -0600, Daniel Oliveira wrote:
> Sebastien, 
> 
> As I was working on a couple of other things related to validating
> parameters/settings, I ended up adding the feature in question and I
> am just in the process of testing it. I will keep you posted.
> 
> Thanks,
> -Daniel 
> 
> 
> On Mon, 2016-08-08 at 14:16 +0200, Sebastien Han wrote:
> > Would be nice if you could get a stab at it, actually I don't know
> > where to look in the code to see where the magic is happening for
> > the
> > admin socket.
> > Most of the logic is there so this shouldn't be too difficult :).
> > 
> > Did you get a chance to look into this Jesse?
> > Thanks for offering your help on this one!
> > 
> > On Fri, Jul 29, 2016 at 8:32 PM, Jesse Williamson <
> > jwilliamson@suse.de> wrote:
> > > On Fri, 29 Jul 2016, Sebastien Han wrote:
> > > 
> > > Hi Sebastien,
> > > 
> > > > I'd like to have the same but for a specific option only.
> > > > 
> > > > So something like:
> > > > 
> > > > ceph daemon mon.ceph-mon-01 config diff get <field>
> > > > 
> > > > Which will return the diff between the actual config value and
> > > > the
> > > > original config value.
> > > 
> > > 
> > > I might be able to help with this, if there's no support that
> > > anyone already
> > > knows of, or clear takers. I'm working on a small config-related
> > > librados
> > > feature right now and am somewhat familiar with the relevant
> > > moving parts on
> > > that end, so I might be in a good position to work on it.
> > > 
> > > WRT the admin socket, I'm less clear, but can be pointed in the
> > > right
> > > direction. :-)
> > > 
> > > -Jesse
> > 
> > 
> > 

  parent reply	other threads:[~2016-08-09  2:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 10:12 [Feature request] config diff on a single option with the admin socket Sebastien Han
2016-07-29 18:32 ` Jesse Williamson
2016-08-08 12:16   ` Sebastien Han
2016-08-08 22:04     ` Daniel Oliveira
2016-08-08 23:50     ` Jesse Williamson
     [not found]     ` <1470691964.14948.2.camel@suse.com>
2016-08-09  2:38       ` Daniel Oliveira [this message]
2016-08-09  9:52         ` Sebastien Han
2016-08-09 10:51           ` Shinobu Kinjo
2016-08-10  0:03             ` Daniel Oliveira
2016-08-10 10:34               ` Shinobu Kinjo
2016-08-11  8:16                 ` Sebastien Han
2016-08-11  9:30                   ` Shinobu Kinjo
2016-08-11 19:45                   ` Daniel Oliveira
2016-08-12  9:28                     ` Sebastien Han

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=1470710335.14948.10.camel@suse.com \
    --to=doliveira@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jwilliamson@suse.de \
    --cc=shan@redhat.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 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.