You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just a messenger to deliver the necessity of standardizing upon the
(presumably machine processable) output from list actions, as discussed
in this pacemaker commit (therefore inviting @kgaillot to follow up here):
Agreed. For backward compatibility, I'd make it a recommendation than a requirement.
Separately but affecting the design here, we should come up with at least a recommendation on what characters are allowed in port names and aliases, possibly including escape sequences for special characters. Currently pacemaker only allows alphanumeric, dash, underbar, and dot, but there have been user requests for port names like "cs-rh7-1 [1/2]".
I'm just a messenger to deliver the necessity of standardizing upon the
(presumably machine processable) output from
list
actions, as discussedin this pacemaker commit (therefore inviting @kgaillot to follow up here):
ClusterLabs/pacemaker@60ad773
By "standardizing", I'd imagine declaring the format explicitly in
https://github.com/ClusterLabs/fence-agents/blob/master/doc/FenceAgentAPI.md#agent-operations-and-return-values
Thanks
The text was updated successfully, but these errors were encountered: