YuniKorn Development: Difference between revisions
Jump to navigation
Jump to search
| Line 40: | Line 40: | ||
Implementation Notes: | Implementation Notes: | ||
* After a "task" allocation ask is successfully handled by the core scheduler and a node is found for it, the actual binding of the Kubernetes Pod to Node is handled in <code>cache.Task#postTaskAllocated()</code>. | * After a "task" allocation ask is successfully handled by the core scheduler and a node is found for it, the actual binding of the Kubernetes Pod to Node is handled in <code>cache.Task#postTaskAllocated()</code>.The binding is done by: | ||
<syntaxhighlight lang='go'> | |||
... | |||
task.context.apiProvider.GetAPIs().KubeClient.Bind(task.pod, task.nodeName) | |||
... | |||
</syntaxhighlight> | |||
==<tt></tt>== | ==<tt></tt>== | ||
==<tt></tt>== | ==<tt></tt>== | ||
Revision as of 00:18, 21 December 2023
External
- GitHub yunikorn-core https://github.com/apache/yunikorn-core
- GitHub yunikorn-k8shim https://github.com/ovidiuf/yunikorn-k8shim
Internal
Overview
yunikorn-scheduler-interface ↑ yunikorn-core ↑ yunikorn-k8shim yunikorn-web yunikorn-release yunikorn-site
Development Environment Setup
Build and Run
Debugger Setup
Packages
yunikorn-scheduler-interface
yunikorn-k8shim
Implementation Notes:
- After a "task" allocation ask is successfully handled by the core scheduler and a node is found for it, the actual binding of the Kubernetes Pod to Node is handled in
cache.Task#postTaskAllocated().The binding is done by:
...
task.context.apiProvider.GetAPIs().KubeClient.Bind(task.pod, task.nodeName)
...
Status
The attempt to build the executable on Mac and cross-compile for linux/amd64 produced an executable that yields:
exec /yunikorn-scheduler: no such file or directory
in the container. Probably the format is not correct.