+1 (binding)
- built the docker images from source on M1 mac
- installed yunikorn locally with the released helm charts
- run simple workloads to verify the scheduler works fine
- verified the web UI pages, home / apps / queues / nodes, look good
- verified the queue utilization bar is workin
+1 (binding) from me
- built images from source
- ran unit tests
- ran validate_cluster.sh to install the release on KIND
- checked REST endpoints
- checked UI
Thank you all for the voting on the RC1 for 1.1.0.
That concludes the voting: it has passed with 5 binding +1, 0 non binding
+1, no 0 or
+1
- build images(ubuntu/amd64)
- run unit test
- deploy Yunikorn to kubernetes cluster
Thanks Peter
Tingyao
Peter Bacsko 於 2022年9月5日 週一 下午4:20寫道：
> Thanks for the votes so far.
>
> Some folks are still out, so I'm extending the voting deadline until
> September 7, 2020 12:00pm CEST.
>
> Than
Thanks for the votes so far.
Some folks are still out, so I'm extending the voting deadline until
September 7, 2020 12:00pm CEST.
Thanks,
Peter
On Sat, Sep 3, 2022 at 5:05 PM 陳Chen宥騰Yuteng wrote:
> +1
> - Built ARM based image(arm64v8)
> - Ran unit tests
> - Deployed Yunikorn on Kubernetes clu
+1
- Built ARM based image(arm64v8)
- Ran unit tests
- Deployed Yunikorn on Kubernetes cluster.
- Tried the sleep example. Pods could be scheduled by Yunikorn.
Wilfred Spiegelenburg 於 2022年9月2日 週五 上午10:35寫道：
> +1 (binding)
>
> - Verified signatures
> - Verified sha512 sum
> - Verified the LICENS
+1 (binding)
- Verified signatures
- Verified sha512 sum
- Verified the LICENSE changes
- Built ARM based image on Mac/amd64
- Ran validation script to verify proper startup
- Ran unit tests
Filed YUNIKORN-1305 to fix the sha labeling in the generated image but that
is not important enough to sto
+1.
- Verified signatures
- Verified sha512 sum
- Built release (on Mac/amd64)
- Ran validation script to verify proper startup
- Executed e2e tests on both standard and plugin mode
Other than a couple of flaky tests (known issue) everything looks great.
Thanks Peter for the release work!
Crai
Thanks Craig.
I re-generated the artifacts with just using "1.1.0" in
release-configs.json.
It's based the same code base/tags, so it's still the RC1.
I removed the previous artifacts and the new ones are available here:
https://dist.apache.org/repos/dist/dev/yunikorn/1.1.0-RC1/
Thanks,
Peter
The version that is used in the name is also in the substitutions in the
Makefile, helm charts etc.
Updating the release-configs.json should be clarified in:
* update the version with the release version: examples: 0.12.2 or 1.1.0
* update the tags with the current release tag examples: 0.12.2-1 o
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
Correction: obviously, there's no more "incubator".
That was a mistake from a copy-paste.
yunikorn-scheduler-interface: v1.1.0-1
yunikorn-core: v1.1.0-1
yunikorn-k8shim: v1.1.0-1
yunikorn-web: v1.1.0-1
yunikorn-release: v1.1.0-1
On Wed, Aug 31, 2022 at 12:03 PM Peter Bacsko wrote:
> Hello every
Hello everyone,
I’d like to call a vote for releasing Apache YuniKorn 1.1.0 RC1.
The release artifacts have been uploaded here:
https://dist.apache.org/repos/dist/dev/yunikorn/1.1.0-RC1/
My public key is located here:
https://downloads.apache.org/yunikorn/KEYS
JIRA issues that have been res
12 matches
Mail list logo
