Re: [VOTE] Accept Gravitino into the ASF Incubator

2024-05-29 Thread Weiwei Yang 
+1

On Wed, May 29, 2024 at 8:59 AM Jean-Baptiste Onofré 
wrote:

> Sorry, the links have not been pasted correctly:
>
> Here's the discussion:
> https://lists.apache.org/thread/5bp5t0hgq2c419m62m2zt71jkv8bhhho
>
> And the proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/GravitinoProposal
>
> Regards
> JB
>
> On Wed, May 29, 2024 at 5:31 PM Jean-Baptiste Onofré 
> wrote:
> >
> > Hi folks,
> >
> > Following the discussion about Gravitino [1], I would like to start
> > the formal vote to accept Gravitino into the ASF Incubator.
> >
> >  As reminder, this is the Gravitino Proposal:
> >
> > Please cast your vote:
> >
> > [ ] +1, accept Gravitino into the ASF Incubator
> > [ ] 0, I don't care either way
> > [ ] -1, do not accept Gravitino into the ASF Incubator, because ...
> >
> > The vote will run for one week starting from today.
> >
> > Thanks !
> >
> > Regards
> > JB
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) V0.8.0 RC3

2023-12-12 Thread Weiwei Yang 
+1

- DISCLAIMER looks good
- Checked LICENSE and NOTICE files look good
- Checked the headers that have Apache License
- Checked both BIN and SRC packages, looks good

On Tue, Dec 12, 2023 at 10:03 AM Liu Xun  wrote:

> +1 (binding) from me,
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
> - Can compile from source
>   `mvn clean install`
>
> Best regards
> Xun Liu
>
> On 2023/12/12 10:18:14 Zhankun Tang wrote:
> > +1.
> >
> > BR,
> > Zhankun
> >
> > On Sat, 9 Dec 2023 at 06:40, Felix Cheung 
> wrote:
> >
> > > +1
> > >
> > > - incubating in name
> > > - signature and hash fine
> > > - DISCLAIMER is fine
> > > - LICENSE and NOTICE are fine
> > > - No unexpected binary files
> > > - All source files have ASF headers
> > >
> > >
> > > On Thu, Dec 7, 2023 at 6:36 AM Xianjing Feng 
> > > wrote:
> > >
> > > > Hello Incubator Community,
> > > >
> > > > This is a call for a vote to release Apache Uniffle(Incubating)
> > > version
> > > > V0.8.0 RC3
> > > >
> > > > The Apache Uniffle community has voted on and approved a
> proposal to
> > > > release
> > > > Apache Uniffle(Incubating) version V0.8.0 RC3
> > > >
> > > > We now kindly request the Incubator PMC members review and vote
> on
> > > this
> > > > incubator release.
> > > >
> > > > Uniffle community vote thread:
> > > > •
> https://lists.apache.org/thread/9psgtxkdynqrcsjcgotfzmx4jl33t0d2
> > > >
> > > > Vote result thread:
> > > > •
> https://lists.apache.org/thread/j8nhy5o4k5j3c1jd5vrmqg9zmxfz7y92
> > > >
> > > > The release candidate:
> > > > •
> > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.8.0-rc3/
> > > >
> > > > Git tag for the release:
> > > > • https://github.com/apache/incubator-uniffle/tree/v0.8.0-rc3
> > > >
> > > > Release notes:
> > > > • https://uniffle.apache.org/download/release-notes-0.8.0
> > > >
> > > > The artifacts signed with PGP key [3E6F20AC33D1F201],
> > > > corresponding to [xianjingf...@apache.org], that can be found in
> keys
> > > > file:
> > > > • https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
> > > >
> > > > As the DISCLAIMER-WIP shows, this release still left some license
> > > > problems, which will be gradually resolved during incubation.
> > > >
> > > > The vote will be open for at least 72 hours or until necessary
> > > > number of votes are reached.
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [] +1 approve
> > > > [] +0 no opinion
> > > > [] -1 disapprove with the reason
> > > >
> > > > Thanks,
> > > > On behalf of Apache Uniffle (Incubating) community
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.7.1 rc2

2023-07-08 Thread Weiwei Yang 
+1 (Binding)

- Checked LICENSE and NOTICE files
- Check the binaries in the package all have Apache headers
- Built from source
- Verified the checksums and signatures

Weiwei

On Wed, Jul 5, 2023 at 5:13 AM Jia Fan  wrote:

> +1,
>
> I have checked:
> - The checksums and signatures are validated
> - The LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - No binary files in the source release
> - incubating in the name
>
> Liu Xun  于2023年7月5日周三 15:35写道：
>
> > +1 (binding) from me,
> >
> > I have checked the following items:
> > - Incubating in name
> > - LICENSE and NOTICE are fine
> > - DISCLAIMER-WIP exists
> > - All links are valid
> > - No unexpected binary files
> > - All ASF files have ASF headers
> > - Can compile from source
> >   `mvn clean install`
> >
> > On 2023/06/28 02:03:01 Jiafu Zhang wrote:
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Uniffle(Incubating)
> > > version 0.7.1 rc2
> > >
> > > The Apache Uniffle community has voted on and approved a proposal to
> > release
> > > Apache Uniffle(Incubating) version 0.7.1 rc2
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Uniffle community vote thread:
> > > • https://lists.apache.org/thread/rfp3cll7l5q6525xs5jths7d4f6t0kt0
> > >
> > > Vote result thread:
> > > • https://lists.apache.org/thread/hnt45glbdkl75gtgb9czbcbc0r9d19s7
> > >
> > > The release candidate:
> > > • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.1-rc2/
> > >
> > > Git tag for the release:
> > > • https://github.com/apache/incubator-uniffle/tree/v0.7.1-rc2/
> > >
> > > Release notes:
> > > • https://uniffle.apache.org/download/release-notes-0.7.1
> > >
> > > The artifacts signed with PGP key A5F1ABF0, corresponding to
> > > jiafu...@apache.org, that can be found in keys file:
> > > • https://downloads.apache.org/incubator/uniffle/KEYS
> > >
> > > As the DISCLAIMER-WIP shows, this release still left some license
> > > problems, which will be gradually resolved during incubation.
> > >
> > > The vote will be open for at least 72 hours or until necessary number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [] +1 approve
> > > [] +0 no opinion
> > > [] -1 disapprove with the reason
> > >
> > > Thanks,
> > > On behalf of Apache Uniffle (Incubating) community
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Celeborn into the Apache Incubator

2022-10-12 Thread Weiwei Yang 
+1 (binding)
Good luck!!

On Wed, Oct 12, 2022 at 12:13 PM Felix Cheung 
wrote:

> +1 (binding)
>
>
>
> On Wed, Oct 12, 2022 at 7:26 AM Ashish  wrote:
>
> > +1 (non-binding)
> >
> > On Tue, Oct 11, 2022 at 8:49 PM Yu Li  wrote:
> >
> > > Hi all,
> > >
> > > Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like
> to
> > > call a VOTE to accept Celeborn into the Apache Incubator, please check
> > out
> > > the Celeborn Proposal from the incubator wiki [3].
> > >
> > > Please cast your vote:
> > >
> > > [ ] +1, bring Celeborn into the Incubator
> > > [ ] +0, I don't care either way
> > > [ ] -1, do not bring Celeborn into the Incubator, because...
> > >
> > > The vote will open at least for 72 hours, and only votes from the
> > Incubator
> > > PMC are binding, but votes from everyone are welcome.
> > >
> > > Best Regards,
> > > Yu
> > >
> > > [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c
> > > [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy
> > > [3]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal
> > >
> >
> >
> > --
> > thanks
> > ashish
> >
>

Re: [VOTE] Accept Uniffle into the Apache Incubator

2022-05-30 Thread Weiwei Yang 
+1 (binding)

On Mon, May 30, 2022 at 8:42 PM Ye Xianjin  wrote:

> +1 (no-binding)
>
> Sent from my iPhone
>
> > On May 31, 2022, at 10:46 AM, Aloys Zhang  wrote:
> >
> > +1 （no-binding）
> >
> > XiaoYu  于2022年5月31日周二 10:12写道：
> >
> >> +1 (no-binding)
> >>
> >> Xun Liu  于2022年5月31日周二 10:07写道：
> >>>
> >>> +1 (binding) for me.
> >>>
> >>> Good luck!
> >>>
> >>> On Tue, May 31, 2022 at 10:04 AM Goson zhang 
> >> wrote:
> >>>
>  +1 (no-binding)
> 
>  Good luck!!
> 
>  tison  于2022年5月31日周二 09:43写道：
> 
> > +1 (binding)
> >
> > Best,
> > tison.
> >
> >
> > Jerry Shao  于2022年5月31日周二 09:37写道：
> >
> >> Hi all,
> >>
> >> Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I
>  would
> >> like to
> >> call a VOTE to accept Uniffle into the Apache Incubator, please
> >> check
>  out
> >> the Uniffle Proposal from the incubator wiki[3].
> >>
> >> Please cast your vote:
> >>
> >> [ ] +1, bring Uniffle into the Incubator
> >> [ ] +0, I don't care either way
> >> [ ] -1, do not bring Uniffle into the Incubator, because...
> >>
> >> The vote will open at least for 72 hours, and only votes from the
> >> Incubator PMC are binding, but votes from everyone are welcome.
> >>
> >> [1]
> >> https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
> >> [2]
> >> https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
> >> [3]
> >
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >>
> >> Best regards,
> >> Jerry
> >>
> >
> 
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSSION] Incubating Proposal of Uniffle

2022-05-24 Thread Weiwei Yang 
+1 (binding)
Good luck!

On Tue, May 24, 2022 at 8:49 PM Ye Xianjin  wrote:

> +1 (non-binding).
>
> Sent from my iPhone
>
> > On May 25, 2022, at 9:59 AM, Goson zhang  wrote:
> >
> > +1 (non-binding)
> >
> > Good luck!
> >
> > Daniel Widdis  于2022年5月25日周三 09:53写道：
> >
> >> +1 (non-binding) from me!  Good luck!
> >>
> >> On 5/24/22, 9:05 AM, "Jerry Shao"  wrote:
> >>
> >>Hi all,
> >>
> >>Due to the name issue in thread (
> >>https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
> we
> >>figured out a new project name "Uniffle" and created a new Thread.
> >> Please
> >>help to discuss.
> >>
> >>We would like to propose Uniffle[1] as a new Apache incubator
> project,
> >> you
> >>can find the proposal here [2] for more details.
> >>
> >>Uniffle is a high performance, general purpose Remote Shuffle Service
> >> for
> >>distributed compute engines like Apache Spark
> >><https://spark.apache.org/>, Apache
> >>Hadoop MapReduce <https://hadoop.apache.org/>, Apache Flink
> >><https://flink.apache.org/> and so on. We are aiming to make
> >> Firestorm a
> >>universal shuffle service for distributed compute engines.
> >>
> >>Shuffle is the key part for a distributed compute engine to exchange
> >> the
> >>data between distributed tasks, the performance and stability of
> >> shuffle
> >>will directly affect the whole job. Current “local file pull-like
> >> shuffle
> >>style” has several limitations:
> >>
> >>   1. Current shuffle is hard to support super large workloads,
> >> especially
> >>   in a high load environment, the major problem is IO problem
> (random
> >> disk IO
> >>   issue, network congestion and timeout).
> >>   2. Current shuffle is hard to deploy on the disaggregated compute
> >>   storage environment, as disk capacity is quite limited on compute
> >> nodes.
> >>   3. The constraint of storing shuffle data locally makes it hard to
> >> scale
> >>   elastically.
> >>
> >>Remote Shuffle Service is the key technology for enterprises to build
> >> big
> >>data platforms, to expand big data applications to disaggregated,
> >>online-offline hybrid environments, and to solve above problems.
> >>
> >>The implementation of Remote Shuffle Service -  “Uniffle”  - is
> heavily
> >>adopted in Tencent, and shows its advantages in production. Other
> >>enterprises also adopted or prepared to adopt Firestorm in their
> >>environments.
> >>
> >>Uniffle's key idea is brought from Salfish shuffle
> >><
> >>
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> >>> ,
> >>it has several key design goals:
> >>
> >>   1. High performance. Firestorm’s performance is close enough to
> >> local
> >>   file based shuffle style for small workloads. For large workloads,
> >> it is
> >>   far better than the current shuffle style.
> >>   2. Fault tolerance. Firestorm provides high availability for
> >> Coordinated
> >>   nodes, and failover for Shuffle nodes.
> >>   3. Pluggable. Firestorm is highly pluggable, which could be suited
> >> to
> >>   different compute engines, different backend storages, and
> different
> >>   wire-protocols.
> >>
> >>We believe that Uniffle project will provide the great value for the
> >>community if it is accepted by the Apache incubator.
> >>
> >>I will help this project as champion and many thanks to the 3
> mentors:
> >>
> >>   -
> >>
> >>   Felix Cheung (felixche...@apache.org)
> >>   - Junping du (junping...@apache.org)
> >>   - Weiwei Yang (w...@apache.org)
> >>   - Xun liu (liu...@apache.org)
> >>   - Zhankun Tang (zt...@apache.org)
> >>
> >>
> >>[1] https://github.com/Tencent/Firestorm
> >>[2]
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >>
> >>Best regards,
> >>Jerry
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-16 Thread Weiwei Yang 
+1
This is an interesting project, I'd be happy to help the project's
incubation process.
Let me know if you need my help, Thanks

On Mon, May 16, 2022 at 8:09 PM Saisai Shao  wrote:

> Got it, thanks a lot Justin.
>
> Best regards,
> Jerry
>
> Justin Mclean  于2022年5月17日周二 10:59写道：
>
> > Hi,
> >
> > The new project name doesn’t need to be a registered trademark, but you
> > would still need to pick a name that is now likely to have any trademark
> > issues.
> >
> > The project may want to get the ASF to register the mark at a later date,
> > but it wold be best to talk abut that on the trademarks@ list.
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Apache Toree 0.5.0-incubating RC5

2022-04-05 Thread Weiwei Yang 
+1 (binding)

Thanks
Weiwei

On Tue, Apr 5, 2022 at 5:25 PM Luciano Resende  wrote:

> Transferring my +1 (binding) from the dev mailing list.
>
> On Fri, Apr 1, 2022 at 7:53 PM Luciano Resende 
> wrote:
>
> > Please vote to approve the release of Apache Toree 0.5.0-incubating
> > (RC5) which brings support for Spark 3.0.
> >
> >
> > The podling dev vote thread:
> > https://www.mail-archive.com/dev@toree.apache.org/msg00112.html
> >
> > And the result:
> > https://www.mail-archive.com/dev@toree.apache.org/msg00123.html
> >
> > Tag: v0.5.0-incubating-rc5 (a803d295d90b39881ccc3de93467a2af199e2dcd)
> >
> > https://github.com/apache/incubator-toree/tree/v0.5.0-incubating-rc5
> >
> > All distribution packages, including signatures, digests, etc. can be
> > found at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/toree
> > /0.5.0-incubating-rc5/
> >
> > Staging artifacts can be found at:
> >
> > https://repository.apache.org/content/repositories/orgapachetoree-1020
> >
> > The vote is open for at least 72 hours and passes if a majority of at
> > least
> > 3 +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Toree 0.5.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

[RESULT][VOTE] Graduate Apache YuniKorn (Incubating) as a top level ASF project

2022-02-20 Thread Weiwei Yang 
Hi all

The IPMC vote for graduating  Apache YuniKorn (Incubating) as a top-level
project has passed. The results are:

Binding  (8)
 - Luciano Resende
 - Xun Liu
 - Felix Cheung
- Wei-Chiu Chuang
- Uma gangumalla
 - Lionel Liu
 - Furkan KAMACI
- Jean-Baptiste Onofré

Non-binding (6)

- Calvin Kirs
- Tan Zhongyi
- heng du
- Goson Zhang
- Brahma Reddy Battula
- Eason Chen

The discussion thread is here:
https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
The voting thread is here:
https://lists.apache.org/thread/vwb09wbx8lfn27low4jh8yt90xvqz5hz

We will now submit the graduation proposal to the ASF board.
Thank you very much for your support.

Weiwei

Re: [VOTE] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-20 Thread Weiwei Yang 
Thank you all for participating in the vote, we are closing the vote now.
We got 8 binding +1 votes and 6 non-binding +1 votes, no +0 or -1 votes.

Binding  (8)
 - Luciano Resende
 - Xun Liu
 - Felix Cheung
- Wei-Chiu Chuang
- Uma gangumalla
 - Lionel Liu
 - Furkan KAMACI
- Jean-Baptiste Onofré

Non-binding (6)

- Calvin Kirs
- Tan Zhongyi
- heng du
- Goson Zhang
- Brahma Reddy Battula
- Eason Chen

Thanks!

On Fri, Feb 18, 2022 at 2:33 AM Furkan KAMACI 
wrote:

> Hi,
>
> +1 (binding)
>
> Kind Regards,
> Furkan KAMACI
>
> On 18 Feb 2022 Fri at 11:26 Jean-Baptiste Onofré  wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On Wed, Feb 16, 2022 at 6:03 AM Weiwei Yang  wrote:
> > >
> > > Hi Incubator Community
> > >
> > > After the discussion in the YuniKorn community [1], and passed the
> > > community vote [2][3]. We have started the discussion in the
> > > general@incubator list [4]. Based on all positive feedback received,
> we
> > > would like to start this voting thread to request graduating the
> YuniKorn
> > > project from the incubator as a TLP.
> > >
> > > Please provide your vote as one of the following options:
> > >
> > > [ ] +1 - Recommend graduation of Apache YuniKorn as a TLP
> > > [ ]  0 -  I don't feel strongly about it, but don't object
> > > [ ] -1 - Do not recommend the graduation of Apache YuniKorn because…
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > To summarize what the YuniKorn community has achieved in the incubating
> > > phase:
> > >
> > >- 6 releases were done by 6 different releases managers.
> > >- 41 unique code contributors and over 1300+ commits.
> > >- A growing community that added 2 new mentors, 10 new committers, 4
> > new
> > >PPMC from 6 different organizations
> > >- A diverse community that has 6 mentors, 23 PPMC, and 29 committers
> > >from at least 14 different organizations [5]
> > >- Well documented web site [6]
> > >- The maturity self-assessment [7]
> > >
> > > [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> > > [2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
> > > [3] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
> > > [4] https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
> > > [5] https://yunikorn.apache.org/community/people
> > > [6] https://yunikorn.apache.org/
> > > [7] https://yunikorn.apache.org/community/maturity
> > >
> > >
> >
> --
> > >
> > > Establish the Apache YuniKorn Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > a Project Management Committee charged with the creation and
> maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a standalone resource scheduler responsible for scheduling
> > > batch jobs and long-running services on large scale distributed systems
> > > running in on-premises environments as well as different public clouds.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache YuniKorn Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache YuniKorn Project be and hereby is responsible
> > > for the creation and maintenance of software related to a standalone
> > > resource scheduler responsible for scheduling batch jobs and
> > > long-running services on large scale distributed systems running in
> > > on-premises environments as well as different public clouds; and be it
> > > further
> > >
> > > RESOLVED, that the office of "Vice President, Apache YuniKorn" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of the Apache YuniKorn
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache YuniKorn
> > > Project; and be it further
> > >
> > > RESOLVED, that

Re: [VOTE] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-16 Thread Weiwei Yang 
Hi Calvin

Thanks for the suggestion.
We've discussed this in the past, but because that was a pretty early stage
so we did not create another mailing list to manage.
But now since the community grows much bigger, I think we are going to
revisit this and discuss this. Thanks for your suggestion, much appreciated!


On Tue, Feb 15, 2022 at 11:36 PM Calvin Kirs  wrote:

> Wei-Chiu Chuang  于2022年2月16日周三 15:27写道：
>
> > Looking at the project notification settings (
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/YUNIKORN/notifications
> > ),
> >  only issue creation, resolution, close, reopen get sent to dev@, not
> > every
> > jira notification.
> > I think this is reasonable. I'm also fine having it more restricted
> though.
> >
> Just a suggestion, for me, I prefer to be apart. What I can see is that
> several projects I have participated in do this.
> Of course, how to do it depends on the community, which can be discussed in
> the community later. :)
>
> >
> > >
> > > BTW, the dev mailing list is best separated from JIRA notifications
> > (which
> > > can be grouped into the commits mailing list) to allow for more focused
> > > discussions.
> > >
> > >
>
>
> --
> Best wishes！
> CalvinKirs
>

[VOTE] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-15 Thread Weiwei Yang 
Hi Incubator Community

After the discussion in the YuniKorn community [1], and passed the
community vote [2][3]. We have started the discussion in the
general@incubator list [4]. Based on all positive feedback received, we
would like to start this voting thread to request graduating the YuniKorn
project from the incubator as a TLP.

Please provide your vote as one of the following options:

[ ] +1 - Recommend graduation of Apache YuniKorn as a TLP
[ ]  0 -  I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend the graduation of Apache YuniKorn because…

The VOTE will remain open for at least 72 hours.

To summarize what the YuniKorn community has achieved in the incubating
phase:

   - 6 releases were done by 6 different releases managers.
   - 41 unique code contributors and over 1300+ commits.
   - A growing community that added 2 new mentors, 10 new committers, 4 new
   PPMC from 6 different organizations
   - A diverse community that has 6 mentors, 23 PPMC, and 29 committers
   from at least 14 different organizations [5]
   - Well documented web site [6]
   - The maturity self-assessment [7]

[1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
[2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
[3] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
[4] https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
[5] https://yunikorn.apache.org/community/people
[6] https://yunikorn.apache.org/
[7] https://yunikorn.apache.org/community/maturity

--

Establish the Apache YuniKorn Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a standalone resource scheduler responsible for scheduling
batch jobs and long-running services on large scale distributed systems
running in on-premises environments as well as different public clouds.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache YuniKorn Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache YuniKorn Project be and hereby is responsible
for the creation and maintenance of software related to a standalone
resource scheduler responsible for scheduling batch jobs and
long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds; and be it
further

RESOLVED, that the office of "Vice President, Apache YuniKorn" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache YuniKorn
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache YuniKorn
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache YuniKorn
Project:

 * Akhil PB
 * Arun Suresh 
 * Carlo Curino
 * Chaoran Yu  
 * Chenya Zhang
 * Craig Condit
 * DB Tsai 
 * Felix Cheung
 * Holden Karau
 * Jason Darrell Lowe  
 * Jonathan Hung   
 * Junping Du  
 * Kinga Marton
 * Konstantinos Karanasos  
 * Luciano Resende 
 * Subramaniam Krishnan
 * Sunil G 
 * Tao Yang
 * Vinod Kumar Vavilapalli 
 * Wangda Tan      
 * Wei-Chiu Chuang 
 * Weiwei Yang 
 * Wilfred Spiegelenburg   

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Weiwei Yang be appointed to
the office of Vice President, Apache YuniKorn, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further

RESOLVED, that the Apache YuniKorn Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator YuniKorn
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
IncubatorYuniKorn podling encumbered upon the Apache Incubator PMC are
hereafter
discharged.



Thank you
Regards

Weiwei on behalf of the Apache YuniKorn (incubating) community

Re: [DISCUSS] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-15 Thread Weiwei Yang 
Thank you all.
Based on the positive feedback, we will start a voting thread soon.

On Mon, Feb 14, 2022 at 10:22 PM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> Thanks for all the details. According to the maturity self-assessment,
> YuniKorn looks ready for graduation.
>
> +1 (binding)
>
> Regards
> JB
>
> On Tue, Feb 15, 2022 at 7:17 AM Weiwei Yang  wrote:
> >
> > Hi Xun
> >
> > Thanks for your feedback, much appreciated.
> > If there is no other feedback from other IPMC members, we'd like to move
> on
> > to the voting phase.
> >
> > Thanks
> >
> >
> > On Sat, Feb 12, 2022 at 1:13 PM Xun Liu  wrote:
> >
> > > +1 (binding) from me,
> > >
> > > It's the New Year's holiday, so sorry for my late reply to the email.
> > >
> > > I have been following the yunikorn project for 2 years, during which
> time I
> > > attended the yunikorn community networking conference,
> > > where many developers from other Internet companies participated in the
> > > development and discussion of the yunikorn project.
> > > We ourselves have done a lot of testing and technical pre-research with
> > > yunikorn in production.
> > > The App-aware scheduling and Hierarchy Resource Queues of the yunikorn
> > > project can greatly enhance the resource scheduling capability of k8s
> > > and increase the throughput of the App system running in k8s.
> > > These features left a deep impression on us.
> > >
> > > In my opinion, after 2 years of incubation, the yunikorn project has
> > > accumulated 1300+ committes in [1][2][3][4][5][6] project repositories,
> > > and each repository has 20 ~ 30 contributors. Among the PPMC members
> are
> > > many experienced ASF community participants.
> > > There are many companies in China using yunikorn in production.
> > > I think that upgrading yunikorn to a top-level project will be more
> > > conducive to the development of the project.
> > >
> > > good luck!
> > >
> > > [1] https://github.com/apache/incubator-yunikorn-k8shim
> > > [2] https://github.com/apache/incubator-yunikorn-core
> > > [3] https://github.com/apache/incubator-yunikorn-scheduler-interface
> > > [4] https://github.com/apache/incubator-yunikorn-release
> > > [5] https://github.com/apache/incubator-yunikorn-web
> > > [6] https://github.com/apache/incubator-yunikorn-site
> > >
> > > Best Regards,
> > > Xun Liu
> > >
> > >
> > > On Thu, Feb 10, 2022 at 3:22 AM Weiwei Yang  wrote:
> > >
> > > > Hi all
> > > >
> > > > Having the discussion thread [1], passed the community vote [2], and
> the
> > > > vote result is published [3]. Our assessment is that Apache YuniKorn
> > > > (Incubating) is ready to graduate as a TLP. We would like to raise
> the
> > > > discussion to IPMC and collect more feedback towards graduation.
> > > >
> > > > To summarize what the YuniKorn community has achieved in the
> incubating
> > > > phase:
> > > >
> > > >- 6 releases were done by 6 different releases managers.
> > > >- 41 unique code contributors and over 1300+ commits.
> > > >- A growing community that added 2 new mentors, 10 new
> committers, 4
> > > new
> > > >PPMC from 6 different organizations
> > > >- A diverse community that has 6 mentors, 23 PPMC, and 29
> committers
> > > >from at least 14 different organizations [4]
> > > >- Well documented web site [5]
> > > >- The maturity self-assessment [6]
> > > >
> > > > The discussion will open for at least 72 hours.
> > > >
> > > > [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> > > > [2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
> > > > [2] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
> > > > [4] https://yunikorn.apache.org/community/people
> > > > [5] https://yunikorn.apache.org/
> > > > [6] https://yunikorn.apache.org/community/maturity
> > > >
> > > >
> > > >
> > >
> --
> > > >
> > > > Establish the Apache YuniKorn Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in

Re: [DISCUSS] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-14 Thread Weiwei Yang 
Hi Xun

Thanks for your feedback, much appreciated.
If there is no other feedback from other IPMC members, we'd like to move on
to the voting phase.

Thanks


On Sat, Feb 12, 2022 at 1:13 PM Xun Liu  wrote:

> +1 (binding) from me,
>
> It's the New Year's holiday, so sorry for my late reply to the email.
>
> I have been following the yunikorn project for 2 years, during which time I
> attended the yunikorn community networking conference,
> where many developers from other Internet companies participated in the
> development and discussion of the yunikorn project.
> We ourselves have done a lot of testing and technical pre-research with
> yunikorn in production.
> The App-aware scheduling and Hierarchy Resource Queues of the yunikorn
> project can greatly enhance the resource scheduling capability of k8s
> and increase the throughput of the App system running in k8s.
> These features left a deep impression on us.
>
> In my opinion, after 2 years of incubation, the yunikorn project has
> accumulated 1300+ committes in [1][2][3][4][5][6] project repositories,
> and each repository has 20 ~ 30 contributors. Among the PPMC members are
> many experienced ASF community participants.
> There are many companies in China using yunikorn in production.
> I think that upgrading yunikorn to a top-level project will be more
> conducive to the development of the project.
>
> good luck!
>
> [1] https://github.com/apache/incubator-yunikorn-k8shim
> [2] https://github.com/apache/incubator-yunikorn-core
> [3] https://github.com/apache/incubator-yunikorn-scheduler-interface
> [4] https://github.com/apache/incubator-yunikorn-release
> [5] https://github.com/apache/incubator-yunikorn-web
> [6] https://github.com/apache/incubator-yunikorn-site
>
> Best Regards,
> Xun Liu
>
>
> On Thu, Feb 10, 2022 at 3:22 AM Weiwei Yang  wrote:
>
> > Hi all
> >
> > Having the discussion thread [1], passed the community vote [2], and the
> > vote result is published [3]. Our assessment is that Apache YuniKorn
> > (Incubating) is ready to graduate as a TLP. We would like to raise the
> > discussion to IPMC and collect more feedback towards graduation.
> >
> > To summarize what the YuniKorn community has achieved in the incubating
> > phase:
> >
> >- 6 releases were done by 6 different releases managers.
> >- 41 unique code contributors and over 1300+ commits.
> >- A growing community that added 2 new mentors, 10 new committers, 4
> new
> >PPMC from 6 different organizations
> >- A diverse community that has 6 mentors, 23 PPMC, and 29 committers
> >from at least 14 different organizations [4]
> >- Well documented web site [5]
> >- The maturity self-assessment [6]
> >
> > The discussion will open for at least 72 hours.
> >
> > [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> > [2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
> > [2] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
> > [4] https://yunikorn.apache.org/community/people
> > [5] https://yunikorn.apache.org/
> > [6] https://yunikorn.apache.org/community/maturity
> >
> >
> >
> --
> >
> > Establish the Apache YuniKorn Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a standalone resource scheduler responsible for scheduling
> > batch jobs and long-running services on large scale distributed systems
> > running in on-premises environments as well as different public clouds.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache YuniKorn Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache YuniKorn Project be and hereby is responsible
> > for the creation and maintenance of software related to a standalone
> > resource scheduler responsible for scheduling batch jobs and
> > long-running services on large scale distributed systems running in
> > on-premises environments as well as different public clouds; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache YuniKorn

[DISCUSS] Graduate Apache YuniKorn (Incubating) as a Top Level Project

2022-02-09 Thread Weiwei Yang 
Hi all

Having the discussion thread [1], passed the community vote [2], and the
vote result is published [3]. Our assessment is that Apache YuniKorn
(Incubating) is ready to graduate as a TLP. We would like to raise the
discussion to IPMC and collect more feedback towards graduation.

To summarize what the YuniKorn community has achieved in the incubating
phase:

   - 6 releases were done by 6 different releases managers.
   - 41 unique code contributors and over 1300+ commits.
   - A growing community that added 2 new mentors, 10 new committers, 4 new
   PPMC from 6 different organizations
   - A diverse community that has 6 mentors, 23 PPMC, and 29 committers
   from at least 14 different organizations [4]
   - Well documented web site [5]
   - The maturity self-assessment [6]

The discussion will open for at least 72 hours.

[1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
[2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
[2] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
[4] https://yunikorn.apache.org/community/people
[5] https://yunikorn.apache.org/
[6] https://yunikorn.apache.org/community/maturity

--

Establish the Apache YuniKorn Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a standalone resource scheduler responsible for scheduling
batch jobs and long-running services on large scale distributed systems
running in on-premises environments as well as different public clouds.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache YuniKorn Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache YuniKorn Project be and hereby is responsible
for the creation and maintenance of software related to a standalone
resource scheduler responsible for scheduling batch jobs and
long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds; and be it
further

RESOLVED, that the office of "Vice President, Apache YuniKorn" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache YuniKorn
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache YuniKorn
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache YuniKorn
Project:

 * Akhil PB
 * Arun Suresh 
 * Carlo Curino
 * Chaoran Yu  
 * Chenya Zhang
 * Craig Condit
 * DB Tsai 
 * Felix Cheung
 * Holden Karau
 * Jason Darrell Lowe  
 * Jonathan Hung   
 * Junping Du  
 * Kinga Marton
 * Konstantinos Karanasos  
 * Luciano Resende 
 * Subramaniam Krishnan
 * Sunil G 
 * Tao Yang
 * Vinod Kumar Vavilapalli 
 * Wangda Tan  
 * Wei-Chiu Chuang 
 * Weiwei Yang 
 * Wilfred Spiegelenburg   

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Weiwei Yang be appointed to
the office of Vice President, Apache YuniKorn, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further

RESOLVED, that the Apache YuniKorn Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator YuniKorn
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
YuniKorn podling encumbered upon the Apache Incubator PMC are hereafter
discharged.


Thank you
Weiwei

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

2021-08-08 Thread Weiwei Yang 
hi Xun, Justin

Thanks for the suggestion!
I have created https://issues.apache.org/jira/browse/YUNIKORN-789 to
address this.

On Sun, Aug 8, 2021 at 10:48 PM Justin Mclean 
wrote:

> Hi,
>
> > I have a question.
> > I did not see the two files `NOTICE` and `DISCLAIMER` in the
> > [1],[2],[3],[4] repo of incubator-yunikorn.
>
> It would be good if they are there, but what matters is if they end up in
> the release artefacts.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Travis job on github

2021-02-03 Thread Weiwei Yang 
Hi Greg

Agreed. No assumption has been made.
I was just hoping that GitHub can hold it up. Just in case the delays come
back again, the Apache community can look for a solution together.
Asking for help from Microsoft is just one possible option.

Weiwei


On Wed, Feb 3, 2021 at 2:40 AM Greg Stein  wrote:

> On Wed, Feb 3, 2021, 01:36 Weiwei Yang  wrote:
> >...
>
> > we can communicate with Microsoft about giving the Apache
> > repo some extra resources.
> > I guess it won't be a big problem to such a wealthy company 😉
> >
>
> Their wealth does not mean they can give us anything we want. That is a
> fallacy. Their wealth means they can be kind to us, and we should be
> thankful. Microsoft is extremely generous to the Foundation, across many
> paths (sponsorship, Azure, MSDN, etc). Let us not presume that we can keep
> asking for more.
>
> Regards,
> -g
>

Re: Travis job on github

2021-02-02 Thread Weiwei Yang 
t; > > > > > 清华大学 软件学院
> > > > > >
> > > > > >
> > > > > > leerho  于2021年2月1日周一 上午10:25写道：
> > > > > >
> > > > > > > Sorry, I must be missing something.  I don't see LCOV
> format in
> > the
> > > > > list
> > > > > > :)
> > > > > > > Doesn't this mean a complete rework of our toolchain ?
> > > > > > >
> > > > > > > On Sun, Jan 31, 2021 at 1:19 PM Matt Sicker <
> boa...@gmail.com>
> > > > wrote:
>     > > > > > >
> > > > > > > > Using https://github.com/jenkinsci/warnings-ng-plugin
> (already
> > > > > > > > installed) combined with the github integration (also
> > installed),
> > > > you
> > > > > > > > can get that in our CloudBees CI instance. They support
> a lot
> > of
> > > > > > > > formats:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
>     > >
> >
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/SUPPORTED-FORMATS.md
> > > > > > > >
> > > > > > > > On Sun, 31 Jan 2021 at 00:53, leerho 
> wrote:
> > > > > > > > >
> > > > > > > > > I am trying to move from Travis to GitHub actions for
> exactly
> > > > this
> > > > > > > > reason,
> > > > > > > > > but in that process discovered that our coverage
> reporting
> > > chain
> > > > of
> > > > > > > > > Maven/Java/Jacoco/Coveralls does not port to GHA
> because the
> > > > > current
> > > > > > > GHA
> > > > > > > > > adapter for Coveralls only supports LCOV format which
> Jacoco
> > > > > doesn’t
> > > > > > > > > generate.  Converting to CodeCov is a nonstarter
> because
> > > CodeCov
> > > > is
> > > > > > $$!
> > > > > > > > >
> > > > > > > > > If anybody has any ideas, please let me know!
> > > > > > > > >
> > > > > > > > > Lee.
> > > > > > > > >
> > > > > > > > > On Thu, Jan 28, 2021 at 10:02 PM Weiwei Yang <
> > w...@apache.org>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Oh, that's good. Then we have no problem at all.
> > > > > > > > > > Thank you Daniel for pointing this out : )
> > > > > > > > > >
> > > > > > > > > > On Thu, Jan 28, 2021 at 9:48 PM Daniel Widdis <
> > > > wid...@gmail.com>
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > The quota is for private repos.
> Public/open-source repos
> > > are
> > > > > > > > essentially
> > > > > > > > > > > unlimited.
> > > > > > > > > > >
> > > > > > > > > > > On 1/28/21, 9:44 PM, "Weiwei Yang" <
> w...@apache.org>
> > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Thank you all for the suggestions.
> > > > > > > > > > > Looks like github action is an option, we'll
> give a
> > > try.
> > > > > > > > > > > Noticed they offer 2000 action
> minutes/month[1] for
> > > > free, I
> > > > > > > think
> > > > > > > > > > that
> > > > > > > > > > > should be enough for most cases.
> > > > > > > > > > >
> > > > > > > > > > > [1]
> > > > > > > > > > >
> > > > > > > > > > >
> &g

Re: Travis job on github

2021-02-02 Thread Weiwei Yang 
Just a quick update.
The YuniKorn team has done the migration from Travis to the github action,
so far it looks great.
The pipeline now only needs ~20 minutes comparing to the past 6~12hours. We
also use codecov and it also works great with github action.
We are pretty happy with this migration, hope github can keep this up.

Thanks!
Weiwei


On Tue, Feb 2, 2021 at 12:17 PM leerho  wrote:

> Xiangdong, I noticed in your GHA yaml script you included the
> Coveralls-repo-token in plaintext, which is not recommended.  You can have
> INFRA load the token into the GitHub repo, which you can then acquire
> securely using GHA secrets.
>
> That is what we do anyway :)
>
> Cheers,
> Lee.
>
> On Tue, Feb 2, 2021 at 12:18 AM Yuanbo Liu  wrote:
>
> > It would be great if we could run a travis job on a private machine. I
> > believe some companies would be glad to donate machines
> > for unit testing of open source projects.
> >
> > On Tue, Feb 2, 2021 at 3:10 PM leerho  wrote:
> >
> > > Xiangdong,
> > > Thank you, I pretty much came up with the same solution.  Nonetheless,
> It
> > > will be interesting to see how your approach differs from mine, I'm
> sure
> > I
> > > will learn something!
> > >
> > > Cheers,
> > >
> > > Lee.
> > >
> > > On Mon, Feb 1, 2021 at 8:04 PM Xiangdong Huang 
> > wrote:
> > >
> > > > Hi leerho,
> > > >
> > > > > because the current GHA
> > > > adapter for Coveralls only supports LCOV format which Jacoco doesn’t
> > > > generate.
> > > >
> > > > Actually, we can find some way to bypass the LCOV requirements,
> > > > that is... do not use official github action provided by coverall.
> > > >
> > > > In our project (Apache IoTDB), we use maven to compile the project
> and
> > > > use maven plugin to upload code coverage results to Coveralls.
> > > >
> > > > see [1] (search "coveralls"), [2], and [3] (search "Coveralls)".
> > > >
> > > > It works well.
> > > >
> > > > [1] https://github.com/apache/iotdb/blob/master/pom.xml
> > > > [2] https://github.com/apache/iotdb/tree/master/code-coverage
> > > > [3]
> > > >
> > > >
> > >
> >
> https://github.com/apache/iotdb/blob/master/.github/workflows/main-linux.yml
> > > >
> > > > Best,
> > > > ---
> > > > Xiangdong Huang
> > > > School of Software, Tsinghua University
> > > >
> > > >  黄向东
> > > > 清华大学 软件学院
> > > >
> > > >
> > > > leerho  于2021年2月1日周一 上午10:25写道：
> > > >
> > > > > Sorry, I must be missing something.  I don't see LCOV format in the
> > > list
> > > > :)
> > > > > Doesn't this mean a complete rework of our toolchain ?
> > > > >
> > > > > On Sun, Jan 31, 2021 at 1:19 PM Matt Sicker 
> > wrote:
> > > > >
> > > > > > Using https://github.com/jenkinsci/warnings-ng-plugin (already
> > > > > > installed) combined with the github integration (also installed),
> > you
> > > > > > can get that in our CloudBees CI instance. They support a lot of
> > > > > > formats:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/SUPPORTED-FORMATS.md
> > > > > >
> > > > > > On Sun, 31 Jan 2021 at 00:53, leerho  wrote:
> > > > > > >
> > > > > > > I am trying to move from Travis to GitHub actions for exactly
> > this
> > > > > > reason,
> > > > > > > but in that process discovered that our coverage reporting
> chain
> > of
> > > > > > > Maven/Java/Jacoco/Coveralls does not port to GHA because the
> > > current
> > > > > GHA
> > > > > > > adapter for Coveralls only supports LCOV format which Jacoco
> > > doesn’t
> > > > > > > generate.  Converting to CodeCov is a nonstarter because
> CodeCov
> > is
> > > > $$!
> > > > > > >
> > > > > > > If anybody has any ideas, please let me know!
> > > > > > >
> > > > > > > Lee.
> > > > > > >
> > > > > >

Re: Travis job on github

2021-01-28 Thread Weiwei Yang 
Oh, that's good. Then we have no problem at all.
Thank you Daniel for pointing this out : )

On Thu, Jan 28, 2021 at 9:48 PM Daniel Widdis  wrote:

> The quota is for private repos.  Public/open-source repos are essentially
> unlimited.
>
> On 1/28/21, 9:44 PM, "Weiwei Yang"  wrote:
>
> Thank you all for the suggestions.
> Looks like github action is an option, we'll give a try.
> Noticed they offer 2000 action minutes/month[1] for free, I think that
> should be enough for most cases.
>
> [1]
>
> https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
>
> On Thu, Jan 28, 2021 at 6:36 PM Matt Sicker  wrote:
>
> > There's also some hosted CI services here like Jenkins, BuildBot,
> > etc., which may have less queueing issues depending on which service
> > attracts the most build minute usage.
> >
> > On Thu, 28 Jan 2021 at 20:23, Jon Malkin 
> wrote:
> > >
> > > There was an issue a few months ago where the GitHub Actions queue
> was
> > very
> > > laggy for Apache jobs, so just make sure you're trying to be
> efficient
> > > about it. It's also a shared resource.
> > >
> > > That said, (part of) our recently graduated project uses GitHub
> Actions
> > and
> > > we've been happy overall. Another part is currently moving to it
> from
> > > Travis for the exact same reason.
> > >
> > >   jon
> > >
> > > On Thu, Jan 28, 2021, 6:15 PM Juan Pan  wrote:
> > >
> > > > Hi Weiwei,
> > > >
> > > >
> > > > +1 for Jeff’s suggestion.
> > > > We also transfer to GitHub Action, and It generally works well
> so far.
> > > >
> > > >
> > > >
> > > >
> > > > 
>     > > >Juan Pan (Trista)
> > > >
> > > > Senior DBA & PMC of Apache ShardingSphere
> > > > E-mail: panj...@apache.org
> > > >
> > > >
> > > >
> > > >
> > > > On 01/29/2021 08:00，Jeff Zhang wrote：
> > > > Hi Weiwei,
> > > >
> > > > May you can consider to use github action for CI
> > > >
> > > >
> > > >
> > > > Weiwei Yang  于2021年1月29日周五 上午7:58写道：
> > > >
> > > > Hi,
> > > >
> > > > The Apache YuniKorn (Incubating) team leverages Travis to run
> > pre-commit
> > > > checks, but recently the Travis Job stays in the queue for long
> hours
> > (6+
> > > > hours, sometimes more than 10 hours) . This is highly impacting
> the
> > > > productivity. I have reached the Travis support and the response
> I got
> > was
> > > > the jobs got rate limited under Apache repo. Is there any
> suggestion
> > how to
> > > > fix this issue?
> > > >
> > > > Thanks
> > > > Weiwei
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards
> > > >
> > > > Jeff Zhang
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Travis job on github

2021-01-28 Thread Weiwei Yang 
Thank you all for the suggestions.
Looks like github action is an option, we'll give a try.
Noticed they offer 2000 action minutes/month[1] for free, I think that
should be enough for most cases.

[1]
https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions

On Thu, Jan 28, 2021 at 6:36 PM Matt Sicker  wrote:

> There's also some hosted CI services here like Jenkins, BuildBot,
> etc., which may have less queueing issues depending on which service
> attracts the most build minute usage.
>
> On Thu, 28 Jan 2021 at 20:23, Jon Malkin  wrote:
> >
> > There was an issue a few months ago where the GitHub Actions queue was
> very
> > laggy for Apache jobs, so just make sure you're trying to be efficient
> > about it. It's also a shared resource.
> >
> > That said, (part of) our recently graduated project uses GitHub Actions
> and
> > we've been happy overall. Another part is currently moving to it from
> > Travis for the exact same reason.
> >
> >   jon
> >
> > On Thu, Jan 28, 2021, 6:15 PM Juan Pan  wrote:
> >
> > > Hi Weiwei,
> > >
> > >
> > > +1 for Jeff’s suggestion.
> > > We also transfer to GitHub Action, and It generally works well so far.
> > >
> > >
> > >
> > >
> > > 
> > >Juan Pan (Trista)
> > >
> > > Senior DBA & PMC of Apache ShardingSphere
> > > E-mail: panj...@apache.org
> > >
> > >
> > >
> > >
> > > On 01/29/2021 08:00，Jeff Zhang wrote：
> > > Hi Weiwei,
> > >
> > > May you can consider to use github action for CI
> > >
> > >
> > >
> > > Weiwei Yang  于2021年1月29日周五 上午7:58写道：
> > >
> > > Hi,
> > >
> > > The Apache YuniKorn (Incubating) team leverages Travis to run
> pre-commit
> > > checks, but recently the Travis Job stays in the queue for long hours
> (6+
> > > hours, sometimes more than 10 hours) . This is highly impacting the
> > > productivity. I have reached the Travis support and the response I got
> was
> > > the jobs got rate limited under Apache repo. Is there any suggestion
> how to
> > > fix this issue?
> > >
> > > Thanks
> > > Weiwei
> > >
> > >
> > >
> > > --
> > > Best Regards
> > >
> > > Jeff Zhang
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Travis job on github

2021-01-28 Thread Weiwei Yang 
Hi,

The Apache YuniKorn (Incubating) team leverages Travis to run pre-commit
checks, but recently the Travis Job stays in the queue for long hours (6+
hours, sometimes more than 10 hours) . This is highly impacting the
productivity. I have reached the Travis support and the response I got was
the jobs got rate limited under Apache repo. Is there any suggestion how to
fix this issue?

Thanks
Weiwei

[RESULT][VOTE] Release Apache YuniKorn (Incubating) 0.8.0

2020-05-03 Thread Weiwei Yang 
Hi all

Thanks for reviewing and voting for Apache YuniKorn (Incubating) 0.8.0
release, I am happy to announce the release voting has passed with 3 +1
binding votes, no +0 or -1 votes. Binding votes are from IPMC

   - Felix Cheung
   - Jason Lowe
   - Justin Mclean

The voting thread is:
https://lists.apache.org/thread.html/r91414382a61a3e76440142dbfc933bc338fefafd324fca52cd3c8b8c%40%3Cgeneral.incubator.apache.org%3E

Many thanks for all our mentors helping us with the release procedure, and
all IPMC helped us to review and vote for YuniKorn's first release. I will
be working on publishing the artifacts soon.

Thanks
On behalf of Apache YuniKorn (Incubating) community

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.8.0

2020-05-03 Thread Weiwei Yang 
Hi all

Thanks for voting for this release.
I have created YUNIKORN-112
 to track the issues
found in this release.
Now the voting is passed and we can close this, I will send a result notice
shortly. Thank you for the review!!

Weiwei


On Fri, May 1, 2020 at 11:39 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes are fine
> - DISCLAIMER exists
> - LICENSE is OK and is missing mention of this license [1]
> -  NOTICE is fine
> - No unexpected binary files
> - A lot of .yml files are missing an ASF header
> - Can compile from source
>
> Btw the build script don’t have the execute bit set.
>
> Thanks,
> Justin
>
> 1. ./core/docs/design/cross-queue-preemption.md
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Apache YuniKorn (Incubating) 0.8.0

2020-04-29 Thread Weiwei Yang 
Hello IPMC

The Apache YuniKorn community has voted and approved the release Apache
YuniKorn (incubating) 0.8.0. We now kindly request the IPMC members review
and vote in this release.

YuniKorn is a standalone, universal resource scheduler that can support
both long-running and batch workloads. The current release provides a fully
functional resource scheduler for K8s.

YuniKorn community vote thread
https://lists.apache.org/thread.html/r3cee36fffb0b0fe72380f188ca290327168ded8ba59a1da02b4bfbd3%40%3Cdev.yunikorn.apache.org%3E

Vote result thread
https://lists.apache.org/thread.html/r7779887aaada163af09bf6c8b33febf97cc64eb3d0134cc87b2dfc01%40%3Cdev.yunikorn.apache.org%3E

Issues included in this release:
https://issues.apache.org/jira/projects/YUNIKORN/versions/12347742

The release candidate:
https://dist.apache.org/repos/dist/dev/incubator/yunikorn/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:
https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS

Git tag for the release:

   - https://github.com/apache/incubator-yunikorn-core/tree/v0.8.0
   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.8.0
   -
   https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.8.0
   - https://github.com/apache/incubator-yunikorn-web/tree/v0.8.0

The vote will be open for at least 72 hours or until the necessary number
of votes is reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache YuniKorn (Incubating) Team

Re: [VOTE] Accept YuniKorn into Apache Incubator

2020-01-29 Thread Weiwei Yang 
Hi Vinod

Thanks a lot for your help.
We really appreciate it.

Weiwei

On Wed, Jan 29, 2020 at 8:47 PM Vinod Kumar Vavilapalli 
wrote:

> Quick final update on the follow-up process.
>
> I got the mailing lists created through ASF Infra team:
> d...@yunikorn.apache.org, priv...@yunikorn.apache.org,
> iss...@yunikorn.apache.org
>
> Mentors and initial committers, please subscribe using whimsy mailing list
> helper tool: https://whimsy.apache.org/committers/subscribe
>
> JIRA is also created:
> https://issues.apache.org/jira/projects/YUNIKORN/issues/?filter=allopenissues
>
> The rest of the communication will now move to the podling specific lists.
>
> Thanks
> +Vinod
>
> > On Jan 21, 2020, at 8:05 PM, 俊平堵  wrote:
> >
> > Hi,
> >
> >The vote passes with 20 binding +1 votes and 10 non-binding +1 votes
> > and no other votes.
> >
> >
> > +1 (binding)
> >
> > *Felix Cheung*
> >
> > *Craig Russell*
> >
> > *Furkan KAMACI*
> >
> > *Michael Wall*
> >
> > *Sheng Wu*
> >
> > *Kevin Ratnasekera*
> >
> > *Dave Meikle*
> >
> > *Byung-Gon Chun*
> >
> > *Jean-Baptiste Onofré*
> >
> > *Justin Mclean*
> >
> > *Vinayakumar B*
> >
> > *Paul King*
> >
> > *Dave Fisher*
> >
> > *Liang Chen*
> >
> > *Hitesh Shah*
> >
> > *Bertrand Delacretaz*
> >
> > *Arpit Agarwal*
> >
> > *Kevin A. McGrail*
> >
> > *Junping Du*
> >
> > *Jason Lowe*
> >
> >
> >
> > +1 (non-binding)
> >
> > *David Lyle*
> >
> > *Tison*
> >
> > *YuanSheng Wang*
> >
> > *Ming Wen*
> >
> > *Brahma Reddy Battula*
> >
> > *Jeff Zhang*
> >
> > *Yiheng Wang*
> >
> > *Junjie Chen*
> >
> > *Rakesh Radhakrishnan*
> >
> > *Supun Kamburugamuva*
> >
> >
> > I am excited to welcome the YuniKorn community into the Apache Incubator.
> >
> >
> >
> > *Thanks,*
> >
> >
> >
> >
> > *Junping*
> >
> >
> >
> > 俊平堵  于2020年1月20日周一 下午5:34写道：
> >
> >> Agree with Justin. @Vinod Kumar Vavilapalli  ,
> would
> >> you like to do the honor?
> >>
> >> Thanks,
> >>
> >> Junping
> >>
> >> Justin Mclean  于2020年1月19日周日 上午7:58写道：
> >>
> >>> HI,
> >>>
> >>> Probably about time this vote stoped and result announced?
> >>>
> >>> Thanks,
> >>> Justin
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
*Weiwei Yang*
Software Engineer, Cloudera

Create your own email signature
<https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112>

Re: [VOTE] Accept YuniKorn into Apache Incubator

2020-01-23 Thread Weiwei Yang 
Hi Justin

This is helpful, thank you!
I am creating another thread with our mentors to work on those things now.

Thanks
Weiwei

On Thu, Jan 23, 2020 at 5:08 PM Justin Mclean 
wrote:

> HI,
>
> See [1] on how to do this, if you need any help please ask here.
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/guides/mentor.html
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
*Weiwei Yang*
Software Engineer, Cloudera

Create your own email signature
<https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112>

Re: [VOTE] Accept YuniKorn into Apache Incubator

2020-01-23 Thread Weiwei Yang 
Thanks all. This is really exciting!
According to the ASF doc, the next step is Podling Instracture Setup. I
will be working with incubating mentors/champion to move this forward.
Thanks to everyone participating in the discussion and voting!

Weiwei

On Tue, Jan 21, 2020 at 6:35 AM 俊平堵  wrote:

> Hi,
>
> The vote passes with 20 binding +1 votes and 10 non-binding +1 votes
> and no other votes.
>
>
> +1 (binding)
>
> *Felix Cheung*
>
> *Craig Russell*
>
> *Furkan KAMACI*
>
> *Michael Wall*
>
> *Sheng Wu*
>
> *Kevin Ratnasekera*
>
> *Dave Meikle*
>
> *Byung-Gon Chun*
>
> *Jean-Baptiste Onofré*
>
> *Justin Mclean*
>
> *Vinayakumar B*
>
> *Paul King*
>
> *Dave Fisher*
>
> *Liang Chen*
>
> *Hitesh Shah*
>
> *Bertrand Delacretaz*
>
> *Arpit Agarwal*
>
> *Kevin A. McGrail*
>
> *Junping Du*
>
> *Jason Lowe*
>
>
>
> +1 (non-binding)
>
> *David Lyle*
>
> *Tison*
>
> *YuanSheng Wang*
>
> *Ming Wen*
>
> *Brahma Reddy Battula*
>
> *Jeff Zhang*
>
> *Yiheng Wang*
>
> *Junjie Chen*
>
> *Rakesh Radhakrishnan*
>
> *Supun Kamburugamuva*
>
>
> I am excited to welcome the YuniKorn community into the Apache Incubator.
>
>
>
> *Thanks,*
>
>
>
>
> *Junping*
>
>
>
> 俊平堵  于2020年1月20日周一 下午5:34写道：
>
> > Agree with Justin. @Vinod Kumar Vavilapalli  , would
> > you like to do the honor?
> >
> > Thanks,
> >
> > Junping
> >
> > Justin Mclean  于2020年1月19日周日 上午7:58写道：
> >
> >> HI,
> >>
> >> Probably about time this vote stoped and result announced?
> >>
> >> Thanks,
> >> Justin
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>


-- 
*Weiwei Yang*
Software Engineer, Cloudera

Create your own email signature
<https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112>

[DISCUSS] YuniKorn Proposal

2019-12-11 Thread Weiwei Yang 
2.4.3 Core developers
The project was initiated in Cloudera and so the core developers are
heavily from this organization. Tao Yang from Alibaba joined the
development at a very early stage. The core developers of YuniKorn are
(listed in alphabetical order):

 - Akhil PB (Cloudera)
 - Sunil Govindan (Cloudera)
 - Tao Yang (Alibaba)
 - Vinod Vavilapalli (Cloudera)
 - Wangda Tan (Cloudera)
 - Weiwei Yang (Cloudera)
 - Wilfred Spiegelenburg (Cloudera)

Given the origin history, the core development team so far has not been
very diverse, but we’ve been attempting to grow that diversity. We have
every hope to continue building a diverse and sustainable community if the
project gets accepted into Apache.

2.4.4 Alignment
The motivation of YuniKorn project is to resolve common resource scheduling
problems for various workloads, on large scale distributed systems. Apache
is home to one of these systems in the form of Apache Hadoop YARN. Many of
thee workloads that we expect to leverage YuniKorn are computing engines
like Apache Spark, Apache Flink whether they run on top of YARN or on
Kubernetes.

2.5 Known Risks

2.5.1 Orphaned products
The core developers of YuniKorn project from different companies plan to
work full time on this project. Currently, the initial team intends to
continue the investments on the YuniKorn project, it will be integrated
into the solutions to the customers. Several other organizations (like
Alibaba) have also started to evaluate the project, and plan to adopt it in
their production environments. We anticipate the adoption will be further
improved once it becomes an Apache project.

We have also got support from core-platform developers and Apache
committers who are interested in contributing to YuniKorn project from
different companies like Microsoft, Nvidia, Tencent, etc. We’re expecting
to see more contributions from these committers and usage by their internal
platforms. So overall, the risk of YuniKorn being an orphaned project is
low.

2.5.2 Inexperience with Open source
Most of the core developers in YuniKorn project are experienced open source
veterans, several developers are Apache committers and PMC members of other
projects, such as Apache™ Hadoop®. And the development style is already
very likely the Apache way
 - We have open community meetings to discuss designs, problems and roadmaps
 - We publish all patches and issue related discussions on Github
 - We enforce the code review and log all comments in GitHub issues

2.5.3 Length of Incubation
We started the work 10 months ago, so far the groundwork for YuniKorn is
done and the initial version can work with K8s seamlessly. Based on the
initial contributors’ experience in ASF projects, we don’t expect that
there will be huge gaps before YuniKorn can graduate with regarding to
ASF’s policies on software and releases. The goal is to grow the community
quickly and increase the user base within a few months while making
releases that adhere to the ASF standards. When it reaches a reasonable
size of adoption and a strong community with a good number of
committers/PMC members, we can prompt the graduation. We expect the length
of incubation to be approximately 6 to 12 months.

2.5.4 Homogenous Development
The initial proposed list of committers and contributors includes
developers from several institutions and industry participants. The
developers are also from different regions like U.S, Australia, India, and
the development team leverages slack, community mailing list, weekly
community calls to collaborate efficiently.

2.5.5 Reliance on Salaried Developers
Clearly, Cloudera has contributed most of the initial development through
salaried developers. But since the very beginning, YuniKorn is built as a
community effort project. We have people from other organizations that are
already collaborating with us on Github. This includes both at the source
code level, as well as participating in designs and providing feedback
through community calls. We expect our reliance on salaried developers to
decrease drastically during the incubation process itself.

2.5.6 Relationship to Other Apache Products

YuniKorn is very closely related to other Big-Data projects in Apache, such
as Hadoop YARN, Spark, Hive, Flink, etc.

YuniKorn’s core idea is to support both long-running and batch workloads
like Spark, Hive, Flink, etc, and provide a consistent, unified way to
manage and schedule resources for Big Data workloads across resource
managers like Apache™ Hadoop® YARN / Kubernetes and on-premise and cloud
environments.

Many of the core ideas for YuniKorn come from the experience of the initial
team building Apache Hadoop YARN’s schedulers - Capacity Scheduler and Fair
Scheduler.

2.5.7 An Excessive Fascination with the Apache Brand
Many of the initial developers in YuniKorn project are already experienced
Apache committers, PMC members. We understand the value of the Apache way,
and how to operate the project development on a day to day basis. The