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

worker: Rename worker_interface to worker #70

Merged
merged 1 commit into from
Apr 26, 2018
Merged

worker: Rename worker_interface to worker #70

merged 1 commit into from
Apr 26, 2018

Conversation

gaocegege
Copy link
Member

worker_interface is a little misunderstanding, since it is not just a package for interface.

/assign @YujiOshima

Signed-off-by: Ce Gao gaoce@caicloud.io

@YujiOshima
Copy link
Contributor

@gaocegege The worker is an instance of evaluating a trial.
So the worker is a k8s job, a TF Job etc.
How about worker-controller?

@gaocegege
Copy link
Member Author

I think worker suits it, because it represents the worker to run these trials 🤔

WDYT @ddysher

@ddysher
Copy link
Member

ddysher commented Apr 26, 2018

conceptual-wise, i agree with @YujiOshima that worker is more like a controller; however, using worker_controller is quite verbose IMO; so my suggestion is to simply use worker as proposed in this PR.

@@ -41,7 +41,7 @@ type studyCh struct {
addMetricsCh chan string
}
type server struct {
wIF worker_interface.WorkerInterface
wIF worker.WorkerInterface
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gaocegege
Copy link
Member Author

Addressed

@ddysher
Copy link
Member

ddysher commented Apr 26, 2018

LGTM

@YujiOshima do you want to take another look?

@YujiOshima
Copy link
Contributor

@ddysher Thanks! LGTM the name worker.Interface !
/approve

@gaocegege
Copy link
Member Author

/lgtm

@k8s-ci-robot
Copy link

@gaocegege: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gaocegege, YujiOshima

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [YujiOshima,gaocegege]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gaocegege
Copy link
Member Author

I am not sure why tide does not merge it automatically. Same as kubeflow/training-operator#557

@gaocegege gaocegege added the lgtm label Apr 26, 2018
@k8s-ci-robot k8s-ci-robot merged commit db8e026 into kubeflow:master Apr 26, 2018
@gaocegege
Copy link
Member Author

It is too hack.. We can not merge a PR without lgtm although we have already added approve.

@gaocegege gaocegege deleted the worker branch April 26, 2018 03:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants