You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@yunikorn.apache.org by "Adam Antal (Jira)" <ji...@apache.org> on 2020/05/27 11:11:00 UTC

[jira] [Commented] (YUNIKORN-170) Create YuniKorn App CRD

    [ https://issues.apache.org/jira/browse/YUNIKORN-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117655#comment-17117655 ] 

Adam Antal commented on YUNIKORN-170:
-------------------------------------

App CRD would be a really perfect fit for YUNIKORN-117. For application related events it would be better to emit those to the app CRDs.

[~wwei] if you agree, I'll link this jira and (probably going to wait for it to be merged).

> Create YuniKorn App CRD
> -----------------------
>
>                 Key: YUNIKORN-170
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-170
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - scheduler
>            Reporter: Weiwei Yang
>            Assignee: Ting Yao,Huang
>            Priority: Major
>
> According to the design doc [https://docs.google.com/document/d/11HjKk351zNCXzBh266r4-LWmbghWnexy_gsAzBel4EQ/edit?ts=5ec4fe1b]. We need to create the app CRD so the scheduler can get the meta info of a job that has the gang scheduling requirement. And more importantly, we can leverage the CRD to do the end2end app lifecycle management.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org