Re: [ClusterLabs] Antw: Pacemaker 2.0.0-rc1 now available

2018-02-19 Thread Ken Gaillot 
On Mon, 2018-02-19 at 10:23 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot  schrieb am 16.02.2018 um
> > > > 22:06 in Nachricht
> 
> <1518815166.31176.22.ca...@redhat.com>:
> [...]
> > It is recommended to run "cibadmin --upgrade" (or the equivalent in
> > your higher-level tool of choice) both before and after the
> > upgrade.
> 
> [...]
> Playing with it (older version), I found two possible improvements.
> Consider:
> 
> h01:~ # cibadmin --upgrade
> The supplied command is considered dangerous.  To prevent accidental
> destruction of the cluster, the --force flag is required in order to
> proceed.
> h01:~ # cibadmin --upgrade --force
> Call cib_upgrade failed (-211): Schema is already the latest
> available
> 
> First, cibadmin should check whether the CIB version is up-to-date
> already. If so, there is no need to insist on using --force, and
> secondly if the CIB is already up-to-date, there should not be a
> failure, but a success.

Good point, I'll change it so it prints the following message and exits
0 in such a case:

 Upgrade unnecessary: Schema is already the latest available

Avoiding the need for --force in such a case is a bigger project and
will have to go on the to-do list. (With the current design, we can't
know it's not needed until after we try to upgrade it.)

> If a status is needed to detect and out-of-date CIB, a different
> option would be the better solution IMHO.
> 
> Regards,
> Ulrich
-- 
Ken Gaillot 
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Antw: Pacemaker 2.0.0-rc1 now available

2018-02-19 Thread Jan Pokorný 
On 19/02/18 10:39 +0100, Ulrich Windl wrote:
 Ken Gaillot  schrieb am 16.02.2018 um 22:06 in 
 Nachricht
> <1518815166.31176.22.ca...@redhat.com>:
> [...]
>> * The master XML tag is deprecated (though still supported) in favor of
> 
> XML guys!
> 
> Everybody is using (and liking?) XML, but please also learn the
> correct names: There are no "tags" in XML (unless we talk about the
> syntax of XML, which is not the case here), only "elements" and
> "attributes".
> 
> "master" element

True, but perhaps no need to be so harsh about the terms widely
understood as synonyms (from pre-XML era, remember HTML tutorials?),
especially when the target audience wrt. XML level of configuration
keeps shifting towards real power (as in maximum-level-of-control
pursuing) users vs. wider audience served with more abstract means
thanks to crm/pcs.

In anything, would expect rather pointing out the "CIB version 1.3+
does support 'tag' elements" paradox ;-)

>> using the standard clone tag with a new "promotable" meta-attribute set
> 
> "clone" element
> 
> ``"promotable" meta-attribute'' --> ``"nvpair" element with name attribute 
> "promotable"''
> 
>> to true. The "master-max" and "master-node-max" master meta-attributes
>> are deprecated in favor of new "promoted-max" and "promoted-node-max"
>> clone meta-attributes. Documentation now refers to these as promotable
>> clones rather than master/slave, stateful or multistate clones.
>> 
>> * The record-pending option now defaults to true, which means pending
>> actions will be shown in status displays.
>> 
>> * Three minor regressions introduced in 1.1.18, and one introduced in
>> 1.1.17, have been fixed.
> 
> I know what you are talking about, but you need quite some
> background to find out that in "master XML tag" the emphasis is not
> on XML (even if in capitals), but on master ;-)

I see, this shakes the message delivery, something I am running into
all the time when proof-reading my own sentences (especially since I am
not a native speaker), and employing various tricks such as the basic
quoted "meta escape" or join-by-dashes one.

Happy Monday

-- 
Poki


pgpnAhmI8JRgx.pgp
Description: PGP signature
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org