Re: [DISCUSS] ARM support for Flink

2022-08-26 Thread bo zhaobo
atform. But I am not > sure what is the current situation. TBH, I have not build an ARM image for > Flink. > > Given that we have not finished the migration from azure pipelines to > github action, I believe we still need to setup the self-hosted ARM > machines for azure pipeline.

Re: [DISCUSS] ARM support for Flink

2022-08-24 Thread bo zhaobo
Hi Flink, Any idea about this? ;-) bo zhaobo 于2022年8月23日周二 19:28写道: > Hi Flinkers, > > In 2019, we raised an discussion in Flink about "ARM support for > Flink"[1]. And we got so many helps and supports from Flink community about > introducing a ARM CI system into

[DISCUSS] ARM support for Flink

2022-08-23 Thread bo zhaobo
Hi Flinkers, In 2019, we raised an discussion in Flink about "ARM support for Flink"[1]. And we got so many helps and supports from Flink community about introducing a ARM CI system into Flink community, which is named "OpenLab"[2], and finally we create a full stack regression Flink tests on Open

[RESULT][VOTE] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-08-01 Thread bo zhaobo
Hi everyone, FLIP-250: Support Customized Kubernetes Schedulers Proposal [1] has been accepted. >From vote thread[2] , there were 7 votes(+1), 4 of them are binding votes: - Yang Wang (binding) - Martijn Visser (binding) - Kelu Tao (non-binding) - William Wang (non-binding) - MrL (non-binding) -

Re: [VOTE] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-29 Thread bo zhaobo
at 03:52, MrL wrote: > > > > > +1 (non-binding) > > > > > > > 2022年7月27日 09:18,William Wang 写道: > > > > > > > > +1 (non-binding) > > > > > > > > bo zhaobo 于2022年7月25日周一 09:38写道: > > > > > > > &

[VOTE] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-24 Thread bo zhaobo
Hi all, Thank you very much for all feedback after the discussion in [2][3]. Now I'd like to proceed with the vote for FLIP-250 [1], as no more objections or issues were raised in ML thread [2][3]. The vote will be opened until July 28th earliest(at least 72 hours) unless there is an objection or

Re: [DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-24 Thread bo zhaobo
Hi Marjtin, Thank you very much that all clear. I will raise a Vote for this then. ;-) BR Bo Zhao Martijn Visser 于2022年7月24日周日 01:42写道: > Hi all, > > Thanks a lot for clarifying Yikun! I have no more concerns. > > Best regards, > > Martijn > > Op vr 22 jul. 2022

Re: [DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-22 Thread bo zhaobo
Hi All, Thanks for all feedbacks from you. All of them are helpful and valuable for us. If there is no further comment towards FLIP-250 we introduced, we plan to setup a VOTE thread next Monday. Thank you all !! BR Bo Zhao bo zhaobo 于2022年7月15日周五 10:02写道: > Thanks all, @Yang Wang

Re: [DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-14 Thread bo zhaobo
link K8S and we are happy to improve it. ;-) > > > > > > > > BR, > > > > > > > > Bo Zhao > > > > > > > > Martijn Visser 于2022年7月13日周三 15:19写道: > > > > > > > > > Hi all, > > > > > > > > > &g

Re: [DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-13 Thread bo zhaobo
mprove this situation? > > Best regards, > > Martijn > > [1] https://issues.apache.org/jira/browse/SPARK-36057 > [2] https://issues.apache.org/jira/browse/FLINK-20392 > > Op wo 13 jul. 2022 om 04:11 schreef 王正 : > > > +1 > > > > On 2022/07/07 01:15:13 b

Re: [DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-07 Thread bo zhaobo
> introduced to make the streaming/batch jobs run more smoothly in a shared > K8s cluster. > > Just to remind that the flink-kubernetes-volcano-*.jar will be an optional > jar located in the $FLINK_HOME/opt. Users who want to try the volcano > scheduler need > to copy it to th

[DISCUSS] FLIP-250: Support Customized Kubernetes Schedulers Proposal

2022-07-06 Thread bo zhaobo
Hi, all. I would like to raise a discussion in Flink dev ML about Support Customized Kubernetes Schedulers. Currentlly, Kubernetes becomes more and more polular for Flink Cluster deployment, and its ability is better, especially, it supports customized scheduling. Essentially, in high-performance