wangdatan commented on a change in pull request #106: YUNIKORN-41 URL: https://github.com/apache/incubator-yunikorn-core/pull/106#discussion_r395784054
########## File path: README.md ########## @@ -1,37 +1,44 @@ -# YuniKorn - A Universal Scheduler +# Apache YuniKorn (incubating) - A Universal Scheduler  <img src="https://raw.githubusercontent.com/apache/incubator-yunikorn-core/master/docs/images/logo/yunikorn-logo-blue.png" width="200"> ---- -YuniKorn is a light-weighted, universal resource scheduler for container orchestrator systems. +Apache YuniKorn (incubating) is a light-weighted, universal resource scheduler for container orchestrator systems. It was created to achieve fine-grained resource sharing for various workloads efficiently on a large scale, multi-tenant, and cloud-native environment. YuniKorn brings a unified, cross-platform scheduling experience for mixed workloads consists -of stateless batch workloads and stateful services. Support for but not limited to, YARN and Kubernetes. +of stateless batch workloads and stateful services. + +YuniKorn now supports K8s and can be deployed as a custom K8s scheduler. YuniKorn's architecture design also allows adding different +shim layer and adopt to different ResourceManager implementation including Apache Hadoop YARN, or any other systems. ## Architecture Following chart illustrates the high-level architecture of YuniKorn. - + YuniKorn consists of the following components spread over multiple code repositories. - _Scheduler core_: the brain of the scheduler, which makes placement decisions (Allocate container X on node Y) according to pre configured policies. See more in current repo [yunikorn-core](https://github.com/apache/incubator-yunikorn-core). + _Scheduler core_ is written in GoLang and implemented in a way to be agnostic to scheduler implementation. Review comment: The reason I add this because many people confused and ask: is it copy of YARN scheduling code? I will add it to the top level. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
