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

Fix: pengine: disable migration for versioned resources #1112

Merged
merged 2 commits into from Aug 4, 2016

Conversation

igor-tsiglyar
Copy link
Contributor

This is a resolution of the issue discussed in #1063.

/* by default, we want baremetal remote-nodes to be able
* to float around the cluster without having to stop all the
* resources within the remote-node before moving. Allowing
* migration support enables this feature. If this ever causes
* problems, migration support can be explicitly turned off with
* allow-migrate=false. */
* allow-migrate=false.
* We don't support migration for versioned resources, though. */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI baremetal_remote_node is for the ocf:pacemaker:remote resource itself, so it will never have versioned parameters. No harm in double-checking here, though.

@kgaillot kgaillot merged commit 5dff106 into ClusterLabs:master Aug 4, 2016
@igor-tsiglyar igor-tsiglyar deleted the versioned-migration branch August 5, 2016 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants