forked from crowbar/crowbar-openstack
-
Notifications
You must be signed in to change notification settings - Fork 1
[backport] horizon: Configure stickiness with haproxy #33
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
Open
matelakat
wants to merge
2
commits into
sap-oc:stable/sap/3.0
Choose a base branch
from
matelakat:backport-841
base: stable/sap/3.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
We use cookie-based stickiness for non-SSL, and we also expire the stickiness based on the session timeout. This should make the haproxy/horizon combo to work well, with each session sticking to one backend, thus avoiding potential issues where requests are spread between multiple backends. Note that we use two cookies: - sessionid, which identifies a session - csrftoken, which identifies a "login session", before a real session really exists, with the proper sessionid token (cherry picked from commit 4da5c63)
Since horizon is really used by browsers, the affinity based on SSL session ID is not enough because the browsers open multiple connections. To make sure a user always ends up on the same backend, we enforce the balance strategy to be "source" (that is based, on the the client IP address). (cherry picked from commit 2471a0e)
Author
|
This seems to fail due to: |
Author
|
That's because we first need to merge the ha change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the backport of crowbar#841