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

Plans for Katib in v0.5 #319

Closed
jlewi opened this issue Jan 7, 2019 · 10 comments
Closed

Plans for Katib in v0.5 #319

jlewi opened this issue Jan 7, 2019 · 10 comments

Comments

@jlewi
Copy link
Contributor

jlewi commented Jan 7, 2019

Opening this issue to track planning for Katib in v0.5?

Do we want to define a minimal critical user journey (CUJ) for Katib and then create a backlog of issues to deliver it?

For me the priority would be enabling users to easily walk through doing a hyperparameter search using Katib. It would be great to get Katib integrated into one of our E2E examples such as

  • mnist
  • GitHub issue summarization
  • object detection

/cc @johnugeorge @YujiOshima @gaocegege

@johnugeorge
Copy link
Member

Currently, mnist example is already added in katib repo
#309

@jlewi you mean, adding the same to the examples repository?

@jlewi
Copy link
Contributor Author

jlewi commented Jan 14, 2019

@johnugeorge I think the example is a good start. However, I think the question is do we have a good E2E story for how users go from building a model to doing a hyperparameter search to identify the best model?

I think a big piece we are missing is a CUJ defining what the experience should look like. I think @richardsliu is going to start putting together an initial draft.

It looks like the instructions for Katib could probably use more work as well.
https://www.kubeflow.org/docs/guides/components/hyperparameter/

@johnugeorge
Copy link
Member

@jlewi Yes. I agree with you. E2E experience is not described well enough. I talked with @richardsliu and he is working on the CUJ . One the CUJ is out, we will fix all the missing pieces for a good E2E story.

@richardsliu richardsliu self-assigned this Jan 18, 2019
@richardsliu
Copy link
Contributor

richardsliu commented Jan 18, 2019

CUJ: https://bit.ly/2QNKMwt

@richardsliu
Copy link
Contributor

Roadmap: #348
Issues for 0.5: https://github.com/kubeflow/katib/issues?utf8=%E2%9C%93&q=+label%3Aarea%2F0.5.0+

For 0.5, I think the P0 goals should be:

  • enhance the status fields
  • enable running katib jobs in different namespaces

The P1 goal is to explore integration with fairing.

@johnugeorge @YujiOshima @gaocegege @hougangliu WDYT?

@YujiOshima
Copy link
Contributor

@richardsliu Thanks, I agree with P0 goals.

The P1 goal is to explore integration with fairing.

Does it mean integration with jupyter? pipeline? or both?

@richardsliu
Copy link
Contributor

@YujiOshima It means integrating with Jupyter notebooks. We want to enable the user to start a StudyJob without needing to write a CRD.

@jlewi
Copy link
Contributor Author

jlewi commented Feb 4, 2019

@richardsliu @johnugeorge Can we file issues related to all the work we want to get done in 0.5 for this CUJ and label them for 0.5 (and ideally add a cuj/hp-tuning label)?

Once we do that I think we can close this issue out.

Looks like there are currently 9 issues tagged in the kanban board for 0.5.
https://github.com/orgs/kubeflow/projects/4

@richardsliu
Copy link
Contributor

I added an area/cuj label and put a bunch of additional issues to the kanban board. Closing this issue for now.

@jlewi
Copy link
Contributor Author

jlewi commented Feb 11, 2019

Renamed the label to cuj/hp-tuning to match other cuj labels.

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

No branches or pull requests

4 participants