You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "Wangda Tan (Jira)" <ji...@apache.org> on 2019/12/16 07:54:00 UTC
[jira] [Commented] (SUBMARINE-258) [SS]Add k8s job submitter in
submarine server to run TF job on k8s
[ https://issues.apache.org/jira/browse/SUBMARINE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997065#comment-16997065 ]
Wangda Tan commented on SUBMARINE-258:
--------------------------------------
[~jiwq], do you still need this Jira? Can we move all K8s-submitter related efforts to a new umbrella, and add the component "[K8s Submitter|https://issues.apache.org/jira/issues/?jql=project+%3D+SUBMARINE+AND+component+%3D+%22K8s+Submitter%22]"? Now it is a bit hard to track these tickets.
> [SS]Add k8s job submitter in submarine server to run TF job on k8s
> ------------------------------------------------------------------
>
> Key: SUBMARINE-258
> URL: https://issues.apache.org/jira/browse/SUBMARINE-258
> Project: Apache Submarine
> Issue Type: Sub-task
> Components: K8s Submitter
> Reporter: Zhankun Tang
> Assignee: Wanqiang Ji
> Priority: Major
>
> As a PoC, we need several below steps to run the TF job on k8s.
> # The submarine server can run as an independent daemon
> # tf-operator deployed in a k8s cluster. Use kubeflow/tf-operator for now
> # REST API in submarine server to accept a generic TF job spec
> # submitter-k8s translate the spec into tf-operator format and use k8s client API to submit this to the cluster
> # REST API to get tf job status from k8s and parse it to a standard format to be consumed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org