-
Notifications
You must be signed in to change notification settings - Fork 918
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
Integration between Orchestrator and ProxySQL #161
Comments
@leeparayno thank you so much for taking notes! cc @renecannao |
These are very detailed notes! |
Hi @leeparayno Thanks allot for your detailed summary of this discussion. I attended as well and told you guys I've done some basic tests with orchestrator + consul + ProxySQL. We are currently, at Wix.com, building and designing the full solution and architecture . I will update in a Separate blog (I will send the link next week ) our progress of the building, designing and POC of the final solution and will be more than Happy to share with the community . Meanwhile please have a look at a question/issue/discussion I've posted regarding the design of the orchestrator placement in the network topology: #172 |
Related: #175, a |
Percona Live 2017 - Birds of a Feather Discussion: Integration Between Orchestrator and ProxySQL
Notes on the BoF discussion tonight. (Apologies if I misquoted anyone).
Amsterdam
Rene - solution that fits most of the stuff
Problem Statement
No overview of entire cluster
Solution provided by someone:
Hooked with Consul with Orchestrator
No knowledge of whole architecture known to individual ProxySQL (Rene)
Jessica (Github)
Consul in production
Chubby - at Google (Sugu)
What is the Source of Truth?
Orchestrator
HA - runs with backend database
Service should be high available
Github
Simon Mudd - always running 2 clusters
We don't need the coupling between these systems to be 100% HA necessarily (Lee)
Potential Solutions
The text was updated successfully, but these errors were encountered: