-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support for other Deep Learning Libraries #74
Comments
Correct! Though we do include TensorFlow to start, we're not TensorFlow
exclusive - at all! We only mention "flow" because it's such a common term
in ML. We'd ABSOLUTELY love some help including other frameworks!
…On Tue, Jan 2, 2018 at 1:26 PM michael mccune ***@***.***> wrote:
@NathanNZ <https://github.com/nathannz> i think issue #33
<#33> covered some of this in
the comments. imo, it will be great to see Kubeflow grow beyond the
perception that it is just a TensorFlow related project.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#74 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADIde83Ioos3VfH215bGxcW8Xk2NDsPks5tGp72gaJpZM4RPfxR>
.
|
I came across a CRD for mxnet in deepinsight/mxnet-operator. We'd be very receptive to including this in Kubeflow if someone is interested in taking this up. Forking the ksonnet prototype for TfJob to create a prototype for mxnet should be fairly straightforward. is anyone interested in taking this on? |
@jlewi Hi! It is great. I'm so interested in a CRD for MxNet. |
pytorch work has started caffe2 has started |
* Refine API Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * add cli Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * add gird demo Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * add GKEDemo Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix test Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * add mnist-models.yaml Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix docs Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * improve GKEdemo docs Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * add more docs Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix test Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * enable get worker from trialid ana add getParameterList from studyid Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix doc Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix test Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com> * fix Signed-off-by: YujiOshima <yuji.oshima0x3fd@gmail.com>
* add kam to ci-team.members.txt * add alphabetically
First of all it's awesome seeing an initiative to help bring a bit of DevOps to ML, something I feel is well overdue - however I have a question just to clarify my own understanding of what KubeFlow actually is.
Regarding this statement in the readme it seems to imply that other OSS solutions will be supported however I'm not sure to what extent, especially regarding TensorFlow. My uncertainty rises from the fact that this is a Google run endeavour and the project name itself (implying the mash up between K8 and TF). As such would it be correct in thinking that other data flow programming libraries are out of this projects scope? (Caffe, CNTK etc)?
The text was updated successfully, but these errors were encountered: