Re: Should we remove Chinese documents
As a non-Chinese speaker I am leaving that decision to our Chinese speaking community members. Would be good to get some feedback on the following point: If the decision is to stop: do we remove current content or let it age out? Wilfred On Fri, 9 Feb 2024 at 17:59, Chia-Ping Tsai wrote: > > Dear all, > > We have a topic in slack > (https://yunikornworkspace.slack.com/archives/CL9CRJ1KM/p1707414644039739) to > discuss the future of Chinese documents. > > As a YK developer, I’d like to get rid of Chinese documents because it is > hard to make it up-to-date. Also, we ought to focus on other more important > features/fixes. > > As a (native) Chinese speaker, I’d like to get rid of Chinese documents > because the translation tools are good enough to help me to read the English > documents. Also, there are some native-Chinese developers in the YK > community, and hence I can have discussion with them by Chinese. > > As a YK committer, I’d like to see more feedbacks from the community before > making this difficult decision. Hence, PLEASE feel free to raise objection to > this proposal via mail or slack. > > > -- > Happy Lunar New Year > Chia-Ping Tsai (蔡嘉平) > - > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org > For additional commands, e-mail: dev-h...@yunikorn.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Closed] (YUNIKORN-1333) [webapp] Expose current user quota usage details
[ https://issues.apache.org/jira/browse/YUNIKORN-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg closed YUNIKORN-1333. --- > [webapp] Expose current user quota usage details > > > Key: YUNIKORN-1333 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1333 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: webapp >Reporter: Manikandan R >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
Should we remove Chinese documents
Dear all, We have a topic in slack (https://yunikornworkspace.slack.com/archives/CL9CRJ1KM/p1707414644039739) to discuss the future of Chinese documents. As a YK developer, I’d like to get rid of Chinese documents because it is hard to make it up-to-date. Also, we ought to focus on other more important features/fixes. As a (native) Chinese speaker, I’d like to get rid of Chinese documents because the translation tools are good enough to help me to read the English documents. Also, there are some native-Chinese developers in the YK community, and hence I can have discussion with them by Chinese. As a YK committer, I’d like to see more feedbacks from the community before making this difficult decision. Hence, PLEASE feel free to raise objection to this proposal via mail or slack. -- Happy Lunar New Year Chia-Ping Tsai (蔡嘉平) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1333) [webapp] Expose current user quota usage details
[ https://issues.apache.org/jira/browse/YUNIKORN-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YUNIKORN-1333. - Target Version: (was: 1.5.0) Resolution: Duplicate Resolving as duplicate in favour of new Jira with a lot of history and discussion. > [webapp] Expose current user quota usage details > > > Key: YUNIKORN-1333 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1333 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: webapp >Reporter: Manikandan R >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2382) Expose K8s supported versions on web
[ https://issues.apache.org/jira/browse/YUNIKORN-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved YUNIKORN-2382. -- Fix Version/s: 1.5.0 Resolution: Fixed > Expose K8s supported versions on web > > > Key: YUNIKORN-2382 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2382 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Critical > Labels: newbie, pull-request-available > Fix For: 1.5.0 > > > The gh-pages branch of yunikorn-release has a list of supported versions for > K8s per YuniKorn release. > This details should be exposed as part of the website. > * gh-pages branch in release repo: index.md file > * add 1.29.x: Supported from version 1.5.0 > Update the README.md in the helm chart with up to date information. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-2400) Upgrade docusaurus to 3.x
Wilfred Spiegelenburg created YUNIKORN-2400: --- Summary: Upgrade docusaurus to 3.x Key: YUNIKORN-2400 URL: https://issues.apache.org/jira/browse/YUNIKORN-2400 Project: Apache YuniKorn Issue Type: Improvement Components: website Reporter: Wilfred Spiegelenburg Docusaurus has released a major version update with updated dependencies. There are a lot of breaking changes in v3 and we need to follow the upgrade guide as things will most likely break: [https://docusaurus.io/docs/migration/v3] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2393) Upgrade codecov/codecov-action to v4
[
https://issues.apache.org/jira/browse/YUNIKORN-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-2393.
-
Fix Version/s: 1.5.0
Resolution: Fixed
Token has been added to all 3 repos, master pushes upload coverage files.
Thank you for the improvement.
> Upgrade codecov/codecov-action to v4
>
>
> Key: YUNIKORN-2393
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2393
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - common, shim - kubernetes, webapp
>Reporter: Yu-Lin Chen
>Assignee: Yu-Lin Chen
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> codecov/codecov-action@v4 was
> [released|https://github.com/codecov/codecov-action/releases] on 2024/01/31.
> The workaround change to support Node.js 20 in v3 was reverted on 2024/01/31.
> ([v3 commits|https://github.com/codecov/codecov-action/commits/v3/])
> We should update codecov/codecov-action from v3 to v4 to surpress below
> warning message in GitHub action workflow:
> {code:json}
> Node.js 16 actions are deprecated. Please update the following actions to use
> Node.js 20: codecov/codecov-action@v3. For more information see:
> https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2392) Concurrent map write in SchedulerCache
[
https://issues.apache.org/jira/browse/YUNIKORN-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-2392.
-
Fix Version/s: 1.5.0
Resolution: Fixed
change committed
> Concurrent map write in SchedulerCache
> --
>
> Key: YUNIKORN-2392
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2392
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
>Reporter: Peter Bacsko
>Assignee: Craig Condit
>Priority: Critical
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> While running the simple performance test with MockScheduler, the following
> error was detected:
> {noformat}
> fatal error: concurrent map writes
> goroutine 16 [running]:
> github.com/apache/yunikorn-k8shim/pkg/cache/external.(*SchedulerCache).removeSchedulingTask(0xc0004261e0,
> {0xc00d6be600?, 0xc00d6be600?})
>
> /home/bacskop/repos/yunikorn-k8shim/pkg/cache/external/scheduler_cache.go:593
> +0x45
> github.com/apache/yunikorn-k8shim/pkg/cache/external.(*SchedulerCache).updatePod(0xc0004261e0,
> 0xc034a96900)
>
> /home/bacskop/repos/yunikorn-k8shim/pkg/cache/external/scheduler_cache.go:511
> +0x8d1
> github.com/apache/yunikorn-k8shim/pkg/cache/external.(*SchedulerCache).UpdatePod(0xc0004261e0,
> 0x1a?)
>
> /home/bacskop/repos/yunikorn-k8shim/pkg/cache/external/scheduler_cache.go:468
> +0xba
> github.com/apache/yunikorn-k8shim/pkg/cache.(*Context).updateYuniKornPod(0xc00012a090,
> 0xc034a96900)
> /home/bacskop/repos/yunikorn-k8shim/pkg/cache/context.go:306 +0x285
> github.com/apache/yunikorn-k8shim/pkg/cache.(*Context).UpdatePod(0xc00012a090,
> {0xc0001da060?, 0xc0001da120?}, {0x1f92940?, 0xc034a96900?})
> /home/bacskop/repos/yunikorn-k8shim/pkg/cache/context.go:288 +0x2b9
> k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnUpdate(...)
>
> /home/bacskop/go/pkg/mod/k8s.io/client-go@v0.29.1/tools/cache/controller.go:246
> github.com/apache/yunikorn-k8shim/pkg/client.(*MockedAPIProvider).RunEventHandler.func1()
> /home/bacskop/repos/yunikorn-k8shim/pkg/client/apifactory_mock.go:284
> +0x5da
> created by
> github.com/apache/yunikorn-k8shim/pkg/client.(*MockedAPIProvider).RunEventHandler
> in goroutine 13
> /home/bacskop/repos/yunikorn-k8shim/pkg/client/apifactory_mock.go:240
> +0xda
> {noformat}
> We need locking inside {{{}SchedulerCache.addSchedulingTask(){}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Reopened] (YUNIKORN-2191) Remove column "partition" from Nodes web page
[ https://issues.apache.org/jira/browse/YUNIKORN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit reopened YUNIKORN-2191: > Remove column "partition" from Nodes web page > - > > Key: YUNIKORN-2191 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2191 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Chia-Ping Tsai >Assignee: JiaChi Wang >Priority: Trivial > Labels: pull-request-available, web > Fix For: 1.5.0 > > Attachments: after_remove_partition_col.png, origin.png, 截圖 > 2023-11-25 晚上9.32.11.png > > > It seems to me the column "partition" is useless. the nodes listed by this > page must belong to a specified partition, so the column "partition" is > redundant. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Reopened] (YUNIKORN-2195) Add Yarn install in Yunikorn web README
[ https://issues.apache.org/jira/browse/YUNIKORN-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit reopened YUNIKORN-2195: > Add Yarn install in Yunikorn web README > > > Key: YUNIKORN-2195 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2195 > Project: Apache YuniKorn > Issue Type: Improvement > Components: deployment >Reporter: Dong-Lin Hsieh >Assignee: Dong-Lin Hsieh >Priority: Minor > Labels: pull-request-available > Fix For: 1.5.0 > > > Add Yarn install in Yunikorn web README -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2191) Remove column "partition" from Nodes web page
[ https://issues.apache.org/jira/browse/YUNIKORN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit resolved YUNIKORN-2191. Resolution: Fixed > Remove column "partition" from Nodes web page > - > > Key: YUNIKORN-2191 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2191 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Chia-Ping Tsai >Assignee: JiaChi Wang >Priority: Trivial > Labels: pull-request-available, web > Fix For: 1.5.0 > > Attachments: after_remove_partition_col.png, origin.png, 截圖 > 2023-11-25 晚上9.32.11.png > > > It seems to me the column "partition" is useless. the nodes listed by this > page must belong to a specified partition, so the column "partition" is > redundant. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2195) Add Yarn install in Yunikorn web README
[ https://issues.apache.org/jira/browse/YUNIKORN-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit resolved YUNIKORN-2195. Resolution: Fixed > Add Yarn install in Yunikorn web README > > > Key: YUNIKORN-2195 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2195 > Project: Apache YuniKorn > Issue Type: Improvement > Components: deployment >Reporter: Dong-Lin Hsieh >Assignee: Dong-Lin Hsieh >Priority: Minor > Labels: pull-request-available > Fix For: 1.5.0 > > > Add Yarn install in Yunikorn web README -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-2088) [umbrella] Node utilisation chart per partition and resource type
[ https://issues.apache.org/jira/browse/YUNIKORN-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit resolved YUNIKORN-2088. Resolution: Fixed Switching from 'closed' to 'resolved' for proper release tracking. > [umbrella] Node utilisation chart per partition and resource type > - > > Key: YUNIKORN-2088 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2088 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - common, webapp >Reporter: Wilfred Spiegelenburg >Assignee: Yu-Lin Chen >Priority: Major > Fix For: 1.5.0 > > Attachments: Add margin-top to Node Resource Utilization chart .png, > demo for new hovering behavior.gif, 截圖 2024-02-04 凌晨4.03.36.png > > > Node utilisation is calculated based on a resource name. The bar chart can > only show one resource. The optimal solution would be to allow selecting a > resource to show in the bar chart via a drop down or show all resource types. > Also need to look at the placing of the chart: the dashboard shows data not > linked to a partition we should consider moving the diagram to the nodes page > which is partition based to provide a better view. > This is a major change of REST objects, endpoints etc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Reopened] (YUNIKORN-2088) [umbrella] Node utilisation chart per partition and resource type
[ https://issues.apache.org/jira/browse/YUNIKORN-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit reopened YUNIKORN-2088: > [umbrella] Node utilisation chart per partition and resource type > - > > Key: YUNIKORN-2088 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2088 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - common, webapp >Reporter: Wilfred Spiegelenburg >Assignee: Yu-Lin Chen >Priority: Major > Fix For: 1.5.0 > > Attachments: Add margin-top to Node Resource Utilization chart .png, > demo for new hovering behavior.gif, 截圖 2024-02-04 凌晨4.03.36.png > > > Node utilisation is calculated based on a resource name. The bar chart can > only show one resource. The optimal solution would be to allow selecting a > resource to show in the bar chart via a drop down or show all resource types. > Also need to look at the placing of the chart: the dashboard shows data not > linked to a partition we should consider moving the diagram to the nodes page > which is partition based to provide a better view. > This is a major change of REST objects, endpoints etc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Closed] (YUNIKORN-2088) [umbrella] Node utilisation chart per partition and resource type
[ https://issues.apache.org/jira/browse/YUNIKORN-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu-Lin Chen closed YUNIKORN-2088. - Fix Version/s: 1.5.0 Resolution: Resolved Close it since all the sub-tasks are done. Thanks to all the reviewers. > [umbrella] Node utilisation chart per partition and resource type > - > > Key: YUNIKORN-2088 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2088 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - common, webapp >Reporter: Wilfred Spiegelenburg >Assignee: Yu-Lin Chen >Priority: Major > Fix For: 1.5.0 > > Attachments: Add margin-top to Node Resource Utilization chart .png, > demo for new hovering behavior.gif, 截圖 2024-02-04 凌晨4.03.36.png > > > Node utilisation is calculated based on a resource name. The bar chart can > only show one resource. The optimal solution would be to allow selecting a > resource to show in the bar chart via a drop down or show all resource types. > Also need to look at the placing of the chart: the dashboard shows data not > linked to a partition we should consider moving the diagram to the nodes page > which is partition based to provide a better view. > This is a major change of REST objects, endpoints etc -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
