from a mail thread about remote nodes:
Part of the issue here is terminology; "remote" is used to refer to both
ocf:pacemaker:remote resources and VirtualDomain resources with remote-node.
Upstream is moving to clarify this by using "remote node" only to refer
to ocf:pacemaker:remote, and "guest node" to refer to VirtualDomain with
remote-node. This is mostly complete at a user-visible level, with the
main exception being the remote-node meta-attribute itself.
So, pcs's remote-node command is actually becoming more confusing, in
that it only applies (in upstream's terms) to guest nodes and not remote
Perhaps it would be a good idea to rename pcs's command to guest-node,
and leave remote-node as a hidden, deprecated alias.
We want to rename the commands and probably improve their documentation.
We should also think about displaying status of nodes, listing remote and guest nodes in their respective categories.
Consider if it is needed to do changes to some other commands in order to clarify the situation.
Created attachment 1282156 [details]
proposed fix (part1)
Created attachment 1282157 [details]
proposed fix (part2)
Created attachment 1282159 [details]
proposed fix (part3)
`pcs cluster remote-node add` and `pcs cluster remote-node remove `commands have been deprecated. They were in fact managing guest nodes, so they were replaced with `pcs cluster node add-guest` and `pcs cluster node remove-guest` commands. The deprecated commands have been removed from man page and usage but are still available in pcs.
`pcs cluster node add-remote` and `pcs cluster node remove-remote` commands have been added. These commands manage remote nodes (ocf:pacemaker:remote).
Do you think that for the purpose of a release note description we could combine this description with the description in BZ#1176018 -- the BZ about the new commands to add and remove remote nodes? It seems as though anybody who needs to know this would need to have both pieces of information.
Yes, this bz's doc should be definitely merged with doc of BZ#1176018.
A note: While the new pcs version recognizes the old syntax for backwards compatibility, it will ask for the --force flag to perform the requested command so any script using the old syntax will have to be amended anyway:
[root@localhost ~]# pcs cluster remote-node add Node9 Resource
Error: this command is deprecated, use 'pcs cluster node add-guest', use --force to override
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.