Wilfred Spiegelenburg closed YUNIKORN-41.
    Fix Version/s: 0.8
       Resolution: Fixed

Just committed PR#106
Thank you [~wangda] for the update

Follow up jira to be logged to update the screenshots when the web UI update is 

> Update YuniKorn main README.md to make user can better get focus of the 
> project
> -------------------------------------------------------------------------------
>                 Key: YUNIKORN-41
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-41
>             Project: Apache YuniKorn
>          Issue Type: Task
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.8
>          Time Spent: 20m
>  Remaining Estimate: 0h
> The message from the Apache YuniKorn Github is a bit confusing when we put 
> YARN, and “general scheduler” together. 
> For most of the companies we spoke to, initially, they’re confused with: Is 
> it a K8s scheduler, or it is a YARN RM but hook up with K8s. I think we need 
> to do massive work to make the marketing message correct.
> To me, the #1 use case YuniKorn trying to solve now is to be the best 
> scheduler in K8s to solve batch workload problems. 
> It is nicely designed to allow yunikorn-core to hook up with other RMs, but 
> that is the next step.
> We can also include other items like highlights of K8s integration, perf 
> test, and community sync ups to the same README.

This message was sent by Atlassian Jira

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

Reply via email to