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

[RFE] Allow to specify a single node configuration for a set of nodes #46

Open
ingvagabund opened this issue Feb 11, 2018 · 3 comments
Open

Comments

@ingvagabund
Copy link

ingvagabund commented Feb 11, 2018

Based on fencing policies a set of nodes can share identical configuration. We should set the configuration only once instead of doing that for each node separately.

For example, if "fence-config-" + nodeName does not exist, try "fence-config-type-" + labelValue(type) instead. The fall-back can be hierarchical as long as it is simple enough to implement without unneeded complexity. Of course, the set of labels that can be actually used this way needs to be limited. It could be part of the fence controller configuration. E.g.

...
node-config-label-fallback:
- type
- label2
- label3
...

In case the "fence-config-type-" + labelValue(type) does not exist, try "fence-config-label2-" + labelValue(label2). And so on.

E.g. a node has type=compute label, then look for "fence-config-type-compute" configmap.

@jfriesse
Copy link
Collaborator

jfriesse commented Feb 12, 2018

How to generate --plug parameter passed to fence agent?

@ingvagabund
Copy link
Author

What is the parameter needed for? Can you provide some example?

@jfriesse
Copy link
Collaborator

It's old version of config map, but use case is still valid:
https://github.com/jfriesse/hpg/blob/master/kubes/config-example.md

And the question is, how to generate the plug option.

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