[
https://issues.apache.org/jira/browse/YUNIKORN-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187685#comment-17187685
]
Adam Antal commented on YUNIKORN-368:
-------------------------------------
The jenkins check also fails with the following error message:
{noformat}
go: vbom.ml/util@v0.0.0-20160121211510-db5cfe13f5cc: unrecognized import path
"vbom.ml/util" (https fetch: Get https://vbom.ml/util?go-get=1: dial tcp:
lookup vbom.ml on 169.254.169.254:53: no such host)
{noformat}
which is exactly the bug of YUNIKORN-389. That issue is blocking this right now.
> Pass namespace's parentQueue annotation to application tag
> ----------------------------------------------------------
>
> Key: YUNIKORN-368
> URL: https://issues.apache.org/jira/browse/YUNIKORN-368
> Project: Apache YuniKorn
> Issue Type: Task
> Components: shim - kubernetes
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Labels: pull-request-available
>
> We can implement a default application placement mechanism based on the
> annotation of the namespace. If shim could pass the
> {{yunikorn.apache.org/parentqueue}} annotation to the core as the
> "namespace.parentqueue" tag, that would enable YK administrator to implement
> this placement mechanism by configuring this placement rule:
> {code:yaml}
> placementrules:
> - name: tag
> value: namespace
> create: true
> parent:
> - name: tag
> value: namespace.parent
> create: true
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
