-
Notifications
You must be signed in to change notification settings - Fork 44
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
BZ #1236180 - Updated redis-vip then ceilo-central constraint #545
BZ #1236180 - Updated redis-vip then ceilo-central constraint #545
Conversation
This diff is comparing the full set of pacemaker constraints before and after this PR. As seen below, the "redis-vip with redis-master" constraint has been removed, and the ceilomenter-central/redis-vip colo constraint changed to kind:Optional.
|
@davidvossel , I can update that. Our usual pattern is to also have colo constraints with haproxy, i.e. for nova-pub it looks like:
Do we want the colo constraint here too? I.e., do the exact same thing for the ip-redis- as we are doing for nova-pub above? |
https://bugzilla.redhat.com/show_bug.cgi?id=1236180 Remove the redis-vip then ceilo-central constraint. Instead use a redis-vip before haproxy 'kind:Optional' constraint which typically has the same effect of ensuring redis is up before ceilo-central. This change is to avoid a big cascade of resources being stopped if the redis vip moves. Also removes redis-vip colocation with redis-master. Not necessary since haproxy forwards from the VIP appropriately.
ac01505
to
0f2e4ba
Compare
Assuming answer is "yes" to above for now. The before-and-after patch diff of the constraints now looks like:
|
@cwolferh Right, if the redis VIP is frontend for HAProxy (which it is based on previous discussions) then that VIP needs to both be ordered before haproxy and colocated with haproxy. The patch as you have it looks right now. |
I'll test this today |
WFM |
…ctor BZ #1236180 - Updated redis-vip then ceilo-central constraint
https://bugzilla.redhat.com/show_bug.cgi?id=1236180
The redis-vip then ceilo-central constraint should be Optional not
Mandator (so as to avoid a big cascade of resources being stopped if
the redis vip moves).
Also removes redis-vip colocation with redis-master. Not necessary
since haproxy forwards from the VIP appropriately.