Re: [VOTE] Release Apache YuniKorn 1.3.0 RC1

[Sunil Govindan]

+1 binding

- Verified license and notice
- Verified source file and release contents
- Checksums and signature is good
- basic install looks good

Thanks
Sunil

On Sat, Jun 10, 2023 at 8:58 AM KatLantyss  wrote:

> +1 binding
>
> - Verified signatures and checksums - Verified LICENSE and NOTICE files -
> Verified release tarball structure - Built release on Ubuntu 22.04 LTS
> (amd64) - Installed locally on Kind cluster and Minikube (1.26)
> - Checked REST endpoints
>
> Kai-Jyun Chen
>
> On 2023/06/06 08:11:38 陳Chen宥騰Yuteng wrote:
> > Hello everyone,
> >
> > I’d like to call a vote for releasing Apache YuniKorn 1.3.0 RC1.
> >
> > The release artifacts have been uploaded here:
> >   https://dist.apache.org/repos/dist/dev/yunikorn/1.3.0-RC1/
> > 
> >
> > My public key is located here:
> >   https://downloads.apache.org/yunikorn/KEYS
> >
> > JIRA issues that have been resolved in this release:
> >
> https://issues.apache.org/jira/browse/YUNIKORN-1609?jql=project%20%3D%20YUNIKORN%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20%22Target%20Version%22%20%3D%201.3.0%20ORDER%20BY%20status%20ASC
> >
> > Git tags for each component are as follows:
> >
> > yunikorn-scheduler-interface: v1.3.0-1
> > yunicorn-core: v1.3.0-1
> > yunikorn-k8shim: v1.3.0-1
> > yunikorn-web: v1.3.0-1
> > yunikorn-release: v1.3.0-1
> >
> > One the release is voted on and approved, all repos will be tagged 1.3.0
> > for consistency.
> >
> > Please review and vote. The vote will be open for at least 72 hours and
> > closes on Friday, June 9 2023, 8 AM GMT.
> >
> > [ ] +1 Approve
> > [ ] +0 No opinion
> > [ ] -1 Disapprove (and the reason why)
> >
> > Thank you,
> > Yu Teng
> >

Re: [ANNOUNCE] New committer: Rainie Li

[Sunil Govindan]

Congrats Rainie!

Sunil

On Wed, Dec 14, 2022 at 8: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.
>
> Congratulations & Welcome aboard Rainie !
>
> Wilfred
>

Fwd: Migrating away from Travis-CI

[Sunil Govindan]

FYKI

-- Forwarded message -
From: Drew Foulks 
Date: Mon, Oct 24, 2022 at 2:43 PM
Subject: Migrating away from Travis-CI
To: 


Greetings PMC Members!

Infrastructure is moving away from Travis-CI at the end of 2022.

If your project is not currently using Travis-CI, this email is not
actionable.

Projects using Travis-CI:

Please take a look at
https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations

and join the builds meetings and mailing list for project updates.


-- 
Cheers,

Drew Foulks
ASF Infra

Re: YuniKorn community meetup: Santa Clara, CA

[Sunil Govindan]

Hi Folks,

Could we also lock in the agenda so we can publish this on our website?

@Chenya Zhang   and @Wilfred Spiegelenburg
 , could you please help?

Thanks
Sunil

On Mon, Oct 3, 2022 at 6:35 PM Sunil Govindan  wrote:

> This is great!
>
> Look forward to meeting you all!
>
> Cheers
> Sunil
>
> On Mon, Oct 3, 2022 at 2:38 PM Weiwei Yang  wrote:
>
>> Sounds good. Wilfred, could you pls create a meetup link on Linkedin so we
>> can start to spread the messages?
>> I'd like to cover 3 topics:
>>  - Karpenter support
>>  - Job priority high-level discussion
>>  - GPU support
>>
>> I'll draft something and share it in the meeting.
>>
>> Weiwei
>>
>> On Mon, Oct 3, 2022 at 10:56 AM Wilfred Spiegelenburg <
>> wilfr...@apache.org>
>> wrote:
>>
>> > I checked with the Cloudera office team and they prefer Thursday 20
>> October
>> > 2022.
>> > Let's lock in that day to start with.
>> >
>> > For the program this is some of the things we should cover:
>> > * progress I have made with the K8s scheduling sig on the pre-enqueue
>> > filtering.
>> > * feedback from the ApacheCON presentations (Chaoran, Bowen & Wilfred).
>> > * discussion: K8s version support.
>> > * General Roadmap
>> >
>> > Wilfred
>> >
>> >
>> > On Mon, 3 Oct 2022 at 12:12, Weiwei Yang  wrote:
>> >
>> > > Hi Wilfred
>> > >
>> > > I suggest having this on Friday afternoon, Oct 21, so we have enough
>> time
>> > > to spread the messages and possibly invite more people to join.
>> > > We can have a few planned presentations and preserve some time for
>> > general
>> > > and roadmap discussions.
>> > > I can't wait for meeting you guys in person!!
>> > >
>> > > Weiwei
>> > >
>> > > On Mon, Oct 3, 2022 at 8:26 AM Chenya Zhang <
>> chenyazhangche...@gmail.com
>> > >
>> > > wrote:
>> > >
>> > > > Big +1!
>> > > >
>> > > > I'll also be in the Bay area the week of Oct 17th. I can also help
>> > > Wilfred
>> > > > to organize this meetup.
>> > > >
>> > > > Let me check if there are topics of interest from our side and share
>> > them
>> > > > here. This is very exciting!
>> > > >
>> > > > Best,
>> > > > Chenya
>> > > >
>> > > > On Fri, Sep 30, 2022 at 4:38 PM Weiwei Yang 
>> wrote:
>> > > >
>> > > > > That sounds great!!
>> > > > > Can we start to collect the topics and finalize the date ASAP?
>> > > > >
>> > > > > Thanks
>> > > > > Weiwei
>> > > > >
>> > > > > On Thu, Sep 29, 2022 at 10:38 PM Wilfred Spiegelenburg <
>> > > > > wilfr...@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > > > HI all,
>> > > > > >
>> > > > > > There has not been a community meetup in a while. With ApacheCON
>> > next
>> > > > > week
>> > > > > > in New Orleans I will be in the USA for a while.
>> > > > > >
>> > > > > > I would like to propose a meetup in Santa Clara, California in
>> the
>> > > 3rd
>> > > > > week
>> > > > > > of October. That is the week from 17-21 October. Cloudera is
>> > willing
>> > > to
>> > > > > > host and organise the meetup at their office.
>> > > > > > We can work on the exact content over the next weeks.
>> > > > > >
>> > > > > > Anyone is welcome, please let me know what you think.
>> > > > > >
>> > > > > > Wilfred
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: YuniKorn community meetup: Santa Clara, CA

[Sunil Govindan]

This is great!

Look forward to meeting you all!

Cheers
Sunil

On Mon, Oct 3, 2022 at 2:38 PM Weiwei Yang  wrote:

> Sounds good. Wilfred, could you pls create a meetup link on Linkedin so we
> can start to spread the messages?
> I'd like to cover 3 topics:
>  - Karpenter support
>  - Job priority high-level discussion
>  - GPU support
>
> I'll draft something and share it in the meeting.
>
> Weiwei
>
> On Mon, Oct 3, 2022 at 10:56 AM Wilfred Spiegelenburg  >
> wrote:
>
> > I checked with the Cloudera office team and they prefer Thursday 20
> October
> > 2022.
> > Let's lock in that day to start with.
> >
> > For the program this is some of the things we should cover:
> > * progress I have made with the K8s scheduling sig on the pre-enqueue
> > filtering.
> > * feedback from the ApacheCON presentations (Chaoran, Bowen & Wilfred).
> > * discussion: K8s version support.
> > * General Roadmap
> >
> > Wilfred
> >
> >
> > On Mon, 3 Oct 2022 at 12:12, Weiwei Yang  wrote:
> >
> > > Hi Wilfred
> > >
> > > I suggest having this on Friday afternoon, Oct 21, so we have enough
> time
> > > to spread the messages and possibly invite more people to join.
> > > We can have a few planned presentations and preserve some time for
> > general
> > > and roadmap discussions.
> > > I can't wait for meeting you guys in person!!
> > >
> > > Weiwei
> > >
> > > On Mon, Oct 3, 2022 at 8:26 AM Chenya Zhang <
> chenyazhangche...@gmail.com
> > >
> > > wrote:
> > >
> > > > Big +1!
> > > >
> > > > I'll also be in the Bay area the week of Oct 17th. I can also help
> > > Wilfred
> > > > to organize this meetup.
> > > >
> > > > Let me check if there are topics of interest from our side and share
> > them
> > > > here. This is very exciting!
> > > >
> > > > Best,
> > > > Chenya
> > > >
> > > > On Fri, Sep 30, 2022 at 4:38 PM Weiwei Yang  wrote:
> > > >
> > > > > That sounds great!!
> > > > > Can we start to collect the topics and finalize the date ASAP?
> > > > >
> > > > > Thanks
> > > > > Weiwei
> > > > >
> > > > > On Thu, Sep 29, 2022 at 10:38 PM Wilfred Spiegelenburg <
> > > > > wilfr...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > HI all,
> > > > > >
> > > > > > There has not been a community meetup in a while. With ApacheCON
> > next
> > > > > week
> > > > > > in New Orleans I will be in the USA for a while.
> > > > > >
> > > > > > I would like to propose a meetup in Santa Clara, California in
> the
> > > 3rd
> > > > > week
> > > > > > of October. That is the week from 17-21 October. Cloudera is
> > willing
> > > to
> > > > > > host and organise the meetup at their office.
> > > > > > We can work on the exact content over the next weeks.
> > > > > >
> > > > > > Anyone is welcome, please let me know what you think.
> > > > > >
> > > > > > Wilfred
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New PMC member: Peter Bacsko

[Sunil Govindan]

Congratulations Peter



On Tue, Jul 26, 2022 at 6:37 AM Craig Condit  wrote:

> 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
> > Wilfred
> >
> > -
> > 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
>
>

Re: [DISCUSS] Building multi architecture images

[Sunil Govindan]

Thank you.
This is a great addition to 1.1.0. 👍

Sunil

On Thu, Jun 16, 2022 at 8:31 PM Wilfred Spiegelenburg 
wrote:

> Craig,
>
> This should be possible already. The python script I wrote uses just
> docker, make and curl for some cleanup. It leverages the standard
> Makefile for the compilation, go itself is used for the cross
> compilation which is there in each install.
> The only bit missing is the documentation to describe what needs to be
> installed on a linux machine to get the docker cross architecture
> build to work.
> I know you need at least docker (moby should suffice) and the open
> source machine emulator qemu [1]. Besides that nothing is, I think,
> needed but some install instructions.
>
> Wilfred
>
> [1] https://www.qemu.org
>
> On Fri, 17 Jun 2022 at 00:33, Craig Condit  wrote:
> >
> > 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 the third-party requirements for an RM as much as possible.
> >
> > Thanks for working on this.
> >
> > - Craig
> >
> >
> > > On Jun 15, 2022, at 8:01 PM, Wilfred Spiegelenburg <
> wilfr...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > By default we only publish images with the AMD64 architecture.
> > > YUNIKORN-725 was implemented to allow builds to at least succeed on
> > > both AMD64 and ARM architectures.
> > >
> > > Building images is a bit more involved and it was briefly discussed as
> > > part of YUNIKORN-725, and then moved to YUNIKORN-1215 for
> > > implementation.
> > > Over the last week I have been working on getting a build working and
> > > generating both AMD (amd64) and ARM (arm64v8) images combined into one
> > > image tag.
> > > I have a solution that works seamlessly if:
> > > * Docker Desktop [1] is installed.
> > > * Rancher Desktop [2] is installed with "dockerd (moby)" as the
> > > container runtime
> > > The code impact will be in the Docker and Makefile for the web and
> > > k8shim repo. Plus a new tool in the release repo.
> > >
> > > Both desktops are free for use in open source development. Docker
> > > desktop is only free within limits and might not work for some of us.
> > > Rancher Desktop is the always free option. The CPU impact of running
> > > Rancher Desktop on my local machine is slightly higher than docker
> > > desktop. Besides that it works the same.
> > >
> > > The next step could be moving to multi stage docker images for the
> > > build [3]. That should also open up the possibility for nedrctl to be
> > > used for building the multi architecture images.
> > >
> > > My proposal is to:
> > > * release multi architecture images for the 1.1.0 release
> > > * delay multi stage build to a later release
> > >
> > > Any comments on this plan? I will raise the PRs against the different
> > > repos as part of YUNIKORN-1215 in the next day or so.
> > >
> > > Wilfred
> > >
> > > [1] https://www.docker.com/products/docker-desktop/
> > > [2] https://rancherdesktop.io
> > > [3]
> https://www.docker.com/blog/faster-multi-platform-builds-dockerfile-cross-compilation-guide/
> > >
> > > -
> > > 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
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

Re: [ANNOUNCE] Apache YuniKorn v1.0.0 release

[Sunil Govindan]

Kudos!

This is a great milestone for the YuniKorn community. Thank you.

Sunil

On Wed, May 4, 2022 at 4:58 PM Chaoran Yu  wrote:

> Congrats! Amazing milestone!
>
>
> On Wed, May 4, 2022 at 1:45 PM Weiwei Yang  wrote:
>
> > Congrats, and thanks for everyone's contribution!!
> >
> > On Wed, May 4, 2022 at 1:31 PM Wilfred Spiegelenburg <
> wilfr...@apache.org>
> > wrote:
> >
> > > Hi all,
> > >
> > > It gives me great pleasure to announce that the Apache YuniKorn
> community
> > > has
> > > voted to release Apache YuniKorn v1.0.0.
> > >
> > > Apache YuniKorn v1.0.0 is the first release for the project as an
> > > Apache top level project. It also marks a major milestone as the first
> > > major release.
> > >
> > > It contains 173 fixes and improvements. The release details, list of
> > > major features and incompatible changes are on the v1.0.0 announcement
> > > page [1].
> > >
> > > You can also download the release from the Downloads page [2],
> > >
> > > Many thanks to everyone who contributed to the release. This release
> > > is a direct result of your great contributions.
> > >
> > > Wilfred
> > >
> > > [1] https://yunikorn.apache.org/release-announce/1.0.0
> > > [2] https://yunikorn.apache.org/download
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache YuniKorn 1.0.0 RC1

[Sunil Govindan]

Thanks Wilfred for the efforts

+1 (binding)

- Checked signatures & verified checksum
- Built from source
- Ran a local test cluster with some basic jobs.
- UI looks ok.
- Website changes can be done later, as we need more changes in 1.0

Thanks
Sunil

On Tue, Apr 26, 2022 at 8:31 PM Wilfred Spiegelenburg 
wrote:

> Hello everyone,
>
> I would like to call a vote for releasing Apache YuniKorn 1.0.0 RC1.
> The first release for Apache YuniKorn as a top level project. Please
> note that the location of artefacts and the KEYS file has changed as
> we are now a top level project.
>
> The release artefacts have been uploaded here:
>   https://dist.apache.org/repos/dist/dev/yunikorn/1.0.0-RC1/
>
> My public key is located in the KEYS file:
>   https://downloads.apache.org//yunikorn/KEYS
>
> JIRA issues that have been resolved in this release:
>   https://issues.apache.org/jira/issues/?filter=12350818
>
> The release contains a number of incompatible changes that could
> impact the release verification. Please read the draft release notes
> attached to this vote for further details.
>
> Git tags for each component are as follows:
> yunikorn-scheduler-interface: v1.0.0-1
> yunikorn-core: v1.0.0-1
> yunikorn-k8shim: v1.0.0-2
> yunikorn-web: v1.0.0-1
> yunikorn-release: v1.0.0-1
>
> Once the release is voted on and approved, all repos will be tagged
> 1.0.0 for consistency.
>
> Please review and vote. The vote will be open for at least 72 hours
> and closes on Sunday, 1 May 2022, midnight PDT.
>
> [ ] +1 Approve
> [ ] +0 No opinion
> [ ] -1 Disapprove (and the reason why)
>
>
> Thank you,
> Wilfred
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: Re-organize community meetings

[Sunil Govindan]

