Re: [ClusterLabs] What happened to "crm resource migrate"?

[Xin Liang]

On 10/15/19 4:26 PM,  Ulrich Windl  wrote:
> Hi!
> 
> I was trying to do a "crm resource migrate" the first time in SLES 12 (the 
> way I did in SLES11), but I got this message:
> # crm resource migrate prm_isr_mail1 PT10M
> ERROR: resource.move: No target node: Move requires either a target node or 
> 'force'
> 
> I'm surprised: In the past the mommand simply added a negative location for 
> the node the was running (at least I think).
> The resource was running on the other node of a two-node cluster...
> 
> Also I noticed that "migrate" no longer appears in crm's help for "resource". 
> There's only a "move".
> 
Hi,

"migrate" is a alias name for "move", we've dropped all sub-command
alias from UI while original alias can still work.

[Related issue] https://github.com/ClusterLabs/crmsh/issues/377
[Related commit] https://github.com/ClusterLabs/crmsh/pull/380

Thanks for use crmsh!
> Help for "move" still says:
> resource# help move
> Move a resource to another node
> 
> Move a resource away from its current location.
> ...
> 
> Regards,
> Ulrich
> 
> 
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> ClusterLabs home: https://www.clusterlabs.org/
> 

-- 
Xin Liang
HA team, Beijing
https://github.com/liangxin1300


pEpkey.asc
Description: pEpkey.asc
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] DLM, cLVM, GFS2 and OCFS2 managed by systemd instead of crm ?

[Gang He]

Hello Lentes,o

In the cluster environment, usually we need to fence(or dynamically add/delete) 
node,
the full stacks provided by packmaker/corosync can help to complete it 
automatically/integrally.


Thanks
Gang


From: Users  on behalf of Lentes, Bernd 

Sent: Wednesday, October 16, 2019 3:35 AM
To: Pacemaker ML 
Subject: [ClusterLabs] DLM, cLVM, GFS2 and OCFS2 managed by systemd instead of 
crm ?

Hi,

i'm a big fan of simple solutions (KISS).
Currently i have DLM, cLVM, GFS2 and OCFS2 managed by pacemaker.
They all are fundamental prerequisites for my resources (Virtual Domains).
To configure them i used clones and groups.
Why not having them managed by systemd to make the cluster setup more 
overseeable ?

Is there a strong reason that pacemaker cares about them ?

Bernd

--

Bernd Lentes
Systemadministration
Institut für Entwicklungsgenetik
Gebäude 35.34 - Raum 208
HelmholtzZentrum münchen
bernd.len...@helmholtz-muenchen.de
phone: +49 89 3187 1241
phone: +49 89 3187 3827
fax: +49 89 3187 2294
http://www.helmholtz-muenchen.de/idg

Perfekt ist wer keine Fehler macht
Also sind Tote perfekt


Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Announcing ClusterLabs Summit 2020

[Digimer]

On 2019-10-15 5:42 p.m., Ken Gaillot wrote:
> I'm happy to announce that we have a date and location for the next
> ClusterLabs Summit: Wednesday, Feb. 5, and Thursday, Feb. 6, 2020, in
> Brno, Czechia. This year's host is Red Hat.
> 
> Details will be given on this wiki page as they become available:
> 
>   http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020
> 
> We are still in the early stages of organizing, and need your input.
> 
> Most importantly, we need a good idea of how many people will attend,
> to ensure we have an appropriate conference room and amenities. The
> wiki page has a section where you can say how many people from your
> organization expect to attend. We don't need a firm commitment or an
> immediate response, just let us know once you have a rough idea.
> 
> We also invite you to propose a talk, whether it's a talk you want to
> give or something you are interested in hearing more about. The wiki
> page has a section for that, too. Anything related to open-source
> clustering is welcome: new features and plans for the cluster software 
> projects, how-to's and case histories for integrating specific services into 
> a cluster, utilizing specific stonith/networking/etc. technologies in a 
> cluster, tips for administering a cluster, and so forth.
> 
> I'm excited about the chance for developers and users to meet in
> person. Past summits have been helpful for shaping the direction of the
> projects and strengthening the community. I look forward to seeing many
> of you there!

