Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-24 Thread Chenya Zhang 
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
> >   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
> > >>>

[jira] [Created] (YUNIKORN-1042) "Why YuniKorn" is not rendered properly on mobile

2022-01-24 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-1042:


 Summary: "Why YuniKorn" is not rendered properly on mobile
 Key: YUNIKORN-1042
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1042
 Project: Apache YuniKorn
  Issue Type: Bug
  Components: website
Reporter: Chaoran Yu
 Attachments: IMG_499E342B4680-1.jpeg

Likely due to YUNIKORN-1036, now the Why YuniKorn section is not rendered 
properly when viewed on mobile. See the attached screenshot



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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

2022-01-24 Thread Wilfred Spiegelenburg 
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 
> >>> 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
>   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

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

2022-01-24 Thread Craig Condit 
Sorry folks, looks like another blocker has been identified in 0.12.2 RC3: 
https://issues.apache.org/jira/browse/YUNIKORN-1041 


I’m canceling this vote and will release another RC once we have the fix in 
place.

Thanks,

Craig



> On Jan 21, 2022, at 12:23 PM, Craig Condit  wrote:
> 
> Hello everyone,
> 
> I’d like to call a vote for releasing Apache YuniKorn (incubating) 0.12.2 RC3.
> 
> The release artifacts have been uploaded here: 
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc3/ 
> 
> 
> My public key is located here: 
> https://downloads.apache.org/incubator/yunikorn/KEYS 
> 
> 
> JIRA issues that have been resolved in this release: 
> 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

[jira] [Created] (YUNIKORN-1041) Fix binding of dynamic volumes to pod

2022-01-24 Thread Craig Condit (Jira) 
Craig Condit created YUNIKORN-1041:
--

 Summary: Fix binding of dynamic volumes to pod
 Key: YUNIKORN-1041
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1041
 Project: Apache YuniKorn
  Issue Type: Task
  Components: shim - kubernetes
Reporter: Craig Condit


Use of dynamic volumes is broken after YUNIKORN-872, and fails with:
{noformat}
Warning  PodVolumesBindFailure  37s   yunikorn  bind pod volumes failed, name: 
/, failed to get cached bindings for pod 
{noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-1040) add e2e test that re-starts the scheduler pod

2022-01-24 Thread Wilfred Spiegelenburg (Jira) 
Wilfred Spiegelenburg created YUNIKORN-1040:
---

 Summary: add e2e test that re-starts the scheduler pod
 Key: YUNIKORN-1040
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1040
 Project: Apache YuniKorn
  Issue Type: Task
  Components: test - e2e
Reporter: Wilfred Spiegelenburg


The manual tests that were required for YUNIKORN-1038 should be added as a e2e 
test to make sure that we do not regress that fix.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-1039) add e2e test that uses volumes

2022-01-24 Thread Wilfred Spiegelenburg (Jira) 
Wilfred Spiegelenburg created YUNIKORN-1039:
---

 Summary: add e2e test that uses volumes
 Key: YUNIKORN-1039
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1039
 Project: Apache YuniKorn
  Issue Type: Task
  Components: test - e2e
Reporter: Wilfred Spiegelenburg


In at least one of the e2e tests we should use a pod that uses a PV and PVC.

This should cover more code and allow some of the predicates and bind of the 
volumes. The deployed kind cluster should support this.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org