Hi Weiwei

Meeting links are updated. Kindly check.

Thanks
Sunil

On Sun, Apr 10, 2022 at 9:18 PM Weiwei Yang  wrote:

> Hi all
>
> The old meeting link in our google calendar no longer works, we are working
> on updating them. We will send out a notification once we get everything
> fixed. And this week (Apr 12th) meeting for APAC will be canceled, we'd
> likely resume the meeting from the week after. Sorry for the
> inconvenience and please be patient with us. Thank you!
>
> Weiwei
>

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

[Sunil Govindan]

+1 (binding)

Thanks Craig for the efforts


   - Verified checksum and signature
   - compiled and built the binaries from source code
   - brought a yunikorn cluster locally
   - Ran basic jobs


Thanks
Sunil

On Wed, Jan 26, 2022 at 10:11 AM Craig Condit 
wrote:

> 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.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc4/ <
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc4/>
> >
> > My public key is located here:
> https://downloads.apache.org/incubator/yunikorn/KEYS <
> https://downloads.apache.org/incubator/yunikorn/KEYS>
> >
> > JIRA issues that have been resolved in this release:
> https://issues.apache.org/jira/issues/?filter=12351270 <
> https://issues.apache.org/jira/issues/?filter=12351270>
> >
> > Git tags for each component are as follows:
> >
> > incubator-yunikorn-scheduler-interface: v0.12.2-1
> > incubator-yunikorn-core: v0.12.2-1
> > incubator-yunikorn-k8shim: v0.12.2-4
> > incubator-yunikorn-web: v0.12.2-1
> > https://github.com/apache/incubator-yunikorn-release: <
> https://github.com/apache/incubator-yunikorn-release:> v0.12.2-4
> >
> > One the release is voted on and approved, all repos will be tagged
> 0.12.2 for consistency.
> >
> > Please review and vote. The vote will be open for at least 72 hours and
> closes on Monday, January 31 2022, 1pm PDT.
> >
> > [ ] +1 Approve
> > [ ] +0 No opinion
> > [ ] -1 Disapprove (and the reason why)
> >
> >
> > Thank you,
> > Craig
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

+1

Sunil

On Tue, Jan 25, 2022 at 9:09 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 is a good time to graduate YuniKorn from the ASF
> incubator and become a top-level Apache project. We have reviewed the ASF
> project maturity model [2] and provided some assessment of the project's
> maturity based on the guidelines. Details are included as the following. I
> have enough reasons to believe the project has done sustainable development
> successfully in the Apache way. Please read this and add your vote by
> replying to this email, your feedback will be much appreciated!!! Note,
> this vote is not just for committers or PPMC members, we welcome anyone in
> the community to vote, thanks!
>
> *Code, License, and Copyright*
>
> All code is maintained on github, under Apache 2.0 license. We have
> reviewed all the dependencies and ensured they do not bring any license
> issues. All the status files, license headers, and copyright are up to date.
>
> *Release*
>
> The community has released 5 releases in the past 2 years, i.e v0.8,
> v0.9, v0.10, v0,11, and v0.12. These releases were done by 5 different
> release managers [3] and indicate the community can create releases
> independently. We have also a well-documented release process, automated
> tools to help new release managers with the process.
>
> *Quality*
>
> The community has developed a comprehensive CI/CD pipeline as a guard of
> the code quality. The pipeline runs per-commit license check, code-format
> check, code-coverage check, UT, and end-to-end tests. All these are built
> as automated github actions, new contributors can easily trigger and view
> results when submitting patches.
>
> *Community*
>
> The community has developed an easy-to-read homepage for the project [4],
> the website hosts all the materials related to the project including
> versioned documentation, user docs, developer docs, design docs,
> performance docs. It provides the top-level navigation to the software
> download page, where links to all our previous releases. It also has the
> pages for the new contributors on-boarding with the project, such as how to
> join community meetings, events links, etc.
>
> The community shows appreciation to all contributors and welcomes all
> kinds of contributions (not just for code). We have built an open, diverse
> community and gathered many people to work together. With that, we have 41
> unique code contributors and some non-code contributors as well. Many of
> them have becoming to be committers and PPMC members while working with the
> community. There were 2 new mentors, 8 new committers, 4 new PPMC from 6
> different organizations [5] added in the incubating phase. And in total,
> the project has 6 mentors, 23 PPMC, and 29 committers from at least 14
> different organizations. All the info are generally available on the
> project website, including some guidelines to help people become
> committer/PPMC member [6]. Community collaboration was done in a
> wide-public, open manner, we leverage regular bi-weekly/weekly community
> meetings for 2 different timezones [7] and dev/user slack channels,
> mailing lists for offline discussions.
>
> *Independence*
>
> The project was initially donated by Cloudera, but with a diverse open
> source community, it has been operated as an independent project since it
> entered into ASF incubator. The committers and PPMC members are a group of
> passionate people from at least 14 different organizations, such as
> Alibaba, Apple, Cloudera, Databricks, LinkedIn, Microsoft, Snowflake,
> etc. The project's success is not depending on any single entity.
>
> [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> [2]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> [3] https://yunikorn.apache.org/community/download
> [4] https://yunikorn.apache.org/
> [5] https://incubator.apache.org/projects/yunikorn.html
> [6] https://yunikorn.apache.org/community/people
>
> [6]
> https://docs.google.com/document/d/165gzC7uhcKc5XDWiMYSRKBiPQBy2tDtXADUPuhGlUa0
>
>
>

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

Yes. I reached out to a couple of them and added them to the list.
We still have a gap. Will try again.

Thanks
 Sunil

On Mon, Jan 24, 2022 at 10:45 PM Chenya Zhang 
wrote:

> Subscribed to the private list! 3 -> 2 ? :)
>
> On Mon, Jan 24, 2022 at 6:02 PM Wilfred Spiegelenburg  >
> wrote:
>
> > When you check the status page [1] you will see that a wiki is no
> > longer required.
> > We can skip adding it.
> >
> > BTW: I added Chenya to the roster that increases the PPMC members not
> > subscribed to 3 again after it was down to 2.
> >
> > Wilfred
> >
> > [1] https://incubator.apache.org/projects/yunikorn.html
> >
> >
> > On Mon, 24 Jan 2022 at 13:12, Weiwei Yang  wrote:
> > >
> > > Hi Sunil
> > >
> > > I don’t think we ever have a wiki, do we still need to add that? I see
> > some projects leave that empty as well.
> > >
> > > Sent from my iPhone
> > >
> > > > On Jan 23, 2022, at 2:07 PM, Sunil Govindan 
> wrote:
> > > >
> > > > @Weiwei Yang 
> > > > Could you please add WIKI as well to this?
> > > >
> > > > Thanks
> > > > Sunil
> > > >
> > > >> On Sun, Jan 23, 2022 at 1:33 PM Weiwei Yang 
> wrote:
> > > >>
> > > >> Thank you Felix.
> > > >> I have added the initial podling status file:
> > > >>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/yunikorn.yml
> > > >> .
> > > >> Please let me know if that looks good or not.
> > > >>
> > > >>> On Sat, Jan 22, 2022 at 10:18 PM Sunil Govindan  >
> > wrote:
> > > >>>
> > > >>> I will reach out to them.
> > > >>>
> > > >>> Thanks
> > > >>> Sunil
> > > >>>
> > > >>> On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung <
> > felixcheun...@hotmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>> Pls add the podling status file
> > > >>>>
> > > >>>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > >>>>
> > > >>>> 3 ppmc members have not subscribed to private@
> > > >>>>
> > > >>>> These can be found on
> > > >>>> https://whimsy.apache.org/roster/ppmc/yunikorn
> > > >>>>
> > > >>>> <
> > > >>>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > >>>>>
> > > >>>> 
> > > >>>> From: Weiwei Yang 
> > > >>>> Sent: Thursday, January 20, 2022 10:05:55 PM
> > > >>>> To: dev@yunikorn.apache.org 
> > > >>>> Cc: priv...@yunikorn.apache.org 
> > > >>>> Subject: Re: Apache YuniKorn (Incubating) - Community Graduation
> > Vote
> > > >>>>
> > > >>>> hi all
> > > >>>>
> > > >>>> Most issues under the graduation preparation JIRA YUNIKORN-1005
> > > >>>> <https://issues.apache.org/jira/browse/YUNIKORN-1005> are fixed.
> > > >>>> The remaining one is the who-are-we web page, I am currently
> > collecting
> > > >>>> info for that, should be done by next week.
> > > >>>> Shall we start to vote now? I can start a new thread for the
> > community
> > > >>>> voting if nobody has objections.
> > > >>>>
> > > >>>> On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
> > > >>>> wilfr...@apache.org>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> None of the security lists mentioned in the security page [1] are
> > > >>>>> moderated. They are private lists, i.e. not openly available for
> > > >>>>> browsing in an archive, but not moderated. Using the private@
> for
> > > >>>>> YuniKorn does not seem to line up with what other projects do
> > either.
> > > >>>>> None of the recently graduated projects mention anything like
> using
> > > >>>>> the private@ maili

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

@Weiwei Yang 
Could you please add WIKI as well to this?

Thanks
Sunil

On Sun, Jan 23, 2022 at 1:33 PM Weiwei Yang  wrote:

> Thank you Felix.
> I have added the initial podling status file:
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/yunikorn.yml
> .
> Please let me know if that looks good or not.
>
> On Sat, Jan 22, 2022 at 10:18 PM Sunil Govindan  wrote:
>
> > I will reach out to them.
> >
> > Thanks
> > Sunil
> >
> > On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung 
> > wrote:
> >
> > > Pls add the podling status file
> > >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > >
> > > 3 ppmc members have not subscribed to private@
> > >
> > > These can be found on
> > > https://whimsy.apache.org/roster/ppmc/yunikorn
> > >
> > > <
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > >
> > > 
> > > From: Weiwei Yang 
> > > Sent: Thursday, January 20, 2022 10:05:55 PM
> > > To: dev@yunikorn.apache.org 
> > > Cc: priv...@yunikorn.apache.org 
> > > Subject: Re: Apache YuniKorn (Incubating) - Community Graduation Vote
> > >
> > > hi all
> > >
> > > Most issues under the graduation preparation JIRA YUNIKORN-1005
> > > <https://issues.apache.org/jira/browse/YUNIKORN-1005> are fixed.
> > > The remaining one is the who-are-we web page, I am currently collecting
> > > info for that, should be done by next week.
> > > Shall we start to vote now? I can start a new thread for the community
> > > voting if nobody has objections.
> > >
> > > On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
> > > wilfr...@apache.org>
> > > wrote:
> > >
> > > > None of the security lists mentioned in the security page [1] are
> > > > moderated. They are private lists, i.e. not openly available for
> > > > browsing in an archive, but not moderated. Using the private@ for
> > > > YuniKorn does not seem to line up with what other projects do either.
> > > > None of the recently graduated projects mention anything like using
> > > > the private@ mailing list on their sites. They all have just used
> the
> > > > general security link mentioned on their site unless they have a
> > > > specific security@ list. YuniKorn would be the one standing out from
> > > > what seems to be the norm.
> > > > Examples from the last 2 years of graduated projects using a simple
> > > > link or a text pointing to [1]: Pinot, Dolphinscheduler, Ratis,
> > > > Echarts, Gobblin, TVM, Superset and Datasketches. There are more but
> I
> > > > think this provides an overview of what is expected on graduation.
> > > >
> > > > Wilfred
> > > >
> > > > [1] https://www.apache.org/security/
> > > >
> > > > On Tue, 11 Jan 2022 at 18:21, Weiwei Yang  wrote:
> > > > >
> > > > > Hi Wilfred
> > > > >
> > > > > Adding a security@ mailing list sounds like a good idea, but I do
> > not
> > > > think that is required in the current stage.
> > > > > We can do that post-graduate. For now, the Apache security doc said
> > > > >
> > > > > > We strongly encourage you to report potential security
> > > vulnerabilities
> > > > to one of our private security mailing lists first, before disclosing
> > > them
> > > > in a public forum.
> > > > >
> > > > > I do not see any issue if we use our private@ mailing list for
> this
> > > > purpose.
> > > > >
> > > > > On Mon, Jan 10, 2022 at 11:01 PM Wilfred Spiegelenburg <
> > > > wilfr...@apache.org> wrote:
> > > > >>
> > > > >> The private@ is a moderated list. This has two issues: a
> moderator
> > > > >> needs to approve any message not sent by a PMC member. This will
> > slow
> > > > >> down the process of interaction with the reporter. It would also
> not
> > > > >> reach the YuniKorn committers group as not all committers are part
> > of
> > > > >> the PMC. Security issues should be handled and worked on by all
> > > > >> committers not just by the PMC members.
> > > > >>
> > > >

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

I will reach out to them.

Thanks
Sunil

On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung 
wrote:

> Pls add the podling status file
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>
> 3 ppmc members have not subscribed to private@
>
> These can be found on
> https://whimsy.apache.org/roster/ppmc/yunikorn
>
>  >
> 
> From: Weiwei Yang 
> Sent: Thursday, January 20, 2022 10:05:55 PM
> To: dev@yunikorn.apache.org 
> Cc: priv...@yunikorn.apache.org 
> Subject: Re: Apache YuniKorn (Incubating) - Community Graduation Vote
>
> hi all
>
> Most issues under the graduation preparation JIRA YUNIKORN-1005
>  are fixed.
> The remaining one is the who-are-we web page, I am currently collecting
> info for that, should be done by next week.
> Shall we start to vote now? I can start a new thread for the community
> voting if nobody has objections.
>
> On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
> wilfr...@apache.org>
> wrote:
>
> > None of the security lists mentioned in the security page [1] are
> > moderated. They are private lists, i.e. not openly available for
> > browsing in an archive, but not moderated. Using the private@ for
> > YuniKorn does not seem to line up with what other projects do either.
> > None of the recently graduated projects mention anything like using
> > the private@ mailing list on their sites. They all have just used the
> > general security link mentioned on their site unless they have a
> > specific security@ list. YuniKorn would be the one standing out from
> > what seems to be the norm.
> > Examples from the last 2 years of graduated projects using a simple
> > link or a text pointing to [1]: Pinot, Dolphinscheduler, Ratis,
> > Echarts, Gobblin, TVM, Superset and Datasketches. There are more but I
> > think this provides an overview of what is expected on graduation.
> >
> > Wilfred
> >
> > [1] https://www.apache.org/security/
> >
> > On Tue, 11 Jan 2022 at 18:21, Weiwei Yang  wrote:
> > >
> > > Hi Wilfred
> > >
> > > Adding a security@ mailing list sounds like a good idea, but I do not
> > think that is required in the current stage.
> > > We can do that post-graduate. For now, the Apache security doc said
> > >
> > > > We strongly encourage you to report potential security
> vulnerabilities
> > to one of our private security mailing lists first, before disclosing
> them
> > in a public forum.
> > >
> > > I do not see any issue if we use our private@ mailing list for this
> > purpose.
> > >
> > > On Mon, Jan 10, 2022 at 11:01 PM Wilfred Spiegelenburg <
> > wilfr...@apache.org> wrote:
> > >>
> > >> The private@ is a moderated list. This has two issues: a moderator
> > >> needs to approve any message not sent by a PMC member. This will slow
> > >> down the process of interaction with the reporter. It would also not
> > >> reach the YuniKorn committers group as not all committers are part of
> > >> the PMC. Security issues should be handled and worked on by all
> > >> committers not just by the PMC members.
> > >>
> > >> The security notification update made to the website I think does not
> > >> line up with the security guidelines referenced in the link provided
> > >> in the dropdown menu of the YuniKorn site [1]. In that link there is a
> > >> well defined way to report security issues. If we need to enhance and
> > >> extend what we do we either establish a security@ mailing list and
> > >> provide a static page with security related information on our site or
> > >> we leave it as is. My preference would be to establish a security@
> > >> list and make all committers a member of that list.
> > >>
> > >> I think we need to roll back the website changes part of YUNIKORN-1006
> > >> [2] in PR [3] for the website.
> > >>
> > >> Wilfred
> > >>
> > >> [1] https://www.apache.org/security/
> > >> [2] https://issues.apache.org/jira/browse/YUNIKORN-1006
> > >> [3] https://github.com/apache/incubator-yunikorn-site/pull/105
> > >>
> > >> On Tue, 11 Jan 2022 at 04:45, Holden Karau 
> > wrote:
> > >> >
> > >> > For "The project provides a well-documented, secure and private
> > channel to report security issues, along with a documented way of
> > responding to them.' the standard that I've seen used is to tell people
> to
> > e-mail private@ when they think they might have a security related
> issue.
> > I think that would probably work well for Yunikorn too.
> > >> >
> > >> >
> > >> > On Mon, Jan 10, 2022 at 7:04 AM Chenya Zhang <
> > chenyazhangche...@gmail.com> wrote:
> > >> >>
> > >> >> Hi Weiwei,
> > >> >>
> > >> >> Thanks for driving this! The evaluation is quite comprehensive
> > overall. I checked our Apache project maturity guidelines and noticed the
> > below three items. Not sure if we already have them but they are not
> > blockers to our graduation. We could think more about them along the way

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

[Sunil Govindan]

+1 (binding)

- Built from source
- Deployed on local k8s cluster
- Ran basic jobs
- Verified checksum and signature
- UI looks good.

Thanks
Sunil

On Fri, Jan 21, 2022 at 10:23 AM 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-rc3/ <
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc3/>
>
> My public key is located here:
> https://downloads.apache.org/incubator/yunikorn/KEYS <
> https://downloads.apache.org/incubator/yunikorn/KEYS>
>
> JIRA issues that have been resolved in this release:
> https://issues.apache.org/jira/issues/?filter=12351270 <
> https://issues.apache.org/jira/issues/?filter=12351270>
>
> Git tags for each component are as follows:
>
> incubator-yunikorn-scheduler-interface: v0.12.2-1
> incubator-yunikorn-core: v0.12.2-1
> incubator-yunikorn-k8shim: v0.12.2-3
> incubator-yunikorn-web: v0.12.2-1
> https://github.com/apache/incubator-yunikorn-release: v0.12.2-3
>
> One the release is voted on and approved, all repos will be tagged 0.12.2
> for consistency.
>
> Please review and vote. The vote will be open for at least 72 hours and
> closes on Tuesday, January 25 2022, 1pm PDT.
>
> [ ] +1 Approve
> [ ] +0 No opinion
> [ ] -1 Disapprove (and the reason why)
>
>
> Thank you,
> Craig

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

[Sunil Govindan]

A late +1 (binding) from me.

I build this from source
- Ran basic spark job
- Verified UI
- Checked signature.
- Checked the images.

Thanks
Sunil

On Wed, Jan 19, 2022 at 8:44 AM Craig Condit  wrote:

> 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 <
> https://lists.apache.org/thread/1gw0k0g5fy86r8ljnjttdco04w7z5j4j>
>
> Thank you to all the members who helped verify this release. We will move
> to IPMC voting shortly.
>
>
> Thanks,
> Craig
>
>
>

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

[Sunil Govindan]

I think this will help our customers who are stuck with K8s 1.22 issue
before 1.0 is out.

+1 to the proposal

Thanks
Sunil

On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg 
wrote:

> Over the last weeks Craig and I have been working on getting the
> admission controller deployment updated. These changes were committed
> yesterday as YUNIKORN-941. The main goal was to move away from old K8s
> objects and API calls and remove the scripts for certificate creation.
>
> With the changes committed deployments and e2e tests against K8s1.22
> and K8s 1.23 are no longer failing.
> I would like to propose that we release v0.12.2 with just the changes
> for the admission controller to allow deployments on the latest
> versions of K8s. Since Craig is the person that has been driving this
> code change I would like to propose him as the release manager.
>
> This is the list of changes related to YUNIKORN-941. It includes a
> number of other jiras as they are all fixed by the new deployment:
> * YUNIKORN-995
> * YUNIKORN-938
> * YUNIKORN-947
> * YUNIKORN-625
> * YUNIKORN-726
> It has one jira it dependents on: YUNIKORN-928
>
> Wilfred
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

Yes, Chenya.
I found that very troubling as well.

We have to clean that up. Thanks for chiming in.

Thanks
Sunil

On Mon, Jan 10, 2022 at 6:57 PM Chenya Zhang 
wrote:

> 👍
>
> Another thing in my mind is our PR code check... :D
>
> The "check warning" from Codecov is everywhere which makes our PR review
> inconvenient. I'm not sure if the ASF board will randomly check our PRs and
> find it not ideal.
>
> If there is no ticket tracking this, I could help to create one and do
> some investigation there.
>
> Thanks,
> Chenya
>
> On Mon, Jan 10, 2022 at 12:49 PM Sunil Govindan  wrote:
>
>> I created YUNIKORN-1007
>> <https://issues.apache.org/jira/browse/YUNIKORN-1007>
>>
>> We have to look at LC20 more closely given the public artifacts that we
>> have.
>>
>> + @Wilfred Spiegelenburg 
>>
>> Thanks
>> Sunil
>>
>> On Mon, Jan 10, 2022 at 11:59 AM Chenya Zhang <
>> chenyazhangche...@gmail.com>
>> wrote:
>>
>> > Thanks Weiwei for creating the tickets! I will help to work on
>> > https://issues.apache.org/jira/browse/YUNIKORN-1006 to address QU 30,
>> 40,
>> > 50.
>> >
>> > On Mon, Jan 10, 2022 at 10:21 AM Weiwei Yang  wrote:
>> >
>> >> I think we can add some documents to clearly address QU 30, 40, 50.
>> >> I have created a task under YUNIKORN-1005
>> >> <https://issues.apache.org/jira/browse/YUNIKORN-1005> to address them.
>> >> Thank you Chenya, Holden for your feedback, please comment more if
>> there
>> >> is
>> >> anything else outstanding.
>> >>
>> >> On Mon, Jan 10, 2022 at 9:45 AM Holden Karau 
>> >> wrote:
>> >>
>> >> > For "The project provides a well-documented, secure and private
>> channel
>> >> to
>> >> > report security issues, along with a documented way of responding to
>> >> them.'
>> >> > the standard that I've seen used is to tell people to e-mail private@
>> >> > when they think they might have a security related issue. I think
>> that
>> >> > would probably work well for Yunikorn too.
>> >> >
>> >> >
>> >> > On Mon, Jan 10, 2022 at 7:04 AM Chenya Zhang <
>> >> chenyazhangche...@gmail.com>
>> >> > wrote:
>> >> >
>> >> >> Hi Weiwei,
>> >> >>
>> >> >> Thanks for driving this! The evaluation is quite comprehensive
>> >> overall. I
>> >> >> checked our Apache project maturity guidelines and noticed the below
>> >> three
>> >> >> items. Not sure if we already have them but they are not blockers to
>> >> our
>> >> >> graduation. We could think more about them along the way.
>> >> >>
>> >> >> QU30
>> >> >>
>> >> >> The project provides a well-documented, secure and private channel
>> to
>> >> >> report security issues, along with a documented way of responding to
>> >> them.
>> >> >>
>> >> >> QU40
>> >> >>
>> >> >> The project puts a high priority on backwards compatibility and
>> aims to
>> >> >> document any incompatible changes and provide tools and
>> documentation
>> >> to
>> >> >> help users transition to new features.
>> >> >>
>> >> >> CO50
>> >> >>
>> >> >> The project documents how contributors can earn more rights such as
>> >> >> commit access or decision power, and applies these principles
>> >> consistently.
>> >> >>
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Chenya
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Mon, Jan 10, 2022 at 12:00 AM 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 is a good time to graduate YuniKorn from the
>> ASF
>> >> >>> incubator and become a top-level Apache project. We have reviewed
>> the
>> >&g

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

I created YUNIKORN-1007


We have to look at LC20 more closely given the public artifacts that we
have.

+ @Wilfred Spiegelenburg 

Thanks
Sunil

On Mon, Jan 10, 2022 at 11:59 AM Chenya Zhang 
wrote:

> Thanks Weiwei for creating the tickets! I will help to work on
> https://issues.apache.org/jira/browse/YUNIKORN-1006 to address QU 30, 40,
> 50.
>
> On Mon, Jan 10, 2022 at 10:21 AM Weiwei Yang  wrote:
>
>> I think we can add some documents to clearly address QU 30, 40, 50.
>> I have created a task under YUNIKORN-1005
>>  to address them.
>> Thank you Chenya, Holden for your feedback, please comment more if there
>> is
>> anything else outstanding.
>>
>> On Mon, Jan 10, 2022 at 9:45 AM Holden Karau 
>> wrote:
>>
>> > For "The project provides a well-documented, secure and private channel
>> to
>> > report security issues, along with a documented way of responding to
>> them.'
>> > the standard that I've seen used is to tell people to e-mail private@
>> > when they think they might have a security related issue. I think that
>> > would probably work well for Yunikorn too.
>> >
>> >
>> > On Mon, Jan 10, 2022 at 7:04 AM Chenya Zhang <
>> chenyazhangche...@gmail.com>
>> > wrote:
>> >
>> >> Hi Weiwei,
>> >>
>> >> Thanks for driving this! The evaluation is quite comprehensive
>> overall. I
>> >> checked our Apache project maturity guidelines and noticed the below
>> three
>> >> items. Not sure if we already have them but they are not blockers to
>> our
>> >> graduation. We could think more about them along the way.
>> >>
>> >> QU30
>> >>
>> >> The project provides a well-documented, secure and private channel to
>> >> report security issues, along with a documented way of responding to
>> them.
>> >>
>> >> QU40
>> >>
>> >> The project puts a high priority on backwards compatibility and aims to
>> >> document any incompatible changes and provide tools and documentation
>> to
>> >> help users transition to new features.
>> >>
>> >> CO50
>> >>
>> >> The project documents how contributors can earn more rights such as
>> >> commit access or decision power, and applies these principles
>> consistently.
>> >>
>> >>
>> >> Thanks,
>> >>
>> >> Chenya
>> >>
>> >>
>> >>
>> >> On Mon, Jan 10, 2022 at 12:00 AM 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 is a good time to graduate YuniKorn from the ASF
>> >>> incubator and become a top-level Apache project. We have reviewed the
>> ASF
>> >>> project maturity model [2] and provided some assessment of the
>> project's
>> >>> maturity based on the guidelines. Details are included as the
>> following.
>> >>> Please read this and share your thoughts by replying to this email,
>> your
>> >>> feedback will be much appreciated!!!
>> >>>
>> >>> *Code, License, and Copyright*
>> >>>
>> >>> All code is maintained on github, under Apache 2.0 license. We have
>> >>> reviewed all the dependencies and ensured they do not bring any
>> license
>> >>> issues. All the status files, license headers, and copyright are up to
>> >>> date.
>> >>>
>> >>> *Release*
>> >>>
>> >>> The community has released 5 releases in the past 2 years, i.e v0.8,
>> >>> v0.9,
>> >>> v0.10, v0,11, and v0.12. These releases were done by 5 different
>> release
>> >>> managers [3] and indicate the community can create releases
>> >>> independently.
>> >>> We have also a well-documented release process, automated tools to
>> help
>> >>> new
>> >>> release managers with the process.
>> >>>
>> >>> *Quality*
>> >>>
>> >>> The community has developed a comprehensive CI/CD pipeline as a guard
>> of
>> >>> the code quality. The pipeline runs per-commit license check,
>> code-format
>> >>> check, code-coverage check, UT, and end-to-end tests. All these are
>> built
>> >>> as automated github actions, new contributors can easily trigger and
>> view
>> >>> results when submitting patches.
>> >>>
>> >>> *Community*
>> >>>
>> >>> The community has developed an easy-to-read homepage for the project
>> [4],
>> >>> the website hosts all the materials related to the project including
>> >>> versioned documentation, user docs, developer docs, design docs,
>> >>> performance docs. It provides the top-level navigation to the software
>> >>> download page, where links to all our previous releases. It also has
>> the
>> >>> pages for the new contributors on-boarding with the project, such as
>> how
>> >>> to
>> >>> join community meetings, events links, etc.
>> >>>
>> >>> The community shows appreciation to all contributors and welcomes all
>> >>> kinds
>> >>> of contributions (not just for code). We have built an open, diverse
>> >>> community and gathered many people to work together. With that, we
>> have
>> >>> 41
>> >>> unique code contributors and some non-code contributors as well. Many

Re: Form a process of YuniKorn Improvement Proposal (YIP)

[Sunil Govindan]

Thanks, Bowen for initiating this.

As an incubating project, do we have permission to define such a process?
And will there be any change once we become a top-level project?

Also, this adds more clarity to the by-laws as well in terms of defining
the structure and process moving forward.
+1

Thank You
Sunil

On Wed, Jan 5, 2022 at 4:32 PM Chaoran Yu  wrote:

> This will be a great initiative to introduce more structure to how we
> handle larger-scale features and improvements.
> So far we have been doing things in an ad-hoc way, which tends to get less
> effective as the community grows.
> +1 from me.
>
> On Wed, Jan 5, 2022 at 4:26 PM Weiwei Yang  wrote:
>
> > Oops, got it wrong, you mean broader review, not ASF board.
> > Sorry, please ignore my last comment : )
> >
> > On Wed, Jan 5, 2022 at 4:25 PM Weiwei Yang  wrote:
> >
> > > Hi Bowen
> > >
> > > +1
> > > Having a formal process will definitely help the cross-org
> communication.
> > > Do we need the ASF board to review this? I am not sure, usually, each
> > > project committee is able to decide what is the best for the project.
> > >
> > > Thanks
> > >
> > > On Wed, Jan 5, 2022 at 4:07 PM Bowen Li  wrote:
> > >
> > >> Hi all,
> > >>
> > >> I'd like to start conversation of building a formal process of
> YuniKorn
> > >> Improvement Proposal (YIP).
> > >>
> > >> (X)IP is a common approach to propose, discuss, collaborate on and
> > tackle
> > >> major or important changes in open source projects and communities.
> > Within
> > >> Apache projects, there're successful examples and adoptions like Spark
> > >> (SPIP), Flink (FLIP), Kafka (KIP).
> > >>
> > >> Similarly, a YIP will define the following parts, including but not
> > >> limited
> > >> to:
> > >> - what's considered a "major change" that needs a YIP
> > >> - what should be included in a YIP (e.g. motivation/business
> > >> justifications, use case requirements, proposed changes, API changes,
> > >> migration/compatibility, rejected alternatives, etc)
> > >> - who should initiate or be involved in a YIP
> > >> - end-to-end process
> > >>
> > >> YK community has been growing, and we've seen cases where such a
> process
> > >> can help to better facilitate communications, understanding, and
> > >> collaborations within YK community.
> > >>
> > >> Please share your thoughts, or +1/-1. If we get a consensus this is
> > good,
> > >> I
> > >> will submit a draft for YIP for broader review.
> > >>
> > >> Thanks,
> > >> Bowen
> > >>
> > >
> >
>

Re: [DISCUSS] Graduate YuniKorn from Apache Incubator

[Sunil Govindan]

I think we can aim for Feb'22, considering we can close all the tasks that
we planned.
We had these discussions earlier, and it is great to see that we are in
much better shape.

Let's go ahead with the TLP path and the work required to complete it.
@Wilfred Spiegelenburg  and @Weiwei Yang
, I referred to a few of the recent TLP threads and come
up with a list of items that they were focussing.

If there are no objections, let's go to the next step of tasks.

Great to see this feedbacks across. Thanks, team.

Thanks,
Sunil

On Tue, Jan 4, 2022 at 8:54 AM Chaoran Yu  wrote:

> +1 from me. I agree we can get started on the graduation process now.
>
>
> > On Jan 4, 2022, at 08:39, Weiwei Yang  wrote:
> >
> > Hi all
> >
> > Thanks for the feedback!
> > Aiming for the next board meeting sounds good to me. This thread is to
> > collect feedback, so please +1 if you think we are good to get started.
> > Thank you Wilfred for putting an eye on the name search and fixing the
> > whimsy.
> >
> > On Tue, Jan 4, 2022 at 2:14 AM Wilfred Spiegelenburg <
> wilfr...@apache.org>
> > wrote:
> >
> >> I think that is cutting it too close. The board meeting is in 2 weeks.
> >> The incubator needs to file its report a week before that on the 12th.
> >> That leaves us with just a week to finish up everything.
> >> We have not done all the work yet  that we need to do (administrative)
> >> and we still need to go through the two voting rounds also.
> >>
> >> I would feel more comfortable aiming for the next meeting which is in
> >> mid February.
> >>
> >> Wilfred
> >>
> >> On Tue, 4 Jan 2022 at 17:27, Wei-Chiu Chuang 
> wrote:
> >>>
> >>> I think it's the time.
> >>> Do we want to propose it as part of the January board meeting report?
> >>> Time's running out.
> >>>
> >>> On Tue, Jan 4, 2022 at 2:08 PM Wilfred Spiegelenburg <
> >> wilfr...@apache.org>
> >>> wrote:
> >>>
>  Graduation is not linked to any release. It is purely a project
> status.
>  There are still a number of things that need to be completed before we
>  can graduate.
>  But I think we should start the discussion and the process to
> graduate.
> 
>  One of the points I cleared up today is the podling name search [1].
>  I fixed the whimsy scans that we should pass before graduation via
> [2].
> 
>  Wilfred
> 
>  [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-193
>  [2] https://issues.apache.org/jira/browse/YUNIKORN-856
> 
>  On Tue, 4 Jan 2022 at 16:45, Chenya Zhang <
> chenyazhangche...@gmail.com
> >>>
>  wrote:
> >
> > Thanks Weiwei for initiating this discussion!
> >
> > So happy to see all the milestones achieved by YuniKorn in the past
> >> two
> > years. Big Kudos to the whole community!
> >
> > A few follow-up questions, do we plan to release the plug-in
> >> framework
> > before graduating from Apache Incubator? Any potential timeline is
> >> needed
> > for 1.00 release?
> >
> > Thanks,
> > Chenya
> >
> > On Mon, Jan 3, 2022 at 9:20 PM Weiwei Yang  wrote:
> >
> >> Hi, yunikorn community
> >>
> >>
> >> Happy new year!! I hope you all have an excellent start in 2022.
> >>
> >>
> >> YuniKorn started incubating in ASF on Jan/21/2020, and the project
> >> has
>  been
> >> incredibly well managed and maintained by the community in almost 2
>  years
> >> under ASF now. There were 5 releases published in a good cadence,
> >> i.e
>  v0.8,
> >> v0.9, v0.10, v0,11, and v0.12. The community works closely
> >> together to
> >> build better open-source software and is committed to success
> >> together.
> >> Since incubating in ASF, the project has:
> >>
> >>
> >>   - Added 2 new mentors, 8 new committers, 2 new PPMC from 6
> >> different
> >>   organizations [1].
> >>   - Published 5 releases by 5 different release managers [2]
> >>   - Regular bi-weekly/weekly community meetings for 2 different
>  timezones,
> >>   meeting minutes recorded here [3]
> >>   - Leveraged mailing list and slack channel for various offline
> >>   discussions, i.e user/dev groups
> >>   - The community co-operates the YouTube channel, with many
>  demo/intro
> >>   videos published [4]
> >>
> >> Now the project has 6 mentors, 21 PPMC, and 27 committers from 14
>  different
> >> organizations. I have enough reasons to believe the project has
> >> done
> >> sustainable development successfully in the Apache way. Thanks to
> >> all
>  the
> >> mentors, committers, release managers, contributors, and
>  evangelists!!! I
> >> have reviewed the Apache maturity doc, I don’t see anything that
>  blocks us
> >> from graduating from the incubator. Therefore, I want to raise this
> >> discussion in the community, appreciate your feedback!!
> >>
> >>
> >> [1] https://incubator.apache.org/projects/yunik

Re: Apache YuniKorn (Incubating) 0.12.1 Released

[Sunil Govindan]

Congratulations 👏

Thanks, Chaoran for the efforts.

Sunil

On Mon, Dec 27, 2021 at 8:02 AM Chenya Zhang 
wrote:

> Thanks Chaoran for the great efforts!
>
> Look forward to our 1.0 release and graduation from the Apache incubator!
>
> Best,
> Chenya
>
> On Sun, Dec 26, 2021 at 11:35 PM Weiwei Yang  wrote:
>
> > Hi Chaoran
> >
> > This is awesome, thank you for getting our release out!!
> >
> > On Sun, Dec 26, 2021 at 10:16 PM Chaoran Yu 
> > wrote:
> >
> > > I forgot to mention that the source code and convenience images can be
> > > found at the Downloads page:
> > > https://yunikorn.apache.org/community/download <
> > > https://yunikorn.apache.org/community/download>
> > >
> > > The Artifact Hub
> https://artifacthub.io/packages/helm/yunikorn/yunikorn
> > <
> > > https://artifacthub.io/packages/helm/yunikorn/yunikorn> has been
> updated
> > > with the latest Helm chart.
> > >
> > >
> > > > On Dec 26, 2021, at 22:09, 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/1h3s77jo977qjf8c3w34flj6lj307yks <
> > > https://lists.apache.org/thread/1h3s77jo977qjf8c3w34flj6lj307yks>.
> > > >
> > > > Now we are officially announcing that v0.12.1 is released. The
> release
> > > notes can be found at
> > https://yunikorn.apache.org/release-announce/0.12.1
> > > . Thanks to all
> the
> > > folks who contributed to this release!
> > > >
> > > > Hope everyone is having a great holiday break. Let’s regroup in the
> new
> > > year to achieve even bigger goals, among them the 1.0 release and
> > > graduation from the Apache incubator!
> > > >
> > > > Cheers,
> > > > Chaoran
> > > >
> > >
> > >
> >
>

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

[Sunil Govindan]

+1 binding

I checked the following
- built from the source and locally ran on a minikube
- check signature and checksum
- checked docs

Thanks
Sunil


On Fri, Dec 17, 2021 at 12:38 PM Chaoran Yu  wrote:

> Thank you everyone for voting! The deadline (12/17 1pm PDT) is almost here
> but we still need one more binding vote from a member of the PPMC to pass
> the release.
> To give more time to the PPMC members who haven't voted yet and given
> the upcoming weekend, I'm extending the deadline.
> Now the vote will close on *Monday 12/20 5pm PDT*.
>
> On Wed, Dec 15, 2021 at 7:42 PM Chenya Zhang 
> wrote:
>
> > +1
> >
> > Verified the following:
> > - Built from source
> > - Docker image
> > - Signature
> > - Installed with Helm Charts
> > - REST API, Web UI
> > - Triggered simple jobs and checked scheduling, events, logs
> > - Unit tests
> >
> > On Wed, Dec 15, 2021 at 10:13 AM Peter Bacsko  wrote:
> >
> > > +1 (non-binding)
> > >
> > > Verified the following:
> > > * Signature
> > > * Hash
> > > * Built image locally
> > > * Installed YK with helm on Minikube
> > > * Run sleep batch job
> > > * Checked some REST endpoints (nodes/queues/apps/statedump/loglevel)
> > > * Checked YK logs
> > >
> > > BR,
> > > Peter
> > >
> > > On Wed, Dec 15, 2021 at 6:58 PM Craig Condit 
> > > wrote:
> > >
> > > > +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:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I'd like to call a vote for a release candidate for Apache YuniKorn
> > > > (incubating) 0.12.1 release.
> > > > >
> > > > > The release artifacts have been uploaded to
> > > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.1/ <
> > > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.1/>
> > > > >
> > > > > My public key is located here
> > > > https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS <
> > > > https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS>
> > > > >
> > > > > The release has been tagged with "v0.12.1" in all our git
> > repositories.
> > > > >
> > > > > The JIRA issues that have been resolved in this release can be
> found
> > > > here <
> > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350843
> > > >.
> > > > >
> > > > > Please review and vote. The vote will be open for at least 72 hours
> > and
> > > > > closes on Friday, December 17 2021, 1pm PDT.
> > > > >
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove (and the reason why)
> > > > >
> > > > >
> > > > > Thank you,
> > > > > Chaoran
> > > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New committer: Craig Condit

[Sunil Govindan]

Congratulations Craig, welcome aboard!

Thanks
Sunil

On Sun, Nov 14, 2021 at 4:44 PM Wilfred Spiegelenburg 
wrote:

> The Project Management Committee (PMC) for Apache YuniKorn has invited
> Craig to
> become a committer and we are pleased to announce that he has accepted.
> Please join me in congratulating him.
>
> Congratulations & Welcome aboard Craig!
>
> Wilfred
> on behalf of The Apache YuniKorn PPMC
>

Re: Prepare for YuniKorn Nov 18th Meetup

[Sunil Govindan]

Hello Folks,

Here is our Twitter feed for the upcoming meetup.
https://twitter.com/YuniKorn_Sched/status/1459906107279757316

Thanks
Sunil

On Fri, Oct 29, 2021 at 5:42 PM Weiwei Yang  wrote:

> Awesome, thank you Chenya!
>
> On Fri, Oct 29, 2021 at 4:39 PM Chenya Zhang 
> wrote:
>
>> + Our LinkedIn event posted:
>> https://www.linkedin.com/events/6859992516305932288/
>>
>> On Fri, Oct 29, 2021 at 3:00 PM Weiwei Yang  wrote:
>>
>> > Thanks. Info updated to: http://yunikorn.apache.org/community/sessions
>> > Please spread this out via twitter, linkedin, etc.
>> >
>> > On Fri, Oct 29, 2021 at 8:53 AM Chenya Zhang <
>> chenyazhangche...@gmail.com>
>> > wrote:
>> >
>> > > Hey devs,
>> > >
>> > > This is the blurb for our meetup. Thanks to Wilfred to provide the
>> > details
>> > > <
>> >
>> https://docs.google.com/document/d/1-NP0J22-Gp3cZ_hfKyA9htXJw7tlk-BmljF-7CBJg44/edit?usp=sharing
>> > >
>> > > !
>> > >
>> > > Feedback welcome! Sending it out today.
>> > >
>> > > *A Big Milestone for Apache YuniKorn (Incubating)**Time*
>> > > Nov. 18th, 4:30 - 6:00 pm PST*Location*
>> > > Online (TBD)*Topic*
>> > > Apache YuniKorn (Incubating) has released v0.11 earlier this year
>> with a
>> > > number of new features and improvements like Gang scheduling, REST API
>> > > enhancements and Kubernetes 1.19 support. In a month, we are planning
>> the
>> > > major v1.0.0 release with Kubernetes 1.20 & 1.21 support, improved
>> node
>> > > sorting and numerous small fixes & enhancements! In this meetup, we
>> will
>> > > deep dive into the implementation of Gang scheduling behind the use of
>> > > temporary placeholder pods on Kubernetes, significant performance
>> > > improvement with simplified scheduler core code and a new node sorting
>> > > algorithm, and a future roadmap of leveraging Kubernetes plugin
>> > > architecture.
>> > >
>> > > On Sun, Oct 24, 2021 at 7:12 PM Chenya Zhang <
>> > chenyazhangche...@gmail.com>
>> > > wrote:
>> > >
>> > >> Sounds good, thanks Sunil!
>> > >>
>> > >> On Sun, Oct 24, 2021 at 4:21 PM Sunil Govindan 
>> > wrote:
>> > >>
>> > >>> Awesome. Thanks, Chenya.
>> > >>>
>> > >>> I think we are good with the initial task lists. We need more
>> > >>> participation, and I will reach to other meetup groups to send this
>> > >>> invite from their members as well.
>> > >>>
>> > >>> Thanks
>> > >>> Sunil
>> > >>>
>> > >>> On Sun, Oct 24, 2021 at 3:20 PM Chenya Zhang <
>> > >>> chenyazhangche...@gmail.com> wrote:
>> > >>>
>> > >>>> Hi devs,
>> > >>>>
>> > >>>> I created an umbrella ticket to hold necessary work for our
>> external
>> > >>>> meetup setup & broadcast. The upcoming one, as we discussed, is Nov
>> > 18th.
>> > >>>>
>> > >>>> => https://issues.apache.org/jira/browse/YUNIKORN-912
>> > >>>>
>> > >>>> Please take a look. Esp. Wilfred, Weiwei, Sunil, and Chaoran: Let
>> me
>> > >>>> know if you have questions or suggestions. Feel free to create more
>> > tasks.
>> > >>>>
>> > >>>> We are also calling for more volunteers. Please reply to this
>> email if
>> > >>>> you are interested, thanks!
>> > >>>>
>> > >>>> Best,
>> > >>>> Chenya
>> > >>>>
>> > >>>>
>> > >>>>
>> >
>>
>

Re: YK Perf benchmark

[Sunil Govindan]

This is great. Thank you Tingyao and Yuteng.
This will be helping to showcase the performance advantage of YuniKorn in
K8s.

Thanks
Sunil

On Thu, Nov 4, 2021 at 11:14 PM Chaoran Yu  wrote:

> Thanks so much Tingyao and Yuteng! These results will certainly help
> promote YuniKorn to newcomers and those who are hesitant in adopting it.
>
> On Thu, Nov 4, 2021 at 10:45 PM Weiwei Yang  wrote:
>
> > Hi all
> >
> > As you know or may not know, in the last 2 months, Tingyao and Yuteng are
> > helping to perform a new round of perf-bench marking based on the latest
> > codebase. They've done this from scratch, set up a simulated env using
> > their lab's hardware, setup up metrics servers to observe and discover
> perf
> > bottleneck, tuning the perf to a reasonably good result. I really
> > appreciate their efforts to get this done.
> >
> > Now, they are summarizing the result and preparing to update the YK
> > website with a bunch of good docs, including perf result, and benchmark
> > tutorial. This will be done before the next release time frame.
> >
> > Again, thank you Tingyao, Yuteng, this is a great example of community
> > collaboration! Well done!
> >
> > Thanks
> > Weiwei
> >
>

Re: Discussion with K8s Sig Team

[Sunil Govindan]

Thanks, Chaoron.


On Thu, Nov 4, 2021 at 5:23 PM Chaoran Yu  wrote:

> Sure, let's use my list as the agenda and finalize next Wednesday
>
> On Thu, Nov 4, 2021 at 3:58 PM Sunil Govindan  wrote:
>
> > Hi Weiwei
> >
> > Yes. I suggest meeting next Wed inside of the YK community.
> > Based on that we can take a call whether to join on 18th.
> >
> > Thanks, Chaoron for summing it up. And we could use that as agenda. Is
> that
> > fine?
> >
> > Thanks
> > Sunil
> >
> > On Thu, Nov 4, 2021 at 3:21 PM Weiwei Yang  wrote:
> >
> > > I think Chaoran covered most of the questions we discussed yesterday.
> > > Sunil, are you suggesting to meet next Wed inside of the YK community
> > > before setting up a call with sig-scheduling?
> > > I noticed the next sig-scheduling meeting is Nov 18, we probably can
> try
> > to
> > > set up sometime earlier than that with a smaller group of people.
> > >
> > > On Thu, Nov 4, 2021 at 1:02 PM Chaoran Yu 
> > wrote:
> > >
> > > > Hi Sunil,
> > > >
> > > > Next Wednesday at the same time works for me. From what I understand
> in
> > > the
> > > > meeting yesterday, we want to initiate a conversation with
> > sig-scheduling
> > > > without committing to any actions just yet.
> > > >
> > > > The information we want to gather from them include the following:
> > > >
> > > > * What's the overall process and timeline when contributing a plugin?
> > > > * Besides contributing code directly in the plugins repo, can the
> code
> > > live
> > > > in an outside repo (e.g. Apache repos)? Any other options?
> > > > * The scheduler-plugins repo doesn't align with Kubernetes itself in
> > > terms
> > > > of release cadence nor does it match the latest k8s version. How is
> it
> > > > maintained?
> > > > * How does the default scheduler in the core K8s repo incorporate
> > > > community-contributed plugins? What's the process of promoting a
> > plugin?
> > > >
> > > > We can finalize the agenda when we meet next week
> > > >
> > > > On Thu, Nov 4, 2021 at 12:21 PM Sunil Govindan 
> > > wrote:
> > > >
> > > > > Hi Folks,
> > > > >
> > > > > Thanks for joining our weekly sync call.
> > > > >
> > > > > We have an action item to discuss with the SIG team sooner. Could
> we
> > > > > conclude the meeting agenda earlier within the YuniKorn community
> > > itself
> > > > > before we have that call?
> > > > > We can have one more YuniKorn community call next week to conclude
> > > before
> > > > > starting the discussion with K8s. I could help schedule this at the
> > > same
> > > > > time as yesterday (3.00 pm PST) if there are no objections.
> > > > >
> > > > > Please share your thoughts.
> > > > >
> > > > > Thanks
> > > > > Sunil
> > > > >
> > > >
> > >
> >
>

Re: Discussion with K8s Sig Team

[Sunil Govindan]

Hi Weiwei

Yes. I suggest meeting next Wed inside of the YK community.
Based on that we can take a call whether to join on 18th.

Thanks, Chaoron for summing it up. And we could use that as agenda. Is that
fine?

Thanks
Sunil

On Thu, Nov 4, 2021 at 3:21 PM Weiwei Yang  wrote:

> I think Chaoran covered most of the questions we discussed yesterday.
> Sunil, are you suggesting to meet next Wed inside of the YK community
> before setting up a call with sig-scheduling?
> I noticed the next sig-scheduling meeting is Nov 18, we probably can try to
> set up sometime earlier than that with a smaller group of people.
>
> On Thu, Nov 4, 2021 at 1:02 PM Chaoran Yu  wrote:
>
> > Hi Sunil,
> >
> > Next Wednesday at the same time works for me. From what I understand in
> the
> > meeting yesterday, we want to initiate a conversation with sig-scheduling
> > without committing to any actions just yet.
> >
> > The information we want to gather from them include the following:
> >
> > * What's the overall process and timeline when contributing a plugin?
> > * Besides contributing code directly in the plugins repo, can the code
> live
> > in an outside repo (e.g. Apache repos)? Any other options?
> > * The scheduler-plugins repo doesn't align with Kubernetes itself in
> terms
> > of release cadence nor does it match the latest k8s version. How is it
> > maintained?
> > * How does the default scheduler in the core K8s repo incorporate
> > community-contributed plugins? What's the process of promoting a plugin?
> >
> > We can finalize the agenda when we meet next week
> >
> > On Thu, Nov 4, 2021 at 12:21 PM Sunil Govindan 
> wrote:
> >
> > > Hi Folks,
> > >
> > > Thanks for joining our weekly sync call.
> > >
> > > We have an action item to discuss with the SIG team sooner. Could we
> > > conclude the meeting agenda earlier within the YuniKorn community
> itself
> > > before we have that call?
> > > We can have one more YuniKorn community call next week to conclude
> before
> > > starting the discussion with K8s. I could help schedule this at the
> same
> > > time as yesterday (3.00 pm PST) if there are no objections.
> > >
> > > Please share your thoughts.
> > >
> > > Thanks
> > > Sunil
> > >
> >
>

Discussion with K8s Sig Team

[Sunil Govindan]

Hi Folks,

Thanks for joining our weekly sync call.

We have an action item to discuss with the SIG team sooner. Could we
conclude the meeting agenda earlier within the YuniKorn community itself
before we have that call?
We can have one more YuniKorn community call next week to conclude before
starting the discussion with K8s. I could help schedule this at the same
time as yesterday (3.00 pm PST) if there are no objections.

Please share your thoughts.

Thanks
Sunil

Re: Prepare for YuniKorn Nov 18th Meetup

[Sunil Govindan]

Awesome. Thanks, Chenya.

I think we are good with the initial task lists. We need more
participation, and I will reach to other meetup groups to send this
invite from their members as well.

Thanks
Sunil

On Sun, Oct 24, 2021 at 3:20 PM Chenya Zhang 
wrote:

> Hi devs,
>
> I created an umbrella ticket to hold necessary work for our external
> meetup setup & broadcast. The upcoming one, as we discussed, is Nov 18th.
>
> => https://issues.apache.org/jira/browse/YUNIKORN-912
>
> Please take a look. Esp. Wilfred, Weiwei, Sunil, and Chaoran: Let me know
> if you have questions or suggestions. Feel free to create more tasks.
>
> We are also calling for more volunteers. Please reply to this email if you
> are interested, thanks!
>
> Best,
> Chenya
>
>
>

Re: [DISCUSS] release v1.0.0 planning

[Sunil Govindan]

+1

Yes. Lets start the planning.

Chaoran, @Chenya, and Wilfred,
Could we create a release wiki and place this timeline with a Jira filter?
I think it will be a good start for this entire process.

Thanks
Sunil


On Fri, Oct 22, 2021 at 11:54 AM Chenya Zhang 
wrote:

> Great to see that we are going to have a new 1.0.0 release!
>
> I could help Chaoran and shadow this release. Would be interested in
> becoming our next release manager but happy to take a fight when it comes.
> :D
>
> Will follow up on this thread for v1.0.0.
>
> Best,
> Chenya
>
> On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang  wrote:
>
> > Hi Craig
> >
> > I think officially supporting 3 major K8s versions should be enough, but
> we
> > need to update to 1.19, 1.20, and 1.21.
> > 1.18 is EoL per https://endoflife.date/kubernetes . If we continue our
> > release cadence, most likely we can move 1 major release at a time and
> that
> > aligns with the K8s releases.
> >
> > On Fri, Oct 22, 2021 at 9:29 AM Craig Condit 
> > wrote:
> >
> > > 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 verified that 1.21 is
> > functional.
> > >
> > > Craig
> > >
> > > > On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> > > >
> > > > Sounds great, thank you Chaoran!
> > > >
> > > > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu  >
> > > wrote:
> > > >
> > > >> Hey guys,
> > > >>
> > > >> I volunteer to be the release manager this time, if nobody else has
> > > >> volunteered already.
> > > >>
> > > >> The proposed timeline sounds right to be. It will allow for ample
> time
> > > for
> > > >> stabilization and verification.
> > > >>
> > > >> Chaoran
> > > >>
> > > >>
> > > >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang 
> wrote:
> > > >>
> > > >>> Hi Wilfred
> > > >>>
> > > >>> Thanks. Sounds good to me.
> > > >>> Does anyone want to be the release manager for 1.0? The apache way
> > > >>> encourages more people to get involved in the release process.
> > > >>>
> > > >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > > >>> wilfr...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Hi,
> > > 
> > >  We have been making big steps since our last release. Some major
> > > >> changes
> > >  have gone in and some are almost ready. The changes include:
> > >  - rest API updates
> > >  - new node storage and sorting
> > >  - upgrade to a later K8s version as a build dependency
> > >  - scheduler interface change
> > > 
> > >  Work is ongoing on generating a new set of performance figures.
> This
> > >  includes documenting how to run our performance tests so we can
> > repeat
> > > >>> them
> > >  when we want to.
> > > 
> > >  Based on all this work I would like to propose a 1.0.0 release to
> be
> > > >>> ready
> > >  for a vote by the incubator PMC by the start of December 2021.
> This
> > > >> will
> > >  give us some time to get the last fixes in and stabilise the
> > release.
> > > A
> > >  release for us is still a multistep project:
> > >  - fork and prepare the release
> > >  - vote in the project
> > >  - vote in the incubator PMC
> > >  Looking back at the last release cycles that means we should have
> a
> > > >> build
> > >  ready for voting by 22 November on the dev list. Which would mean
> > that
> > > >> we
> > >  fork the release at the latest in the second week of November.
> > > 
> > >  Please let me know if the timeline is too ambitious or not
> ambitious
> > >  enough.
> > > 
> > >  Wilfred
> > > 
> > > >>>
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > >
> > >
> >
>

Re: Broadcast YuniKorn to the Industry!

[Sunil Govindan]

Awesome!

Yes, we can create PR against our website branch and get this information
posted.
@wilfr...@apache.org  , could we create a banner on
yunikorn website for this?

Also, let's broadcast from YuniKorn twitter handle as well. Once we have
that writeup, I can help to post that.

Thanks
Sunil

On Fri, Oct 22, 2021 at 12:03 PM Chenya Zhang 
wrote:

> +1 need a short description from Wilfred, thanks!
>
> Meanwhile, I'm thinking about adding a new section "Meetup" under
> "Community" on our website and also adding a section on our homepage for
> the next event.
>
> Do we have a process that can be shared to update our website?
>
> Thanks,
> Chenya
>
> On Fri, Oct 22, 2021 at 11:42 AM Weiwei Yang  wrote:
>
> > ACK'd, sounds great.
> > We need to have a sharable message to adv this. @Wilfred Spiegelenburg
> >  , could you pls share a short description of the
> > session so we can put that in a message + planedDate + howToJoin and
> start
> > to spread?
> >
> > On Fri, Oct 22, 2021 at 7:17 AM Chenya Zhang <
> chenyazhangche...@gmail.com>
> > wrote:
> >
> > > Wonderful, thanks Sunil and Chaoran for the input!
> > >
> > > Our first speaker will be Wilfred sharing about features in the latest
> > > release, Gang scheduling, bin packing, node sorting improvement, etc.
> > >
> > > We will post an event from YuniKorn website, use LinkedIn meetup &
> posts
> > to
> > > attract more attendees, and YouTube for a live broadcast.
> > >
> > > If everyone agrees, we will finalize our 1st external meetup this year
> on
> > > Nov 18th 4:30 - 6:00pm PST.
> > >
> > > Look forward to more ideas from everyone, and let’s get ready &
> excited!
> > >
> > > Cheers,
> > > Chenya
> > >
> > >
> > > On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu 
> > > wrote:
> > >
> > > > Thanks Sunil for the input. Then let's do Nov 18th for the first
> event.
> > > > 4:30-6:00pm PST should be a good start. We can gauge interest and
> then
> > > > change time to cater to multiple time zones for alternating
> > occurrences.
> > > >
> > > >
> > > > On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan 
> > > wrote:
> > > >
> > > > > Thanks, Charon. Yes, I second this.
> > > > > Monthly events could be organized from Linkedin also. Meetup is not
> > > much
> > > > > used, I think.
> > > > >
> > > > > Let's start with November 18th, as you suggested. And each
> > alternative
> > > > > month, we can do one on PST morning and then during the evening.
> > > > > This will help to cover all time zones as we have folks from
> > Budapest,
> > > > > India, China, East Asia, and Australia.
> > > > >
> > > > > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> > > > chenyazhangche...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Sure, that sounds great!
> > > > > >
> > > > > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st
> event,
> > > how
> > > > > > does this slot fit into your schedules?
> > > > > >
> > > > > > Besides speaker talks, we could also have panel or roundtable
> > > > > discussions.
> > > > > >
> > > > > > To broadcast YuniKorn to more people, we could also find if there
> > are
> > > > > other
> > > > > > highly popular meetups in the industry and do a joint talk or
> > > > discussion.
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > Cheers,
> > > > > > Chenya
> > > > > >
> > > > > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu <
> > yuchaoran2...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Great, that works too. Chenya, do you want to schedule such a
> > > monthly
> > > > > > > meeting starting November? The first one can be during the week
> > > > before
> > > > > > > Thanksgiving. Once we finalize the schedule, we can think about
> > > > > speakers
> > > > > > > and topics.
> > > > > > >
> > > > &

Re: Broadcast YuniKorn to the Industry!

[Sunil Govindan]

Thanks, Charon. Yes, I second this.
Monthly events could be organized from Linkedin also. Meetup is not much
used, I think.

Let's start with November 18th, as you suggested. And each alternative
month, we can do one on PST morning and then during the evening.
This will help to cover all time zones as we have folks from Budapest,
India, China, East Asia, and Australia.

On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang 
wrote:

> Sure, that sounds great!
>
> If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st event, how
> does this slot fit into your schedules?
>
> Besides speaker talks, we could also have panel or roundtable discussions.
>
> To broadcast YuniKorn to more people, we could also find if there are other
> highly popular meetups in the industry and do a joint talk or discussion.
>
> Thoughts?
>
> Cheers,
> Chenya
>
> On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu 
> wrote:
>
> > Great, that works too. Chenya, do you want to schedule such a monthly
> > meeting starting November? The first one can be during the week before
> > Thanksgiving. Once we finalize the schedule, we can think about speakers
> > and topics.
> >
> > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang  wrote:
> >
> >> I am not aware of that sort of sponsorship. We can at least setup
> virtual
> >> meetings via Zoom.
> >> A monthly recurring meeting might be a good start : )
> >>
> >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu 
> >> wrote:
> >>
> >> > I second this proposal!
> >> >
> >> > Instead of a one-time event, we can do a recurring meetup (monthly or
> >> > bi-monthly) and invite YuniKorn developers and users to talk about
> their
> >> > experience and insights. A recurring event is well suited for
> >> cultivating a
> >> > community. I took a look at Meetup.com. They charge a monthly fee for
> >> > organizing a meetup group (see attached). Does ASF have any programs
> >> that
> >> > can sponsor such an effort? Or we can explore other options as well.
> >> >
> >> > Chaoran
> >> >
> >> >
> >> > On Tue, Oct 12, 2021 at 6:22 PM Weiwei Yang  wrote:
> >> >
> >> >> Hi Chenya
> >> >>
> >> >> Thanks. This is a great idea, definitely +1.
> >> >> A few suggestions:
> >> >>
> >> >>- We can call for volunteers for the 1st event
> >> >>- Once we have that decided, we need to spread this to a wider
> >> group of
> >> >>audiences, via email, twitter, LinkedIn, or ASF, etc
> >> >>- We need to publish the agenda & schedule of the next meeting on
> >> our
> >> >>web-site
> >> >>- We need to log the event recording onto the yunikorn youtube
> >> channel
> >> >>
> >> >>- Can we create a website page to track all these events?
> >> >>
> >> >> Let's start with calling for speakers : )
> >> >>
> >> >> On Tue, Oct 12, 2021 at 5:57 PM Chenya Zhang <
> >> chenyazhangche...@gmail.com
> >> >> >
> >> >> wrote:
> >> >>
> >> >> > Hi YuniKorn devs,
> >> >> >
> >> >> > We have achieved a lot together in the past year on major releases
> >> >> > including exciting new features, important bug fixes, and multiple
> >> >> > improvements!
> >> >> >
> >> >> > It could be a wonderful time for us to further broadcast YuniKorn
> to
> >> the
> >> >> > industry and welcome more people onboard.
> >> >> >
> >> >> > What could be some interesting topics and the best event time for
> >> you?
> >> >> >
> >> >> > Some starters here:
> >> >> > - Apache YuniKorn Gang Scheduling and Bin Packing?
> >> >> > - Spark on K8s Autoscaling and Cost Efficiency?
> >> >> > - Flink Stream Processing with YuniKorn?
> >> >> > - TensorFlow Model Training with YuniKorn?
> >> >> >
> >> >> > Your thoughts? :)
> >> >> >
> >> >> > Best,
> >> >> > Chenya
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> >> > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> >>
> >
>

Re: [ANNOUNCE] New committer: Chenya Zhang

[Sunil Govindan]

Congratulations Chenya!

On Thu, Sep 23, 2021 at 10:51 AM Craig Condit 
wrote:

> 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.
> >
> > Congratulations & Welcome aboard Chenya!
> >
> > Wilfred
> > on behalf of The Apache YuniKorn PPMC
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

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

[Sunil Govindan]

Congratulations Chia-Ping!

Thanks
Sunil

On Fri, Sep 24, 2021 at 3:30 AM Weiwei Yang  wrote:

> Well deserved, congrats Chia-Ping!
>
> On Wed, Sep 22, 2021 at 10:21 PM Craig Condit 
> wrote:
>
> > Congratulations Chia-Ping!
> >
> >
> > > On Sep 22, 2021, at 10:59 PM, Wilfred Spiegelenburg <
> wilfr...@apache.org>
> > 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.
> > >
> > > Congratulations & Welcome aboard Chia-Ping!
> > >
> > > Wilfred
> > > on behalf of The Apache YuniKorn PPMC
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> >
> >
>

Re: [ANNOUNCE] New committer: Manikandan R

[Sunil Govindan]

Many congratulations Mani.

Thanks,
Sunil

On Sat, Sep 25, 2021 at 12:53 PM Manikandan R  wrote:

> Hi Everyone,
>
> Thank you for your wishes and support during this journey. Looking forward
> to more contributions.
>
> Thanks,
> Mani
>
> On Fri, Sep 24, 2021 at 3:31 AM Weiwei Yang  wrote:
>
> > Hi Mani
> >
> > Congratulations!
> >
> > On Wed, Sep 22, 2021 at 10:21 PM Craig Condit 
> > wrote:
> >
> > > Congratulations Mani!
> > >
> > >
> > > > On Sep 22, 2021, at 10:56 PM, Wilfred Spiegelenburg <
> > wilfr...@apache.org>
> > > 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.
> > > >
> > > > Congratulations & Welcome aboard Mani!
> > > >
> > > > Sorry for the delay in this announcement.
> > > >
> > > > Wilfred
> > > > on behalf of The Apache YuniKorn PPMC
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > >
> > >
> >
>

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

[Sunil Govindan]

+1 (binding)

I am carrying over my previous vote here.

Thanks
Sunil

On Wed, Aug 4, 2021 at 8:13 PM Chaoran Yu  wrote:

> +1 (nonbinding). I haven't done any additional verifications since my vote
> on RC1. But since the changes are on licensing only, I'll be able to give
> my thumb up
>
> On Mon, Aug 2, 2021 at 3:05 PM Julia Kinga Marton 
> wrote:
>
> > Hi all,
> >
> > Even though the first RC passed this vote here, the IPMC found some
> > licensing issues (missing license headers), which we fixed in this second
> > RC.
> >
> > I'd like to call a vote for the second release candidate for Apache
> > YuniKorn (incubating) 0.11.0 release.
> >
> > The release artifacts are uploaded to:
> > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.11/
> >
> > My public key is located here:
> > https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
> >
> > The release has been tagged with "v0.11.0" in all our git repositories.
> >
> > The JIRA issues that have been resolved in this release can be found on
> > this link:
> > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350025
> >
> > Please review and vote. The vote will be open for at least 72 hours and
> > closes on Thursday, 5 August 2021, 12:00 PST.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and the reason why)
> >
> >
> > Thank you,
> > Kinga
> >
>

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

[Sunil Govindan]

+1

- I have verified checksum.
- all attached docs look good.
- docs look good.
- basic compilation looks good.

Thanks
Sunil


On Tue, Jul 27, 2021 at 9:57 AM Weiwei Yang  wrote:

> +1 (binding)
> All look good, I have done the following validations:
>
>1. Verified checksum
>2. Verified the release files: README, LICENSE, DISCLAIMER, NOTICE and
>CHANGELOG
>3. Verified 0.11 helm charts, image versions, and chart version
>4. Built docker images from source, verified image tags, verified
>revisions with docker inspect
>5. Installed on a K8s cluster with helm, checked pod status and logs
>6. Verified the installation with simple workloads, e.g nginx and sleep
>pods.
>7. Verified the web UI, reviewed pages for Apps/queues/nodes
>8. Verified the legacy REST APIs, as well as the new APIs, such as
>"ws/v1/partition/default/queues", "ws/v1/partition/default/nodes".
>
> Thanks!
>
> On Mon, Jul 26, 2021 at 8:27 PM Wilfred Spiegelenburg  >
> wrote:
>
> > Sorry for the late reply.
> >
> > +1 binding, verified:
> > - signature
> > - checksum
> > - build from scratch
> > - ran all unit tests
> > - started scheduler and web interface in a clean K8s cluster v1.18
> >
> > Wilfreda  WilfredW
> >
> > On Fri, 23 Jul 2021 at 04:56, kinga marton  wrote:
> >
> > > Hi all
> > >
> > > This is the first release candidate for the Apache YuniKorn
> (incubating)
> > > 0.11.0 release.
> > >
> > > The release artifacts are uploaded to:
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.11/
> > >
> > > My public key is located here:
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS
> > >
> > > The release has been tagged with "v0.11.0" in all our git repositories.
> > >
> > > The JIRA issues that have been resolved in this release can be found on
> > > this link:
> > > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350025
> > >
> > > Please review and vote. The vote will be open for at least 72 hours and
> > > closes on *Sunday, 25 July 2021, 12:00 PST*).
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and the reason why)
> > >
> > > Thank you,
> > > Kinga
> > >
> >
>

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

[Sunil Govindan]

Hi Mani and Weiwei,

Do we need to spin a new RC with these changes? or could we continue this
vote and update doc separately?

Thanks
Sunil

On Sat, Jul 24, 2021 at 10:48 AM Weiwei Yang  wrote:

> Hi Mani
>
> Yes, we should do that. But that is not part of our release tarball, we can
> update our website repo, that should be enough.
> Do you want to submit a PR for the backport? File to update:
>
> https://github.com/apache/incubator-yunikorn-site/blob/master/versioned_docs/version-0.11.0/api/scheduler.md
>
> On Fri, Jul 23, 2021 at 10:08 PM Manikandan R 
> wrote:
>
> > Thanks, Kinga.
> >
> > Weiwei, Kinga,
> >
> > Should we backport YUNIKORN-746 (Rest Api doc changes) into this release?
> >
> > Thanks,
> > Mani
> >
> > On Sat, 24 Jul, 2021, 1:46 AM Weiwei Yang,  wrote:
> >
> > > Thanks for the efforts to put all these together.
> > > I met an issue while verifying the signature, not sure if this only
> > happens
> > > to me or not.
> > > When I tried to follow the doc:
> > > https://www.apache.org/info/verification.html, to verify the signature
> > > based on your pgp KEY:
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS. The
> > > following command fails:
> > >
> > > gpg --keyserver pgpkeys.mit.edu
> EA196FD1376CFF059CA6F5379EF1E6643CC437D0
> > > gpg: keyserver receive failed: No keyserver available
> > >
> > > have you done the step:
> > >
> > >
> >
> https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#generate-a-key
> > > and
> > > uploaded your pub key to a key server? If it is not MIT key server, is
> it
> > > uploaded somewhere else?
> > >
> > > On Thu, Jul 22, 2021 at 11:56 AM kinga marton 
> > wrote:
> > >
> > > > Hi all
> > > >
> > > > This is the first release candidate for the Apache YuniKorn
> > (incubating)
> > > > 0.11.0 release.
> > > >
> > > > The release artifacts are uploaded to:
> > > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.11/
> > > >
> > > > My public key is located here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS
> > > >
> > > > The release has been tagged with "v0.11.0" in all our git
> repositories.
> > > >
> > > > The JIRA issues that have been resolved in this release can be found
> on
> > > > this link:
> > > > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350025
> > > >
> > > > Please review and vote. The vote will be open for at least 72 hours
> and
> > > > closes on *Sunday, 25 July 2021, 12:00 PST*).
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove (and the reason why)
> > > >
> > > > Thank you,
> > > > Kinga
> > > >
> > >
> >
>

Re: [ANNOUNCE] new committer: Manikandan R

[Sunil Govindan]

Great news!

Well deserved Mani. All the best, and looking forward to working with you.

Thanks
Sunil

On Tue, Jul 13, 2021 at 5:53 AM Chaoran Yu  wrote:

> Congrats Mani on a well-deserved achievement!
>
>
>
> > On Jul 12, 2021, at 17:49, Weiwei Yang  wrote:
> >
> > The Podling Project Management Committee (PMC) for Apache YuniKorn
> > (Incubating)
> > has invited Manikandan R to become a committer and we are pleased to
> > announce that he has accepted.
> >
> > On behalf of
> > Apache YuniKorn (Incubating) PPMC
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

Re: [DISCUSS] Release manager for 0.10

[Sunil Govindan]

Hi Tao,

All the best and thanks for chiming in!

Thanks
Sunil

On Sat, Jan 30, 2021 at 9:12 AM Tao Yang  wrote:

> Thanks Weiwei, I will try my best to do this work and prepare for it next
> week.
>
> Best,
> Tao
>
> Weiwei Yang  于2021年1月29日周五 下午2:03写道：
>
> > Absolutely, we'll help you go through the process.
> > With enough tools in the yunikorn-release repo, you'll be good!
> >
> > Thanks
> >
> > On Thu, Jan 28, 2021 at 7:15 PM Tao Yang  wrote:
> >
> > > Hi, Wilfred.
> > >
> > > Thanks for your efforts to keep this work going. May I have a chance to
> > be
> > > the release manager for 0.10?
> > > I have no experience about this before, but I would like to study from
> > the
> > > document you mentioned above which I think is clear enough at first,
> > > and will ask for help from you and Weiwei if there is any trouble.
> > >
> > > Thanks,
> > > Tao
> > >
> > > Wilfred Spiegelenburg  于2021年1月28日周四 下午5:14写道：
> > >
> > > > Hi All,
> > > >
> > > > As you might have noticed we have forked branch-0.10. Work is ongoing
> > to
> > > > stabilise the release and test. The major functionality in this
> release
> > > is
> > > > gang scheduling and the cache removal in the core.
> > > >
> > > > We hope to release soon as the last release was already 4 months
> ago. I
> > > am
> > > > hoping someone will volunteer to be the release manager.
> > > >
> > > > I have added a lot of documentation here [1] while working on the
> last
> > > > release. Most of the process is automated. I will be around to help
> > with
> > > > the process. If we find bits that we have not documented or steps
> where
> > > we
> > > > can improve automation I will help out with that too.
> > > >
> > > > Thank you,
> > > > Wilfred
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md
> > > >
> > >
> >
>

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

[Sunil Govindan]

Thanks Wilfred for putting this release together

+1 binding

- verified the signature and it looks good
- changelog, readme, license etc looks good
- locally built the images and binaries. This was done based on README.md
instructions.
- MINOR issue: yunikorn UI docker build reports few warnings which can be
fixed separately. This doesn't block release.
- Was able to bring up Yunikorn scheduler and admission controller via helm
chart. However I couldn't see UI pods.
- Simple ngnix deployment and sleepbox also went successfully.
- Killed few pods, and YK was able to bring them up.

Thanks
Sunil

On Thu, Aug 13, 2020 at 1:34 PM Wilfred Spiegelenburg 
wrote:

> Hi all
>
>
> This is the second release candidate RC2 for the Apache YuniKorn
> (incubating) 0.9.0 release.
>
> We have resolved 130 issues. Including an extended testing framework,
> Travis CI, improved auto scaling support and FIFO scheduling. Details are
> included in the CHANGELOG as part of the release.
>
>
> The release artifacts are uploaded to:
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
>
> My public key is located here:
>
> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
>
>
> The release has been tagged with "v0.9.0" in all our git repositories.
>
>
> The JIRA issues that have been resolved in this release can be found on
> this link
>
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
>
>
> Please review and vote. The vote will be open for at least 72 hours and
> closes on *Sunday, 16 August 2020, 17:00 PST*).
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and the reason why)
>
>
> Thank you,
>
> Wilfred
>

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

[Sunil Govindan]

Hi Wilfred

I would like to add one more point.
Its better we use name of the files like this
*apache-yunikorn-0.9.0-incubating-src.tar.gz*
We could omit RC tag from file name.

Thanks
Sunil

On Wed, Aug 12, 2020 at 5:24 PM Wilfred Spiegelenburg 
wrote:

> Thank you for the update.
>
> The app CRD changes in the helm charts should not have been there. I'll
> generate a new RC and restart the vote.
>
> Thank you,
> Wilfred
>
> On Wed, 12 Aug 2020 at 09:50, Weiwei Yang  wrote:
>
> > Thank you @wilfr...@apache.org  for driving this
> > release
> >
> >- Verified DISCLAIMER, NOTICE, LICENSE, and README
> >- Build from source, tweak the versions and registry for docker
> >images, worked fine
> >- Install scheduler using helm, worked fine
> >- Run some sample workloads on a local cluster, worked fine
> >
> > A few things found in the RC1
> >
> >- In the README file, I suggest removing the dependency requirement
> >for the web UI build, node.js, angular CI, and yarn are only needed
> for
> >developers. To build the docker image, they are not required
> >- In the README file, the command "helm install ./yunikorn"  should be
> >changed to "helm install yunikorn ./helm-charts/yunikorn" (assume
> users run
> >this from the root dir of the build, also we need a chart name
> specified
> >otherwise it won't work for helm3)
> >- In the README file, the doc ref should be:
> >https://yunikorn.apache.org/docs/
> >- The helm chart is shipped the master version, that includes some
> >fields that not supposed to be included in 0.9.0.
> >
> > I am -1 on this, suggest to roll an RC2 to get these issues fixed since
> > they are user-facing.
> >
> > On Mon, Aug 10, 2020 at 7:23 AM Wilfred Spiegelenburg <
> wilfr...@apache.org>
> > wrote:
> >
> >> Hi all
> >>
> >>
> >> This is the first release candidate for the Apache YuniKorn (incubating)
> >> 0.9.0 release.
> >>
> >> We have resolved 130 issues. Including an extended testing framework,
> >> Travis CI, improved auto scaling support and FIFO scheduling.
> >>
> >>
> >> The release artifacts are uploaded to:
> >> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
> >>
> >> My public key is located here:
> >>
> >> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
> >>
> >>
> >> The release has been tagged with "v0.9.0" in all our git repositories.
> >>
> >>
> >> The JIRA issues that have been resolved in this release can be found on
> >> this link
> >>
> >> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
> >>
> >>
> >> Please review and vote. The vote will be open for at least 72 hours and
> >> closes on *Wednesday, 13 August 2020, 17:00 PST*).
> >>
> >>
> >> [ ] +1 approve
> >>
> >> [ ] +0 no opinion
> >>
> >> [ ] -1 disapprove (and the reason why)
> >>
> >>
> >> Thank you,
> >>
> >> Wilfred
> >>
> >
>

Re: [ANNOUNCE] Commits to the repos not using github UI

[Sunil Govindan]

I will try this as well.

Thanks
Sunil

On Thu, Jun 11, 2020 at 12:16 AM Weiwei Yang  wrote:

> Hi Wilfred
>
> I think the problem with the PR merge is due to
>
> https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-on-github
> ,
> I think if the PR submitter doesn't have this box checked in their github
> setting, the email settings will be correct:
>
> Keep my email addresses private
>
> otherwise, github hides the email address. I just did a test with
> https://github.com/apache/incubator-yunikorn-release/pull/7. Please take a
> look if this is the case.
>
> Thanks!
>
> On Tue, Jun 2, 2020 at 12:24 AM Wilfred Spiegelenburg  >
> wrote:
>
> > The way github commits has been the same for a long time. It has been the
> > way github commits since they added it to the UI. From a github
> perspective
> > they cannot or will not fix this, it is linked to authentication,
> > authorisation and code sign off.
> > We will never get the committer set to anything but "Github <
> > nore...@github.com>" if you use the web UI.
> > I have gone back over more than 2 years of discussions and numerous
> support
> > tickets logged by other groups with github and it has not changed.
> >
> > It is more than just the email address that is not associated. Editing
> and
> > getting the message layout is also more difficult.
> > I am working on a way to almost fully script the process: pulling the
> > change(s), creating a local branch, squash merge into master etc. That
> > would just leave the writing of the message locally without the need to
> do
> > anything "manually"
> >
> > Wilfred
> >
> > On Tue, 2 Jun 2020 at 06:27, Weiwei Yang  wrote:
> >
> > > Hi Wilfred
> > >
> > > I just tried to follow these steps to push a commit. (I was always
> using
> > > the github merge PR button)
> > > The manual steps are quite time consuming, I think we need to fix this
> > > issue in github.
> > > IIUC, the problematic commits are caused by the PR submitter did not
> > > associate their email address while submitting the PR, if this is the
> > case,
> > > we could just ensure the user name and email are correctly set?
> > >
> > >
> > > On Mon, Jun 1, 2020 at 9:28 AM Weiwei Yang 
> wrote:
> > >
> > > > Hi Wilfred
> > > >
> > > > Thank you for putting this together. Agree to have some doc and
> > examples
> > > > and every committer should follow the same rule.
> > > > Moving on, it might also good to look at some auto-merge features,
> such
> > > as
> > > > leveraging github action or github bot to enforce these rules. That
> > might
> > > > be fun to look at as well.
> > > >
> > > > Weiwei
> > > >
> > > >
> > > > On Mon, Jun 1, 2020 at 8:41 AM Sunil Govindan 
> > wrote:
> > > >
> > > >> Thanks Wilfred
> > > >> I agree.
> > > >>
> > > >> I think we can add these to our github and mandatory params for a PR
> > > >>
> > > >> Thanks
> > > >> Sunil
> > > >>
> > > >> On Mon, Jun 1, 2020 at 9:07 PM Wilfred Spiegelenburg <
> > > wilfr...@apache.org
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > I have had only one response to this discussion. I spoke offline
> to
> > > >> Weiwei
> > > >> > and looking at the lasts commits we are losing details and get
> badly
> > > >> > formatted commit messages.
> > > >> > * Committer is the generic github account. Here is an example of a
> > > >> commit
> > > >> > from github.
> > > >> > * Badly formatted messages as github does not insert line breaks.
> > > >> >
> > > >> > Since there was no strong -1 on this I am going to add the steps
> to
> > > the
> > > >> > documentation, and ask everyone that commits to follow the simple
> > > manual
> > > >> > merge steps:
> > > >> >
> > > >> > * git checkout master
> > > >> >
> > > >> > * git pull
> > > >> >
> > > >> > * git checkout -b  master
> > > >> >
> > > >> > * git p

Re: [ANNOUNCE] Commits to the repos not using github UI

[Sunil Govindan]

Thanks Wilfred
I agree.

I think we can add these to our github and mandatory params for a PR

Thanks
Sunil

On Mon, Jun 1, 2020 at 9:07 PM Wilfred Spiegelenburg 
wrote:

> I have had only one response to this discussion. I spoke offline to Weiwei
> and looking at the lasts commits we are losing details and get badly
> formatted commit messages.
> * Committer is the generic github account. Here is an example of a commit
> from github.
> * Badly formatted messages as github does not insert line breaks.
>
> Since there was no strong -1 on this I am going to add the steps to the
> documentation, and ask everyone that commits to follow the simple manual
> merge steps:
>
> * git checkout master
>
> * git pull
>
> * git checkout -b  master
>
> * git pull   
>
> * git checkout master
>
> * git merge --squash 
>
> * git commit --author “ORIGINAL AUTHOR ”
> * git push origin master
>
> On commit you will be given the change to properly format the message of
> the commit. We can use magic github words in the commit to automatically
> close the PR on commit.
> I will add examples for the messages and the auto close
>
> Wilfred
>
> On Sun, 26 Apr 2020 at 05:01, Wangda Tan  wrote:
>
> > This looks reasonable to me. If everybody agrees, we should add it to the
> > dev doc.
> >
> > Thanks,
> > Wangda
> >
> > On Mon, Apr 13, 2020 at 11:56 PM Wilfred Spiegelenburg <
> > wilfr...@apache.org> wrote:
> >
> >> Hi,
> >>
> >> We have been using the github squash and commit button to merge requests
> >> for a most of our commits. I have noticed a problem with that usage. The
> >> commit that is added by GitHub will be attributed to the person that
> >> opened
> >> the PR (that is good and correct). However the committer is set to
> github.
> >> This means that we cannot track back a commit to a committer unless you
> >> use
> >> the github UI and open the PR. The code that is committed into the repo
> is
> >> also not signed off by the person performing the commit but by using a
> >> general github signature.
> >>
> >> As an example [YUNIKORN-85] shows the following commit log entry:
> >> -+-+-+-+-
> >> Author: Tao Yang 
> >> AuthorDate: Sat Apr 11 01:55:41 2020 +0800
> >> Commit: GitHub 
> >> CommitDate: Fri Apr 10 10:55:41 2020 -0700
> >> -+-+-+-+-
> >>
> >> And on the UI it just shows Tao committed the change while Weiwei was
> the
> >> person that merged. You cannot find the correct detail unless you dig
> into
> >> the original PR on github itself.
> >>
> >> -+-+-+-+-
> >> [YUNIKORN-85] Improve recovery performance by querying all pods once … …
> >> TaoYang526 committed 4 days ago
> >> -+-+-+-+-
> >>
> >> Because of this I already switched back to a manual squash and commit of
> >> the changes setting the author etc. That shows up correctly in the logs:
> >> -+-+-+-+-
> >> Author: Weiwei Yang 
> >> AuthorDate: Fri Apr 10 02:17:16 2020 +1000
> >> Commit: Wilfred Spiegelenburg 
> >> CommitDate: Fri Apr 10 02:17:16 2020 +1000
> >> -+-+-+-+-
> >> And also in the github UI:
> >> -+-+-+-+-
> >> [YUNIKORN-72] data race in unit test (#96) …
> >> yangwwei authored and wilfred-s committed 5 days ago
> >> -+-+-+-+-
> >>
> >> I want to propose that we all go back to that way so we do not lose
> >> the information of whom committed and get the correct signatures on the
> >> committed code.
> >>
> >> Please let me know if this is acceptable.
> >>
> >> Wilfred
> >>
> >
>

Re: [ANNOUNCE] Travis-CI for the core and shim

[Sunil Govindan]

Kudos. This will be really helpful

Cheers,
Sunil

On Thu, May 14, 2020 at 7:57 PM Wilfred Spiegelenburg 
wrote:

> Hi all,
>
> Over the last couple of days we have been working on getting the build
> moved from a github workflow to Travis. We got the two main repositories
> moved over yesterday and have fixed the main unit test failure we had just
> a couple of hours ago.
>
> The main changes:
> - rename of the license target to *license-check*
> - extension of the list of files checked to include all yaml and md files
> - fix of the lint check to only check the PR changes
> - badges for build status and other bits update in the README
>
> From this point on new PRs *must* pass the build before they will be
> committed. There will be no exceptions for the lint and license checks.
> Unit test failures will need to be analysed and if the failure is linked to
> the change it must be fixed. We can and will make exceptions for some unit
> test failures specially since we are still detection some new race
> conditions in our tests..
>
> Preparation is on its way to also start building the docker images
> automatically and push them to the apache hub. More on that will follow.
>
> Thank you to Weiwei for all the work setting up travis.
>
> Wilfred
>

Re: [ANNOUNCE] Updated web site deployed

[Sunil Govindan]

Thanks Wilfred!!  Appreciate it

On Wed, Apr 29, 2020 at 10:34 AM Wilfred Spiegelenburg 
wrote:

> Hi all,
>
> In preparation of the release and the requirement around site branding I
> have deployed an updated site.
> The changes include:
> - branding update
> - preparation of release download page
> - removal of unneeded files and references in the source
> - removal of hidden and unreferenced files in the deployement
> - updated build instructions
>
> The site is managed in the git repo:
> https://github.com/apache/incubator-yunikorn-site
>
> If you see anything incorrect or missing open a jira and add the label
> *website* to it.
>
> Thanks,
> Wilfred
>

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc4

[Sunil Govindan]

+1 binding

- verified signature and checksum
- built the source and prepared the docker images
- ran basic job and looks good

Thanks
Sunil

On Mon, Apr 27, 2020 at 6:27 AM Weiwei Yang  wrote:

> Hi all
>
> I'd like to call a vote for Apache YuniKorn (incubating) 0.8.0-rc4.
>
> All release artifacts, including source code package, signatures, and
> checksum, etc, can be found at:
> http://people.apache.org/~wwei/apache-yunikorn-incubating-0.8.0-rc4/
>
> this release has been signed with PGP
> key 8D076B6491A66D7B94E94519F57176CE11856D1F, corresponding to
> w...@apache.org. You can find the KEYS file here:
> http://people.apache.org/~wwei/KEYS.
>
> The release has been tagged with "v0.8.0" in all our git repos.
> The JIRA issues have been resolved for this release can be found:
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347742.
>
> Please review and vote. Note, the only diff between RC4 and RC3 is the
> DISCLAIMER file is replaced with DISCLAIMER-WIP. Past voting threads: RC1
> <
> https://lists.apache.org/thread.html/r22d8784b09ceead38f470534cae41e503c796b47144f62994e8a2115%40%3Cdev.yunikorn.apache.org%3E
> >,
> RC2
> <
> https://lists.apache.org/thread.html/rec0286566f4169563408c698c2ac02cdb4db0f4c587ac3a375a042ee%40%3Cdev.yunikorn.apache.org%3E
> >,
> RC3
> <
> https://lists.apache.org/thread.html/r09317bd6af041a9aa49fe1a23eb5a355e3a6768afc82e0bdbb06fea3%40%3Cdev.yunikorn.apache.org%3E
> >
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and the reason why)
>

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc3

[Sunil Govindan]

+1 (binding)

- checksum & signature is fine.
- Basic build is fine
- ran sample spark job, all looks good.

Thanks
Sunil

On Fri, Apr 24, 2020 at 6:55 AM Weiwei Yang  wrote:

> Hi all
>
> I'd like to call a vote for Apache YuniKorn (incubating) 0.8.0-rc3. (Note,
> the only diff between RC3 and RC2 is the "-rc2" suffix has been removed
> from the tarball/folder name)
>
> All release artifacts, including source code package, signatures, and
> checksum, etc, can be found at:
> http://people.apache.org/~wwei/apache-yunikorn-incubating-0.8.0-rc3/
>
> this release has been signed with PGP
> key 8D076B6491A66D7B94E94519F57176CE11856D1F, corresponding to
> w...@apache.org. You can find the KEYS file here:
> http://people.apache.org/~wwei/KEYS.
>
> The release has been tagged with "*v0.8.0*" in all our git repos.
> The JIRA issues have been resolved for this release can be found:
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347742.
>
> Please review and vote. The vote will be open for at least 72 hours (that
> ends on *Monday, Apr 26, 2020, 20:00 PST*).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and the reason why)
>

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc2

[Sunil Govindan]

Thanks Wilfred for clarifying this.

+1 from side.
- checksum & signature is fine.
- Basic build is fine
- ran sample spark job, all looks good.

Thanks +1 (binding)

Sunil

On Thu, Apr 23, 2020 at 7:31 PM Wilfred Spiegelenburg 
wrote:

> Hi Weiwei,
>
> checked:
> - signature
> - checksum
> - content (DISCLAIMER, NOTICE) is good
> - The instructions in README.md should be extended to contain more details
> on how to build from source. I think we can leave that for the next steps.
> - Build of the code passes
>
> +1 (binding) for RC2
>
> @Sunil Govindan : we can rename the files without
> needing to re-generate the checksum, signature or content of the file
> before we push them to the site for distribution. This is the last step and
> is part of the normal process we do not have to change this at this point.
> What we do now is similar to other Apache projects.
>
> Wilfred
>
> On Wed, 22 Apr 2020 at 16:57, Weiwei Yang  wrote:
>
>> Hi all
>>
>> I'd like to call a vote for Apache YuniKorn (incubating) 0.8.0-rc2.
>> All release artifacts, including source code package, signatures, and
>> checksum, etc, can be found at:
>> http://people.apache.org/~wwei/apache-yunikorn-incubating-0.8.0-rc2/
>>
>> this release has been signed with PGP
>> key 8D076B6491A66D7B94E94519F57176CE11856D1F, corresponding to
>> w...@apache.org. You can find the KEYS file here:
>> http://people.apache.org/~wwei/KEYS.
>>
>> The release has been tagged with "*v0.8.0*" in all our git repos.
>> The JIRA issues have been resolved for this release can be found:
>> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347742.
>>
>> Please review and vote. The vote will be open for at least 72 hours (that
>> ends on *Monday, Apr 25, 2020, 17:00 PST*).
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and the reason why)
>>
>

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc2

[Sunil Govindan]

Hi Weiwei.

Generally release package looks good. I could verify your signature and
checksum as well.
However after unzipping apache-yunikorn-incubating-0.8.0-rc2.tar.gz, i can
see the folder name is still apache-yunikorn-incubating-0.8.0-rc2

If this is final release candidate, then we cant change the name of package
and this folder will always be named with -rc2 at the end in final release
as well.
In my opinion, its better to avoid suffixing -rc2 from unzipped folder name.

Thanks
Sunil

On Wed, Apr 22, 2020 at 12:27 PM Weiwei Yang  wrote:

> Hi all
>
> I'd like to call a vote for Apache YuniKorn (incubating) 0.8.0-rc2.
> All release artifacts, including source code package, signatures, and
> checksum, etc, can be found at:
> http://people.apache.org/~wwei/apache-yunikorn-incubating-0.8.0-rc2/
>
> this release has been signed with PGP
> key 8D076B6491A66D7B94E94519F57176CE11856D1F, corresponding to
> w...@apache.org. You can find the KEYS file here:
> http://people.apache.org/~wwei/KEYS.
>
> The release has been tagged with "*v0.8.0*" in all our git repos.
> The JIRA issues have been resolved for this release can be found:
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347742.
>
> Please review and vote. The vote will be open for at least 72 hours (that
> ends on *Monday, Apr 25, 2020, 17:00 PST*).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and the reason why)
>

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc1

[Sunil Govindan]

Thanks Weiwei for addressing the comments. Only comment for below point

@wilfr...@apache.org , this is also something I am not
quite sure about. Imagine that we have our RC2 voting passed and prepare to
release based on RC2, I think we need to add another tag "0.8.0-incubating"
and then refresh all references in go.mod. then create another tarball with
that. Is this OK?

[Sunil]: Since this require a change in source tar ball, it is like
completely redoing the release artefacts again
And we need to again check the packages even after getting a release +1
VOTE's.
I think this may not be a good process

Thanks
Sunil

On Tue, Apr 21, 2020 at 5:19 AM Weiwei Yang  wrote:

> Hi Wilfred/Kinga/Sunil
>
> Thanks for the efforts validating it, let's fix these issues and roll out
> an RC2 this week. Please see my responses below:
>
> > NOTICE file contains a Copyright 2018-2020 message.
> Fixed. (I referred to Openwhisk:
> https://github.com/apache/openwhisk/blob/master/NOTICE.txt). But I guess
> it
> is more appropriate to add "Incubating".
>
> > DISCLAIMER text is not correct.
> Fixed.
>
> > I would extend it with changing the image pull policy as well
> I don't think this is a must. Given the user will build their own docker
> images, the image pull policy will be totally up to them. And it's right
> below the link where they change the address, hard to miss : )
>
> >  the helm chart link is wrong
> ah, good catch. my code refers to an absolute path on my local env (that's
> how I miss it from my testing). My bad. Fixed it now.
>
> > for the uninstall issue in
> https://issues.apache.org/jira/browse/YUNIKORN-102
> this is due to a limitation of the helm. the uninstall command works fine
> for helm3.x, but for helm2, it's different. Since helm3.x is the
> recommended version based on https://helm.sh/docs/intro/install/. It would
> be nice for us to add some steps for helm2.x in YUNIKORN-102, but I don't
> think this is a release blocker.
>
> > In the webUI the pending and terminated pods are shown as Running
> applications.
> This is a known issue, we cannot do much for this release. I suggest
> planning YUNIKORN-103 <https://issues.apache.org/jira/browse/YUNIKORN-103>
> for
> 0.9.
>
> > the web UI is not working properly and the admission controller
> installation is missing the yunikorn-service as well.
> I have commented on YUNIKORN-104
> <https://issues.apache.org/jira/browse/YUNIKORN-104>, but I think this can
> be fixed (improved) by improving our docs.
>
> > *"**Apache YuniKorn (incubating)"*: For consistency, we can keep
> (Incubating)
> Fixed
>
> > May be, its better to add in user-guide.md or in this README.md.
> I have already pointed the user to the doc we have on github. But in
> future, we might want to build docs on our web site, and point users to
> there.
>
> > - .github folder present in k8shim, core  - .gitignore present in
> scheduler-interface, web, core, k8shim
> @Sunil, I believe I have excluded these files in the tarball, can you
> please double-check?
>
> > yunikorn-web Dockerfile is missing ASF license header
> Created PR: https://github.com/apache/incubator-yunikorn-web/pull/30
>
> One issue left for discussion is:
>
> 5) The tag that has been used is v0.8.0-incubating-rc1. That reference is
> in the go.mod files. That means we cannot use this source release and
> promote it to the real release. We cannot have a pointer to the rc1 tag in
> the files.
>
> @wilfr...@apache.org , this is also something I am
> not
> quite sure about. Imagine that we have our RC2 voting passed and prepare to
> release based on RC2, I think we need to add another tag "0.8.0-incubating"
> and then refresh all references in go.mod. then create another tarball with
> that. Is this OK?
>
> We need to put all release blockers with targetVersion=0.8, use this query
> <
> https://issues.apache.org/jira/browse/YUNIKORN-105?jql=project%20%3D%20YUNIKORN%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20%22Target%20Version%22%20%3D%200.8
> >
> to check. For now, I think the following ones need our attention
>
>1. https://issues.apache.org/jira/browse/YUNIKORN-105 *[PR Available]*
>2. https://issues.apache.org/jira/browse/YUNIKORN-92 *[In Progress]*
>3. Source code tagging issue raised by Wilfred
>
> Please let me know if I miss anything, thanks!
>
> Weiwei
>
>
> On Mon, Apr 20, 2020 at 10:16 AM Sunil Govindan  wrote:
>
> > HI Weiwei,
> >
> > Thanks for leading efforts in preparing this RC build. I agree to the
> > points given by Wilfred and Julia above.
> &

Re: [VOTE] Release Apache YuniKorn (incubating) 0.8.0-rc1

[Sunil Govindan]

HI Weiwei,

Thanks for leading efforts in preparing this RC build. I agree to the
points given by Wilfred and Julia above.
I think we can call for another RC by correcting the comments.

Apart from other comments above,

- Basic testing seems fine. Deployed  YuniKorn in my local cluster, it went
fine and I was able to run SPARK jobs in my K8s cluster
- UI has come up and pages are accessible.

General comments which we can fix as we are doing next RC
1. In README.md,
 - *"**you can find the templates in the release package `helm-charts`."*
However the charts are assuming a repo-name called *yunikorn*. Its better
to call out that as README.md is assuming *foo* as the repo name in
examples.
 -  *"**Apache YuniKorn (incubating)"*: For consistency, we can keep
(Incubating)
than (incubating)
 - May be, its better to add in user-guide.md or in this README.md. I think
we are missing to say what happens after we do "helm install ./yunikorn".
We can say that under a given namespace, 2 pods ll be started. And what
will be done by admission controller, web containers etc.
2. Source dirs
 - .github folder present in k8shim, core
 - .gitignore present in scheduler-interface, web, core, k8shim
3. License
 - yunikorn-web Dockerfile is missing ASF license header

Thanks,
Sunil

On Mon, Apr 20, 2020 at 7:39 PM Julia Kinga Marton
 wrote:

> Hi Weiwei,
>
> I did some testing on the RC as well, below you can find my notes:
> Tested the following things:
> - verified sha512 sum: OK
> - verified signature: OK
> - built docker images
> - installed Yunikorn both with Helm chart and manually
>
> *During the testing I found the following issues:*
> - the helm chart link is wrong
> - in the README.md *Run YuniKorn on an existing K8s cluster *I would extend
> it with changing the image pull policy as well (It is very easy to forget
> about it and keep it as latest).
> - the documentation about how to uninstall it is not complete, because it
> describes a one step command, however there are further steps we had to
> perform in order to have it completely uninstalled (scale the cluster to 0
> if we want to uninstall the admission controller as well, than we have to
> delete the configmap manually). Opened YUNIKORN-102
>  for fixing it.
> - In the webUI the pending and terminated pods are show as Running
> applications. I think this may cause misunderstandings in the future.
> Opened YUNIKORN-103 
> for
> discussing and fixing this gap.
> - In case of manual installation using scheduler.yaml
> <
> https://github.com/apache/incubator-yunikorn-k8shim/blob/master/deployments/scheduler/scheduler.yaml
> >descriptor
> the web UI is not working properly and the admission controller
> installation is missing the yunikorn-service as well. Opened YUNIKORN-104
>  for fixing the
> deployment descriptor.
>
> Regards,
> Kinga
>
>
> On Mon, Apr 20, 2020 at 6:48 AM Wilfred Spiegelenburg  >
> wrote:
>
> > Hi Weiwei,
> >
> > Thank you for the first RC for YuniKorn.
> >
> > There are some issues with the release which means that I have to give a
> -1
> > at this point.
> >
> > 1) NOTICE file contains a Copyright 2018-2020 message. The first commit
> is
> > from 2019 so that date is not correct.The code was donated to Apache in
> > 2020.
> > 2) DISCLAIMER text is not correct. The project name should contain
> > incubating, i.e. Apache Yunikorn (Incubating).
> > The text "name of Apache TLP sponsor." should be replaced by the text
> > " Apache Incubator PMC."
> > 3) README.md does not state the fact that there is a pre-requisite of
> > having a full build environment with tools installed. We need a link to
> the
> > build doc at least to show where the information can be found. There are
> > some small grammar issues also but those are minor.
> > 4) The helm-charts directory in the root of the package points to a non
> > existing location. The link that was created is wrong.
> > 5) The tag that has been used is v0.8.0-incubating-rc1. That reference is
> > in the go.mod files. That means we cannot use this source release and
> > promote it to the real release. We cannot have a pointer to the rc1 tag
> in
> > the files.
> >
> > I think we need to stop the vote and create a new RC to fix these issues.
> >
> > Wilfred
> >
> > On Sat, 18 Apr 2020 at 06:43, Weiwei Yang  wrote:
> >
> > > Hi all
> > >
> > > I'd like to call a vote for Apache YuniKorn (incubating) 0.8.0-rc1.
> > > All release artifacts, including source code package, signatures, and
> > > checksum, etc, can be found at:
> > > http://people.apache.org/~wwei/apache-yunikorn-incubating-0.8.0-rc1/
> > >
> > > this release has been signed with PGP
> > > key 8D076B6491A66D7B94E94519F57176CE11856D1F, corresponding to
> > > w...@apache.org. You can find the KEYS file here:
> > > http://people.apache.org/~wwei/KEYS.
> > >
> > > The release has been tagged

Re: YuniKorn 0.8 release updates

[Sunil Govindan]

Thanks Weiwei and Wilfred.

+0 on this approach. I am overall feeling fine with the approach suggested.
However I may have personally prefer to do this in a create-release.sh and
Dockerfile like hadoop model.

As Weiwei pointed out, its used in Opwnwhisk pjct as well, may be we can
try this out and find the positiveness.

I think, we should make the scripts or configs in this repo more dynamic in
nature agnostic to any release version.
RM can supply this version etc as a run time param to these scripts.

Thanks
Sunil

On Tue, Apr 14, 2020 at 12:26 PM Weiwei Yang  wrote:

> Hi Wilfred
>
> Thanks for the feedback.
>
> The reason to introduce a new repo is to have some tools/docs easier for
> release managers. I found this is a good practice when you have multiple
> repos. Please see Apache OpenWhisk as an example.
>
> If you look at the config file I shared, that helps to track source code
> revision of different repos, which is easy to assemble a release.
>
> I propose to do unified release, which means we alway release all repos
> together. This is simpler to manage.
>
> If you look at the archive file, I should have put a script and a README
> about how to build docker images. Can you please take a look at that? If
> that is not there, pls see the script on github.
>
> Thanks for verifying the content. Could you please let me know what files
> are wrong?
>
>
>
> --
> Weiwei
> On Apr 13, 2020, 11:30 PM -0700, Wilfred Spiegelenburg <
> wilfr...@apache.org>, wrote:
> > Hi Weiwei,
> >
> > Do we really need another repo for three files?
> > We should sleep track of this in the core repo not in another repo which
> we
> > need to release manage again. I think managing the release from the core
> > repo will make it easier later on if we need to or want to change the
> build
> > process further. Now we need need to manage and track soo many repos that
> > it becomes more and more difficult.
> > We also need to keep in mind that version information is in the module
> > files. There might thus be more that needs to change for a release. The
> > other thing is that we might not want to release a new version of one of
> > the components while updating another component. That would means that we
> > need to release manage 5 repositories for one release, including all the
> > overhead.
> >
> > Apache releases are source releases. We still need to provide some kind
> of
> > make etc over the source code also. I agree with the fact that we need to
> > provide one source archive that is signed. However with the current build
> > process just the k8shim code is enough to build the docker image. The
> other
> > code repos will be pulled in from github. The mod file point there for
> all
> > go dependencies including the core and SI. It does not provide any detail
> > on the how and what for any of the repos. We need to provide some build
> > instructions in the root of the source archive. I would not know how to
> > build from the source package if we just add the checked out code into
> it.
> > We need to provide some steps even if they are just pointers to existing
> > docs.
> > I also don't think we have the correct files in the archive with the
> > current generated archive.
> >
> > Wilfred
> >
> >
> > > On Mon, 13 Apr 2020 at 14:01, Weiwei Yang  wrote:
> >
> > > For 0.8 release, I did some work and I wanted to share the latest
> status. I
> > > think we should target for *docker-image-based* release mode. I
> propose to
> > > release a unified open-source tarball, we don't release a binary
> tarball
> > > (not a must [1]). Things have been *DONE*:
> > >
> > > 1. I have created a repo for release mgmt:
> > > https://github.com/yangwwei/yunikorn-release, I think we need to move
> > > this to apache repo too.
> > >
> > 2. This repo has the instructions and tools for a release. The tool
> > > loads configs from
> > >
> > >
> https://github.com/yangwwei/yunikorn-release/blob/master/tools/release-configs.json
> > > and
> > > downloads source code from certain repo/branch/hash to assemble the
> > > release
> > > artifacts
> >
> > 3. This repo contains a *build-docker-image.sh* to build yunikorn docker
> > > images (scheduler, admission-controller, and web)
> > > 4. I have created *branch-0.8* for all 4 repos
> > > 5. The generated tarball will also have the helm chart for user to
> > > install and run yunikorn on an existing K8s cluster
> > > 6. I tried to generate PGP key and sign the tarball
> > >
> > > Things *TODO*
> > >
> > > 1. Create a repo for yunikorn-release under ASF
> > > 2. IIUC, https://issues.apache.org/jira/browse/YUNIKORN-79 is a
> blocker
> > > for 0.8. Can we get this fixed ASAP?
> > > 3. Once #2 is done, create a tag for 0.8-rc1 and start the voting
> thread
> > >
> > > Thanks!
> > >
> > > [1] https://infra.apache.org/release-publishing.html *The Apache
> Software
> > > Foundation exists to create open source software, so the fundamental
> > > requirement for a release is that it has the necessary source 

Re: Improve node sorting algorithm

[Sunil Govindan]

Thanks Tao for the efforts. Appreciate it.
I will help to take a look on this.

Thanks
Sunil

On Wed, Apr 15, 2020 at 12:09 PM Tao Yang  wrote:

> Hello everyone
>
> I have uploaded a design doc to improve node sorting algorithm in
> https://issues.apache.org/jira/browse/YUNIKORN-21, we are trying to make
> node sorting algorithm more flexible and pluggable, have better performance
> and can support preferred nodes requirements for specific requests.
> If you are interested on this, we are looking forward to your comments and
> suggestions.
>
> Thanks,
> Tao Yang
>

Re: YuniKorn community sync up today!

[Sunil Govindan]

Hi Ayub
Details are here in this wiki.
 https://github.com/apache/incubator-yunikorn
-core/blob/master/docs/community-sync-up.md.

Thanks
Sunil


On Wed, Apr 8, 2020 at 9:02 PM Ayub Khan Pathan
 wrote:

> Is this a recurring sync up? Can you please share calendar invite, just to
> block the time?
>
> Thanks
> Ayub Khan
>
> On Wed, Apr 8, 2020 at 8:26 AM Sunil Govindan  wrote:
>
> > 👍 Thanks for the reminder.
> >
> > On Wed, Apr 8, 2020 at 8:41 PM Wangda Tan  wrote:
> >
> > > Added correct users.
> > >
> > > On Wed, Apr 8, 2020 at 8:09 AM Wangda Tan  wrote:
> > >
> > > > Hi yunikorn-dev/users,
> > > >
> > > > Today US morning Pacific time (Wednesday 9:30 AM)  we're going to
> > > > host YuniKorn community sync up, please join if you could!  Join Zoom
> > > > Meeting https://cloudera.zoom.us/j/721195559
> > > >
> > > > Thanks,
> > > > Wangda Tan
> > > >
> > >
> >
>

Re: YuniKorn community sync up today!

[Sunil Govindan]

👍 Thanks for the reminder.

On Wed, Apr 8, 2020 at 8:41 PM Wangda Tan  wrote:

> Added correct users.
>
> On Wed, Apr 8, 2020 at 8:09 AM Wangda Tan  wrote:
>
> > Hi yunikorn-dev/users,
> >
> > Today US morning Pacific time (Wednesday 9:30 AM)  we're going to
> > host YuniKorn community sync up, please join if you could!  Join Zoom
> > Meeting https://cloudera.zoom.us/j/721195559
> >
> > Thanks,
> > Wangda Tan
> >
>

Re: Thoughts about community sync up for YuniKorn?

[Sunil Govindan]

+1 for the proposal.

Such a syncup will definitely help our project as we are observing from
other Apache projects.
1. EU/US/India one meeting (I am nt sure whether we can cover AUS here)
2. Mandarin one meeting

Thanks
Sunil

On Sun, Mar 15, 2020 at 6:39 AM Wangda Tan  wrote:

> Hi YuniKorn Developper,
>
> I'm thinking to start community sync up for YuniKorn projects for community
> members to exchange thoughts about the project, and periodically get
> updates from the community.
>
> The target audiences are users and developers.
>
> I suggest doing this twice a month, one for US/EU/India friendly timezone
> (most likely we can do US morning time, which is afternoon for EU and
> evening for India), and one for Mandarin-speaking area (Around noon).
>
> Thoughts?
>
> Thanks,
> Wangda
>

Re: emails notification updates for JIRA and GitHub

[Sunil Govindan]

Hi Weiwei and Wilfred,

I have not seen a reviews@ list so far. In other projects, I have seen
issues@ list where all updates on jira will go.
In any case, I agree in removing such notifications from dev@ list. And if
possible, also having an issues@ list as well

- Sunil

On Tue, Mar 10, 2020 at 10:04 AM Wilfred Spiegelenburg 
wrote:

> Hi Weiwei,
>
> Currently all notifications for github go to dev@, that is a setting on
> the
> github repos that can be changed.
> I propose to move all of them to the reviews@ list and remove dev@ from
> the
> github notifications
> We should be using dev@ for mails that require discussions and votes not
> as
> a generic notification list I think.
>
> Wilfred
>
> On Tue, 10 Mar 2020 at 15:18, Weiwei Yang  wrote:
>
> > Hi Wilfred
> >
> > Thanks for taking care of this.
> > For the second one, since we already have GitBox notification about PRs,
> > creating reviews@ mailing list would get us too many duplicated
> messages?
> >
> > Weiwei
> >
> > On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <
> wilfr...@apache.org>
> > wrote:
> >
> >> Hi all,
> >>
> >> I noticed last week when moving all issues into the JIRA that there is
> no
> >> email send for JIRAs at all. I checked the project settings and we have
> >> currently not linked up the JIRA notifications to the correct list.
> >> The original plan was to use issues@ as the mailing list. However we
> seem
> >> to have missed that change.
> >>
> >> If there are no reservations to using this I will ask INFRA to change
> the
> >> notification list to issues@ for the following events:
> >> * Created
> >> * Updated
> >> * Assigned
> >> * Resolved
> >> * Closed
> >> * Commented
> >> * Comment Edited
> >> That will bring us in line with most of the other projects.
> >>
> >> Second point for mailing lists: commits@ was originally slated for
> GitHub
> >> emails. The mailing list does not exist at the moment. Currently all the
> >> git emails come in on the dev@ mailing list which clutters that list.
> >> Instead of creating commits@ I would like to propose to change the name
> >> to
> >> reviews@ as it better covers what we do on GitHub with the PRs and the
> >> review on the code.
> >>
> >> Please respond to this mail if you are not OK with the changes. If there
> >> are no objections I will start the changes on Monday 16 March 2020 (AEDT
> >> +11).
> >>
> >> Thank you,
> >> Wilfred
> >>
> >
> >
> > --
> > *Weiwei Yang*
> > Software Engineer, Cloudera
> >
> > Create your own WiseStamp email signature
> > <
> https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112
> >
> >
>