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

make katib-db configurable #533

Closed
naseemkullah opened this issue May 16, 2019 · 12 comments · Fixed by #868
Closed

make katib-db configurable #533

naseemkullah opened this issue May 16, 2019 · 12 comments · Fixed by #868
Assignees

Comments

@naseemkullah
Copy link

dbNameTmpl = "root:%s@tcp(katib-db:3306)/katib?timeout=5s"

Please make katib-db:3306 configurable with os.Getenv("MYSQL_HOST") and os.Getenv("MYSQL_PORT")

@gaocegege
Copy link
Member

We expected that katib mysql is running in k8s, thus we use katib-db directly. But we should make it configurable. I agree.

@naseemkullah
Copy link
Author

Thanks. I am working on a helm chart now, and it is not guaranteed that the name of the service will be katib-db for the helm release. In fact it probably won't be. This would really help!!

@gaocegege
Copy link
Member

@naseemkullah Oh I really love helm chart! Do you have a deadline for it? We will release a new version at the end of this month maybe.

@naseemkullah
Copy link
Author

naseemkullah commented May 16, 2019

Thanks! :) :)
Also want to shoutout @dodizzle who has been helping out.

I think we can have it ready soon (maybe 1 more week?), but we would be nice to get some fixes in on code side, mostly parameterizations for MYSQL configs.

Ideally we can use a single MySQL instance with a db for katib and a db for ml-pipeline.

@gaocegege
Copy link
Member

@naseemkullah @dodizzle Thanks for your work!

Are you packaging v1alpha1 or v1alpha2 for katib?

@naseemkullah
Copy link
Author

naseemkullah commented May 16, 2019

I was confused about that actually. Never used kubeflow, really approaching this from Ops perspective.

https://github.com/kubeflow/katib/tree/master/manifests

Which should be ported?

So far we have the following workloads (please ignore helm generated prefix)

lumbering-pika-katib-core
lumbering-pika-katib-core-rest
lumbering-pika-katib-studyjob-controller
lumbering-pika-katib-suggestion-bayesian-optimization
lumbering-pika-katib-suggestion-grid
lumbering-pika-katib-suggestion-hyperband
lumbering-pika-katib-suggestion-random
lumbering-pika-katib-ui

@gaocegege
Copy link
Member

Now we are working on v1alpha2. Thus we recommend doing it after v1alpha2 is released.

If you want to run v1alpha1, you should install all the components in manifests/v1alpha1

@gaocegege
Copy link
Member

lumbering-pika-katib-core
lumbering-pika-katib-core-rest
lumbering-pika-katib-studyjob-controller
lumbering-pika-katib-suggestion-bayesian-optimization
lumbering-pika-katib-suggestion-grid
lumbering-pika-katib-suggestion-hyperband
lumbering-pika-katib-suggestion-random
lumbering-pika-katib-ui

Here missed a DB

@naseemkullah
Copy link
Author

@gaocegege
Copy link
Member

Then I think it should work. If the url is configurable.

@naseemkullah
Copy link
Author

bump

@gaocegege
Copy link
Member

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants