[jira] [Updated] (YUNIKORN-353) Disable version alert for older versions
[ https://issues.apache.org/jira/browse/YUNIKORN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-353: - Summary: Disable version alert for older versions (was: Disable version alert for non-latest versions) > Disable version alert for older versions > > > Key: YUNIKORN-353 > URL: https://issues.apache.org/jira/browse/YUNIKORN-353 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: website >Reporter: Weiwei Yang >Assignee: Weiwei Yang >Priority: Major > > Currently, for multi-version docs, there is an alert in each of the doc pages > says "This is the documentation for xxx, which is no longer actively > maintained." > This assumes there is only 1 active release, which is not good. -- 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
[jira] [Updated] (YUNIKORN-353) Disable version alert for non-latest versions
[ https://issues.apache.org/jira/browse/YUNIKORN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-353: - Summary: Disable version alert for non-latest versions (was: Disable version alert for versions) > Disable version alert for non-latest versions > - > > Key: YUNIKORN-353 > URL: https://issues.apache.org/jira/browse/YUNIKORN-353 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: website >Reporter: Weiwei Yang >Assignee: Weiwei Yang >Priority: Major > > Currently, for multi-version docs, there is an alert in each of the doc pages > says "This is the documentation for xxx, which is no longer actively > maintained." > This assumes there is only 1 active release, which is not good. -- 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
[jira] [Created] (YUNIKORN-353) Disable version alert for versions
Weiwei Yang created YUNIKORN-353: Summary: Disable version alert for versions Key: YUNIKORN-353 URL: https://issues.apache.org/jira/browse/YUNIKORN-353 Project: Apache YuniKorn Issue Type: Sub-task Components: website Reporter: Weiwei Yang Assignee: Weiwei Yang Currently, for multi-version docs, there is an alert in each of the doc pages says "This is the documentation for xxx, which is no longer actively maintained." This assumes there is only 1 active release, which is not good. -- 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
[jira] [Resolved] (YUNIKORN-283) Support query params to filter the apps using queue name/namespace for v1/apps endpoint
[
https://issues.apache.org/jira/browse/YUNIKORN-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang resolved YUNIKORN-283.
--
Fix Version/s: 0.10
Resolution: Fixed
Doc PR also merged. Thanks for getting this done [~maniraj...@gmail.com]. And
thanks for the review [~wilfreds].
> Support query params to filter the apps using queue name/namespace for
> v1/apps endpoint
> ---
>
> Key: YUNIKORN-283
> URL: https://issues.apache.org/jira/browse/YUNIKORN-283
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: webapp
>Reporter: Ayub Pathan
>Assignee: Manikandan R
>Priority: Critical
> Labels: pull-request-available
> Fix For: 0.10
>
>
> In an environment where there are multiple apps running at any point in time,
> there is no way to filter out the apps running on any particular queue. This
> Jira is add support for filtering the apps via query params, something like
> ??{{v1/apps?queue=spark-jobs..}}??
>
> The same can be extended for other end points as well. like
> /ws/v1/nodes,
> /ws/v1/queues etc...
--
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
[jira] [Updated] (YUNIKORN-349) Remove installCRD option during helm install for e2e test
[ https://issues.apache.org/jira/browse/YUNIKORN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-349: Labels: pull-request-available (was: ) > Remove installCRD option during helm install for e2e test > - > > Key: YUNIKORN-349 > URL: https://issues.apache.org/jira/browse/YUNIKORN-349 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: test - e2e >Reporter: Weiwei Yang >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > > Since this option has been removed by YUNIKONR-346, the following line can be > also removed: > https://github.com/apache/incubator-yunikorn-k8shim/blob/657c62c92687614bf4f089cfaff6b7f5a0db9ad8/scripts/run-e2e-tests.sh#L111 -- 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
[jira] [Assigned] (YUNIKORN-352) when child queue capacity greater than parent, the configmap update is rejected but not notified to end user
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang reassigned YUNIKORN-352:
Assignee: Wilfred Spiegelenburg
> when child queue capacity greater than parent, the configmap update is
> rejected but not notified to end user
>
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Assignee: Wilfred Spiegelenburg
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Updated] (YUNIKORN-352) when child queue capacity greater than parent, the configmap update is rejected but not notified to end user
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-352:
-
Summary: when child queue capacity greater than parent, the configmap
update is rejected but not notified to end user (was: Nested static queues
information is not returned by yunikorn, when child queue capacity greater than
parent, maybe rejected but not notified to end user)
> when child queue capacity greater than parent, the configmap update is
> rejected but not notified to end user
>
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Updated] (YUNIKORN-352) Nested static queues information is not returned by yunikorn, when child queue capacity greater than parent, maybe rejected but not notified to end user
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-352:
-
Summary: Nested static queues information is not returned by yunikorn, when
child queue capacity greater than parent, maybe rejected but not notified to
end user (was: Nested static queues information is not returned by yunikorn,
when child queue capacity greater than parent queue)
> Nested static queues information is not returned by yunikorn, when child
> queue capacity greater than parent, maybe rejected but not notified to end
> user
>
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Commented] (YUNIKORN-352) Nested static queues information is not returned by yunikorn
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172728#comment-17172728
]
Ayub Pathan commented on YUNIKORN-352:
--
The queue information is not shown because the child queue max capacity is
greater than parent queue capacity. The configuration update is rejected by
Yunikorn for this reason but there is no error or any kind of notification to
the end user.
[~cheersyang] / [~wilfreds] How can this be communicated to the end user?
validate-conf??
> Nested static queues information is not returned by yunikorn
>
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Updated] (YUNIKORN-352) Nested static queues information is not returned by yunikorn, when child queue capacity greater than parent queue
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-352:
-
Summary: Nested static queues information is not returned by yunikorn, when
child queue capacity greater than parent queue (was: Nested static queues
information is not returned by yunikorn)
> Nested static queues information is not returned by yunikorn, when child
> queue capacity greater than parent queue
> -
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Created] (YUNIKORN-352) Nested static queues information are not returned by yunikorn
Ayub Pathan created YUNIKORN-352:
Summary: Nested static queues information are not returned by
yunikorn
Key: YUNIKORN-352
URL: https://issues.apache.org/jira/browse/YUNIKORN-352
Project: Apache YuniKorn
Issue Type: Bug
Components: core - scheduler
Reporter: Ayub Pathan
Create a nested static queue like below.
{noformat}
partitions:
-
name: default
placementrules:
- name: tag
value: namespace
create: true
queues:
- name: root
submitacl: '*'
queues:
- name: queue2
resources:
guaranteed:
memory: 300
cpu: 300
max:
memory: 1000
cpu: 1000
queues:
- name: queue3
resources:
guaranteed:
memory: 300
cpu: 300
max:
memory: 2000
cpu: 2000
{noformat}
Validate the same through rest API /queues - queues3 is not even shown in the
response.
{noformat}
{
"capacity": {
"capacity": "map[attachable-volumes-aws-ebs:75
ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
pods:87 vcore:4875]",
"usedcapacity": "0"
},
"nodes": null,
"partitionName": "[mycluster]default",
"queues": {
"capacities": {
"absusedcapacity": "[memory:0 vcore:2]",
"capacity": "[]",
"maxcapacity": "[attachable-volumes-aws-ebs:75
ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
pods:87 vcore:4875]",
"usedcapacity": "[memory:1 vcore:110]"
},
"properties": {},
"queuename": "root",
"queues": [
{
"capacities": {
"absusedcapacity": "[]",
"capacity": "[]",
"maxcapacity": "[]",
"usedcapacity": "[memory:1]"
},
"properties": {},
"queuename": "monitoring",
"queues": null,
"status": "Active"
},
{
"capacities": {
"absusedcapacity": "[]",
"capacity": "[]",
"maxcapacity": "[]",
"usedcapacity": "[vcore:110]"
},
"properties": {},
"queuename": "kube-system",
"queues": null,
"status": "Active"
},
{
"capacities": {
"absusedcapacity": "[]",
"capacity": "[cpu:300 memory:300]",
"maxcapacity": "[cpu:1000 memory:1000]",
"usedcapacity": "[]"
},
"properties": {},
"queuename": "queue2",
"queues": null,
"status": "Active"
}
],
"status": "Active"
}
}
{noformat}
--
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
[jira] [Updated] (YUNIKORN-352) Nested static queues information is not returned by yunikorn
[
https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-352:
-
Summary: Nested static queues information is not returned by yunikorn
(was: Nested static queues information are not returned by yunikorn)
> Nested static queues information is not returned by yunikorn
>
>
> Key: YUNIKORN-352
> URL: https://issues.apache.org/jira/browse/YUNIKORN-352
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> Create a nested static queue like below.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: queue2
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 1000
> cpu: 1000
> queues:
> - name: queue3
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2000
> cpu: 2000
> {noformat}
> Validate the same through rest API /queues - queues3 is not even shown in the
> response.
> {noformat}
> {
> "capacity": {
> "capacity": "map[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "0"
> },
> "nodes": null,
> "partitionName": "[mycluster]default",
> "queues": {
> "capacities": {
> "absusedcapacity": "[memory:0 vcore:2]",
> "capacity": "[]",
> "maxcapacity": "[attachable-volumes-aws-ebs:75
> ephemeral-storage:94992122100 hugepages-1Gi:0 hugepages-2Mi:0 memory:18966
> pods:87 vcore:4875]",
> "usedcapacity": "[memory:1 vcore:110]"
> },
> "properties": {},
> "queuename": "root",
> "queues": [
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[memory:1]"
> },
> "properties": {},
> "queuename": "monitoring",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[]",
> "maxcapacity": "[]",
> "usedcapacity": "[vcore:110]"
> },
> "properties": {},
> "queuename": "kube-system",
> "queues": null,
> "status": "Active"
> },
> {
> "capacities": {
> "absusedcapacity": "[]",
> "capacity": "[cpu:300 memory:300]",
> "maxcapacity": "[cpu:1000 memory:1000]",
> "usedcapacity": "[]"
> },
> "properties": {},
> "queuename": "queue2",
> "queues": null,
> "status": "Active"
> }
> ],
> "status": "Active"
> }
> }
> {noformat}
--
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
[jira] [Updated] (YUNIKORN-351) Support validate conf to reject the config with 2 top level queues
[
https://issues.apache.org/jira/browse/YUNIKORN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-351:
-
Summary: Support validate conf to reject the config with 2 top level queues
(was: Add validate conf to reject the config with 2 top level queues)
> Support validate conf to reject the config with 2 top level queues
> --
>
> Key: YUNIKORN-351
> URL: https://issues.apache.org/jira/browse/YUNIKORN-351
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> admission controller should reject the config with 2 top level queues..
> something like below.
> {noformat}
> queues.yaml:
>
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> - name: queue1
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2024
> cpu: 2000
> {noformat}
> YK reads this config and creates the queue1 as child to the first top level
> queue.
--
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
[jira] [Updated] (YUNIKORN-351) Add validate conf to reject the config with 2 top level queues
[
https://issues.apache.org/jira/browse/YUNIKORN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated YUNIKORN-351:
-
Summary: Add validate conf to reject the config with 2 top level queues
(was: admission controller should reject the config with 2 top level queues)
> Add validate conf to reject the config with 2 top level queues
> --
>
> Key: YUNIKORN-351
> URL: https://issues.apache.org/jira/browse/YUNIKORN-351
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Ayub Pathan
>Priority: Critical
>
> admission controller should reject the config with 2 top level queues..
> something like below.
> {noformat}
> queues.yaml:
>
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> - name: queue1
> resources:
> guaranteed:
> memory: 300
> cpu: 300
> max:
> memory: 2024
> cpu: 2000
> {noformat}
> YK reads this config and creates the queue1 as child to the first top level
> queue.
--
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
[jira] [Created] (YUNIKORN-351) admission controller should reject the config with 2 top level queues
Ayub Pathan created YUNIKORN-351:
Summary: admission controller should reject the config with 2 top
level queues
Key: YUNIKORN-351
URL: https://issues.apache.org/jira/browse/YUNIKORN-351
Project: Apache YuniKorn
Issue Type: Bug
Components: core - scheduler
Reporter: Ayub Pathan
admission controller should reject the config with 2 top level queues..
something like below.
{noformat}
queues.yaml:
partitions:
-
name: default
placementrules:
- name: tag
value: namespace
create: true
queues:
- name: root
submitacl: '*'
- name: queue1
resources:
guaranteed:
memory: 300
cpu: 300
max:
memory: 2024
cpu: 2000
{noformat}
YK reads this config and creates the queue1 as child to the first top level
queue.
--
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
[jira] [Resolved] (YUNIKORN-322) Add Help pop-up window
[ https://issues.apache.org/jira/browse/YUNIKORN-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YUNIKORN-322. --- Resolution: Fixed This is implemented in YUNIKORN-350. > Add Help pop-up window > -- > > Key: YUNIKORN-322 > URL: https://issues.apache.org/jira/browse/YUNIKORN-322 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: webapp >Reporter: Weiwei Yang >Assignee: Akhil PB >Priority: Major > > Suggest to add a "Help" button at the side-bar, and by clicking that, it pops > up a window with the following content: > * Understand more about Apache YuniKorn (link to yunikorn.apache.org) > * Get help by reading docs: link to our documents in web-site > * Watch demos: (link to yunikorn demos) > * Ask questions by sending an email or ask questions in slack channel -- 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
[jira] [Updated] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-350: Labels: pull-request-available (was: ) > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Labels: pull-request-available > -- 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
[jira] [Updated] (YUNIKORN-322) Add Help pop-up window
[ https://issues.apache.org/jira/browse/YUNIKORN-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YUNIKORN-322: -- Target Version: 0.10 > Add Help pop-up window > -- > > Key: YUNIKORN-322 > URL: https://issues.apache.org/jira/browse/YUNIKORN-322 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: webapp >Reporter: Weiwei Yang >Assignee: Akhil PB >Priority: Major > > Suggest to add a "Help" button at the side-bar, and by clicking that, it pops > up a window with the following content: > * Understand more about Apache YuniKorn (link to yunikorn.apache.org) > * Get help by reading docs: link to our documents in web-site > * Watch demos: (link to yunikorn demos) > * Ask questions by sending an email or ask questions in slack channel -- 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
[jira] [Updated] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YUNIKORN-350: -- Fix Version/s: 0.10 > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Fix For: 0.10 > > -- 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
[jira] [Updated] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YUNIKORN-350: -- Fix Version/s: (was: 0.10) > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > -- 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
[jira] [Updated] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YUNIKORN-350: -- Target Version: 0.10 > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Fix For: 0.10 > > -- 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
[jira] [Created] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
Akhil PB created YUNIKORN-350: - Summary: Implement the revamped ux for yunikorn-web Key: YUNIKORN-350 URL: https://issues.apache.org/jira/browse/YUNIKORN-350 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Akhil PB Assignee: Akhil PB -- 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
[jira] [Commented] (YUNIKORN-346) Register the CRD programatically if it is turned on
[ https://issues.apache.org/jira/browse/YUNIKORN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172580#comment-17172580 ] Weiwei Yang commented on YUNIKORN-346: -- Thanks [~kmarton], [~Huang Ting Yao]. PR merged. Marked this one as done. [~kmarton], as a follow-up, can we update the helm chart helm package as well? And [~Huang Ting Yao], we need to remove this option in the e2e test as well. Opened https://issues.apache.org/jira/browse/YUNIKORN-349 for this. > Register the CRD programatically if it is turned on > > > Key: YUNIKORN-346 > URL: https://issues.apache.org/jira/browse/YUNIKORN-346 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > > Right now there are 2 places where we can enable the CRD: in the > schedulerconfig and in the helm chart. It is very easy to forget to turn on > on one of the places, so I suggest to register the CRD programatically if it > is not registered and it is turned on via the config. -- 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
[jira] [Created] (YUNIKORN-349) Remove installCRD option during helm install for e2e test
Weiwei Yang created YUNIKORN-349: Summary: Remove installCRD option during helm install for e2e test Key: YUNIKORN-349 URL: https://issues.apache.org/jira/browse/YUNIKORN-349 Project: Apache YuniKorn Issue Type: Sub-task Components: test - e2e Reporter: Weiwei Yang Assignee: Ting Yao,Huang Since this option has been removed by YUNIKONR-346, the following line can be also removed: https://github.com/apache/incubator-yunikorn-k8shim/blob/657c62c92687614bf4f089cfaff6b7f5a0db9ad8/scripts/run-e2e-tests.sh#L111 -- 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
[jira] [Resolved] (YUNIKORN-346) Register the CRD programatically if it is turned on
[ https://issues.apache.org/jira/browse/YUNIKORN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-346. -- Fix Version/s: 0.10 Resolution: Fixed > Register the CRD programatically if it is turned on > > > Key: YUNIKORN-346 > URL: https://issues.apache.org/jira/browse/YUNIKORN-346 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > Fix For: 0.10 > > > Right now there are 2 places where we can enable the CRD: in the > schedulerconfig and in the helm chart. It is very easy to forget to turn on > on one of the places, so I suggest to register the CRD programatically if it > is not registered and it is turned on via the config. -- 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
[jira] [Commented] (YUNIKORN-311) Code coverage is not updating for the core builds
[ https://issues.apache.org/jira/browse/YUNIKORN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172394#comment-17172394 ] Adam Antal commented on YUNIKORN-311: - Codecov reports are back. Closing this. > Code coverage is not updating for the core builds > -- > > Key: YUNIKORN-311 > URL: https://issues.apache.org/jira/browse/YUNIKORN-311 > Project: Apache YuniKorn > Issue Type: Bug > Components: build, core - scheduler >Affects Versions: 0.9 >Reporter: Wilfred Spiegelenburg >Assignee: Adam Antal >Priority: Critical > Labels: pull-request-available > > Code coverage is a important phase in CI/CD, but we are missing the report > now. > Not sure when and how this happens, but in the past, we were able to see the > report published to each PR. > https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/Makefile#L81 > this is supposed to generate the coverage txt, and this > https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/.travis.yml#L42 > is supposed to do the reporting. -- 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
[jira] [Resolved] (YUNIKORN-311) Code coverage is not updating for the core builds
[ https://issues.apache.org/jira/browse/YUNIKORN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal resolved YUNIKORN-311. - Resolution: Fixed > Code coverage is not updating for the core builds > -- > > Key: YUNIKORN-311 > URL: https://issues.apache.org/jira/browse/YUNIKORN-311 > Project: Apache YuniKorn > Issue Type: Bug > Components: build, core - scheduler >Affects Versions: 0.9 >Reporter: Wilfred Spiegelenburg >Assignee: Adam Antal >Priority: Critical > Labels: pull-request-available > > Code coverage is a important phase in CI/CD, but we are missing the report > now. > Not sure when and how this happens, but in the past, we were able to see the > report published to each PR. > https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/Makefile#L81 > this is supposed to generate the coverage txt, and this > https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/.travis.yml#L42 > is supposed to do the reporting. -- 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
[jira] [Updated] (YUNIKORN-346) Register the CRD programatically if it is turned on
[ https://issues.apache.org/jira/browse/YUNIKORN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-346: Labels: pull-request-available (was: ) > Register the CRD programatically if it is turned on > > > Key: YUNIKORN-346 > URL: https://issues.apache.org/jira/browse/YUNIKORN-346 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > > Right now there are 2 places where we can enable the CRD: in the > schedulerconfig and in the helm chart. It is very easy to forget to turn on > on one of the places, so I suggest to register the CRD programatically if it > is not registered and it is turned on via the config. -- 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
[jira] [Assigned] (YUNIKORN-346) Register the CRD programatically if it is turned on
[ https://issues.apache.org/jira/browse/YUNIKORN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ting Yao,Huang reassigned YUNIKORN-346: --- Assignee: Ting Yao,Huang > Register the CRD programatically if it is turned on > > > Key: YUNIKORN-346 > URL: https://issues.apache.org/jira/browse/YUNIKORN-346 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Ting Yao,Huang >Priority: Major > > Right now there are 2 places where we can enable the CRD: in the > schedulerconfig and in the helm chart. It is very easy to forget to turn on > on one of the places, so I suggest to register the CRD programatically if it > is not registered and it is turned on via the config. -- 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
[jira] [Commented] (YUNIKORN-346) Register the CRD programatically if it is turned on
[ https://issues.apache.org/jira/browse/YUNIKORN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172095#comment-17172095 ] Kinga Marton commented on YUNIKORN-346: --- I had a short with [~wwei] related this issue and we came to the conclusion that we don't need to register programatically, but we should remove the config option from the helm chart, so the CRD will be registered in every case. > Register the CRD programatically if it is turned on > > > Key: YUNIKORN-346 > URL: https://issues.apache.org/jira/browse/YUNIKORN-346 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Priority: Major > > Right now there are 2 places where we can enable the CRD: in the > schedulerconfig and in the helm chart. It is very easy to forget to turn on > on one of the places, so I suggest to register the CRD programatically if it > is not registered and it is turned on via the config. -- 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
