kubeflow/mxnet-operator

Request for roadmap

sandeep-krishnamurthy opened this issue · 6 comments

sandeep-krishnamurthy commented

Hello @suleisl2000, great work! Excited to see MXNet with Kubeflow.
I am very interested in working on MXNet + Kubeflow. Do you see the need for new contributions that can be helpful in this project? Can you please share the roadmap/ToDos/how to get started with the contributions?

Thanks for working on this.

suleisl2000 commented

@sandeep-krishnamurthy Thank you for your interesting. We are glad and open for new contributions.
Firstly, we are working on mxnet v2 version (see #2) and also there are some trivial things to do like CI, e2e test. Secondly, we plan to integrate with kube-arbitrator project for better workload scheduling, e.g. latest gang scheduling, GPU topology aware scheduling and so on. Thirdly, we may take mxboard integration and other mxnet training mode (e.g. allreduce) into account. Finally, any ideas are welcome and please feel free to raise an issue if you want and we can discuss there.

Append Kubeflow Contributor Guide here

gaocegege commented

I think we could add the roadmap in the repository.

jlewi commented

Would it be more useful just to open up issues?

Kubeflow does a major release at the end of each quarter.
0.3 end of September

  • We aim to cut mid september although we will do many cherry picks and minor releases after that
    0.4 end of December
  • (Although since Kubecon is in early December we might cut a preview version early to support demos and then finalize at end of December)

My suggestion would be to try to identify the minimum amount of work needed to get an alpha version of the mxnet operator into 0.3 and then push all the other items into 0.4.

I've added the labels
area/0.3.0
area/0.4.0
(see kubeflow/community#174 for why /area)

You can apply the labels using the /label command (see kubeflow/community#174) for more info
provided you are members of the kubeflow GitHub org.

@jzp1025 I sent you an invite; please send a PR adding yourself to
https://github.com/kubeflow/community/blob/master/members.yaml

suleisl2000 commented

Thanks for your information. I have added a markdown file to describe roadmap plan. I think we can close this issue and update roadmap there on demand.

gaocegege commented

/close

k8s-ci-robot commented

@gaocegege: 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.