Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification request: standardized "list" representation #275

Open
jnpkrn opened this issue Jun 13, 2019 · 1 comment
Open

Clarification request: standardized "list" representation #275

jnpkrn opened this issue Jun 13, 2019 · 1 comment

Comments

@jnpkrn
Copy link
Contributor

jnpkrn commented Jun 13, 2019

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):

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

@kgaillot
Copy link

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]".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants