- Tc - mailweb.openeuler.org

TC议题申报：关于加速库配合带有硬件license 包引入openEuler 社区策略议题申请
by Dukaitian (Dukaitian, Intelligent Computing R&D) 02 Mar '20

02 Mar '20

Hi,TC: 目前了解到有些项目开发了KAE加速库，软件本身是开源的，目前代码放在github托管平台. 裁决点：软件本身全部开源，但是需要依赖硬件license的特性才能开启的软件，是否可以引入到openEuler社区，进而纳入到openEuler发行光盘。相关背景：左图是license与KAE加速软件的关系，右图是加速库的整体软件框架相关用法：客户在购买license后，在生产阶段或者用户自己通过BMC将license导入到BIOS，由BIOS开启对应的设备，在操作系统测试增加对应的设备，当前KAE 内核通过识别对应设备，目前已经支持openssl/zlib库的加速引擎。如果客户未采购license ，则无法使用KAE提供的加速功能。 [cid:image004.png@01D5F0C1.3D5395A0][cid:image005.png@01D5F0C1.3D5395A0]

1 0

【Meeting Notice】openEuler TC meeting Time: 2020-03-04 10:00-12:00
by Meeting Book 02 Mar '20

02 Mar '20

1 0

apply to setup dev-utils SIG
by myeuler 02 Mar '20

02 Mar '20

apply to setup dev-utils SIG, which collect tools help developers to easy coding. for example: iperf, sar, netperf and so on.

1 0

TC topic collection
by myeuler＠163.com 02 Mar '20

02 Mar '20

1 0

Regarding to improvement to openeuler's wiki and issues handling on gitee
by Huxinwei 28 Feb '20

28 Feb '20

