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

Its difficult to discern which unit is a leader in amulet #131

Open
lazypower opened this issue May 2, 2016 · 1 comment
Open

Its difficult to discern which unit is a leader in amulet #131

lazypower opened this issue May 2, 2016 · 1 comment

Comments

@lazypower
Copy link
Contributor

Often times when I'm working with quorem or need special behaviour out of a "leader" unit, I use leader-election to do things, like spin up a management service, or deploy specialized configuration.

I will often need to test this in amulet, and thus far the only way i've come up with to find the leader is basically sentry.run('is-leader') in a loop and break when we find the leader.

What would be handy is to have this exposed in amulet with a get_leader('service') so I can scope assertions without implementing the same for loop in all of my amulet tests.

@lazypower
Copy link
Contributor Author

This has a line item in #116 and is somewhat a duplicate of it

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

1 participant