[
https://issues.apache.org/jira/browse/YUNIKORN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398860#comment-17398860
]
Weiwei Yang commented on YUNIKORN-22:
-------------------------------------
hi [~chia7712] you are correct. currently, the node registration from the shim
side is hard coded to use the "default" partition, so there is no
multi-partition support right now. however, the design allows us to enable the
multi-partition scenario if needed, which requires some code changes in the
shim side to register node by certain conditions, e.g labels or annotations,
etc. just like you said.
> k8shim is hardcoded to the default partition
> --------------------------------------------
>
> Key: YUNIKORN-22
> URL: https://issues.apache.org/jira/browse/YUNIKORN-22
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Priority: Major
>
> In the application and node code the partition is hardcoded to use the
> DefaultPartition constant when creating new objects:
> * application.NewApplication
> * schedulerNode.addExistingAllocation
> This means that in the configuration for the core we must have that same
> partition and that we currently would not be able to create a second shim for
> the same core as they would interfere with each other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
