Not use ModelDB as Default UI for Katib

[YujiOshima]

Currently, Katib uses ModelDB as Default UI.
But There is some issue on ModelDB.

• It uses Mongo and sqlite and cannot persistent datas
• The community is not active

We are looking for alternatives.
We are trying to distinguish management data between long term and short term.
Long-term: For Experimental tracking. It contains the path of Model data and Training Data. etc
Short-term: For Hyper-parameter tuning. It contains Study, Trial, Worker Info.

Experimental tracking is discussed here
But since StudioML and MLFlow and others are not for HP-tuning finding a rough trend of hyperparameter is difficult by their UI.
We should introduce Katib UI that is specialized to figure out a trend of hyperparameter space.
It will visualize Short-term data.
@jlewi @gaocegege WDYT?

[jlewi]

Are you suggesting building a whole new UI for Katib?

Do we have the resources to do this right now?

I'd be very happy if we just made ModelDB work well. The animated GiF on the Katib web page seems to show that ModelDB provides most of the features mentioned in
kubeflow/community#195

For Katib, I'd really like to see Katib working E2E and integrated with some of our examples like GitHub Issue Summarization or GitHub code search.

[jlewi]

@YujiOshima Can tag this issue with a release and priority please?

[YujiOshima]

@jlewi Model DB has its own data scheme and DB.
And since it is not an active community, we need to fork it and develop for working well.
I made a new simple UI for Katib #208 it completely depends only Katib API.
When we need more rich UI for Experimental Tracking, integrate an Experimental Tracking tool (MLFlow or StudioML) loosely with its API.

[jlewi]

The ModelDB folks just chimed in on Slack. They formed a company around ModelDB. Here's there RoadMap
https://docs.google.com/document/d/1ZRNgqDENw7QE1jOVkJcdxHbH8dZID88e5KmQ-nkcTwo/edit

[gaocegege]

/close

Now we have our own UI.

[k8s-ci-robot]

@gaocegege: Closing this issue.

In response to this:

/close

Now we have our own UI.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.