commit | f7b1d524d628a0bbb604dfcccf0e678dae86b7d2 | [log] [tgz] |
---|---|---|
author | Ryan Lo <lowc1012@gmail.com> | Wed Sep 14 12:24:52 2022 +1000 |
committer | Wilfred Spiegelenburg <wilfreds@apache.org> | Wed Sep 14 12:24:52 2022 +1000 |
tree | fd92c872e9eea2ce62a598cc73d4a322e744e392 | |
parent | 3e6942ff41a99c0a0f788074cdceebeea90c8230 [diff] |
[YUNIKORN-1086] expose reservation in node rest response (#436) The reservations details are exposed in the node object. A flag to show if the node is reserved and a list of reservations keys. The reservation key is the application ID and allocation ID separated by a pipe symbol "|" Closes: #436 Signed-off-by: Wilfred Spiegelenburg <wilfreds@apache.org>
Apache YuniKorn is a light-weight, universal resource scheduler for container orchestrator systems. It is 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 that consist 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.
See how to get started with running YuniKorn on Kubernetes, please read the documentation on yunikorn.apache.org.
Want to know more about the value of the YuniKorn project, and what YuniKorn can do? Here is some session recordings and demos.
Please read get involved document if you want to discuss issues, contribute your ideas, explore use cases, or participate the development.
If you want to contribute code to this repo, please read the developer doc. All the design docs are available here.
Apache YuniKorn project has the following git repositories:
The yunikorn-core
is the brain of the scheduler, which makes placement decisions (allocate container X on node Y) according to the builtin rich scheduling policies. Scheduler core implementation is agnostic to the underneath resource manager system.