-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Deploy Model DB with durable storage #1860
Comments
I think there are two databases used by ModelDB
So both of these need to be stored on PVC. For MongoDB we are just using the standard MongoDB image; so I'm guessing there are command line arguments or environment variables that we can use to store the database on a PVC. For ModelDB I think we might need: VertaAI/modeldb#310 It looks like that PR makes some changes to store the model in the directory "/db" which we could then mount on PV. |
@mpvartak To integrate this into Kubeflow you'll want to port over the changes in VertaAI/modeldb#310 into the modeldb.libsonnet file at the locations mentioned in the previous comment. Once you have the changes integrated you can follow the instructions for using kfctl To deploy Kubeflow on GCP. If you run it from your local repo; it will use whatever changes you've made to the Katib/Modeldb components. |
@mpvartak any update on this? |
@mpvartak @YujiOshima @gaocegege; anyone working on this? |
Yep! We got the kssonnet figured out. Please watch for a PR to ModelDB in
the next day or two.
…On Mon, Dec 3, 2018 at 10:41 AM Jeremy Lewi ***@***.***> wrote:
@mpvartak <https://github.com/mpvartak> @YujiOshima
<https://github.com/YujiOshima> @gaocegege <https://github.com/gaocegege>;
anyone working on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1860 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFeWwz-EBmOcGlStRkJSUZ_cI3Tttjm0ks5u1XBOgaJpZM4X6opV>
.
|
#2050 was merged so closing this out. |
In 0.4.0 we should be able to deploy ModelDB with durable storage so that it can be used for primitive model tracking.
Context:
kubeflow/katib#137
kubeflow/community#195
kubeflow/examples#134
I know there's discussion about redesigning model tracking from scratch (kubeflow/community#195 ) but I don't see that landing in 0.4.
ModelDB on the other hand covers a lot of the use cases we care about. I wouldn't expect it to be difficult to deploy ModelDB with durable storage (e.g. PVC). That would unblock a lot of useful scenarios as people could begin using it to track models.
Related:
ModelDB v2: goo.gl/NaDXpQ
/cc @mpvartak
/cc @garganubhav
The text was updated successfully, but these errors were encountered: