Design review request: (YUNIKORN-807) Improve performance of node sorting

is (IMO) a simplified approach vs. YUNIKORN-21 and hopefully carries less risk. Any review or comments would be greatly appreciated. Thanks, Craig Condit > On Aug 19, 2021, at 10:03 AM, Craig Condit (Jira) wrote: > > Craig Condit created YUN

Re: [ANNOUNCE] New committer: Chenya Zhang

Congratulations Chenya! > On Sep 22, 2021, at 10:58 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Chenya to > become a committer and we are pleased to announce that she has accepted. > Please join me in congratulating her. > >

Re: [ANNOUNCE] New committer: Manikandan R

Congratulations Mani! > On Sep 22, 2021, at 10:56 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited Mani > to > become a committer and we are pleased to announce that he has accepted. > Please join me in congratulating him. > > Congr

Re: [ANNOUNCE] New committer: Chia-Ping Tsai

Congratulations Chia-Ping! > On Sep 22, 2021, at 10:59 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Chia-Ping to > become a committer and we are pleased to announce that he has accepted. > Please join me in congratulating him.

Re: [ANNOUNCE] New committer: Chaoran Yu

Congratulations Chaoran! > On Oct 14, 2021, at 12:01 AM, Bowen Li wrote: > > Congrats Chaoran! > > On Wed, Oct 13, 2021 at 6:08 PM Chenya Zhang > wrote: > >> Congrats Chaoran! Well deserved. >> >> On Wed, Oct 13, 2021 at 6:05 PM Wilfred Spiegelenburg >> >> wrote: >> >>> The Project Manage

Re: [DISCUSS] release v1.0.0 planning

Looking forward to 1.0 release as well, and thanks Chaoran for volunteering to manage the release. Should we also update our supported version matrix to include 1.18, 1.19, 1.20, and 1.21? Updating the e2e test matrix should be a one-line change, and as part of the rebuild against 1.20, I verif

Announcement: New K8s scheduler plugin mode for YuniKorn (experimental)

On Dec 8, 2021, at 1:47 PM, Craig Condit (Jira) wrote: > > Craig Condit created YUNIKORN-971: > - > > Summary: Implement YuniKorn as a Kubernetes Scheduler Plugin > Key: YUNIKORN-971 > URL: http

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.0

I’m -1 on this one. I pulled down the source archive, built it and attempted to run e2e tests. However, I’m seeing several issues (even after the revert of YUNIKORN-941 from the release repo): - Verify_Non_Matching_NodeSelector_Respected e2e test times out (cause unknown) - Admission controlle

Re: Renaming v0.12.0 to v0.12.1

o rename the 0.12.0 release to 0.12.1. > > Last week we had a release candidate for 0.12.0 that had issues and didn’t > pass the voting process. Now thanks to Craig Condit who promptly resolved all > the blockers, we are ready to start the release process again. Due to > YUNIKORN-

Re: Renaming v0.12.0 to v0.12.1

option 3 is the best option to go >> to in the future. >> >> For this release I think we need to move to v0.12.1 >> >> Wilfred >> >> [1] https://github.com/golang/go/issues/33969 >> [2] https://sum.golang.org >> >> On Tue, 14 Dec 2021 at

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.1

Hi Chaoran, Thanks for putting all this together. I’m trying to verify the release, but am running into some issues with the signing key. Did you upload it to pgpkeys.mit.edu ? Also, it seems that it is not an @apache.org address. AFAIK, that is required? Thanks, Cra

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.1

sing the key corresponding to my Apache email. New artifacts have been > uploaded to the same location. My key has been uploaded to the MIT key server > as well. > > >> On Dec 14, 2021, at 12:45, Craig Condit > <mailto:apa...@craigcondit.com>> wrote: >> >> H

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.1

-0.12.1 upstream. 3) helm-charts/yunikorn/README.md seems to be missing the updated K8s versions (probably a missing commit somewhere). Craig > On Dec 14, 2021, at 4:05 PM, Craig Condit wrote: > > Was able to verify this time. However, I think the archive needs to be > regenerated

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.1

+1. Verified the following: - Verified SHA256 hash - Verified GPG signature - Ran unit and e2e tests - Built docker images - Installed via helm chart into local Minikube cluster - Tested basic functionality including gang scheduling Craig > On Dec 14, 2021, at 1:46 PM, Chaoran Yu wrote: >

Re: Apache YuniKorn (Incubating) 0.12.1 Released

Great news! Thanks Chaoran for all your work on this release. Craig > On Dec 27, 2021, at 12:09 AM, Chaoran Yu wrote: > > Hi all, > > The IPMC has voted in approval of the v0.12.1 release candidate. The voting > result thread can be found at > https://lists.apache.org/thread/1h3s77jo977qj

Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments

Thank you all for the good discussion. I will be happy to act as release manager for 0.12.2 and will begin the process right away. Craig > On Jan 11, 2022, at 11:33 PM, Wilfred Spiegelenburg > wrote: > > We have already run the e2e tests against k8s 1.22 and k8s 1.23. They > all passed. > B

[VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC1

Hello everyone, I’d like to call a vote for a release candidate for Apache YuniKorn (incubating) 0.12.2 release. The release artifacts have been uploaded here: https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2/

Re: [ANNOUNCE] New committer: Yu Teng Chen

Congratulations Yu Teng, and welcome to the team! Craig > On Jan 12, 2022, at 6:35 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Yu Teng to > become a committer and we are pleased to announce that he has accepted. > Please join

[VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC2

Hello everyone, I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC2. The release artifacts have been uploaded here: https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc2/ My public

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC1

quired so RC2 will be the same source code + the helm chart fix. Stay tuned for RC2. Craig > On Jan 12, 2022, at 3:22 PM, Craig Condit wrote: > > Hello everyone, > > I’d like to call a vote for a release candidate for Apache YuniKorn > (incubating) 0.12.2 release. > &

[RESULT] [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC2

Hi all, The vote to Release Apache YuniKorn (incubating) 0.12.2 RC2 has passed with 3 binding +1 votes and 3 non-binding +1 votes. Vote thread: https://lists.apache.org/thread/1gw0k0g5fy86r8ljnjttdco04w7z5j4j Thank you to all t

[DISCUSS] Kubernetes supported version policy

Hi all, I’d like to open a discussion around how we support upstream Kubernetes releases. Up until now, there has been a somewhat unofficial policy of supporting 3 releases at any one time (i.e. 1.19, 1.20, 1.21). This, in fact, was the documented set of releases supported by the most recent Y

Re: [RESULT] [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC2

>>> wrote: >>>> >>>>> I just spotted a bug >>> https://issues.apache.org/jira/browse/YUNIKORN-1038. >>>>> which is critical and worth porting back into branch 0.12 >>>>> >>>>> On Thu, Jan 20, 2022 at 12:12 PM Sunil Go

[WITHDRAWN] [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC2

All, I was discussing this a bit more with Weiwei offline, and I think we are better off withdrawing 0.12.2 RC2 and releasing 0.12.2 RC3 instead. I will get a build together shortly and issue a new vote. Thanks, Craig > On Jan 21, 2022, at 9:39 AM, Craig Condit wrote: > > Chao

[VOTE} Release Apache YuniKorn (incubating) 0.12.2 RC3

Hello everyone, I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC3. The release artifacts have been uploaded here: https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc3/ My public

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC3 (WITHDRAWN)

On Jan 21, 2022, at 12:23 PM, Craig Condit wrote: > > Hello everyone, > > I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC3. > > The release artifacts have been uploaded here: > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

+1 to graduate YuniKorn to a top level project. Looking forward to this important milestone. Craig > On Jan 25, 2022, at 11:08 PM, Weiwei Yang wrote: > > Hi YuniKorn community and mentors > > Based on the discussion thread [1], after 2 years time of incubating, it is > considered that now i

[VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC4

Hello everyone, I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC3. The release artifacts have been uploaded here: https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc4/ My public

Re: [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC4

Sorry, description should say RC4. > On Jan 26, 2022, at 12:10 PM, Craig Condit wrote: > > Hello everyone, > > I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC3. > > The release artifacts have been uploaded here: > https://dist.a

[RESULT] [VOTE] Release Apache YuniKorn (incubating) 0.12.2 RC4

Hello all, The vote to release Apache YuniKorn (incubating) 0.12.2 RC4 has passed with 4 binding +1 votes, 2 non-binding +1 votes, and no 0 or -1 votes. Vote thread: https://lists.apache.org/thread/r4f0f6rkcrxdlx5f3ywpgb9cxhk30ncv

[ANNOUNCE] Apache YuniKorn (incubating) 0.12.2 Released

ackages/helm/yunikorn/yunikorn> Thanks to everyone who helped with the release! Sincerely, Craig Condit

[NOTICE] Pause PRs: migration of repositories as part of graduation has begun

All, The YuniKorn repositories have been renamed in GitHub as part of the graduation process. From this point until we complete the migration tasks, please do not submit any non-migration related PRs or approve any PRs. A follow-up email will sent to this list once these tasks have been complet

[NOTICE] Migration of code repositories as part of graduation complete

All, Migration of the YuniKorn code repositories (other than website) is now complete. Please resume normal operations. I will be updating the website over the next few days to remove incubator references. Thanks, Craig > On Mar 25, 2022, at 8:33 AM, Craig Condit wrote: > > All,

Re: [VOTE] Release Apache YuniKorn 1.0.0 RC1

+1 (binding) Minor nit: There’s a couple of Mac .DS_Store files in the archive: * .DS_Store * helm-charts/.DS_Store * helm-charts/yunikorn/.DS_Store I don’t see this as a blocker, but something to keep in mind for future releases. Checked the following: * no unexpected binaries or files (with

Re: Renaming *_test.go as *test.go

Go files need to end in _test.go in order to be ignored during the build process. The two examples you gave are testing *libraries* in which case they are named differently so that the test files *are* included in the default go build. I’m -1 on changing this within YuniKorn, as it is working

Re: [DISCUSS] Building multi architecture images

I think this is a great start. I would additionally like to see instructions that allow for building multi-arch images on a (relatively) stock Linux install without third-party software other than Docker itself. I know it’s possible, and probably mostly there, but I think it’s important to limit

Re: [DISCUSS] removal of latest tag from docker hub

We need to be careful about how we do this, as it will cause breakage. Off the top of my head, e2e tests for the shim will definitely break, as they will be unable to deploy the web UI successfully if the web:latest tag goes away. There may be others as well… - Craig > On Jun 19, 2022, at 8:

Re: [DISCUSS] removal of latest tag from docker hub

t" images. > For e2e tests, IIRC, we are pulling > the source code and building the docker images locally on the testing VM, > it probably won't break. That's true for the shim itself, but NOT for the web UI. The shim e2e tests use the "latest" tag for the web UI.

Re: [ANNOUNCE] New PMC member: Peter Bacsko

Congratulations Peter! > On Jul 25, 2022, at 8:03 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Peter Bacsko to become a PMC member and we are pleased to announce > that he has accepted. > > On behalf of the Apache YuniKorn PMC

Re: [DISCUSSION] Yunikorn release 1.1.0

Hi Peter, Thanks for taking on the 1.1.0 release. I think this plan looks good. - Craig > On Aug 8, 2022, at 7:30 AM, Peter Bacsko wrote: > > Hi all, > > we've been discussing the next release of Apache Yunikorn. I was asked to > be the release manager of 1.1.0. > > Besides misc bug fixes,

Re: [DISCUSSION] k8shim: running e2e tests only on successful build

I think I would be +1 on the e2e-after-build proposal, but I’m a strong -1 on pre-commit enforcement. Due to the interdependencies between our different modules, there have been (and likely will be again) scenarios where we need to push multiple changes to get a build back into a “healthy state”

Re: [VOTE] Release Apache YuniKorn 1.1.0 RC1

Unfortunately, I have to vote -1 on this. Release candidates, if they are to become actual releases, must be binary identical once voted upon and released. This archive contains numerous references to “RC1” including the top-level directory within the archive itself. All of these will at a mini

Re: [VOTE] Release Apache YuniKorn 1.1.0 RC1

0.0-1 >> >> We need to re-run the release tool with the update in the version. >> >> Wilfred >> >> On Thu, 1 Sept 2022 at 00:17, Craig Condit wrote: >> >>> Unfortunately, I have to vote -1 on this. >>> >>> Release candidates, i

[DISCUSS] Removal of configmap update logic via REST API

moving forward. Let me know if you have any concerns, Craig Condit [1] https://issues.apache.org/jira/browse/YUNIKORN-997 <https://issues.apache.org/jira/browse/YUNIKORN-997> [2] https://issues.apache.org/jira/browse/YUNIKORN-1221 <https://issues.apache.org/jira/browse/YUNIKORN-1221>

Re: [ANNOUNCE] New committer: Rainie Li

Congratulations Rainie! > On Dec 14, 2022, at 10:57 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Rainie Li to become a committer and we are pleased to announce that she has > accepted. > Please join me in congratulating her. >

[DISCUSS] Removal of periodic state dumps

All, I’d like to open a discussion about the future of the periodic state dump feature. To jumpstart the discussion, I opened https://issues.apache.org/jira/browse/YUNIKORN-1483, which is copied below for context. In the process of writing this up, it seems to me that we might actually be bett

Re: [DISCUSS] Removal of periodic state dumps

YMMDD-HHMM.json > On Dec 19, 2022, at 6:18 PM, Craig Condit wrote: > > All, > > I’d like to open a discussion about the future of the periodic state dump > feature. To jumpstart the discussion, I opened > https://issues.apache.org/jira/browse/YUNIKORN-1483, which is copied be

Re: [DISCUSS] Inclusive language: change git default branch name

This will probably be an unpopular opinion, but I’m -1 on this. I agree with being inclusive where it makes sense, however this whole “master vs. main” controversy is rooted in an idea that is ill-informed, ill-conceived, and provides no technical benefit. I’ll make my case as follows: 1. Ill-i

Re: [VOTE] Release Apache YuniKorn 1.2.0 RC1

+1 (Binding) - Verified signatures - Verified sha512 - Built amd64 images - Ran unit tests - Ran e2e tests for standard and plugin build on K8s 1.25.3 - Ran sleep jobs > On Feb 1, 2023, at 10:40 AM, Peter Bacsko wrote: > > +1 (Binding) > > - Verified signatures > - Verified sha512 sum > - Bui

Re: K8s ConfigMap missing in k8shim repository

Hi Marc, You can use helm locally to generate the templates for YuniKorn and save them to local files which can be applied. Something like this should work: helm repo add yunikorn https://apache.github.io/yunikorn-release helm template --namespace yunikorn yunikorn/yunikorn --version 1.2

Re: [VOTE] Release Apache YuniKorn 1.3.0 RC1

+1 (binding) - Verified signatures and checksums - Verified LICENSE and NOTICE files - Verified release tarball structure - Built release on Mac Ventura (amd64) - Installed locally on Kind cluster (1.26) - Ran some simple applications - Executed e2e test suite in both standard and plugin deployme

[ANNOUNCE] Build system updates

This is useful when deploying to local repositories as it avoids the necessity of renaming the images after the build. Regards, Craig Condit PS - See the following JIRAs for more information: - https://issues.apache.org/jira/browse/YUNIKORN-1862 Shim: Use privately installed build

Re: [DISCUSS] removal of the yunikorn application CRD

I’m definitely in favor of removing the CRD, and sooner rather than later. It negatively impacts some of the ongoing refactoring tasks as it influences the recovery pipeline. I think given the alpha state of the CRD, if there are no objections we can remove this in 1.4.0. Craig > On Jul 27, 2

Re: [ANNOUNCE] New committer: Hsuang Zong Wu

Congrats! > On Sep 6, 2023, at 10:35 AM, Desai, Mit wrote: > > That’s great! Congrats Hsuang Zong! > > -Mit > > On 9/5/23, 10:54 PM, "Wilfred Spiegelenburg" > wrote: > > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Hsuang Zong to b

Re: [ANNOUNCE] New PMC member: Rainie Li

Congratulations Rainie! Craig > On Nov 15, 2023, at 8:21 PM, Wilfred Spiegelenburg > wrote: > > The Project Management Committee (PMC) for Apache YuniKorn has invited > Rainie Li to become a PMC member and we are pleased to announce > that she has accepted. > > On behalf of the Apache YuniKo

Re: [VOTE] Release Apache YuniKorn 1.4.0 RC1

+1 (binding). - Verified keys and sums - Built images from source with go 1.21.4 on Mac (amd64) - Ran e2e tests and some simple applications Only issue encountered was it seems the (relatively) new UserGroupLimit e2e tests are not stable. Given this is a brand new feature and that test was rece

Re: Should we remove Chinese documents

As a fellow non-Chinese speaker I’ll defer to others on the decision whether to stop providing Chinese docs. *If* we decide to stop, I’d be in favor of removing the existing docs due to staleness (as Chia-Ping Tsai indicated). We won’t lose them permanently; there is still git history if we woul

Re: [VOTE] Release Apache YuniKorn 1.5.0 RC1

I’m trying to validate the binaries produced using the new reproducible builds feature, but I’m getting different checksums than what the README indicates I should. Was the release tarball created from a fresh checkout of the release repository with no uncommitted changes? README.md shows these

Re: [VOTE] Release Apache YuniKorn 1.5.0 RC1

rom the core when a pod is completed (PR available; needs review to determine if this is a 1.5 blocker). I think we should address each of these and cut an rc2. Thought? Craig Condit > On Mar 2, 2024, at 10:38 AM, TingYao wrote: > > Hello everyone, > > I would like to call

Re: [VOTE] Release Apache YuniKorn 1.5.0 RC1

 PM, Craig Condit wrote: > > -1 (binding). > > All, > > We have a few issues in rc1 that I believe we should address before shipping > 1.5.0: > > CVEs: > > - CVE-2024-24783 (requires rebuild with go 1.21.8) > - CVE-2023-45290 (requires rebuild with go 1.21.8) &g

Re: [VOTE]Release Apache YuniKorn 1.5.0 RC2

+1 (binding). - Verified signatures and checksums - Verified LICENSE and NOTICE - Verified tarball structure - Build release on macOS Sonoma (amd64) - Installed locally on Kind cluster (1.29) - Ran E2E tests Craig > On Mar 7, 2024, at 8:31 AM, TingYao wrote: > > Hello everyone, > > I would l

Re: [DISCUSSION] (Potential) Locking issues in Yunikorn

I’m all for fixing these… and in general where lockless algorithms can be implemented cleanly, I’m in favor of those implementations instead of requiring locks, so for RMProxy I’m +1 on that. The extra memory for an RMProxy instance is irrelevant. The recursive locking case is a real problem, a

[DISCUSSION] Deprecation of YuniKorn plugin deployment mode

--- Preface === There have been quite a few informal discussions on this topic, and it's time that we bring this formally to the yunikorn-dev mailing list for further discussion... --- Summary === We are actively planning to deprecate the YuniKorn plugin mode for eventual rem

Re: [DISCUSSION] Deprecation of YuniKorn plugin deployment mode

asting from the existing kube-scheduler so we can >> obtain the reference. This also means that from time to time, we need to >> see how much our copy-pasted code deviates from the actual K8s code. >> >> 3. I believe all e2e tests runs on a single machine inside VMs/containers.

Re: [VOTE] Release Apache YuniKorn 1.5.1 RC1

Sent with the wrong address (sorry). > On May 13, 2024, at 4:58 PM, Craig Condit wrote: > > +1 (binding). > > - Verified keys and hashes > - Built and deployed to on-prem cluster > - Ran some test workloads > > > Craig Condit > > >> On May

Re: [VOTE] Release Apache YuniKorn 1.5.1 RC1

IMO, it’s too late to update 1.5.1. We’ve already cut the tags, and those must remain immutable. Our best bet would probably be to continue with 1.5.1 as-is; the new issue is unlikely to affect non-autoscaled clusters and it’s better than 1.5.0. We should, I think, get this latest issue fixed an

Re: [VOTE] Release Apache YuniKorn 1.5.2 RC1

+1 (binding). - Verified signature and checksums - Verified LICENSE and NOTICE files - Verified release tarball structure - Built both arm64 and amd64 releases on M3 Mac using go 1.22.5. - Installed arm64 locally on Kind cluster (1.30.0) - Installed amd64 on real cluster (1.29.2+rke2r1) - Ran simp

[DISCUSS] YuniKorn E2E Testing Policy

intervals before release, but also that we don't waste resources on every PR. The overall impact of making these changes will reduce our e2e test load on PRs by 75%. Please, let's discuss here further. Craig Condit --

[VOTE] [CANCELED] Release Apache YuniKorn 1.6.1 RC1

It's been suggested that we should add YUNIKORN-2953. I agree, and since we have yet to get any +1 vots for RC1, I have canceled this release. I will cut RC2 shortly and open a new voting thread. Craig > On Jan 15, 2025, at 11:57 AM, Craig Condit wrote: > > Hello everyone, >

[VOTE] Release Apache YuniKorn 1.6.1-RC1

Hello everyone, I would like to call a vote for releasing Apache YuniKorn 1.6.1 RC2. This is a bugfix release, meant to address several critical issues found in 1.6.0. The only change from RC1 is the backport of the fix for YUNIKORN-2953. [1] The release artifacts have been uploaded here: https

Re: [VOTE] Release Apache YuniKorn 1.6.1-RC2

Sorry, wrong subject. (Should have said RC2). > On Jan 21, 2025, at 8:59 AM, Craig Condit wrote: > > Hello everyone, > > I would like to call a vote for releasing Apache YuniKorn 1.6.1 RC2. This is > a bugfix release, meant to address several critical issues found in 1.6.0.

Re: [VOTE] Release Apache YuniKorn 1.6.1-RC1

For those hitting the 'ERROR: failed to detect containerd snapshotter' issue, I believe this is a bad interaction between recent Docker Desktop with containerd storage enabled and the latest kind node image. See https://github.com/kubernetes-sigs/kind/issues/3795 for details. For now, the worka

Re: [VOTE] Release Apache YuniKorn 1.6.1-RC2

+1 (binding). - Verified signature and checksums - Built on macOS (arm64) - Verified reproducible signatures on binaries - Installed locally on Kubernetes 1.32.0 cluster - Verified basic tests and scheduling Thanks, Craig > On Jan 21, 2025, at 8:59 AM, Craig Condit wrote: > > Hello

Re: [VOTE] Release Apache YuniKorn 1.6.1-RC2

you, Craig > On Jan 21, 2025, at 8:59 AM, Craig Condit wrote: > > Hello everyone, > > I would like to call a vote for releasing Apache YuniKorn 1.6.1 RC2. This is > a bugfix release, meant to address several critical issues found in 1.6.0. > The only change from RC1 is th

[ANNOUNCE] YuniKorn 1.6.1 released

Hello everyone, I am pleased to announce that the Apache YuniKorn community has voted to release Apache YuniKorn v1.6.1. It contains 12 fixes and improvements, several of which resolve critical issues in 1.6.0. All users of 1.6.0 are urged to upgrade. The release details are listed on the v1.6

[VOTE] Release Apache YuniKorn 1.6.1 RC1

Hello everyone, I would like to call a vote for releasing Apache YuniKorn 1.6.1 RC1. This is a bugfix release, meant to address several critical issues found in 1.6.0. The release artifacts have been uploaded here: https://dist.apache.org/repos/dist/dev/yunikorn/1.6.1-RC1/ My public key is loc

Re: [DISCUSS] YuniKorn 1.6.2 release

+1 on getting this out ASAP. I've already backported the mentioned issues as well as the CVE fixes to branch-1.6. Craig > On Mar 5, 2025, at 8:14 PM, Wilfred Spiegelenburg wrote: > > Hi all, > > A regression of a race condition was found in YuniKorn 1.6.0 and > 1.6.1. The regression reintrod

Re: [VOTE] Release Apache YuniKorn 1.6.2-RC1

+1 (binding). - Verified signature and checksums - Built on macOS (arm64) - Verified reproducible signatures for both linux/amd64 and linux/arm64 binaries - Installed on bare metal Kubernetes 1.32.2 cluster - Ran e2e test suite. All passed except for spark (test is known to be a little flaky) N

[jira] [Created] (YUNIKORN-780) Refactor node sorting policies into separate implementations

Craig Condit created YUNIKORN-780: - Summary: Refactor node sorting policies into separate implementations Key: YUNIKORN-780 URL: https://issues.apache.org/jira/browse/YUNIKORN-780 Project: Apache

[jira] [Created] (YUNIKORN-807) Improve performance of node sorting

Craig Condit created YUNIKORN-807: - Summary: Improve performance of node sorting Key: YUNIKORN-807 URL: https://issues.apache.org/jira/browse/YUNIKORN-807 Project: Apache YuniKorn Issue Type

[jira] [Created] (YUNIKORN-847) Use resource weighting for node sorting

Craig Condit created YUNIKORN-847: - Summary: Use resource weighting for node sorting Key: YUNIKORN-847 URL: https://issues.apache.org/jira/browse/YUNIKORN-847 Project: Apache YuniKorn Issue

[jira] [Created] (YUNIKORN-852) Document changes from YUNIKORN-847

Craig Condit created YUNIKORN-852: - Summary: Document changes from YUNIKORN-847 Key: YUNIKORN-852 URL: https://issues.apache.org/jira/browse/YUNIKORN-852 Project: Apache YuniKorn Issue Type

[jira] [Created] (YUNIKORN-857) Add ENV var to disable gang scheduling

Craig Condit created YUNIKORN-857: - Summary: Add ENV var to disable gang scheduling Key: YUNIKORN-857 URL: https://issues.apache.org/jira/browse/YUNIKORN-857 Project: Apache YuniKorn Issue

[jira] [Resolved] (YUNIKORN-21) Optimize node sorting algorithms

[ https://issues.apache.org/jira/browse/YUNIKORN-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit resolved YUNIKORN-21. -- Fix Version/s: 1.0.0 Resolution: Duplicate Resolving in favor of YUNIKORN-847

[jira] [Created] (YUNIKORN-866) Support multiple versions of Kubernetes

Craig Condit created YUNIKORN-866: - Summary: Support multiple versions of Kubernetes Key: YUNIKORN-866 URL: https://issues.apache.org/jira/browse/YUNIKORN-866 Project: Apache YuniKorn Issue

[jira] [Created] (YUNIKORN-867) [Umbrella] Remove kubernetes private API usage

Craig Condit created YUNIKORN-867: - Summary: [Umbrella] Remove kubernetes private API usage Key: YUNIKORN-867 URL: https://issues.apache.org/jira/browse/YUNIKORN-867 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-872) [Umbrella] Build against kubernetes 1.20

Craig Condit created YUNIKORN-872: - Summary: [Umbrella] Build against kubernetes 1.20 Key: YUNIKORN-872 URL: https://issues.apache.org/jira/browse/YUNIKORN-872 Project: Apache YuniKorn Issue

[jira] [Closed] (YUNIKORN-866) Support multiple versions of Kubernetes

[ https://issues.apache.org/jira/browse/YUNIKORN-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit closed YUNIKORN-866. - Assignee: Craig Condit Resolution: Abandoned Closing in favor of YUNIKORN-866

[jira] [Created] (YUNIKORN-873) Update core build dependencies to 1.20.11

Craig Condit created YUNIKORN-873: - Summary: Update core build dependencies to 1.20.11 Key: YUNIKORN-873 URL: https://issues.apache.org/jira/browse/YUNIKORN-873 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-874) Replace predicator.go with 1.20+ compatible version

Craig Condit created YUNIKORN-874: - Summary: Replace predicator.go with 1.20+ compatible version Key: YUNIKORN-874 URL: https://issues.apache.org/jira/browse/YUNIKORN-874 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-875) Fix compilation of unit tests on K8S 1.20

Craig Condit created YUNIKORN-875: - Summary: Fix compilation of unit tests on K8S 1.20 Key: YUNIKORN-875 URL: https://issues.apache.org/jira/browse/YUNIKORN-875 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-880) Remove obsolete "Predicates" configuration option

Craig Condit created YUNIKORN-880: - Summary: Remove obsolete "Predicates" configuration option Key: YUNIKORN-880 URL: https://issues.apache.org/jira/browse/YUNIKORN-880 Project: Apach

[jira] [Created] (YUNIKORN-881) Fix e2e test failures after predicates refactor

Craig Condit created YUNIKORN-881: - Summary: Fix e2e test failures after predicates refactor Key: YUNIKORN-881 URL: https://issues.apache.org/jira/browse/YUNIKORN-881 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-883) Merge YUNIKORN-872 into master

Craig Condit created YUNIKORN-883: - Summary: Merge YUNIKORN-872 into master Key: YUNIKORN-883 URL: https://issues.apache.org/jira/browse/YUNIKORN-883 Project: Apache YuniKorn Issue Type: Sub

[jira] [Created] (YUNIKORN-884) Fix linter issue in e2e tests

Craig Condit created YUNIKORN-884: - Summary: Fix linter issue in e2e tests Key: YUNIKORN-884 URL: https://issues.apache.org/jira/browse/YUNIKORN-884 Project: Apache YuniKorn Issue Type: Sub

[jira] [Created] (YUNIKORN-887) Automate k8shim FSM state transitions

Craig Condit created YUNIKORN-887: - Summary: Automate k8shim FSM state transitions Key: YUNIKORN-887 URL: https://issues.apache.org/jira/browse/YUNIKORN-887 Project: Apache YuniKorn Issue

[jira] [Created] (YUNIKORN-888) Add documentation for k8shim state diagrams

Craig Condit created YUNIKORN-888: - Summary: Add documentation for k8shim state diagrams Key: YUNIKORN-888 URL: https://issues.apache.org/jira/browse/YUNIKORN-888 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-921) Applications should be able to opt-out of state-aware scheduling

Craig Condit created YUNIKORN-921: - Summary: Applications should be able to opt-out of state-aware scheduling Key: YUNIKORN-921 URL: https://issues.apache.org/jira/browse/YUNIKORN-921 Project: Apache

[jira] [Created] (YUNIKORN-922) Add application.stateaware.disable tag handling

Craig Condit created YUNIKORN-922: - Summary: Add application.stateaware.disable tag handling Key: YUNIKORN-922 URL: https://issues.apache.org/jira/browse/YUNIKORN-922 Project: Apache YuniKorn

[jira] [Created] (YUNIKORN-923) k8s-shim changes for YUNIKORN-921

Craig Condit created YUNIKORN-923: - Summary: k8s-shim changes for YUNIKORN-921 Key: YUNIKORN-923 URL: https://issues.apache.org/jira/browse/YUNIKORN-923 Project: Apache YuniKorn Issue Type

  1   2   3   4   5   6   7   8   9   10   >