YuniKorn Concepts

Internal

• YuniKorn

Resource Manager (RM)

YuniKorn communicates with various implementation of resource management systems (Kubernetes, YARN) via a standard interface defined in the yunikorn-scheduler-interface package.

Allocation

A core scheduler-level concept. An allocation can be in one of two states ("Pending" and "In-Progress"). A pending allocation is one which has been decided upon by YuniKorn but has not yet been communicated to the default scheduler via PreFilter()/Filter(). Once PreFilter()/Filter() pass, the allocation transitions to "In-Progress" to signify that the default scheduler is responsible for fulfilling the allocation. Once PostBind() is called in the plugin to signify completion of the allocation, it is removed.

Application

Application Metadata

Application ID

Looks in this order:

• Annotation "yunikorn.apache.org/app-id"
• Label "applicationId"
• ...

OwnerReference

Usually a pod, designated by its UID.

Application Task

For the Kubernetes implementations, Kubernetes pods are mapped onto YuniKorn Core Tasks, and the task ID is the pod UID.

A task may be the "originator" of the Application, if it's the first one seen for the application. If that is the case, it is considered "first pod"/"owner"/"driver".

Task Metadata

TaskID

(same as the Pod ID)

Node

Can a node be declared to be part of a partition with the "si/node-partition" label? It seems that the node Attributes partially come from the node labels.

Context

yunikorn-k8shim cache.Context

Queue

A namespace can have a "queue" if annotated with "yunikorn.apache.org/queue".

A namespace can have a "parent queue" is annotated with "yunikorn.apache.org/parentqueue".