-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Vitess production testing/onboarding #2707
Labels
Comments
I've produced this video https://youtu.be/71nTBafPtcM, which should address 1 & 2. |
ajm188
added
Component: Documentation
docs related issues/PRs
Component: Examples
labels
Jun 24, 2022
frouioui
added a commit
to planetscale/vitess
that referenced
this issue
Mar 26, 2024
… CI (vitessio#2707) Co-authored-by: Florent Poinsard <35779988+frouioui@users.noreply.github.com> Co-authored-by: Matt Lord <mattalord@gmail.com> Co-authored-by: Florent Poinsard <florent.poinsard@outlook.fr>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
As we look to bring more users onto vitess, one area we can smooth over is helping the new user easily validate whether vitess will work in their system. There are a few areas I think any new person should concern themselves with:
When I was doing this process a few months ago, I wrote a binary called vtparse that could do all of the validation parts for the first item and output any errors found. This got the job done, but was clunky and is now outdated.
@sougou believes
vtcombo
could handle the first 2 parts. We'd need to provide some ease-of-access improvements to it:Finally, all of this should be documented in an Onboarding document.
cc @o1egl @derekperkins
The text was updated successfully, but these errors were encountered: