Re: [Linux-HA] Documenting ocf:pacemaker:ping
On Thu, Feb 10, 2011 at 12:48:17PM +0100, Andrew Beekhof wrote:
> On Thu, Feb 10, 2011 at 12:28 PM, Dejan Muhamedagic
> wrote:
> > On Thu, Feb 10, 2011 at 09:29:41AM +0100, Andrew Beekhof wrote:
> >> On Thu, Feb 10, 2011 at 9:14 AM, Ulrich Windl
> >> wrote:
> >> > Hi!
> >> >
> >> > I'm getting into Linux-HA, and it seems the "documentation" was made
> >> > with a very "hot needle". For example, ocf:pacemaker:ping has the
> >> > following documentation ("crm(live)ra# info ocf:ping" in SLES11
> >> > SP3+Updates):
> >> >> crm(live)ra# info ocf:ping
> >> >> PID file
> >> >>
> >> >> dampen (integer, [5s]): Dampening interval
> >> >> The time to wait (dampening) further changes occur
> >> >
> >> > The sentence above is grammatically wrong.
> >>
> >> At least its spelt correctly, which is more than people usually get from
> >> me.
> >>
> >> >
> >> >>
> >> >> name (string, [pingd]): Attribute name
> >> >> The name of the attributes to set. This is the name to be used in
> >> >> the constraints.
> >> >>
> >> >> multiplier (integer): Value multiplier
> >> >> The number by which to multiply the number of connected ping nodes
> >> >> by
> >> >
> >> > Please explain the reason (semantics) for the multiplication!
> >>
> >> Please read "Pacemaker Explained"
> >>
> >> >
> >> >>
> >> >> host_list* (string): Host list
> >> >> The list of ping nodes to count.
> >> >
> >> > "to count", or "to ping", or both?
> >>
> >> My, we are pedantic today.
> >>
> >> "To ping and count towards the number of active hosts"
> >>
> >> >> attempts (integer, [2]): no. of ping attempts
> >> >> Number of ping attempts, per host, before declaring it dead
> >> >>
> >> >> timeout (integer, [2]): ping timeout in seconds
> >> >> How long, in seconds, to wait before declaring a ping lost
> >> >
> >> > "a ping lost" == "a host dead"?
> >>
> >> Yes
> >>
> >> > Or is it the "the monitor reports a failure"?
> >>
> >> No
> >>
> >> >> options (string): Extra Options
> >> >> A catch all for any other options that need to be passed to ping.
> >> >
> >> > What about "Additional options to be passed to ping"?
> >>
> >> This text is too short, this text is too long... are you ever happy?
> >>
> >> >
> >> >>
> >> >> debug (string, [false]): Verbose logging
> >> >> Enables to use default attrd_updater verbose logging on every call.
> >> >
> >> > What about "`true' enables verbose logging"?
> >> >
> >> >>
> >> >> Operations' defaults (advisory minimum):
> >> >>
> >> >> start timeout=60
> >> >> stop timeout=20
> >> >> reload timeout=100
> >> >> monitor_0 interval=10 timeout=60
> >> >
> >> > Is it really "monitor_0"? What is that "_0"?
> >>
> >> I'm guessing a typo
> >
> > Not a typo, but monitor with depth check 0. Well, perhaps
> > appending depth could be skipped in this case.
>
> Oh, I mistook it for a non-recurring monitor op
I could distinctly recall not wanting to print it, but there
was a bit of a problem in logic, fixed now
> ___
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Documenting ocf:pacemaker:ping
On Thu, Feb 10, 2011 at 12:28 PM, Dejan Muhamedagic wrote:
> On Thu, Feb 10, 2011 at 09:29:41AM +0100, Andrew Beekhof wrote:
>> On Thu, Feb 10, 2011 at 9:14 AM, Ulrich Windl
>> wrote:
>> > Hi!
>> >
>> > I'm getting into Linux-HA, and it seems the "documentation" was made with
>> > a very "hot needle". For example, ocf:pacemaker:ping has the following
>> > documentation ("crm(live)ra# info ocf:ping" in SLES11 SP3+Updates):
>> >> crm(live)ra# info ocf:ping
>> >> PID file
>> >>
>> >> dampen (integer, [5s]): Dampening interval
>> >> The time to wait (dampening) further changes occur
>> >
>> > The sentence above is grammatically wrong.
>>
>> At least its spelt correctly, which is more than people usually get from me.
>>
>> >
>> >>
>> >> name (string, [pingd]): Attribute name
>> >> The name of the attributes to set. This is the name to be used in
>> >> the constraints.
>> >>
>> >> multiplier (integer): Value multiplier
>> >> The number by which to multiply the number of connected ping nodes by
>> >
>> > Please explain the reason (semantics) for the multiplication!
>>
>> Please read "Pacemaker Explained"
>>
>> >
>> >>
>> >> host_list* (string): Host list
>> >> The list of ping nodes to count.
>> >
>> > "to count", or "to ping", or both?
>>
>> My, we are pedantic today.
>>
>> "To ping and count towards the number of active hosts"
>>
>> >> attempts (integer, [2]): no. of ping attempts
>> >> Number of ping attempts, per host, before declaring it dead
>> >>
>> >> timeout (integer, [2]): ping timeout in seconds
>> >> How long, in seconds, to wait before declaring a ping lost
>> >
>> > "a ping lost" == "a host dead"?
>>
>> Yes
>>
>> > Or is it the "the monitor reports a failure"?
>>
>> No
>>
>> >> options (string): Extra Options
>> >> A catch all for any other options that need to be passed to ping.
>> >
>> > What about "Additional options to be passed to ping"?
>>
>> This text is too short, this text is too long... are you ever happy?
>>
>> >
>> >>
>> >> debug (string, [false]): Verbose logging
>> >> Enables to use default attrd_updater verbose logging on every call.
>> >
>> > What about "`true' enables verbose logging"?
>> >
>> >>
>> >> Operations' defaults (advisory minimum):
>> >>
>> >> start timeout=60
>> >> stop timeout=20
>> >> reload timeout=100
>> >> monitor_0 interval=10 timeout=60
>> >
>> > Is it really "monitor_0"? What is that "_0"?
>>
>> I'm guessing a typo
>
> Not a typo, but monitor with depth check 0. Well, perhaps
> appending depth could be skipped in this case.
Oh, I mistook it for a non-recurring monitor op
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Documenting ocf:pacemaker:ping
On Thu, Feb 10, 2011 at 09:29:41AM +0100, Andrew Beekhof wrote:
> On Thu, Feb 10, 2011 at 9:14 AM, Ulrich Windl
> wrote:
> > Hi!
> >
> > I'm getting into Linux-HA, and it seems the "documentation" was made with a
> > very "hot needle". For example, ocf:pacemaker:ping has the following
> > documentation ("crm(live)ra# info ocf:ping" in SLES11 SP3+Updates):
> >> crm(live)ra# info ocf:ping
> >> PID file
> >>
> >> dampen (integer, [5s]): Dampening interval
> >> The time to wait (dampening) further changes occur
> >
> > The sentence above is grammatically wrong.
>
> At least its spelt correctly, which is more than people usually get from me.
>
> >
> >>
> >> name (string, [pingd]): Attribute name
> >> The name of the attributes to set. This is the name to be used in the
> >> constraints.
> >>
> >> multiplier (integer): Value multiplier
> >> The number by which to multiply the number of connected ping nodes by
> >
> > Please explain the reason (semantics) for the multiplication!
>
> Please read "Pacemaker Explained"
>
> >
> >>
> >> host_list* (string): Host list
> >> The list of ping nodes to count.
> >
> > "to count", or "to ping", or both?
>
> My, we are pedantic today.
>
> "To ping and count towards the number of active hosts"
>
> >> attempts (integer, [2]): no. of ping attempts
> >> Number of ping attempts, per host, before declaring it dead
> >>
> >> timeout (integer, [2]): ping timeout in seconds
> >> How long, in seconds, to wait before declaring a ping lost
> >
> > "a ping lost" == "a host dead"?
>
> Yes
>
> > Or is it the "the monitor reports a failure"?
>
> No
>
> >> options (string): Extra Options
> >> A catch all for any other options that need to be passed to ping.
> >
> > What about "Additional options to be passed to ping"?
>
> This text is too short, this text is too long... are you ever happy?
>
> >
> >>
> >> debug (string, [false]): Verbose logging
> >> Enables to use default attrd_updater verbose logging on every call.
> >
> > What about "`true' enables verbose logging"?
> >
> >>
> >> Operations' defaults (advisory minimum):
> >>
> >> start timeout=60
> >> stop timeout=20
> >> reload timeout=100
> >> monitor_0 interval=10 timeout=60
> >
> > Is it really "monitor_0"? What is that "_0"?
>
> I'm guessing a typo
Not a typo, but monitor with depth check 0. Well, perhaps
appending depth could be skipped in this case.
Thanks,
Dejan
> > Regards,
> > Ulrich
> >
> >
> > ___
> > Linux-HA mailing list
> > Linux-HA@lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> ___
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Documenting ocf:pacemaker:ping
On Thu, Feb 10, 2011 at 9:14 AM, Ulrich Windl
wrote:
> Hi!
>
> I'm getting into Linux-HA, and it seems the "documentation" was made with a
> very "hot needle". For example, ocf:pacemaker:ping has the following
> documentation ("crm(live)ra# info ocf:ping" in SLES11 SP3+Updates):
>> crm(live)ra# info ocf:ping
>> PID file
>>
>> dampen (integer, [5s]): Dampening interval
>> The time to wait (dampening) further changes occur
>
> The sentence above is grammatically wrong.
At least its spelt correctly, which is more than people usually get from me.
>
>>
>> name (string, [pingd]): Attribute name
>> The name of the attributes to set. This is the name to be used in the
>> constraints.
>>
>> multiplier (integer): Value multiplier
>> The number by which to multiply the number of connected ping nodes by
>
> Please explain the reason (semantics) for the multiplication!
Please read "Pacemaker Explained"
>
>>
>> host_list* (string): Host list
>> The list of ping nodes to count.
>
> "to count", or "to ping", or both?
My, we are pedantic today.
"To ping and count towards the number of active hosts"
>> attempts (integer, [2]): no. of ping attempts
>> Number of ping attempts, per host, before declaring it dead
>>
>> timeout (integer, [2]): ping timeout in seconds
>> How long, in seconds, to wait before declaring a ping lost
>
> "a ping lost" == "a host dead"?
Yes
> Or is it the "the monitor reports a failure"?
No
>> options (string): Extra Options
>> A catch all for any other options that need to be passed to ping.
>
> What about "Additional options to be passed to ping"?
This text is too short, this text is too long... are you ever happy?
>
>>
>> debug (string, [false]): Verbose logging
>> Enables to use default attrd_updater verbose logging on every call.
>
> What about "`true' enables verbose logging"?
>
>>
>> Operations' defaults (advisory minimum):
>>
>> start timeout=60
>> stop timeout=20
>> reload timeout=100
>> monitor_0 interval=10 timeout=60
>
> Is it really "monitor_0"? What is that "_0"?
I'm guessing a typo
>
> Regards,
> Ulrich
>
>
> ___
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Documenting ocf:pacemaker:ping
Hi!
I'm getting into Linux-HA, and it seems the "documentation" was made with a
very "hot needle". For example, ocf:pacemaker:ping has the following
documentation ("crm(live)ra# info ocf:ping" in SLES11 SP3+Updates):
> crm(live)ra# info ocf:ping
> PID file
>
> dampen (integer, [5s]): Dampening interval
> The time to wait (dampening) further changes occur
The sentence above is grammatically wrong.
>
> name (string, [pingd]): Attribute name
> The name of the attributes to set. This is the name to be used in the
> constraints.
>
> multiplier (integer): Value multiplier
> The number by which to multiply the number of connected ping nodes by
Please explain the reason (semantics) for the multiplication!
>
> host_list* (string): Host list
> The list of ping nodes to count.
"to count", or "to ping", or both?
>
> attempts (integer, [2]): no. of ping attempts
> Number of ping attempts, per host, before declaring it dead
>
> timeout (integer, [2]): ping timeout in seconds
> How long, in seconds, to wait before declaring a ping lost
"a ping lost" == "a host dead"? Or is it the "the monitor reports a failure"?
>
> options (string): Extra Options
> A catch all for any other options that need to be passed to ping.
What about "Additional options to be passed to ping"?
>
> debug (string, [false]): Verbose logging
> Enables to use default attrd_updater verbose logging on every call.
What about "`true' enables verbose logging"?
>
> Operations' defaults (advisory minimum):
>
> start timeout=60
> stop timeout=20
> reloadtimeout=100
> monitor_0 interval=10 timeout=60
Is it really "monitor_0"? What is that "_0"?
Regards,
Ulrich
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