Thanks for getting this going! Looking forward to seeing everyone again!

If anyone wants to contribute to the wiki but doesn't have an account
yet, email me directly (mke...@alteeve.ca) or catch me on freenode
(#clusterlabs -> digimer) and I'll get an account setup.

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

[ClusterLabs] Announcing ClusterLabs Summit 2020

[Ken Gaillot]

I'm happy to announce that we have a date and location for the next
ClusterLabs Summit: Wednesday, Feb. 5, and Thursday, Feb. 6, 2020, in
Brno, Czechia. This year's host is Red Hat.

Details will be given on this wiki page as they become available:

  http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020

We are still in the early stages of organizing, and need your input.

Most importantly, we need a good idea of how many people will attend,
to ensure we have an appropriate conference room and amenities. The
wiki page has a section where you can say how many people from your
organization expect to attend. We don't need a firm commitment or an
immediate response, just let us know once you have a rough idea.

We also invite you to propose a talk, whether it's a talk you want to
give or something you are interested in hearing more about. The wiki
page has a section for that, too. Anything related to open-source
clustering is welcome: new features and plans for the cluster software 
projects, how-to's and case histories for integrating specific services into a 
cluster, utilizing specific stonith/networking/etc. technologies in a cluster, 
tips for administering a cluster, and so forth.

I'm excited about the chance for developers and users to meet in
person. Past summits have been helpful for shaping the direction of the
projects and strengthening the community. I look forward to seeing many
of you there!
-- 
Ken Gaillot 

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] DLM, cLVM, GFS2 and OCFS2 managed by systemd instead of crm ?

[Ken Gaillot]

On Tue, 2019-10-15 at 21:35 +0200, Lentes, Bernd wrote:
> Hi,
> 
> i'm a big fan of simple solutions (KISS).
> Currently i have DLM, cLVM, GFS2 and OCFS2 managed by pacemaker.
> They all are fundamental prerequisites for my resources (Virtual
> Domains).
> To configure them i used clones and groups.
> Why not having them managed by systemd to make the cluster setup more
> overseeable ?
> 
> Is there a strong reason that pacemaker cares about them ?
> 
> Bernd 

Either approach is reasonable. The advantages of keeping them in
pacemaker are:

- Service-aware recurring monitor (if OCF)

- If one of those components fails, pacemaker will know to try to
recover everything in the group from that point, and if necessary,
fence the node and recover the virtual domain elsewhere (if they're in
systemd, pacemaker will only know that the virtual domain has failed,
and likely keep trying to restart it fruitlessly)

- Convenience of things like putting a node in standby mode, and
checking resource status on all nodes with one command

If you do move them to systemd, be sure to use the resource-agents-deps 
target to ensure they're started before pacemaker and stopped after
pacemaker.
-- 
Ken Gaillot 

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

[ClusterLabs] DLM, cLVM, GFS2 and OCFS2 managed by systemd instead of crm ?

[Lentes, Bernd]

Hi,

i'm a big fan of simple solutions (KISS).
Currently i have DLM, cLVM, GFS2 and OCFS2 managed by pacemaker.
They all are fundamental prerequisites for my resources (Virtual Domains).
To configure them i used clones and groups.
Why not having them managed by systemd to make the cluster setup more 
overseeable ?

Is there a strong reason that pacemaker cares about them ?

Bernd 

-- 

Bernd Lentes 
Systemadministration 
Institut für Entwicklungsgenetik 
Gebäude 35.34 - Raum 208 
HelmholtzZentrum münchen 
bernd.len...@helmholtz-muenchen.de 
phone: +49 89 3187 1241 
phone: +49 89 3187 3827 
fax: +49 89 3187 2294 
http://www.helmholtz-muenchen.de/idg 

Perfekt ist wer keine Fehler macht 
Also sind Tote perfekt
 

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Antw: Coming in Pacemaker 2.0.3: crm_mon output changes

[Ken Gaillot]

On Tue, 2019-10-15 at 08:42 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot  schrieb am 15.10.2019 um
> > > > 00:47 in
> 
> Nachricht
> :
> > Hi all,
> > 
> > With Pacemaker 2.0.2, we introduced a new experimental option for
> > XML
> > output from stonith_admin. This was the test case for a new output
> > model for Pacemaker tools. I'm happy to say this has been extended
> > to
> > crm_mon and will be considered stable as of 2.0.3.
> > 
> > crm_mon has always supported text, curses, HTML, and XML output,
> > and
> > that doesn't change. However the command‑line options for those
> > have
> > been deprecated and replaced with new forms:
> > 
> > Old:New:
> > ‑‑as‑xml‑‑output‑as=xml
> > ‑‑as‑html=FILE  ‑‑output‑as=html ‑‑output‑to=FILE
> > ‑‑web‑cgi   ‑‑output‑as=html ‑‑output‑cgi
> > ‑‑disable‑ncurses   ‑‑output‑as=text
> 
> I'd prefer "--output-format|output-fmt|format" over "--format-as",
> because I
> think it's more clear.

That's a good question, what it should be called. We chose --output-as
in 2.0.2 for stonith_admin, so that has some weight now. I think the
main reason was to keep it shorter for typing (there's no single-letter 
equivalent at the moment because there's not an obvious choice
available across all tools).

I'm open to changing it if there's a lot of demand for it, otherwise
I'd rather keep it compatible with 2.0.2.

> Accordingly I'd prefer "--output-file" over "--output-to".

I like the more generic meaning of this one. The new approach also
supports --output-to="-" for stdout (which is the default). One could
imagine adding some other non-file capability in the future.

> Why not replace "--weg-cgi" with "--output-format=cgi"?

CGI output is identical to HTML, with just a header change, so it was
logically more of an option to the HTML implementation rather than a
separate one.

With the new approach, each format type may define any additional
options to modify its behavior, and all tools automatically inherit
those options. These will be grouped together in the help/man page. For
example, the HTML option help is:

Output Options (html):
  --output-cgi  Add text needed to use output in a CGI 
program
  --output-meta-refresh=SECONDS How often to refresh
  --output-stylesheet-link=URI  Link to an external CSS stylesheet
  --output-title=TITLE  Page title

> > 
> > The new ‑‑output‑as and ‑‑output‑to options are identical to
> > stonith_admin's, and will eventually be supported by all Pacemaker
> > tools. Each tool may support a different set of formats; for
> > example,
> > stonith_admin supports text and xml.
> > 
> > When called with ‑‑as‑xml, crm_mon's XML output will be identical
> > to
> > previous versions. When called with the new ‑‑output‑as=xml option,
> > it
> > will be slightly different: the outmost element will be a
> >  > result> element, which will be consistent across all tools. The old
> > XML
> 
> Why not as simple "status" element? "-result" doesn't really add
> anything
> useful.

We wanted the design to allow for future flexibility in how users ask
pacemaker to do something. The XML output would be the same whether the
request came from a command-line tool, GUI, C API client application,
REST API client, or any other future interface. The idea is that
 might be a response to a .

 was also introduced with stonith_admin in 2.0.2, so
that carries some weight, but it was announced as experimental at the
time, so I'm open to changing the syntax if there's a clear preference
for an alternative.

> > schema remains documented in crm_mon.rng; the new XML schema will
> > be
> > documented in an api‑result.rng schema that will encompass all
> > tools'
> > XML output.
> > 
> > Beyond those interface changes, the text output displayed by
> > crm_mon
> > has been tweaked slightly. It is more organized with list headings
> > and
> > bullets. Hopefully you will find this easier to read. We welcome
> > any
> > feedback or suggestions for improvement.
> 
> Older versions use a mixture of space for indent, and '*' and '+' as
> bullets.
> A unified approach would be either to use some amount of spaces or
> one TAB for
> indenting consistently, maybe combined with a set of bullet
> characters for the
> individual levels of indent.
> 
> So "--bullet-list='*+'" and "--indent-string=..." could set such.

That's an interesting suggestion.

