[jira] [Created] (YUNIKORN-233) Change default number of items in datatable in yunikorn-web to 10

2020-06-19 Thread Akhil PB (Jira) 
Akhil PB created YUNIKORN-233:
-

 Summary: Change default number of items in datatable in 
yunikorn-web to 10
 Key: YUNIKORN-233
 URL: https://issues.apache.org/jira/browse/YUNIKORN-233
 Project: Apache YuniKorn
  Issue Type: Improvement
  Components: webapp
Reporter: Akhil PB
Assignee: Akhil PB






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

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Resolved] (YUNIKORN-160) release build on a fresh machine is failing

2020-06-19 Thread Akhil PB (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akhil PB resolved YUNIKORN-160.
---
Resolution: Not A Problem

> release build on a fresh machine is failing
> ---
>
> Key: YUNIKORN-160
> URL: https://issues.apache.org/jira/browse/YUNIKORN-160
> Project: Apache YuniKorn
>  Issue Type: Bug
>  Components: release
>Reporter: Sunil G
>Priority: Major
>
> While building ./build-docker-images.sh on a fresh machine, command is failing
> {code:java}
> Successfully tagged yunikorn/yunikorn-scheduler-admission-controller:latest
> /Users/sgovindan/Work/releases/yunikorn/0.8.0/apache-yunikorn-0.8.0-incubating-src
> yarn install && yarn build:prod
> /bin/sh: yarn: command not found
> make: *** [build-prod] Error 127 {code}
> Proposal:
>  # Its not good to install "yarn" locally with the node version which we have 
> in machine manages the web build process. In YARNUI2, i have seen this error 
> regularly that some non-compatible package breaks the build
>  # Its better to do all the build process in docker which will have a sane 
> version compatibility of all support s/w versions



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

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Resolved] (YUNIKORN-217) Update deployment api-version to a stable version for the scheduler and all examples

2020-06-19 Thread Weiwei Yang (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiwei Yang resolved YUNIKORN-217.
--
Fix Version/s: 0.9
   Resolution: Fixed

> Update deployment api-version to a stable version for the scheduler and all 
> examples
> 
>
> Key: YUNIKORN-217
> URL: https://issues.apache.org/jira/browse/YUNIKORN-217
> Project: Apache YuniKorn
>  Issue Type: Bug
>  Components: shim - kubernetes
>Reporter: Weiwei Yang
>Assignee: Kinga Marton
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.9
>
>
> Currently, the deployment api version is extensions/v1beta1, which is 
> deprecated now.
> We should replace this with apps/v1.



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

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Closed] (YUNIKORN-232) Send essential container scheduling state to shim as a supplementary info for autoscaling

2020-06-19 Thread Weiwei Yang (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiwei Yang closed YUNIKORN-232.

Resolution: Duplicate

> Send essential container scheduling state to shim as a supplementary info for 
> autoscaling 
> --
>
> Key: YUNIKORN-232
> URL: https://issues.apache.org/jira/browse/YUNIKORN-232
> Project: Apache YuniKorn
>  Issue Type: Improvement
>  Components: core - scheduler, scheduler-interface, shim - kubernetes
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Major
>  Labels: pull-request-available
>
> On cloud env, when partition resource (physical nodes) resource is not 
> enough, but YK still has enough capacity, we do want to trigger auto-scaling; 
> but if queue capacity is exceeded, we do not want to trigger auto-scaling.
> Introduce a scheduler plugin to send some supplementary info to the shim to 
> handle this accordingly.



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

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-232) Send essential container scheduling state to shim as a supplementary info for autoscaling

2020-06-19 Thread Weiwei Yang (Jira) 
Weiwei Yang created YUNIKORN-232:


 Summary: Send essential container scheduling state to shim as a 
supplementary info for autoscaling 
 Key: YUNIKORN-232
 URL: https://issues.apache.org/jira/browse/YUNIKORN-232
 Project: Apache YuniKorn
  Issue Type: Improvement
  Components: core - scheduler, scheduler-interface, shim - kubernetes
Reporter: Weiwei Yang
Assignee: Weiwei Yang


On cloud env, when partition resource (physical nodes) resource is not enough, 
but YK still has enough capacity, we do want to trigger auto-scaling; but if 
queue capacity is exceeded, we do not want to trigger auto-scaling.

Introduce a scheduler plugin to send some supplementary info to the shim to 
handle this accordingly.



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

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org