[jira] [Commented] (YUNIKORN-914) Prepare an abstract of talk for YuniKorn meetup in Nov 2021
[ https://issues.apache.org/jira/browse/YUNIKORN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434103#comment-17434103 ] Weiwei Yang commented on YUNIKORN-914: -- Thank you [~chenya_zhang] for creating this to track. [~wilfreds], can you pls write up an abstract and share it with us ASAP? We need this in order to create a meeting schedule on Google calendar, spread messages on social media.. etc. Thanks a lot. > Prepare an abstract of talk for YuniKorn meetup in Nov 2021 > --- > > Key: YUNIKORN-914 > URL: https://issues.apache.org/jira/browse/YUNIKORN-914 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: community >Reporter: Chenya Zhang >Assignee: Wilfred Spiegelenburg >Priority: Major > > An abstract of 200 - 300 words for the talk which could share about features > in the latest release, Gang scheduling, bin packing, node sorting > improvement, etc. > It will be used to post on YuniKorn website, LinkedIn, Twitter, etc. to > broadcast the upcoming event. -- 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-625) Use v1 for CertificateSigningRequest instead of v1beta1
[ https://issues.apache.org/jira/browse/YUNIKORN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu updated YUNIKORN-625: Fix Version/s: 1.0.0 > Use v1 for CertificateSigningRequest instead of v1beta1 > --- > > Key: YUNIKORN-625 > URL: https://issues.apache.org/jira/browse/YUNIKORN-625 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > Starting from Kubernetes v. 1.19 the CertificateSigningRequest API is > promoted to certificates.k8s.io/v1 with the following changes: > * spec.signerName is now required, and requests for > kubernetes.io/legacy-unknown are not allowed to be created via the > certificates.k8s.io/v1 API > * spec.usages is now required, may not contain duplicate values, and must > only contain known usages > * status.conditions may not contain duplicate types > * status.conditions[*].status is now required > * status.certificate must be PEM-encoded, and contain only CERTIFICATE > blocks (#91685, @liggitt) [SIG API Machinery, Architecture, Auth, CLI and > Testing] > See more details at: > https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.19.md -- 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-625) Use v1 for CertificateSigningRequest instead of v1beta1
[ https://issues.apache.org/jira/browse/YUNIKORN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-625. - Resolution: Done > Use v1 for CertificateSigningRequest instead of v1beta1 > --- > > Key: YUNIKORN-625 > URL: https://issues.apache.org/jira/browse/YUNIKORN-625 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > Starting from Kubernetes v. 1.19 the CertificateSigningRequest API is > promoted to certificates.k8s.io/v1 with the following changes: > * spec.signerName is now required, and requests for > kubernetes.io/legacy-unknown are not allowed to be created via the > certificates.k8s.io/v1 API > * spec.usages is now required, may not contain duplicate values, and must > only contain known usages > * status.conditions may not contain duplicate types > * status.conditions[*].status is now required > * status.certificate must be PEM-encoded, and contain only CERTIFICATE > blocks (#91685, @liggitt) [SIG API Machinery, Architecture, Auth, CLI and > Testing] > See more details at: > https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.19.md -- 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-920) Fix scheduling latency metrics
Weiwei Yang created YUNIKORN-920: Summary: Fix scheduling latency metrics Key: YUNIKORN-920 URL: https://issues.apache.org/jira/browse/YUNIKORN-920 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Weiwei Yang The scheduling latency is not recorded correctly, it is smaller than actual values. Because not every scheduling cycle will generate allocations, when the cycle could not generate an allocation and it skips most of the steps, in that case, the latency is almost 0. We should only track the latency when there is actually an allocation generated. -- 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-878) Add an another latency metrics to measure tryNode() latency
[ https://issues.apache.org/jira/browse/YUNIKORN-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433925#comment-17433925 ] Weiwei Yang commented on YUNIKORN-878: -- Pls track all related issues under this umbrella. [~tingyao], [~chenya_zhang], can you help to review? > Add an another latency metrics to measure tryNode() latency > > > Key: YUNIKORN-878 > URL: https://issues.apache.org/jira/browse/YUNIKORN-878 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: scheduler-core >Reporter: Chen Yu Teng >Assignee: Chen Yu Teng >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-878) Add an another latency metrics to measure tryNode() latency
[ https://issues.apache.org/jira/browse/YUNIKORN-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-878: - Parent: YUNIKORN-842 Issue Type: Sub-task (was: Improvement) > Add an another latency metrics to measure tryNode() latency > > > Key: YUNIKORN-878 > URL: https://issues.apache.org/jira/browse/YUNIKORN-878 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: scheduler-core >Reporter: Chen Yu Teng >Assignee: Chen Yu Teng >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] [Resolved] (YUNIKORN-75) REST API for changing log level
[ https://issues.apache.org/jira/browse/YUNIKORN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-75. -- Fix Version/s: 1.0.0 Resolution: Fixed > REST API for changing log level > --- > > Key: YUNIKORN-75 > URL: https://issues.apache.org/jira/browse/YUNIKORN-75 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - scheduler >Reporter: Adam Antal >Assignee: Peter Bacsko >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > We need a rest API to change the logging level, so we can change the logging > level on-the-fly. It can be used to debug in production issues where for most > of the time, only INFO level log is needed. -- 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-886) Fix e2e tests after YUNIKORN-794
[
https://issues.apache.org/jira/browse/YUNIKORN-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-886.
---
Fix Version/s: 1.0.0
Resolution: Fixed
> Fix e2e tests after YUNIKORN-794
>
>
> Key: YUNIKORN-886
> URL: https://issues.apache.org/jira/browse/YUNIKORN-886
> Project: Apache YuniKorn
> Issue Type: Test
> Components: shim - kubernetes
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> YUNIKORN-794 changed the REST API, which broke the e2e tests:
> {noformat}
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:34
> Verify_Queue_Quota_Allocation [It]
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:69
> Test Panicked
> interface conversion: interface {} is nil, not string
> /opt/hostedtoolcache/go/1.15.15/x64/src/runtime/iface.go:261
> Full Stack Trace
>
> github.com/apache/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt_test.glob..func3.2()
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:105
> +0x29ff
> github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc38360,
> 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
>
> /home/runner/go/pkg/mod/github.com/onsi/ginkgo@v1.16.5/internal/leafnodes/runner.go:113
> +0xa3
> [...]
>
> github.com/apache/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt_test.TestStateAwareAppScheduling(0xcee780)
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_suite_test.go:83
> +0x156
> testing.tRunner(0xcee780, 0x1b75ca8)
> /opt/hostedtoolcache/go/1.15.15/x64/src/testing/testing.go:1123 +0xef
> created by testing.(*T).Run
> /opt/hostedtoolcache/go/1.15.15/x64/src/testing/testing.go:1168 +0x2b3
> --
> {noformat}
> Problem is that we expect strings like "maxcapacity", "usedcapacity", etc.
> but the JSON response was slightly modified.
--
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
