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

New versions of proxysql #38

Closed
narcisbcn opened this issue Sep 28, 2017 · 1 comment · Fixed by #62
Closed

New versions of proxysql #38

narcisbcn opened this issue Sep 28, 2017 · 1 comment · Fixed by #62

Comments

@narcisbcn
Copy link
Contributor

How to evolve this project

Hi,
I would like to get some feedback or just open a discussion about how we can progress with new proxysql versions, those will introduce new fields in tables, then some compatibility could be broken.

Also, another issue candidate I see: we use automatic failover techniques, then to make this module compatible to our design is to specify to the provider do not look at some specific fields such as hostgroups or status, otherwise if the failover happens, puppet would move back the promoted slave to the original hostgroup (readers) set by puppet.

I have work done regarding this second step.

Thoughts?

Cheers

@mcrauwel
Copy link
Member

As for new fields and features: it's on my radar, just haven't had time to look into it...

For the failover techniques: you could set the puppet command to not load the config to runtime so puppet does not touch the active runtime tables. We ended up not managing STATUS but we do manage hostgroup_id.

If you have work done, always welcome to PR.

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