The new approach does use a consistent style, with 2-space indents (to
fit as much as possible in a screen width) and '*' bullets (with an
additional indent for each deeper level). Also all list headings are
First Cap ending with a colon (':'). Example:

Active Resources:
  * Clone Set: myclone-clone [myclone]:
* Started: [ f20node1 f20node2 ]

Allowing the bullets and indents to be configurable are something that
could theoretically be done with new options to the text format.

> > The HTML output gains a new feature as well: it uses CSS
> > throughout,
> > rather 

Re: [ClusterLabs] What happened to "crm resource migrate"?

[Yan Gao]

On 10/15/19 11:32 AM, Gao,Yan wrote:
> On 10/15/19 11:10 AM, Strahil wrote:
>> What about the constraint.
>> I think there is no 'crm resource unmove'  to remmove the constraint.
> "crm resource clear" does that.
And "unmove" is deprecated/hidden, but should still work.

Regards,
   Yan

> 
> Regards,
>    Yan
> 
>>
>> Best Regards,
>> Strahil NikolovOn Oct 15, 2019 11:52, Yan Gao  wrote:
>>>
>>> Hi Ulrich,
>>>
>>> On 10/15/19 10:26 AM,  Ulrich Windl  wrote:
 Hi!

 I was trying to do a "crm resource migrate" the first time in SLES 
 12 (the way I did in SLES11), but I got this message:
 # crm resource migrate prm_isr_mail1 PT10M
 ERROR: resource.move: No target node: Move requires either a target 
 node or 'force'

 I'm surprised: In the past the mommand simply added a negative 
 location for the node the was running (at least I think).
 The resource was running on the other node of a two-node cluster...

 Also I noticed that "migrate" no longer appears in crm's help for 
 "resource". There's only a "move".
>>> Yes, the term/sub-command "migrate" is deprecated in favor of "move", so
>>> that it's consistent with "crm_resource --move ". But "migrate" is
>>> supposed to still work.
>>>

 Help for "move" still says:
 resource# help move
 Move a resource to another node

 Move a resource away from its current location.
>>> Looks like an issue in the version of crmsh.
>>>
>>> Xin, could you please take a look?
>>>
>>> "crm_resource --move -r " is allowed to run without being specified
>>> a node.
>>>
>>> Regards,
>>>     Yan
>>> ___
>>> Manage your subscription:
>>> https://lists.clusterlabs.org/mailman/listinfo/users
>>>
>>> ClusterLabs home: https://www.clusterlabs.org/
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] What happened to "crm resource migrate"?

[Strahil]

What about the constraint.
I think there is no 'crm resource unmove'  to remmove the constraint.

Best Regards,
Strahil NikolovOn Oct 15, 2019 11:52, Yan Gao  wrote:
>
> Hi Ulrich, 
>
> On 10/15/19 10:26 AM,  Ulrich Windl  wrote: 
> > Hi! 
> > 
> > I was trying to do a "crm resource migrate" the first time in SLES 12 (the 
> > way I did in SLES11), but I got this message: 
> > # crm resource migrate prm_isr_mail1 PT10M 
> > ERROR: resource.move: No target node: Move requires either a target node or 
> > 'force' 
> > 
> > I'm surprised: In the past the mommand simply added a negative location for 
> > the node the was running (at least I think). 
> > The resource was running on the other node of a two-node cluster... 
> > 
> > Also I noticed that "migrate" no longer appears in crm's help for 
> > "resource". There's only a "move". 
> Yes, the term/sub-command "migrate" is deprecated in favor of "move", so 
> that it's consistent with "crm_resource --move ". But "migrate" is 
> supposed to still work. 
>
> > 
> > Help for "move" still says: 
> > resource# help move 
> > Move a resource to another node 
> > 
> > Move a resource away from its current location. 
> Looks like an issue in the version of crmsh. 
>
> Xin, could you please take a look? 
>
> "crm_resource --move -r " is allowed to run without being specified 
> a node. 
>
> Regards, 
>    Yan 
> ___ 
> Manage your subscription: 
> https://lists.clusterlabs.org/mailman/listinfo/users 
>
> ClusterLabs home: https://www.clusterlabs.org/ 
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] What happened to "crm resource migrate"?

[Andrei Borzenkov]

On Tue, Oct 15, 2019 at 11:58 AM Yan Gao  wrote:
> >
> > Help for "move" still says:
> > resource# help move
> > Move a resource to another node
> >
> > Move a resource away from its current location.
> Looks like an issue in the version of crmsh.
>
> Xin, could you please take a look?
>
> "crm_resource --move -r " is allowed to run without being specified
> a node.

This is actually documented in crmsh manual.

If the destination node is left out, the resource is migrated by
creating a constraint which prevents it from running on the current
node. For this type of constraint to be created, the force argument is
required.

So at least this is not a bug, but intentional design decision.

https://github.com/ClusterLabs/crmsh/commit/9f05d366d273239dc332f430548cb0f1edfacafc
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] What happened to "crm resource migrate"?

[Yan Gao]

Hi Ulrich,

On 10/15/19 10:26 AM,  Ulrich Windl  wrote:
> Hi!
> 
> I was trying to do a "crm resource migrate" the first time in SLES 12 (the 
> way I did in SLES11), but I got this message:
> # crm resource migrate prm_isr_mail1 PT10M
> ERROR: resource.move: No target node: Move requires either a target node or 
> 'force'
> 
> I'm surprised: In the past the mommand simply added a negative location for 
> the node the was running (at least I think).
> The resource was running on the other node of a two-node cluster...
> 
> Also I noticed that "migrate" no longer appears in crm's help for "resource". 
> There's only a "move".
Yes, the term/sub-command "migrate" is deprecated in favor of "move", so 
that it's consistent with "crm_resource --move ". But "migrate" is 
supposed to still work.

> 
> Help for "move" still says:
> resource# help move
> Move a resource to another node
> 
> Move a resource away from its current location.
Looks like an issue in the version of crmsh.

Xin, could you please take a look?

"crm_resource --move -r " is allowed to run without being specified 
a node.

Regards,
   Yan
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] What happened to "crm resource migrate"?

[Strahil]

It still works and I keep using it... Even in SLES 15.
I think that the warning is a nice addition as it  puts a negative constraint 
which can cause issue with you don't use lifetime option.

Best Regards,
Strahil NikolovOn Oct 15, 2019 11:26, Ulrich Windl 
 wrote:
>
> Hi! 
>
> I was trying to do a "crm resource migrate" the first time in SLES 12 (the 
> way I did in SLES11), but I got this message: 
> # crm resource migrate prm_isr_mail1 PT10M 
> ERROR: resource.move: No target node: Move requires either a target node or 
> 'force' 
>
> I'm surprised: In the past the mommand simply added a negative location for 
> the node the was running (at least I think). 
> The resource was running on the other node of a two-node cluster... 
>
> Also I noticed that "migrate" no longer appears in crm's help for "resource". 
> There's only a "move". 
>
> Help for "move" still says: 
> resource# help move 
> Move a resource to another node 
>
> Move a resource away from its current location. 
> ... 
>
> Regards, 
> Ulrich 
>
>
> ___ 
> Manage your subscription: 
> https://lists.clusterlabs.org/mailman/listinfo/users 
>
> ClusterLabs home: https://www.clusterlabs.org/ 
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

[ClusterLabs] What happened to "crm resource migrate"?

[Ulrich Windl]

Hi!

I was trying to do a "crm resource migrate" the first time in SLES 12 (the way 
I did in SLES11), but I got this message:
# crm resource migrate prm_isr_mail1 PT10M
ERROR: resource.move: No target node: Move requires either a target node or 
'force'

I'm surprised: In the past the mommand simply added a negative location for the 
node the was running (at least I think).
The resource was running on the other node of a two-node cluster...

Also I noticed that "migrate" no longer appears in crm's help for "resource". 
There's only a "move".

Help for "move" still says:
resource# help move
Move a resource to another node

Move a resource away from its current location.
...

Regards,
Ulrich


___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Definition of function pointer cpg_totem_confchg_fn_t

[Jan Friesse]

DaShi,