Infra team: On behave of TC, I’m proposing following changes to openEuler infrastructure for your consideration. 1. Regarding to Wiki Background: We think Wiki is a good way to consolidate and present knowledge systematically. openEuler already has its own document site (https://openeuler.org/zh/docs), we think it could be further improved. a) The namespace of pages should be flattened. For example, https://openeuler.org/zh/docs/Administration/简介.html , the name of page implies to be an introduction to system administration. But in fact, it’s an introduction to system only. We propose to add directories for each domain. b) Currently documents are divided into different SIG, we think it’s important to extend it for multiple SIG. For example, if we introduce oVirt into openEuler, the document of oVirt should be part of the https://openeuler.org/zh/docs/Virtualization, not it’s own. c) It’s very different to use cross reference now. We think it is an important feature to have. For example, https://openeuler.org/zh/docs/Administration/设置语言环境.html should refer to systemd. It’ difficult or even impossible to do so now. 2. Regarding to issues handling Background: There’re difficulties during day-to-day work on openEuler community. Especially, when issues are reported. We think it needs to be further improved. a) When an issue is reported, we think it’s very helpful to have it assigned to a default triage. The developers don’t know each other, and even they know each other, they can not match the ID with real people. The best way now is to assigned to a default triage based on the components or sub-module. b) There’re too many messages on the web interface. Developers are easily overwhelmed. We suggest to have a default mail notification for all un-handled or un-closed issue to assigned developers. If there’re existing mechanism we can leverage, please advise too. Looking forward to your feedback and suggestions. Shinwell Technical Committee openEuler Community

2 2

[ 新SIG提案 ] 申请成立oVirt SIG
by Joey Ma 27 Feb '20

27 Feb '20

Hi Dear TC, We are so pleased to make a proposal here for a new SIG: oVirt, the relevant PR is https://gitee.com/openeuler/community/pulls/182 . Please let me take time for a brief introduction on oVirt. oVirt is an open source solution for enterprise virtualization, designed to manage the entire enterprise infrastructure. oVirt uses the trusted KVM hypervisor and is built upon several other community projects. For now, oVirt has already supported x86_64 and PowerPC architecture, but not for ARM64. The new oVirt SIG will enrich the community and work on the migration and optimization on ARM64 platform, which will help users to eliminate the difficulty of deploying oVirt on ARM64 physical machines. Looking forward to your feedback. Thanks for your time. Best regards, Joey

3 3

答复: Re: 【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30
by Huxinwei 19 Feb '20

19 Feb '20

没有这方面的经验，这样基于关键字检索得到的owner，准确率怎么样？发件人: wufengguang 发送时间: 2020年2月19日 16:13 收件人: Huxinwei <huxinwei(a)huawei.com>; tc(a)openeuler.org 抄送: Xiexiuqi <xiexiuqi(a)huawei.com>; Guohanjun (Hanjun Guo) <guohanjun(a)huawei.com>; Zhanghailiang <zhang.zhanghailiang(a)huawei.com>; Xiongwei (William, Euler) <xiongwei888(a)huawei.com>; Wangxun (Dream) <dream.wangxun(a)huawei.com>; Xiehong (Cynthia) <xiehong(a)huawei.com>; Zhangwenfeng (A) <wind.zhangwenfeng(a)huawei.com>; Jiangdayong <jiangdayong(a)huawei.com>; zhangxianmin <zhangxianmin1(a)huawei.com>; caihaomin <caihaomin(a)huawei.com>; Yanan (Euler) <yanan(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Liyongle (Fred) <liyongle(a)huawei.com> 主题: 答复: [Tc] Re: 【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30 关于gitee issue的主动通知机制可能需要长期有人（轮值）做triage。这个人可以作为以下脚本在找不到自动owner的情况下，作为默认接收者。下面是一个技术上的自动triage思路，请大家提意见。背景在有新issue等其他事件发生时，gitee支持email/wechat notification. 然而openEuler包数量众多，精准通知到直接责任人是个挑战。提议在gitee上统一设置通知地址为 <some.robot(a)some.com<mailto:some.robot@some.com>> 然后写一个脚本，跑在一台公有云虚机上 input: a pre-configured large keyword=>owner mapping loop: wait email to <some.robot(a)some.com<mailto:some.robot@some.com>> read issue content map keywords to owner emails forward email to owners 其中的keyword可以是包名字和描述关键字。Owner就是责任人邮箱。这种搜索尤其是相关性打分，如果用elasticsearch来查询的话，效果应该不错。邮件处理脚本样板应该能在github上找到类似的，拿过来改一改，加上我们的自定义逻辑即可。此致，敬礼吴峰光发件人: Huxinwei 发送时间: 2020年2月19日 12:23 收件人: tc(a)openeuler.org<mailto:tc@openeuler.org> 抄送: Xiexiuqi <xiexiuqi(a)huawei.com<mailto:xiexiuqi@huawei.com>>; Guohanjun (Hanjun Guo) <guohanjun(a)huawei.com<mailto:guohanjun@huawei.com>>; Zhanghailiang <zhang.zhanghailiang(a)huawei.com<mailto:zhang.zhanghailiang@huawei.com>>; Xiongwei (William, Euler) <xiongwei888(a)huawei.com<mailto:xiongwei888@huawei.com>>; Wangxun (Dream) <dream.wangxun(a)huawei.com<mailto:dream.wangxun@huawei.com>>; Xiehong (Cynthia) <xiehong(a)huawei.com<mailto:xiehong@huawei.com>>; wufengguang <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>>; Zhangwenfeng (A) <wind.zhangwenfeng(a)huawei.com<mailto:wind.zhangwenfeng@huawei.com>>; Jiangdayong <jiangdayong(a)huawei.com<mailto:jiangdayong@huawei.com>>; zhangxianmin <zhangxianmin1(a)huawei.com<mailto:zhangxianmin1@huawei.com>>; caihaomin <caihaomin(a)huawei.com<mailto:caihaomin@huawei.com>>; Yanan (Euler) <yanan(a)huawei.com<mailto:yanan@huawei.com>>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; Liyongle (Fred) <liyongle(a)huawei.com<mailto:liyongle@huawei.com>> 主题: 答复: [Tc] Re: 【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30 2020-02-19 openEuler TC 第二次例行会议: 10：00 ~ 11：55 与会： Guohanjun myeuler Hailiang Zhang xiexiuqi Shinwell Hu （主持，纪要） Cynthia yanan （议题） Haomin （议题） Hufeng （议题） Wufengguang （列席）缺席： Wangxun 议题一：申请openEuler LTS ISO中不带python2 (by Yanan) 1. TC认同在openEuler LTS中应该去除python2，及依赖python2的功能。提供python3的相应功能来替换。这样有助降低openEuler LTS版本的安全风险。 2. 同意在gitee上为python2建仓，并继续在openEuler社区中提供python2。 TC建议python2在openEuler中进入legacy状态。所有针对python2的issue自动关闭并且建议升级到python3，但可以接纳新的MR。 3. 删除python2过程中可能还会发现兼容性bug。wufengguang建议通过对#！扫描来找到潜在问题点。 TC同意这类问题数量可控，建议yanan执行时注意。议题二：审视iSula开源进展 (by Haomin) 1. iSula开源项目缺少CI。TC建议 - 联系Hufeng了解openEuler的CI如何适配iSula -- 责任人 Haomin - TC跟踪这个问题的解决 -- 责任人 Cynthia 2. 当前gitee上缺少机制来将commit关联到issue等 - 给gitee提issue -- 责任人 Haomin - TC跟踪这个问题的解决，并且梳理和gitee沟通的渠道 -- 责任人 myeuler 3. iSula的release应该遵循流程 - 杨丽之前有开发过相应的流程，请杨丽上TC会议介绍流程 -- 责任人 Cynthia - iSula建议考虑独立的网站，如isula.openeuler.org -- 责任人 Haomin 4. TC认同iSula能够和其他开源项目形成互动，是好的实践方式。后续建议其他项目学习。临时议题：在openEuler上建立独立的wiki系统 (xieqiuxi) 1. TC认同当前gitee上建立wiki缺少功能。建议以openEuler认证的开发人员为范围，构建全功能的wiki。 2. TC整理并正式给INFRA团队提需求 -- 责任人：Shinwell 议题三：开放driver kit到openEuler以支持驱动合入与第三方认证。 1. TC同意开放driver kit，作为openEuler驱动的流程一部分 2. TC请业务团队决策是否开源，以及采用什么license。议题四：openEuler如何及时相应gitee上针对openEuler的特性诉求： 1. TC建议所有的issue在2~3天内acknowlodge。这一SLA建议沟通到openEuler开发人员全员。 2. 当前issue没有好的主动通知机制，依赖开发团队去做polling。TC整理并形成改建需求，反馈给INFRA团队 -- 责任人 xiexiuqi Shinwell 3. 在INFRA改进前，TC建议各个开发团队安排专人定期检视新增issue 议题五：openEuler用户反馈 1. Fred Li未参会，本议题取消临时议题：openEuler是否需要支持桌面系统 (Cynthia) 1. TC委托myeuler牵头，对当前Linux桌面环境现状，以及openEuler的差距做调研分析。 -- 责任 myeuler 总结：下次会议时间 2020-03-04 10:00 am 下次会议召集人 myeuler 发件人: Huxinwei via Tc [mailto:tc@openeuler.org] 发送时间: 2020年2月17日 16:42 收件人: tc(a)openeuler.org<mailto:tc@openeuler.org> 主题: [Tc] Re: 【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30 Hi all, This is welink conference is for next TC regular meeting. I booked it half an hour ahead in case you want to try before the meeting officially started. For now, following topics have been proposed; 1. Review the progress of iSula project. (via Caihaomin) 2. Proposed on a new SIG focusing on openEuler driver test kit. (via Shinwell) 3. Proposed on a way to address feature requests timely (via myeuler) i.e. https://gitee.com/openeuler/community/issues/I196AQ?from=project-issue for this kind of technical issue, we should set up a process assign some guy to respond timely. and make a process to make sure if this kind of request should be turn to be a release requirements. 4. Voice from user (to-be-confirmed) Please feel free to propose additional topics based on your experience. Regards Xinwei From: Meeting Book via Tc [mailto:tc@openeuler.org] Sent: Monday, February 17, 2020 4:34 PM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Subject: [Tc] 【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30 Topic [WeLink Meeting] openEuler TC regular meeting Time 2020-02-19 09:30-12:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/185594445> Meeting ID 185 594 445 Convener 胡欣蔚 Tips: WeMeeting客户端无法入会，请点击会议链接按照提示下载ZOOM客户端入会。 WeMeeting cannot join the conference. Please click the conference link and download the ZOOM to join the conference. Huawei and all its affiliates respect your privacy and are committed to protecting it. When inviting you to join a video meeting, we will collect and use your personal information, including your name, device type, IP address, network type, microphone, speaker, camera, joining time, and leaving time. For more information about Huawei’s privacy policy, visit https://www.huawei.com/cn/privacy-policy

1 0

【Meeting Notice】openEuler TC regular meeting Time: 2020-02-19 09:30-12:30
by Meeting Book 19 Feb '20

19 Feb '20

2 2

【会议纪要】openEuler的tc例会关于关于python2是否在openeuler的LTS iso中是否集成会议纪要
by Yanan (Euler) 19 Feb '20

19 Feb '20

会议参与人：胡欣蔚、熊伟、谢红、张海亮、吴峰光等openEuler的tc例会成员会议时间：2020年2月19日星期三 10:00 背景：python2在2019年12月30日社区已经停止维护，不会提供漏洞补丁和问题支撑，原计划在openeuler的LTS版本的iso中不带python2，并且如果iso中带有python2，外部的安全风险等级较高。会议结论： 1．从提升os质量，安全风险角度考虑，openeuler的iso中不集成，python2相关的包放到repo源里，仅在社区维护，不做LTS支持。 2． Python2相关的软件包还在码云的仓库里，将此类软件包定位成End-of-life，同时需要再软件包中添加readme，告诉开发者，长期不会接纳issue，但是会接受cherry-pick，并建议用户升级此软件包。遗留问题： 1．需要再软件包中添加readme，告诉开发者，长期不会接纳issue，但是会接受cherry-pick，并建议用户升级此软件包。 ---责任人：严安组织去落实 2．原先依赖python2的软件包升级为依赖python3的软件包，需要确认软件包运行态不能隐含的有对python2的依赖。确认方法： ---责任人：严安组织去落实 a) 首先去从上游社区官网上找此版本是否已经说明support python3了 b) 通过使能软件包的单元测试用例来覆盖。 c) 对于没有单元测试用例的软件包，从软件包的依赖、功能重要性上分析，是否需要添加测试用例覆盖。发件人: Yanan (Euler) 发送时间: 2020年2月17日 21:08 收件人: Licihua <licihua(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Xiehong (Cynthia) <xiehong(a)huawei.com>; Qiuchengfeng (qiuchengfeng, Cloud Computing Solution Development Dept) <qiuchengfeng(a)huawei.com>; 'tc(a)openeuler.org' <tc(a)openeuler.org> 抄送: Zhangwenfeng (A) <wind.zhangwenfeng(a)huawei.com>; Jiangdayong <jiangdayong(a)huawei.com>; Zhuyanpeng <zhuyanpeng(a)huawei.com>; Dukaitian (Dukaitian, Intelligent Computing R&D) <dukaitian(a)huawei.com>; Zengweifeng (Weifeng Zeng) <zwfeng(a)huawei.com>; songnannan (A) <songnannan2(a)huawei.com>; Chenxiang (EulerOS) <rose.chen(a)huawei.com>; Hexiaowen (Hex, EulerOS) <hexiaowen(a)huawei.com> 主题: 关于python2是否在openeuler的LTS iso中是否集成讨论背景：python2在2019年12月30日社区已经停止维护，不会提供漏洞补丁和问题支撑，原计划在openeuler的LTS版本的iso中不带python2。分歧点： 1．移动苏研、软件所、银河麒麟和同源OS对python2都有需求，目前还在广泛使用。 2． Redhat8在2019年5月7日发布的iso里带有python2，但是其官网建议用户基于python3进行开发，并且下个版本不会再带入python2。 3． Suse的15SP1在2019年8月12日发布的标准iso没带python2，其Packages包（类似于openeuler的everything）带了python2相关的包，并且推荐用户使用python3。建议：openeuler的iso中不集成，python2相关的包放到repo源里，仅在社区维护，不做LTS支持。 iso中去除python2的方案： 1．挂载openeuler的本地源，使用repo-graph > p2.log找出全部依赖，识别出依赖python2的软件包。目前识别出总计16个软件包强依赖python2，需要通过升级或者回合社区补丁的方式来解除对python2的依赖； 2． iso中本身有Python2相关的包有43个，需要替换为python3相关的包，并且需要查看python3相关包provides的功能相对于python2相关包的provides的功能是否有丢失。风险点： 1．后续iso中新增的包不能引入python2相关的软件包。

1 0

关于python2是否在openeuler的LTS iso中是否集成讨论
by Yanan (Euler) 18 Feb '20

18 Feb '20

背景：python2在2019年12月30日社区已经停止维护，不会提供漏洞补丁和问题支撑，原计划在openeuler的LTS版本的iso中不带python2。分歧点： 1．移动苏研、软件所、银河麒麟和同源OS对python2都有需求，目前还在广泛使用。 2． Redhat8在2019年5月7日发布的iso里带有python2，但是其官网建议用户基于python3进行开发，并且下个版本不会再带入python2。 3． Suse的15SP1在2019年8月12日发布的标准iso没带python2，其Packages包（类似于openeuler的everything）带了python2相关的包，并且推荐用户使用python3。建议：openeuler的iso中不集成，python2相关的包放到repo源里，仅在社区维护，不做LTS支持。 iso中去除python2的方案： 1．挂载openeuler的本地源，使用repo-graph > p2.log找出全部依赖，识别出依赖python2的软件包。目前识别出总计16个软件包强依赖python2，需要通过升级或者回合社区补丁的方式来解除对python2的依赖； 2． iso中本身有Python2相关的包有43个，需要替换为python3相关的包，并且需要查看python3相关包provides的功能相对于python2相关包的provides的功能是否有丢失。风险点： 1．后续iso中新增的包不能引入python2相关的软件包。

2 1

2024

2023

2022

2021

2020

2019

Tc