decider: initial import of Orchestrator#6582
Conversation
deepthi
left a comment
There was a problem hiding this comment.
To be clear, this continues to build orchestrator as a separate binary, and no orchestrator code is included in vitess binaries, correct?
In that case, LGTM
|
@sougou : to review this PR, is b1366b7 a faithful copy of original |
harshit-gangal
left a comment
There was a problem hiding this comment.
If there is no change in functionality and only plain import of orch code, I will let it merge.
* go modules enabled * go -> go/vt/orchestrator * go/cmd -> go/cmd * vendor-> external: golib, raft, zk * imports fixed * lint checks are failing Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
There is currently no plan to use raft. So, we should eventually delete this entire dependency. Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
c8c1423 to
d09aac9
Compare
|
planetscale#68 is a simplification of this PR, and is more review-able. |
|
actually, planetscale#68 is just linter changes. What I'd like to see is a PR with the actual code changes on top of import+linter. |
In that case, you'll probably find the oc2 branch interesting. I can merge this and create a new PR from oc2 to master. |
This project is code named
maestro.This copies the core code base from Orchestrator so we can modify it to become a native vitess component. This is the initial copy, with go modules and linter fixes. Not all linter errors are fixed, but the Orchestrator builds. There's otherwise no change in functionality.