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

Code restructuring #866

Closed
johnugeorge opened this issue Nov 8, 2018 · 6 comments
Closed

Code restructuring #866

johnugeorge opened this issue Nov 8, 2018 · 6 comments
Assignees

Comments

@johnugeorge
Copy link
Member

I am little confused with the code structure

With recent changes,

  1. We have duplicated jobcontroller in common package. However, v1beta1 code still uses controller.v2 job controller. (https://github.com/kubeflow/tf-operator/blob/master/pkg/controller.v1beta1/tensorflow/pod.go#L29)

  2. Files in https://github.com/kubeflow/tf-operator/tree/master/pkg/common/util are specific to TF and its version. ( eg: https://github.com/kubeflow/tf-operator/blob/master/pkg/common/util/unstructured/informer.go#L16) Does the util folder need to be in common folder?

/assign @richardsliu

@gaocegege
Copy link
Member

Files in https://github.com/kubeflow/tf-operator/tree/master/pkg/common/util are specific to TF and its version. ( eg: https://github.com/kubeflow/tf-operator/blob/master/pkg/common/util/unstructured/informer.go#L16) Does the util folder need to be in common folder?

I think so.

@richardsliu
Copy link
Contributor

1 is my mistake, it should be using the common package.

For 2, maybe we can move util under controller.v1beta1?

@richardsliu
Copy link
Contributor

@johnugeorge Anything else needed here?

@johnugeorge
Copy link
Member Author

2 is not done yet. But we can take it up in a separate PR when we move to a new version later

@johnugeorge
Copy link
Member Author

/close

@k8s-ci-robot
Copy link

@johnugeorge: Closing this issue.

In response to this:

/close

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.

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

No branches or pull requests

4 participants