gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Glusterd: A New Hope


From: Anand Babu Periasamy
Subject: Re: [Gluster-devel] Glusterd: A New Hope
Date: Mon, 25 Mar 2013 20:44:43 -0700

On Sun, Mar 24, 2013 at 8:57 PM, Justin Clift <address@hidden> wrote:
> On 23/03/2013, at 11:58 PM, Anand Babu Periasamy wrote:
> <snip>
>> (4) Auto-generated volume spec is too limiting. There are other useful
>> translators, but not even included (but disabled) by default. Volume
>> spec file does not list all possible volume options (but commented)
>> with default values and possible range of input values. CLI for volume
>> options does not list them all. There is no good documentation about
>> these options. Either remove those unexposed options entirely (better)
>> or document them. Allow user supplied customization (templates) to
>> default auto-generated volume specification (with clear warning).
>
> Out of curiosity, why the preference for killing the options instead
> of documenting them?
>
> Are those undocumented options not potentially useful for some people,
> or they're just dodgy code that needs cleanup by someone, or ?
>
> Not arguing at all, just learning. :)
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> Open Source and Standards @ Red Hat
>
> twitter.com/realjustinclift
>

Options that are not documented are not tested. If it is not tested,
it should not be used.

The reason why them killing is better is: if they have not been
documented for this long, it is time to let them go. Keep the code
clean. Even experienced sysadmins expect file system defaults to work
well. Every time we add a new option, we have to be sure how it
behaves in combination with other options. Testing becomes real hard.

-- 
-ab

Imagination is more important than knowledge --Albert Einstein



reply via email to

[Prev in Thread] Current Thread [Next in Thread]