What the status of ModelDB project is?

[YujiOshima]

Hi! @mpvartak
I'm from kubeflow/katib.
We are using modelDB in our project.
And we have some requests for this project.
But this project does not active since Feb.
Could we get involved in the development of ModelDB and help to maintain it?

[gaocegege]

/cc @gaocegege

[mpvartak]

Hi there, thanks for pinging! Absolutely, we'd be super interested in getting more contributors to help maintain modeldb. We're in the middle of a transition, so things have been slow. What's the best way to reach you? Please feel free to email at mvartak_at_csail.mit.edu.

PS: Katib looks really good!

[gaocegege]

@mpvartak

Thanks for your reply! We (Kubeflow guys) have a slack channel. @YujiOshima and me, maintainers of katib, usually discuss in the topic #hyperparameter-tuning. Thus we prefer to use Slack if you do not mind since there are other people also interested in the project.

As @YujiOshima said, we are using modeldb for model management. And we found some pain points from our side to be enhanced or implemented:

• not user-friendly API. We need to maintain go thrift interfaces.
• Data can not be deleted from DB.

We are glad to help modeldb in the things that we are interetsed in first, to demonstrate our knowledge on modeldb code base. And as the development of katib is going on, maybe we need some more features from modeldb. We hope that we could collaborate deeply. We could discuss about how to achieve it via slack or email, e.g. outside collaborator or we file PR then request owner's review.

BTW, thanks for your awesome work on model management! 🎉 😄

[jlewi]

I'm experimenting with using Model DB to track experiments/models in Kubeflow and I ran into some problems accessing the data in the UI:

kubeflow/examples#134

Any help would be greatly appreciated.

[jlewi]

I think forking is premature. What are the features/fixes that we want? Do we have folks in the Kubeflow community to work on this? I don't think we Kubeflow have really started trying to tap into modelDB yet. So my highest priority would be trying to leverage modelDB and seeing whats Missing for our use cases.

…

On Mon, Jul 2, 2018, 5:15 PM bhack ***@***.***> wrote: @jlewi <https://github.com/jlewi> Do you think that Model DB needs to be forked? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#290 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAvcA9J7kdD92sDhc4t0d2A6RddkEYX7ks5uCreqgaJpZM4Ty4C5> .

[mpvartak]

@jlewi responded to your comment on Kubeflow repo. Need to repro your bug and will update.

[ryandawsonuk]

The README says that V2 is coming soon but there hasn't been a commit to master for 9 months and I don't see any active branches. Is this project still actively maintained? Anyone have any insight?

[gaocegege]

Same question. I cannot see any progress here.

[mpvartak]

Hi all -- we have been developing the project under VertaAI (https://github.com/VertaAI/) -- the company we started around ModelDB. We are actively maintaining it the OSS fork there while we figure out the best way to update the MIT repo too (since it's a different org). We should have this sorted out by end of year, but for now, please check out the VertaAI repos, they are up-to-date. Also happy to get you set up with a trial account on VertaAI, please send me at note!

[ryandawsonuk]

Ok so basically https://github.com/VertaAI/modeldb is how to run V2 and the other repos there are components of V2?