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

[API][discussion] Create a CRD for study #6

Closed
gaocegege opened this issue Apr 4, 2018 · 4 comments
Closed

[API][discussion] Create a CRD for study #6

gaocegege opened this issue Apr 4, 2018 · 4 comments

Comments

@gaocegege
Copy link
Member

We have some discussions on slack and I have a idea to define a CRD and operator to manage studies, thus we could eliminate the customized CLI katib-cli and reuse kubectl to do the same thing.

I opened the issue to keep track of the idea.

@ddysher
Copy link
Member

ddysher commented Apr 16, 2018

Two random thoughts:

  • should we create CRD for trails as well?
  • since hyper-tuning system is fairly standalone system, we might also consider using API aggregation, which gives you higher flexibility, e.g. we can keep using mysql as our storage backend but provides the same API interface to katib users

@gaocegege
Copy link
Member Author

gaocegege commented Apr 16, 2018

Yeah, I think so. API aggregation is more appropriate.

But it requires lots of work, and I am not sure if we have plan to do it.

@gaocegege
Copy link
Member Author

I am not sure if we should create CRD for trails, since we define it in study config. Thus I think we could treat it as worker/ps in TensorFlow.

@jlewi
Copy link
Contributor

jlewi commented Jul 7, 2018

Duplicate of #87

@jlewi jlewi marked this as a duplicate of #87 Jul 7, 2018
@jlewi jlewi closed this as completed Jul 7, 2018
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

3 participants