You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2020/08/26 13:11:00 UTC

[jira] [Commented] (YUNIKORN-343) Provide a placement rule that can support attaching NSs to parent queue

    [ https://issues.apache.org/jira/browse/YUNIKORN-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185179#comment-17185179 ] 

Wilfred Spiegelenburg commented on YUNIKORN-343:
------------------------------------------------

The preferred way to configure YuniKorn with the following existing placement rules:
{code:java}
placement:   
  - name: tag
    value: namespace
    create: true
    parent:        
      - name: tag
        value: parentqueue
        create: false
{code}
The parent queue annotation should be on the namespace object. That links a namespace to a specific parent queue. The core does not know the namespace and should not know what a namespace is either. It must stay deployment agnostic. We should follow the same method as we do for the name space resource quota. The two things are closely linked.

The quota is added to each application in the shim code via: Context.AddApplication() That should be the location to hook in for the parent queue too. We pull the quota out of the name space via the utility method: utils.GetNamespaceQuotaFromAnnotation(namespaceObj) We should replicate that behaviour for the parent queue tag.

In the same way we can pull the parent queue annotation out and add is as a tag to the application. The tag can have any name on the application. As long as that tag we choose is lined up with the tag proposed in the config we are OK. If we want to map that annotation to a simpler tag we can do that in the shim.

This means that the code change is on the shim side and not the core side
* shim must process all annotations and add the tags to the application object
* everything needs to be based on the application tags in the core

> Provide a placement rule that can support attaching NSs to parent queue
> -----------------------------------------------------------------------
>
>                 Key: YUNIKORN-343
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-343
>             Project: Apache YuniKorn
>          Issue Type: Task
>          Components: core - scheduler
>            Reporter: Adam Antal
>            Assignee: Adam Antal
>            Priority: Critical
>              Labels: pull-request-available
>
> Let's have a placement rule that can support attaching NSs to parent queues (currently we only have rule to do 1:1 namespace:queue mapping).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org