typedef void (*cpg_totem_confchg_fn_t) (
 cpg_handle_t handle,
 struct cpg_ring_id ring_id,
 uint32_t member_list_entries,
 const uint32_t *member_list);

Should "struct cpg_ring_id ring_id" be "struct cpg_ring_id *ring_id"?


Nope, ringid is really passed as a structure, not a pointer.

https://github.com/corosync/corosync/blob/ee8b8993d98b3f6af9c058194228fc534fcd0796/test/testcpg.c#L212 
is an example how to use this callback.


Regards,
  Honza



Regards,
Dashi Cao
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/



___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

[ClusterLabs] Antw: Coming in Pacemaker 2.0.3: crm_mon output changes

[Ulrich Windl]

>>> Ken Gaillot  schrieb am 15.10.2019 um 00:47 in
Nachricht
:
> Hi all,
> 
> With Pacemaker 2.0.2, we introduced a new experimental option for XML
> output from stonith_admin. This was the test case for a new output
> model for Pacemaker tools. I'm happy to say this has been extended to
> crm_mon and will be considered stable as of 2.0.3.
> 
> crm_mon has always supported text, curses, HTML, and XML output, and
> that doesn't change. However the command‑line options for those have
> been deprecated and replaced with new forms:
> 
> Old:New:
> ‑‑as‑xml‑‑output‑as=xml
> ‑‑as‑html=FILE  ‑‑output‑as=html ‑‑output‑to=FILE
> ‑‑web‑cgi   ‑‑output‑as=html ‑‑output‑cgi
> ‑‑disable‑ncurses   ‑‑output‑as=text

I'd prefer "--output-format|output-fmt|format" over "--format-as", because I
think it's more clear.
Accordingly I'd prefer "--output-file" over "--output-to".
Why not replace "--weg-cgi" with "--output-format=cgi"?

> 
> The new ‑‑output‑as and ‑‑output‑to options are identical to
> stonith_admin's, and will eventually be supported by all Pacemaker
> tools. Each tool may support a different set of formats; for example,
> stonith_admin supports text and xml.
> 
> When called with ‑‑as‑xml, crm_mon's XML output will be identical to
> previous versions. When called with the new ‑‑output‑as=xml option, it
> will be slightly different: the outmost element will be a  result> element, which will be consistent across all tools. The old XML

Why not as simple "status" element? "-result" doesn't really add anything
useful.

> schema remains documented in crm_mon.rng; the new XML schema will be
> documented in an api‑result.rng schema that will encompass all tools'
> XML output.
> 
> Beyond those interface changes, the text output displayed by crm_mon
> has been tweaked slightly. It is more organized with list headings and
> bullets. Hopefully you will find this easier to read. We welcome any
> feedback or suggestions for improvement.

Older versions use a mixture of space for indent, and '*' and '+' as bullets.
A unified approach would be either to use some amount of spaces or one TAB for
indenting consistently, maybe combined with a set of bullet characters for the
individual levels of indent.

So "--bullet-list='*+'" and "--indent-string=..." could set such.


> 
> The HTML output gains a new feature as well: it uses CSS throughout,
> rather than ancient HTML formatting, and you can provide a custom
> stylesheet (via ‑‑output‑stylesheet‑link=URL) to control how the page
> looks.

As it only applies to HTML, why not "--html-style=URL". I think nobody will
confuse this with providing the stylesheet literally as parameter...

> 
> If you are a heavy user of crm_mon, we encourage you to test the new
> release (expected later this week) and let us know what you like and
> don't like. You don't have to upgrade a whole cluster to test crm_mon;
> you can install the new release on a test machine, copy the CIB from
> your cluster to it, and run it like: CIB_file=/path/to/copied/cib.xml
> crm_mon . That won't work with curses output, but you can test
> text, HTML, and XML that way.

BTW: Can we rename "-?" (version) to "-V" and "-V" (verbose) to "-v"? That'll
be more standard.
The possible outputs of "-s" could be documented in greater detail, possibly
allowing to query a specific resource (implementing some simple query language)
would be great. Not only for "-s", but also for all other output.

Regards,
Ulrich


___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/