Add Docker images for Percona Server.#1547
Conversation
enisoc
commented
Mar 3, 2016
|
Is it really a different GTID implementation than MySQL 5.6? |
|
I don't think so. This was contributed as a patch file by another Googler, and I turned it into a PR so I can take a look and clean it up. I asked him if there are any changes in the copied GTID files, and he said he just copied them because he's not familiar with how our flavor plugin system works. So I should be able to dedup those Go files. |
|
I reviewed the whole change because I was interested in the GTID implementation ;) So I left some comments there. I didn't know that you didn't write this, so excuse me when I meant you :) Reviewed 17 of 17 files at r1. bootstrap.sh, line 143 [r1] (raw file): dev.env, line 88 [r1] (raw file): docker/bootstrap/build.sh, line 18 [r1] (raw file): docker/bootstrap/Dockerfile.percona, line 8 [r1] (raw file): docker/lite/Dockerfile.percona, line 5 [r1] (raw file): docker/lite/Dockerfile.percona, line 9 [r1] (raw file): docker/lite/Dockerfile.percona, line 18 [r1] (raw file): go/vt/mysqlctl/mysql_flavor_percona.go, line 167 [r1] (raw file): go/vt/mysqlctl/replication/percona_gtid.go, line 73 [r1] (raw file): go/vt/mysqlctl/replication/percona_gtid_set.go, line 36 [r1] (raw file): Comments from the review on Reviewable.io |
|
If the GTID code is the same as MySQL 5.6, it just shouldn't be duplicated... The rest I think is just using the right docker image for Percona in our scripts. |
|
I've cleaned it up to re-use the $ go run test.go -flavor=percona
35 PASSED, 0 FLAKY, 0 FAILED, 0 SKIPPED |
|
LGTM Review status: 2 of 6 files reviewed at latest revision, 10 unresolved discussions. Comments from the review on Reviewable.io |
|
Reviewed 15 of 15 files at r2. Comments from the review on Reviewable.io |
Add Docker images for Percona Server.