All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	dm-devel@redhat.com,
	Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: Re: [PATCH] multipath-tools: replace multipath configuration output
Date: Wed, 07 Dec 2016 17:17:30 +0100	[thread overview]
Message-ID: <1481127450.3358.21.camel@suse.com> (raw)
In-Reply-To: <d793306a-011a-2332-9c81-3dd898aff44a@gmail.com>

On Wed, 2016-12-07 at 16:44 +0100, Xose Vazquez Perez wrote:
> On 11/25/2016 10:00 AM, Martin Wilck wrote:
> 
> > I am not sure I see the merit of these changes. If it's really
> > necessary to change the wording of the log messages which people
> > have
> > got used to, the new ones should be really more self-explanatory
> > than
> > the old ones.
> 
> Some of them are a riddle, wrapped in a mystery, inside an enigma.
> For example "LUN setting". "setting: multipath.conf multipaths
> section"
> is, by far, a better description.

Agreed.

> > The common "setting: " formatting is nice but IMHO this alone
> > doesn't
> > really justify overthrowing old habits.
> 
> I really don't care the marker name, "setting:" "conf:" ...
> But a standard one should be used.

Agreed.

> > On Thu, 2016-11-24 at 23:44 +0100, Xose Vazquez Perez wrote:
> > > sysfs setting           -> setting: kernel sysfs
> > > 
> > > detected setting        -> setting: array autodetected
> > > 
> > > controller setting      -> setting: array configuration
> > Is "array" really more understandable to users than "controller"?
> 
> "controller", what controller? local hba? array controller?
> "array" is unequivocal.

I tend to associate "array" with "RAID", and therefore I found this
term confusing. Perhaps "storage" or "storage array"? Or even "device",
overloaded as it may be, because that would match the section name in
multipath.conf?

> > These settings come from hwentries, so in reality they're either
> > part
> > of the built-in hwtable or of the multipath.conf "devices"
> > section, 
> > or am I wrong here? 
> Also from /sys fs, from the array or auto-negotiated kernel<->array.

> > It would be helpful for users to be able to distinguish which
> > config file section
> > the option was taken from (defaults/devices/multipaths/overrides).
> > The
> > same argument applies to the hardware enries - being able to
> > distinguish built in hardware defaults from config file "devices"
> > settings would be really helpful, but this patch doesn't provide
> > that
> > functionality.
> 
> This is a first step. Anyhow only "multipath.conf defaults/devices"
> could be split.
> overrides and multipaths sections already are independent as you can
> see in
> libmultipath/propsel.c

OK.

>From an end user perspective, figuring out the "sysfs" and "auto-
negotiated" config option origin, as you mentioned above, might be most
important, in particular when these take precedence over config file
settings.

Anyway, thanks for putting thought into this.

Best Regards
Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2016-12-07 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 22:44 [PATCH] multipath-tools: replace multipath configuration output Xose Vazquez Perez
2016-11-25  9:00 ` Martin Wilck
2016-11-26  9:21   ` Christophe Varoqui
2016-12-02  3:52     ` Benjamin Marzinski
2016-12-07 22:48       ` Xose Vazquez Perez
2016-12-14 18:29         ` Christophe Varoqui
2017-02-22 16:20         ` multipath-tools: Fixes/features for upstream Xose Vazquez Perez
2017-02-23  6:56           ` Hannes Reinecke
2016-12-07 15:44   ` [PATCH] multipath-tools: replace multipath configuration output Xose Vazquez Perez
2016-12-07 16:17     ` Martin Wilck [this message]
     [not found]       ` <c78854cd-f7f2-77ef-2d19-a5ff236e9a37@gmail.com>
2017-08-20  0:47         ` Xose Vazquez Perez
  -- strict thread matches above, loose matches on Subject: below --
2017-04-08 13:30 Xose Vazquez Perez
2017-04-12  7:35 ` Christophe Varoqui
2017-04-13 23:56   ` Xose Vazquez Perez
2017-04-14  8:29     ` Christophe Varoqui
2017-04-18  0:07 [PATCH] multipath-tools: Replace " Xose Vazquez Perez
2017-05-18  0:06 ` Xose Vazquez Perez
2017-06-21 10:33   ` Christophe Varoqui

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=1481127450.3358.21.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=xose.vazquez@gmail.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.