- Dev - mailweb.openeuler.org

磁盘使用和多机测试
by openEuler conference 03 Jun '21

03 Jun '21

1 0

【会议纪要】SIG-compliance双周例会
by yangcong 02 Jun '21

02 Jun '21

SIG-compliance双周例会：时间：2021年6月1日下午15:30-17:00 与会者（请与会者在下面添加您的姓名）：杨昭、王悦良、杨聪、王建民、颜小兵、陈一雄、吕非、李冠庆、王小军、郑志鹏、黄威俊、魏东、何仁贵、孟朝明议题（描述-发起人）： 1.scantist工具与其它license扫描和漏洞扫描工具优缺点对比分享李冠庆 2. 代码血缘关系分析报告确认系统试用前演示交流王小军 3 解读开源软件license并分析license兼容性李自会议纪要： 1.scantist工具与其它license扫描和漏洞扫描工具优缺点对比分享责任人：李冠庆刘杨教授团队开发了scantist工具，主要功能是对开源软件合规及漏洞风险进行静态扫描。工具的详细内容可参考4月13日的会议纪要。这次分享与Synk(S厂)的fossid、Whitesource公司（W厂）扫描工具进行了比较，从下面的对比图可看出，fossid不支持多维度（第三方组件、许可证友好度、bug是否修复）合规政策，Whitesource不包含信息通知（如漏洞已修复）机制； scantist的在支持多维度合规政策和信息通知机制的基础上，引入了许可证属性分析：（1）企业可自定义合规政策（白名单+黑名单），如MIT协议许可证加入白名单、GPL协议许可证加入黑名单；（2）可通过定义许可证属性防范未知许可证，如第三方许可证协议里包含使用该软件必须开源等字段则给出不建议引入第三方软件的意见；（3）可通过组件内容、有无修复内容等情况，多维度制定政策。如基于许可证属性引入了打分机制，许可证的友好程度作为打分的评断标准之一，方便用户判断。 2.代码血缘关系分析报告确认系统试用前演示交流责任人：王小军集成scanoss软件到jenkins门禁系统上，提供代码血缘关系分析能力。系统提供了基于PR触发和全量扫描的能力，生成的报告中： - 会显示提交的代码与开源软件的相似度，并给出开源软件的链接，提交者需要确认是抄袭的代码。 - 当相似代码经过提交者确认后，再次扫描时不会再提示代码疑似抄袭。系统也可以自定义扫描时间，如一天或者一周扫描一次等；另外，系统还提供漏洞检测功能并给出漏洞的评分。这个工具的配置会陆续开源，并提供给大家使用。现在这个软件系统已经陆续开放使用，可通过web界面查看已上线的仓库的扫描报告：生产环境：HTTPS://SCA.OSINFRA.CN/ 测试环境：HTTP://159.138.49.20:39100/ 遗留问题：由于相关责任人时间冲突，可在下次例会进行分享 1.解读开源软件license并分析license兼容性责任人：李自 | | yangcong | | yangcong_hit(a)163.com | 签名由网易邮箱大师定制

1 0

增加SIG-AccelerationLibrary提案
by Zhangxuelei (Derek) 02 Jun '21

02 Jun '21

各TC委员会成员好，本邮件拟进行关于鲲鹏加速库的新SIG组及项目申报，具体内容参考如下：【SIG名】：AccelearionLibrary 【SIG简介与目的】鲲鹏加速库提供基于鲲鹏指令深度优化开发的专有加速库，还对开源社区提供的ARM原生支持加速库完成了鲲鹏平台兼容性和性能验证，覆盖系统库、压缩、加解密、媒体、数学库、存储、网络等7类加速库，为大数据加解密、分布式存储压缩、视频转码等应用场景提供高性能加速，构建鲲鹏平台的开源生态。同时在建立SIG后将新增第一个项目是AVX2Neon，未来会在SIG组中增加压缩库、系统库等其他加速库内容。【AVX2Neon项目简介】： AVX2Neon是一款接口集合库。当使用Intrinsic类接口的应用程序从传统平台迁移到鲲鹏计算平台时，由于各个平台的Intrinsic函数定义不同，需要逐一对于Intrinsic函数重新进行适配开发。针对该问题，我们提供了AVX2Neon模块，将传统平台的Intrinsic接口集合使用鲲鹏指令重新实现，并封装为独立的接口模块（C语言头文件方式），以减少大量迁移项目重复开发的工作量。用户可以通过将头文件导入应用程序即可继续使用传统平台的Intrinsic函数。注：Intrinsic指的是基于gcc编译的一种内建函数，一般是对处理器高级指令（如向量化指令等）的C内联函数格式封装，各个处理器厂商的接口定义存在较大差异。【License】: Apache 2.0 祝好！张学磊鲲鹏计算产品部 Kunpeng Computing PDU, Huawei Technologies Co., Ltd Mobile: (+86) 18868113668 Email: zhangxuelei4(a)huawei.com<mailto:zhangxuelei4@huawei.com> 浙江省杭州市滨江区360号华为杭研所 No 360, Jiangshu Road, Binjiang District,Hangzhou 310052, P.R.China [鲲鹏社区]<https://www.huaweicloud.com/kunpeng/?utm_source=huaweiyun&utm_medium=stock-…>

1 0

RaspberryPi例会
by openEuler conference 02 Jun '21

02 Jun '21

1 0

sig-Migration 开放会议
by openEuler conference 02 Jun '21

02 Jun '21

1 0

Re: Compiler SIG双周例会【会议纪要】
by hedongbo 01 Jun '21

01 Jun '21

会议纪要 MEETING MINUTES 主题 Subject Compiler SIG双周例会时间 Date & Time 2021年06月01日星期二 10:00-11:00 地点 Location 线上会议与会者 Attendees 郭建军（保兰德），李兵（保兰德），卫少坤（麒麟），ljl（麒麟），陈晨，jianningsheng（ARM），王篁（华为），张云博（华为），贺东博（华为）等纪要者 Note Taker 贺东博议题一：KAEProvider实现原理介绍(贺东博) 1. 分享KAEProvider的实现原理和使用方式 2. 分享KAEProvider的性能测试结果 3. 和保兰德的李兵和建军对实现原理进行了讨论，李兵提出可以默认提供经过注释的kaeprovider.conf配置文件，方便使用。和内部讨论后，该需求很有必要，会带入6.30二进制版本。议题二：arm intrinsic讨论（王篁、ningsheng） 1．对SVE开发过程中遇到的问题进行了讨论分享资料见附件。会议录屏已自动上传至B站: https://www.bilibili.com/video/BV1R54y137BA?from=search&seid=13325926385559… From: hedongbo [mailto:hedongbo@huawei.com] Sent: Monday, May 31, 2021 5:19 PM To: openEuler conference <public(a)openeuler.org>; dev(a)openeuler.org Subject: [Dev] Re: Compiler SIG双周例会新增议题：arm intrinsic讨论 10:30-11:00 From: openEuler conference [mailto:public@openeuler.org] Sent: Friday, May 28, 2021 5:23 PM To: dev(a)openeuler.org<mailto:dev@openeuler.org> Subject: [Dev] Compiler SIG双周例会您好！ openEuler Compiler SIG 邀请您参加 2021-06-01 10:00 召开的ZOOM会议(自动录制) 会议主题：Compiler SIG双周例会会议内容：1. KAEProvider实现原理介绍欢迎上报议题，新增议题回复邮件即可会议链接：https://us06web.zoom.us/j/87277002397?pwd=aXplNFFzVm9reUM2TER3UWNCczdXQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Compiler SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-06-01 10:00, The subject of the conference is Compiler SIG双周例会, Summary: 1. KAEProvider实现原理介绍欢迎上报议题，新增议题回复邮件即可 You can join the meeting at https://us06web.zoom.us/j/87277002397?pwd=aXplNFFzVm9reUM2TER3UWNCczdXQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

安全委员会例会
by openEuler conference 01 Jun '21

01 Jun '21

1 0

sig-confidential-computing双周例会
by openEuler conference 31 May '21

31 May '21

1 0

品牌委员会例会
by openEuler conference 31 May '21

31 May '21

1 0

Compliance-SIG双周例会
by openEuler conference 31 May '21

31 May '21

2 1

【TC】例会顺延//答复: [Tc] TC双周例会
by liyongqiang (H) 31 May '21

31 May '21

此次例会因没有议题申报，顺延至下次列会，请知晓发件人: openEuler conference [mailto:public@openeuler.org] 发送时间: 2021年5月24日 14:13 收件人: tc(a)openeuler.org; dev(a)openeuler.org 主题: [Tc] TC双周例会您好！ openEuler TC SIG 邀请您参加 2021-05-26 10:00 召开的ZOOM会议(自动录制) 会议主题：TC双周例会会议内容：欢迎申报议题会议链接：https://us06web.zoom.us/j/84460589918?pwd=b3BJRjZBQjNyUzYvQk0zay90WmxMQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-26 10:00, The subject of the conference is TC双周例会, Summary: 欢迎申报议题 You can join the meeting at https://us06web.zoom.us/j/84460589918?pwd=b3BJRjZBQjNyUzYvQk0zay90WmxMQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

2 1

Compiler SIG双周例会
by openEuler conference 31 May '21

31 May '21

2 1

Re: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/28 release评审通知
by Wang Jianmin 30 May '21

30 May '21

Hi，Senlin，请问 issue 链接是哪一个？谢谢。 ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of xiasenlin <xiasenlin1(a)huawei.com> Date: Sunday, 30 May 2021 at 9:03 AM To: "release(a)openeuler.org" <release(a)openeuler.org>, "qa(a)openeuler.org" <qa(a)openeuler.org>, "sa-announce(a)openeuler.org" <sa-announce(a)openeuler.org>, "dev(a)openeuler.org" <dev(a)openeuler.org> Cc: "Guoge(JVM)" <ge.guo(a)huawei.com>, chenyaqiang <chenyaqiang(a)huawei.com>, "liyongqiang (H)" <liyongqiang10(a)huawei.com>, "Chenzhendong (alex)" <alex.chen(a)huawei.com>, Liyiting <liyiting(a)huawei.com>, Mingpei <mingpei(a)huawei.com>, Xuxiaosong <xuxiaosong(a)huawei.com>, Solar <Hufeng>, "<solar.hu(a)huawei.com>, Yanxiaobing <yanxiaobing(a)huawei.com>, Liujingang (Bob) ," <liujingang09(a)huawei.com>, "fanjiachen (A)" <fanjiachen3(a)huawei.com>, guoxiaoqi <guoxiaoqi2(a)huawei.com>, xingchaochao <xingchaochao(a)huawei.com>, Yanxiaobing <yanxiaobing(a)huawei.com> Subject: [Dev] 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/28 release评审通知 openEuler 20.03 LTS SP1 Update 20210528 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月30日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210526 代码冻结： 20210526 转测试时间：20210527 版本发布： 20210530 本次更新主要涉及：mysql、ImageMagick等包的CVE修复以及RPM的bugfix；修复cve：49个 CVE清单： issue ID任务标题CVE评分关联仓库责任田是否涉及接口变更接口变更是否有影响 I3NYKTCVE-2021-22129.8src-openEuler/mysql智能计算是无（仅新增命令） I3NYKSCVE-2021-22999.8src-openEuler/mysql智能计算是无（仅新增命令） I3NYKRCVE-2021-22937.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKQCVE-2021-22137.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKPCVE-2021-22157.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKOCVE-2021-22787.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKNCVE-2021-21647.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKMCVE-2021-22088.8src-openEuler/mysql智能计算是无（仅新增命令） I3NYKLCVE-2021-22177.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKKCVE-2021-22037.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKJCVE-2021-22267.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKICVE-2021-22028.2src-openEuler/mysql智能计算是无（仅新增命令） I3NYKHCVE-2021-22327.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKGCVE-2021-23017.1src-openEuler/mysql智能计算是无（仅新增命令） I3NYKFCVE-2021-22984.9src-openEuler/mysql智能计算是无（仅新增命令） I3NYKECVE-2021-22304.9src-openEuler/mysql智能计算是无（仅新增命令） I3NYKDCVE-2021-23005.5src-openEuler/mysql智能计算是无（仅新增命令） I3NYKCCVE-2021-23046.5src-openEuler/mysql智能计算是无（仅新增命令） I3NX9ACVE-2021-23083.7src-openEuler/mysql智能计算是无（仅新增命令） I3NX96CVE-2021-21724.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX91CVE-2021-21944.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX90CVE-2021-21704.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX8PCVE-2021-21964.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX8OCVE-2021-22016.1src-openEuler/mysql智能计算是无（仅新增命令） I3NX8MCVE-2021-21804.4src-openEuler/mysql智能计算是无（仅新增命令） I3NX8JCVE-2021-23074.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX8ICVE-2021-21694.4src-openEuler/mysql智能计算是无（仅新增命令） I3NX8GCVE-2021-21714.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX8FCVE-2021-23054.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX7XCVE-2021-21794.9src-openEuler/mysql智能计算是无（仅新增命令） I3NX7WCVE-2021-21746.5src-openEuler/mysql智能计算是无（仅新增命令） I3NX7VCVE-2021-21935.5src-openEuler/mysql智能计算是无（仅新增命令） I3OC6GCVE-2021-21664.9src-openEuler/mysql智能计算是无（仅新增命令） I3OC66CVE-2021-21447.2src-openEuler/mysql智能计算是无（仅新增命令） I3OC26CVE-2021-21464.9src-openEuler/mysql智能计算是无（仅新增命令） I3OC20CVE-2021-21604.9src-openEuler/mysql智能计算是无（仅新增命令） I3OC1VCVE-2021-21624.3src-openEuler/mysql智能计算是无（仅新增命令） I3OUV2CVE-2020-277527.1src-openEuler/ImageMagick智能计算否不涉及 I3QYAHCVE-2020-94928.8src-openEuler/hadoop智能计算否不涉及 I3RQ13CVE-2021-203107.5src-openEuler/ImageMagick智能计算否不涉及 I3RQ12CVE-2021-203097.5src-openEuler/ImageMagick智能计算否不涉及 I3RQ10CVE-2021-203127.5src-openEuler/ImageMagick智能计算否不涉及 I3RQ0OCVE-2021-203117.5src-openEuler/ImageMagick智能计算否不涉及 I3RQ0MCVE-2021-203137.5src-openEuler/ImageMagick智能计算否不涉及 I3RQQICVE-2021-233839.8src-openEuler/nodejs-handlebars智能计算否不涉及 I3SC5RCVE-2020-150787.5src-openEuler/openvpn智能计算否不涉及 I3SC4UCVE-2021-35048.1src-openEuler/hivex智能计算否不涉及 I3SCANCVE-2020-277693.3src-openEuler/ImageMagick智能计算否不涉及 BUgfix清单： bug/featurerelated reporelated issue/PR责任田修复tpm2-abrmd-selinux子包中存储的SELinux标签信息tpm2-abrmdhttps://gitee.com/open_euler… 构建时长优化clanghttps://gitee.com/open_euler/dashboard?issue_id=I3AGT3智能计算 rpm bug修复，主要问题是升级rpm、rpm-libs包后，影响其他软件包升级及yum等工具使用rpmhttps://gitee.com/open_eul… 例外说明：本周转测的audit升级和fuse拆包因为issue未闭环，不发布，计划下周解决后发布发件人: xiasenlin 发送时间: 2021年5月24日 10:37 收件人: release(a)openeuler.org; qa(a)openeuler.org; sa-announce(a)openeuler.org; dev(a)openeuler.org 抄送: Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com>; xingchaochao <xingchaochao(a)huawei.com> 主题: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/20 release评审通知 openEuler 20.03 LTS SP1 Update 20210520 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月24日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210519 代码冻结： 20210519 转测试时间：20210520 版本发布： 20210524 本次更新主要涉及：qemu、ruby等包的CVE修复以及libvirt的新特性IO悬挂，需要与qemu一起发布；修复cve：9个 CVE清单： CVE-2021-34166次要src-openEuler/qemu CVE-2021-34095.7次要src-openEuler/qemu CVE-2021-33923.2不重要src-openEuler/qemu CVE-2019-145625.5次要src-openEuler/edk2 CVE-2020-250855次要src-openEuler/qemu CVE-2021-202086.1次要src-openEuler/cifs-utils CVE-2021-289657.5主要src-openEuler/ruby CVE-2021-200957.8主要src-openEuler/babel CVE-2020-180329.8严重src-openEuler/graphviz 涉及新增libvirt特性一个 From: xiasenlin Sent: Friday, May 14, 2021 6:15 PM To: 'release(a)openeuler.org' <release(a)openeuler.org>; 'qa(a)openeuler.org' <qa(a)openeuler.org>; 'sa-announce(a)openeuler.org' <sa-announce(a)openeuler.org>; 'dev(a)openeuler.org' <dev(a)openeuler.org> Cc: Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com> Subject: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知 openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月15日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210515 代码冻结： 20210512 转测试时间：20210514 版本发布： 20210515 本次更新主要涉及：golang、xstream等；修复cve：25个 CVE清单： CVE-2021-29425 次要 src-openEuler/apache-commons-io CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-27506 次要 src-openEuler/clamav CVE-2021-3448 不重要 src-openEuler/dnsmasq CVE-2021-29470 次要 src-openEuler/exiv2 CVE-2021-29457 主要 src-openEuler/exiv2 CVE-2021-29458 次要 src-openEuler/exiv2 CVE-2021-28650 次要 src-openEuler/gnome-autoar CVE-2021-27918 主要 src-openEuler/golang CVE-2021-28168 次要 src-openEuler/jersey CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-15169 次要 src-openEuler/rubygem-actionview CVE-2021-21349 主要 src-openEuler/xstream CVE-2021-21350 严重 src-openEuler/xstream CVE-2021-21348 主要 src-openEuler/xstream CVE-2021-21351 严重 src-openEuler/xstream CVE-2021-21341 主要 src-openEuler/xstream CVE-2021-21342 严重 src-openEuler/xstream CVE-2021-21343 主要 src-openEuler/xstream CVE-2021-21344 严重 src-openEuler/xstream CVE-2021-21345 严重 src-openEuler/xstream CVE-2021-21346 严重 src-openEuler/xstream CVE-2021-21347 严重 src-openEuler/xstream From: guoxiaoqi Sent: Friday, May 14, 2021 9:34 AM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com> Cc: Yanxiaobing <yanxiaobing(a)huawei.com>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com>; wangchong (J) <wangchong56(a)huawei.com>; yaokai (G) <yaokai13(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; xiasenlin <xiasenlin1(a)huawei.com> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试新增依赖软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-ioCVESP1不涉及openEuler src-openEuler/binutilsCVESP1不涉及基础服务 src-openEuler/dnsmasqCVESP1不涉及网络组 src-openEuler/exiv2CVESP1不涉及网络组 src-openEuler/gnome-autoarCVESP1不涉及网络组 src-openEuler/golangCVESP1不涉及容器组 src-openEuler/jerseyCVESP1不涉及openEuler src-openEuler/python-jinja2CVESP1不涉及基础服务 src-openEuler/rubygem-actionviewCVESP1不涉及openEuler src-openEuler/velocityCVESP1不涉及openEuler src-openEuler/xstreamCVESP1不涉及openEuler src-openEuler/mxparser依赖SP1不涉及openEuler src-openEuler/xmlpull依赖SP1不涉及openEuler From: guoxiaoqi Sent: Thursday, May 13, 2021 9:10 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com> Cc: Yanxiaobing <yanxiaobing(a)huawei.com>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com>; wangchong (J) <wangchong56(a)huawei.com>; yaokai (G) <yaokai13(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试更新，xstream不涉及接口变更。thrift涉及变更，本次版本暂时不发布软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-ioCVESP1不涉及openEuler src-openEuler/binutilsCVESP1不涉及基础服务 src-openEuler/dnsmasqCVESP1不涉及网络组 src-openEuler/exiv2CVESP1不涉及网络组 src-openEuler/gnome-autoarCVESP1不涉及网络组 src-openEuler/golangCVESP1不涉及容器组 src-openEuler/jerseyCVESP1不涉及openEuler src-openEuler/python-jinja2CVESP1不涉及基础服务 src-openEuler/rubygem-actionviewCVESP1不涉及openEuler src-openEuler/velocityCVESP1不涉及openEuler src-openEuler/xstreamCVESP1不涉及openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… From: guoxiaoqi Sent: Thursday, May 13, 2021 3:39 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com> Cc: Yanxiaobing <yanxiaobing(a)huawei.com>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com>; wangchong (J) <wangchong56(a)huawei.com>; yaokai (G) <yaokai13(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com> Subject: 【20.03-LTS-SP1 512 update周版本】启动测试请启动openEuler-20.03-LTS-SP1 2021年512 周版本测试软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-ioCVESP1不涉及openEuler src-openEuler/binutilsCVESP1不涉及基础服务 src-openEuler/dnsmasqCVESP1不涉及网络组 src-openEuler/exiv2CVESP1不涉及网络组 src-openEuler/gnome-autoarCVESP1不涉及网络组 src-openEuler/golangCVESP1不涉及容器组 src-openEuler/jerseyCVESP1不涉及openEuler src-openEuler/python-jinja2CVESP1不涉及基础服务 src-openEuler/rubygem-actionviewCVESP1不涉及openEuler src-openEuler/velocityCVESP1不涉及openEuler src-openEuler/xstreamCVESP1涉及接口变更openEuler src-openEuler/thriftCVESP1不涉及openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

1 0

【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/28 release评审通知
by xiasenlin 30 May '21

30 May '21

openEuler 20.03 LTS SP1 Update 20210528 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月30日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210526 代码冻结： 20210526 转测试时间：20210527 版本发布： 20210530 本次更新主要涉及：mysql、ImageMagick等包的CVE修复以及RPM的bugfix；修复cve：49个 CVE清单： issue ID 任务标题 CVE评分关联仓库责任田是否涉及接口变更接口变更是否有影响 I3NYKT CVE-2021-2212 9.8 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKS CVE-2021-2299 9.8 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKR CVE-2021-2293 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKQ CVE-2021-2213 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKP CVE-2021-2215 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKO CVE-2021-2278 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKN CVE-2021-2164 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKM CVE-2021-2208 8.8 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKL CVE-2021-2217 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKK CVE-2021-2203 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKJ CVE-2021-2226 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKI CVE-2021-2202 8.2 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKH CVE-2021-2232 7.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKG CVE-2021-2301 7.1 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKF CVE-2021-2298 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKE CVE-2021-2230 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKD CVE-2021-2300 5.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NYKC CVE-2021-2304 6.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX9A CVE-2021-2308 3.7 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX96 CVE-2021-2172 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX91 CVE-2021-2194 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX90 CVE-2021-2170 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8P CVE-2021-2196 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8O CVE-2021-2201 6.1 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8M CVE-2021-2180 4.4 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8J CVE-2021-2307 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8I CVE-2021-2169 4.4 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8G CVE-2021-2171 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX8F CVE-2021-2305 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX7X CVE-2021-2179 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX7W CVE-2021-2174 6.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3NX7V CVE-2021-2193 5.5 src-openEuler/mysql 智能计算是无（仅新增命令） I3OC6G CVE-2021-2166 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3OC66 CVE-2021-2144 7.2 src-openEuler/mysql 智能计算是无（仅新增命令） I3OC26 CVE-2021-2146 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3OC20 CVE-2021-2160 4.9 src-openEuler/mysql 智能计算是无（仅新增命令） I3OC1V CVE-2021-2162 4.3 src-openEuler/mysql 智能计算是无（仅新增命令） I3OUV2 CVE-2020-27752 7.1 src-openEuler/ImageMagick 智能计算否不涉及 I3QYAH CVE-2020-9492 8.8 src-openEuler/hadoop 智能计算否不涉及 I3RQ13 CVE-2021-20310 7.5 src-openEuler/ImageMagick 智能计算否不涉及 I3RQ12 CVE-2021-20309 7.5 src-openEuler/ImageMagick 智能计算否不涉及 I3RQ10 CVE-2021-20312 7.5 src-openEuler/ImageMagick 智能计算否不涉及 I3RQ0O CVE-2021-20311 7.5 src-openEuler/ImageMagick 智能计算否不涉及 I3RQ0M CVE-2021-20313 7.5 src-openEuler/ImageMagick 智能计算否不涉及 I3RQQI CVE-2021-23383 9.8 src-openEuler/nodejs-handlebars 智能计算否不涉及 I3SC5R CVE-2020-15078 7.5 src-openEuler/openvpn 智能计算否不涉及 I3SC4U CVE-2021-3504 8.1 src-openEuler/hivex 智能计算否不涉及 I3SCAN CVE-2020-27769 3.3 src-openEuler/ImageMagick 智能计算否不涉及 BUgfix清单： bug/feature related repo related issue/PR 责任田修复tpm2-abrmd-selinux子包中存储的SELinux标签信息 tpm2-abrmd https://gitee.com/open_euler/dashboard?issue_id=I3SHS5 基础服务构建时长优化 clang https://gitee.com/open_euler/dashboard?issue_id=I3AGT3 智能计算 rpm bug修复，主要问题是升级rpm、rpm-libs包后，影响其他软件包升级及yum等工具使用 rpm https://gitee.com/open_euler/dashboard?issue_id=I3RPU3 基础服务例外说明：本周转测的audit升级和fuse拆包因为issue未闭环，不发布，计划下周解决后发布发件人: xiasenlin 发送时间: 2021年5月24日 10:37 收件人: release(a)openeuler.org; qa(a)openeuler.org; sa-announce(a)openeuler.org; dev(a)openeuler.org 抄送: Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com>; xingchaochao <xingchaochao(a)huawei.com> 主题: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/20 release评审通知 openEuler 20.03 LTS SP1 Update 20210520 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月24日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210519 代码冻结： 20210519 转测试时间：20210520 版本发布： 20210524 本次更新主要涉及：qemu、ruby等包的CVE修复以及libvirt的新特性IO悬挂，需要与qemu一起发布；修复cve：9个 CVE清单： CVE-2021-3416 6 次要 src-openEuler/qemu CVE-2021-3409 5.7 次要 src-openEuler/qemu CVE-2021-3392 3.2 不重要 src-openEuler/qemu CVE-2019-14562 5.5 次要 src-openEuler/edk2 CVE-2020-25085 5 次要 src-openEuler/qemu CVE-2021-20208 6.1 次要 src-openEuler/cifs-utils CVE-2021-28965 7.5 主要 src-openEuler/ruby CVE-2021-20095 7.8 主要 src-openEuler/babel CVE-2020-18032 9.8 严重 src-openEuler/graphviz 涉及新增libvirt特性一个 From: xiasenlin Sent: Friday, May 14, 2021 6:15 PM To: 'release(a)openeuler.org' <release(a)openeuler.org<mailto:release@openeuler.org>>; 'qa(a)openeuler.org' <qa(a)openeuler.org<mailto:qa@openeuler.org>>; 'sa-announce(a)openeuler.org' <sa-announce(a)openeuler.org<mailto:sa-announce@openeuler.org>>; 'dev(a)openeuler.org' <dev(a)openeuler.org<mailto:dev@openeuler.org>> Cc: Guoge(JVM) <ge.guo(a)huawei.com<mailto:ge.guo@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; Chenzhendong (alex) <alex.chen(a)huawei.com<mailto:alex.chen@huawei.com>>; Liyiting <liyiting(a)huawei.com<mailto:liyiting@huawei.com>>; Mingpei <mingpei(a)huawei.com<mailto:mingpei@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; guoxiaoqi <guoxiaoqi2(a)huawei.com<mailto:guoxiaoqi2@huawei.com>> Subject: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知 openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月15日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210515 代码冻结： 20210512 转测试时间：20210514 版本发布： 20210515 本次更新主要涉及：golang、xstream等；修复cve：25个 CVE清单： CVE-2021-29425 次要 src-openEuler/apache-commons-io CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-27506 次要 src-openEuler/clamav CVE-2021-3448 不重要 src-openEuler/dnsmasq CVE-2021-29470 次要 src-openEuler/exiv2 CVE-2021-29457 主要 src-openEuler/exiv2 CVE-2021-29458 次要 src-openEuler/exiv2 CVE-2021-28650 次要 src-openEuler/gnome-autoar CVE-2021-27918 主要 src-openEuler/golang CVE-2021-28168 次要 src-openEuler/jersey CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-15169 次要 src-openEuler/rubygem-actionview CVE-2021-21349 主要 src-openEuler/xstream CVE-2021-21350 严重 src-openEuler/xstream CVE-2021-21348 主要 src-openEuler/xstream CVE-2021-21351 严重 src-openEuler/xstream CVE-2021-21341 主要 src-openEuler/xstream CVE-2021-21342 严重 src-openEuler/xstream CVE-2021-21343 主要 src-openEuler/xstream CVE-2021-21344 严重 src-openEuler/xstream CVE-2021-21345 严重 src-openEuler/xstream CVE-2021-21346 严重 src-openEuler/xstream CVE-2021-21347 严重 src-openEuler/xstream From: guoxiaoqi Sent: Friday, May 14, 2021 9:34 AM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>>; xiasenlin <xiasenlin1(a)huawei.com<mailto:xiasenlin1@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试新增依赖软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler src-openEuler/mxparser 依赖 SP1 不涉及 openEuler src-openEuler/xmlpull 依赖 SP1 不涉及 openEuler From: guoxiaoqi Sent: Thursday, May 13, 2021 9:10 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试更新，xstream不涉及接口变更。thrift涉及变更，本次版本暂时不发布软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… From: guoxiaoqi Sent: Thursday, May 13, 2021 3:39 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; guoxiaoqi <guoxiaoqi2(a)huawei.com<mailto:guoxiaoqi2@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: 【20.03-LTS-SP1 512 update周版本】启动测试请启动openEuler-20.03-LTS-SP1 2021年512 周版本测试软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 涉及接口变更 openEuler src-openEuler/thrift CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base…

1 0

【会议纪要】RE: [Tc] virt-sig双周例会0528
by Chenqun (kuhn) 29 May '21

29 May '21

时间：2021年5月28日 14：15 - 15：40 参会人员来自：麒麟、统信、移动、电信、浪潮、中国电子集团、华为等居多公司成员及个人参与者（详见与会人员信息） 2020-05-28会议纪要： 1、openEuler 版本需求进展当前openEuler 20.03 LTS SP2版本Feature 9个，已开展测试过程中。新增2个Intel CPU支持Cooper lake和 Cascade lake，预期在7月30日完成SP2 Update版本发布；各个Feature说明：https://gitee.com/openeuler/qemu/wikis/openEuler%2020.03%20LTS%… 2、分享了基于stratovirt的安全容器配置方法和使用演示主要分享了基于StratoVirt安全容器详细配置操作方法，现场操作演示安全容器效果；视频连接：https://www.bilibili.com/video/BV1eB4y1u7qH 本主题时间段：00:20:35~ 00:47:24 3、开放式议题会议讨论：基于virt sig组参与者提问及问题答复，主要涉及问题情况如下 1、介绍6月10日北京开发者日邀请及参与方式； 2、openEule支持飞腾服务器情况求助及介绍； 3、参与openEuler社区贡献指导及CLA签署说明介绍； 4、Virt sig当前贡献者介绍； 5、openEuler版本虚拟化最佳性能实践介绍；参会人信息： [cid:image005.jpg@01D7549C.CF6D09E0] [cid:image006.jpg@01D7549C.CF6D09E0] From: openEuler conference [mailto:public@openeuler.org] Sent: Thursday, May 27, 2021 11:51 AM To: virt(a)openeuler.org; dev(a)openeuler.org; tc(a)openeuler.org Subject: [Tc] virt-sig双周例会0528 您好！ openEuler Virt SIG 邀请您参加 2021-05-28 14:15 召开的ZOOM会议(自动录制) 会议主题：virt-sig双周例会0528 会议内容： 1、openEuler 版本需求进展 2、基于stratovirt的安全容器配置方法和使用演示会议链接：https://us06web.zoom.us/j/82747035194?pwd=YTlWRGxwZFZrY1lRYWR3N21rMGxGQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Virt SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-28 14:15, The subject of the conference is virt-sig双周例会0528, Summary: 1、openEuler 版本需求进展 2、基于stratovirt的安全容器配置方法和使用演示 You can join the meeting at https://us06web.zoom.us/j/82747035194?pwd=YTlWRGxwZFZrY1lRYWR3N21rMGxGQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

@全球开发者，openEuler Developer Day 2021邀请函来啦！
by Marketing openEuler 28 May '21

28 May '21

[image: cid:image001.jpg@01D753CF.6DB345C0] <https://e-campaign.huawei.com/events2/registerPc/pcRegister.html?eventId=44…> [image: cid:image002.jpg@01D753CF.6DB345C0] [image: cid:image003.jpg@01D753CF.6DB345C0] [image: cid:image004.jpg@01D753CF.6DB345C0] [image: cid:image005.jpg@01D753CF.6DB345C0] [image: cid:image006.jpg@01D753CF.6DB345C0] [image: cid:image007.jpg@01D753CF.6DB345C0]

1 0

@全球开发者，openEuler Developer Day 2021邀请函来啦！
by Marketing openEuler 28 May '21

28 May '21

[image: cid:image001.jpg@01D753CF.6DB345C0] <https://e-campaign.huawei.com/events2/registerPc/pcRegister.html?eventId=44…> [image: cid:image002.jpg@01D753CF.6DB345C0] [image: cid:image003.jpg@01D753CF.6DB345C0] [image: cid:image004.jpg@01D753CF.6DB345C0] [image: cid:image005.jpg@01D753CF.6DB345C0] [image: cid:image006.jpg@01D753CF.6DB345C0] [image: cid:image007.jpg@01D753CF.6DB345C0]

1 0

openEuler 20.03 LTS SP2 Test round 3转测试通知
by Xuxiaosong 28 May '21

28 May '21

转测试计划比原计划有2天延期。请相关责任人最晚于2021-5-29前完成特性进展更新为正常状态。 Test round 3版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-20.03-LTS-SP2/openeuler-2021-05-2… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 20.03-LTS-SP2-round-3）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-20.03-… 1、本轮转5个特性见附件； 2、新增和删除包见附件； Test round1已解决问题单37个，未解决的问题单40，详见： https://e.gitee.com/open_euler/issues/list?is%5Bmilestone_id%5D=69297&is%5B… https://e.gitee.com/open_euler/issues/list?is%5Bmilestone_id%5D=116380&is%5… https://e.gitee.com/open_euler/issues/list?is%5Bmilestone_id%5D=118806&is%5… Release plan Stage name Begin time End time key feature collect 2021-03-16 2021-03-31 Develop 2021-03-16 2021-04-26 Kernel freezing 2021-04-16 2021-04-16 Build 2021-04-26 2021-04-30 Test round 1 2021-05-6 2021-05-12 Test round 2 2021-05-17 2021-05-25 Test round 3（we are here） 2021-05-26 2021-06-02 Test round 4 2021-06-03 2021-06-07 Test round 5 2021-06-09 2021-06-11 release 2021-06-28 2021-06-30 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 21.03，vmtop支持x86<https://gitee.com/openeuler/release-management/issues/I3NLWF?from=project-i…> Testing 2 openEuler 20.03-LTS-SP2支持内存分级扩展特性<https://gitee.com/openeuler/release-management/issues/I2C2NI?from=project-i…> Testing storage liuzhiqiang26<https://gitee.com/liuzhiqiang26> 3 openEuler 20.03-LTS-SP2版本集成secgear组件<https://gitee.com/openeuler/release-management/issues/I3JE3U?from=project-i…> Testing sig-confidential-computing chenmaodong<https://gitee.com/chenmaodong> 4 openEuler 20.03 LTS SP2 support OpenStack Rocky discussion sig-openstack @joec88 @liksh @xiyuanwang @huangtianhua 5 openEuler 20.03 LTS SP2支持osinfo软件包<https://gitee.com/openeuler/release-management/issues/I3N30H?from=project-i…> Testing 6 openEuler 20.03 LTS SP2开源openEuler-rpm-config宏定义文件<https://gitee.com/openeuler/release-management/issues/I3N30J?from=project-i…> Testing 7 openEuler 20.03 LTS SP2 支持 compat-openssl10、libzip等<https://gitee.com/openeuler/release-management/issues/I3N30L?from=project-i…> Testing 8 openEuler 20.03 LTS SP2 支持libwbxml、hyperscan<https://gitee.com/openeuler/release-management/issues/I3N30N?from=project-i…> Testing 9 openEuler 20.03 LTS SP2支持microcode_ctl<https://gitee.com/openeuler/release-management/issues/I3N30S?from=project-i…> Testing 10 openEuler 20.03 LTS SP2支持bcc软件包<https://gitee.com/openeuler/release-management/issues/I3N30Q?from=project-i…> Testing 11 openEuler 20.03 LTS SP2支持树莓派<https://gitee.com/openeuler/release-management/issues/I3N30P?from=project-i…> Testing 12 openEuler 20.03 LTS SP2支持1822 HBA卡<https://gitee.com/openeuler/release-management/issues/I3N30V?from=project-i…> Testing 13 openEuler 20.03 LTS SP2支持飞腾2000+/64<https://gitee.com/openeuler/release-management/issues/I3N30W?from=project-i…> Testing 14 openEuler 20.03 LTS SP2支持maildrop和proftpd<https://gitee.com/openeuler/release-management/issues/I3N30X?from=project-i…> Testing 15 openEuler 20.03 LTS SP2支持 iSulad 2.0<https://gitee.com/openeuler/release-management/issues/I3N312?from=project-i…> Testing 16 openEuler 20.03 LTS SP2 A-tune 2.0<https://gitee.com/openeuler/release-management/issues/I3N314?from=project-i…> Testing 17 openEuler 20.03 LTS SP2 支持网络安装<https://gitee.com/openeuler/release-management/issues/I3N315?from=project-i…> Testing 18 openEuler 20.03 LTS SP2 支持 criu组件<https://gitee.com/openeuler/release-management/issues/I3N319?from=project-i…> Testing 19 openEuler 20.03 LTS SP2支持config_acpi_nfit<https://gitee.com/openeuler/release-management/issues/I3N31B?from=project-i…> Testing 20 openEuler 20.03 LTS SP2 虚拟化增强<https://gitee.com/openeuler/release-management/issues/I3N31E?from=project-i…> Testing 21 openEuler 20.03 LTS SP2 支持 UKUI桌面<https://gitee.com/openeuler/release-management/issues/I3N31F?from=project-i…> Testing 22 openEuler 20.03 LTS SP2 支持openGauss<https://gitee.com/openeuler/release-management/issues/I3N31I?from=project-i…> Discussion 23 openEuler 20.03 LTS SP2 支持DDE桌面<https://gitee.com/openeuler/release-management/issues/I3N31J?from=project-i…> Testing 24 openEuler 20.03 LTS SP2 编译器支持openjdk<https://gitee.com/openeuler/release-management/issues/I3N31M?from=project-i…> Testing 25 openEuler 20.03 LTS SP2支持HA<https://gitee.com/openeuler/release-management/issues/I3N31O?from=project-i…> Testing 26 openEuler 20.03 LTS SP2 加速库版本同步<https://gitee.com/openeuler/release-management/issues/I3N31Q?from=project-i…> Testing 27 openEuler 20.03 LTS SP2支持金融领域软件包<https://gitee.com/openeuler/release-management/issues/I3N311?from=project-i…> Testing 28 openEuler 20.03 LTS SP2支持kmod功能<https://gitee.com/openeuler/release-management/issues/I3N30C?from=project-i…> Testing 29 openEuler 20.03 LTS SP2支持华为多路径<https://gitee.com/openeuler/release-management/issues/I3N2XS?from=project-i…> Discussion 30 openEuler 20.03 LTS SP2 CPU核故障在线隔离解决方案<https://gitee.com/openeuler/release-management/issues/I3N36L?from=project-i…> Testing 31 openEuler 20.03 LTS SP2 支持多应用版本构建和发布<https://gitee.com/openeuler/release-management/issues/I3N36K?from=project-i…> Testing 32 openEuler 20.03 LTS SP2 内存UCE故障降级，用户数据保持一致，业务可持续运行<https://gitee.com/openeuler/release-management/issues/I3N36H?from=project-i…> Testing 33 openEuler 20.03 LTS SP2 故障预测框架<https://gitee.com/openeuler/release-management/issues/I3N36F?from=project-i…> Testing 34 openEuler 20.03 LTS SP2 IO_URING全栈使能<https://gitee.com/openeuler/release-management/issues/I3N36C?from=project-i…> Testing 35 openEuler 20.03 LTS SP2 Qemu：虚拟化可靠性和可维护性增强<https://gitee.com/openeuler/release-management/issues/I3N369?from=project-i…> Testing 36 openEuler 20.03 LTS SP2 Qemu：热迁移pro，提升热迁移性能+安全<https://gitee.com/openeuler/release-management/issues/I3N368?from=project-i…> Testing 37 openEuler 20.03 LTS SP2支持StratoVirt：下一代轻量化虚拟化平台<https://gitee.com/openeuler/release-management/issues/I3N364?from=project-i…> Testing 38 【openEuler 20.03 LTS SP2】继承xfce 4.14<https://gitee.com/openeuler/release-management/issues/I3NC3I?from=project-i…> Testing xfce @dillon_chen<https://gitee.com/dillon_chen> 39 【openEuler 20.03 LTS SP2】继承Kubernetes 1.18<https://gitee.com/openeuler/release-management/issues/I3NC5H?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 40 【openEuler 20.03 LTS SP2】继承门禁检查功能<https://gitee.com/openeuler/release-management/issues/I3O08F?from=project-i…> Testing 41 openEuler 20.03-LTS-SP2 集成 kubernetes 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I2BHF4?from=project-i…> Testing 42 openEuler 20.03-LTS-SP2 arm虚拟机支持NMI watchdog<https://gitee.com/openeuler/release-management/issues/I2B4WL?from=project-i…> Testing 43 openEuler 20.03-LTS-SP2 集成 coredns 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXLJ?from=project-i…> Testing 44 【openEuler 20.03 LTS SP2】虚拟机热迁移支持TLS<https://gitee.com/openeuler/release-management/issues/I3IE57?from=project-i…> Testing 45 【kernel-4.19】openEuler kernel nvme 驱动增强<https://gitee.com/openeuler/release-management/issues/I1WGZE?from=project-i…> Testing 46 openEuler 20.03-LTS-SP2 集成 etcd 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXGJ?from=project-i…> Testing 历史转测试版本取用链接 Test round 2版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-20.03-LTS-SP2/openeuler-2021-05-1…

1 0

ROS-SIG 24th 会议纪要
by 安传旭 27 May '21

27 May '21

您好： ROS-SIG 24th双周例会会议纪要如下：完成了stage orocos_kdl、rosconsole_bridge、python_qt_binding、cartographer_ros对于openEuler20.03的适配和打包；提交了共计13个PR到13个仓库。遇到问题：由于ROS基于python2，当前21年新发的openEuler创新版本都是基于python3，所以ROS组件没有办法在创新版本上测试，暂时无法加入SP2，需要release组给出解决方案，将ROS组件加入后续的openEuler20.03-next； Hello: The minutes of the Ros-Sig 24TH biweekly regular meeting are as follows: - Adaptation and packaging of 'stage orocos_kdl', 'rosconsole_bridge', 'python_qt_binding', 'cartographer_ros' for OpenEuler20.03 was completed; - Submitted a total of 13 PR to 13 warehouses. Problems: Since ROS is based on Python 2 and all the newly released innovative versions of OpenEuler in the past 21 years are based on Python 3, ROS components cannot be tested on the innovative version and cannot be added to SP2 for the time being. The release group needs to provide a solution. Add the ROS component to the subsequent OpenEuler20.03-next;

1 0

完成任务，获得荣誉，openEuler 社区的这项比赛有点逆天！
by Marketing openEuler 27 May '21

27 May '21

先说比赛规则独立开发者参赛 *做题得分* *每周结算* 这是任务打榜赛不满足？来看一下*特性命题赛*？独立开发者组队参赛区域赛、半决赛、总决赛过五关斩六将谁可以独占鳌头？你将是*社区贡献者* *你的 ID* 会被铭刻在社区还有*“一”点奖金* [image: WechatIMG16.jpeg]

1 0

sig-RaspberryPi例会
by openEuler conference 27 May '21

27 May '21

2 1

【Meeting Notice】openEuler kernel 技术分享第六期 & 双周例会 Time: 2021-05-28 14:00-18:00
by Meeting Book 27 May '21

27 May '21

1 0

virt-sig双周例会0528
by openEuler conference 27 May '21

27 May '21

1 0

Openstack SIG 例会
by openEuler conference 26 May '21

26 May '21

4 3

【Meeting Notice】openEuler kernel 技术分享第六期 & 双周例会 Time: 2021-05-28 14:00-18:00
by Meeting Book 25 May '21

25 May '21

1 0

sig-openstack 例会
by openEuler conference 25 May '21

25 May '21

1 0

欢迎大家申报议题！转发：sig-bio双周例会
by zhouzhongyuan96 25 May '21

25 May '21

| | 周中元开源软件工程师 | | 华为技术有限公司 18673967233 zhouzhongyuan96(a)163.com | 签名由网易邮箱大师定制 --------- 转发邮件信息 --------- 发件人： openEuler conference <public(a)openeuler.org> 发送日期： 2021年5月25日 09:28 主题： [Dev] sig-bio双周例会您好！ openEuler sig-bio SIG 邀请您参加 2021-05-27 10:00 召开的ZOOM会议(自动录制) 会议主题：sig-bio双周例会会议内容：sig-bio双周例会，欢迎大家申报议题。会议链接：https://us06web.zoom.us/j/82330174392?pwd=eE5nTmFpWVRLc25zS1FxN09peFhyZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-bio SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-27 10:00, The subject of the conference is sig-bio双周例会, Summary: sig-bio双周例会，欢迎大家申报议题。 You can join the meeting at https://us06web.zoom.us/j/82330174392?pwd=eE5nTmFpWVRLc25zS1FxN09peFhyZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

TC双周例会
by openEuler conference 25 May '21

25 May '21

2 1

sig-bio双周例会
by openEuler conference 25 May '21

25 May '21

1 0

安全委员会例会
by openEuler conference 24 May '21

24 May '21

1 0

南向兼容性sig组例会
by openEuler conference 24 May '21

24 May '21

1 0

sig-Gatekeeper双周例会
by openEuler conference 24 May '21

24 May '21

1 0

【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/20 release评审通知
by xiasenlin 24 May '21

24 May '21

openEuler 20.03 LTS SP1 Update 20210520 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月24日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210519 代码冻结： 20210519 转测试时间：20210520 版本发布： 20210524 本次更新主要涉及：qemu、ruby等包的CVE修复以及libvirt的新特性IO悬挂，需要与qemu一起发布；修复cve：9个 CVE清单： CVE-2021-3416 6 次要 src-openEuler/qemu CVE-2021-3409 5.7 次要 src-openEuler/qemu CVE-2021-3392 3.2 不重要 src-openEuler/qemu CVE-2019-14562 5.5 次要 src-openEuler/edk2 CVE-2020-25085 5 次要 src-openEuler/qemu CVE-2021-20208 6.1 次要 src-openEuler/cifs-utils CVE-2021-28965 7.5 主要 src-openEuler/ruby CVE-2021-20095 7.8 主要 src-openEuler/babel CVE-2020-18032 9.8 严重 src-openEuler/graphviz 涉及新增libvirt特性一个 From: xiasenlin Sent: Friday, May 14, 2021 6:15 PM To: 'release(a)openeuler.org' <release(a)openeuler.org>; 'qa(a)openeuler.org' <qa(a)openeuler.org>; 'sa-announce(a)openeuler.org' <sa-announce(a)openeuler.org>; 'dev(a)openeuler.org' <dev(a)openeuler.org> Cc: Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com> Subject: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知 openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月15日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210515 代码冻结： 20210512 转测试时间：20210514 版本发布： 20210515 本次更新主要涉及：golang、xstream等；修复cve：25个 CVE清单： CVE-2021-29425 次要 src-openEuler/apache-commons-io CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-27506 次要 src-openEuler/clamav CVE-2021-3448 不重要 src-openEuler/dnsmasq CVE-2021-29470 次要 src-openEuler/exiv2 CVE-2021-29457 主要 src-openEuler/exiv2 CVE-2021-29458 次要 src-openEuler/exiv2 CVE-2021-28650 次要 src-openEuler/gnome-autoar CVE-2021-27918 主要 src-openEuler/golang CVE-2021-28168 次要 src-openEuler/jersey CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-15169 次要 src-openEuler/rubygem-actionview CVE-2021-21349 主要 src-openEuler/xstream CVE-2021-21350 严重 src-openEuler/xstream CVE-2021-21348 主要 src-openEuler/xstream CVE-2021-21351 严重 src-openEuler/xstream CVE-2021-21341 主要 src-openEuler/xstream CVE-2021-21342 严重 src-openEuler/xstream CVE-2021-21343 主要 src-openEuler/xstream CVE-2021-21344 严重 src-openEuler/xstream CVE-2021-21345 严重 src-openEuler/xstream CVE-2021-21346 严重 src-openEuler/xstream CVE-2021-21347 严重 src-openEuler/xstream From: guoxiaoqi Sent: Friday, May 14, 2021 9:34 AM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>>; xiasenlin <xiasenlin1(a)huawei.com<mailto:xiasenlin1@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试新增依赖软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler src-openEuler/mxparser 依赖 SP1 不涉及 openEuler src-openEuler/xmlpull 依赖 SP1 不涉及 openEuler From: guoxiaoqi Sent: Thursday, May 13, 2021 9:10 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试更新，xstream不涉及接口变更。thrift涉及变更，本次版本暂时不发布软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… From: guoxiaoqi Sent: Thursday, May 13, 2021 3:39 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; guoxiaoqi <guoxiaoqi2(a)huawei.com<mailto:guoxiaoqi2@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: 【20.03-LTS-SP1 512 update周版本】启动测试请启动openEuler-20.03-LTS-SP1 2021年512 周版本测试软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 涉及接口变更 openEuler src-openEuler/thrift CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base…

1 0

Re: Compiler SIG双周例会【会议纪要】
by hedongbo 20 May '21

20 May '21

会议纪要 MEETING MINUTES 主题 Subject Compiler SIG双周例会时间 Date & Time 2021年05月18日星期二 10:00-11:00 地点 Location 线上会议与会者 Attendees 郭建兴（麒麟），徐赫（麒麟），李城宏（麒麟），沙文娜（麒麟），孟朝明（麒麟），刘吉林（麒麟），liwenchong(麒麟)，xiaozai(麒麟)，郭炳荣（金蝶），郭建军（保兰德），Erik Yuan(ARM), 刘金刚（华为），郭歌（华为），王篁（华为），王坤（华为），张高峰（华为），张云博（华为），贺东博（华为）纪要者 Note Taker 贺东博议题一：如何基于OpenJDK制作自己的发行版(郭歌) 1. 介绍OpenJDK的一些基本知识 2. 介绍如何制作单包发行版 3．介绍如何制作rpm包发型吧 4．回答麒麟同学关于制作发行的一些疑问议题二：从0到1构建BishengJDK-rpm包(基于openeuler和树莓派)（张云博） 1．分享如何基于openeuler上的bishengjdk源码构建出来rpm包，以及构建过程中常遇到的坑。 2．对相关的疑问进行解答分享资料见附件。会议录屏已自动上传至B站: https://www.bilibili.com/video/BV1w44y1r7jq?from=search&seid=69299028430501… From: openEuler conference [mailto:public@openeuler.io] Sent: Friday, May 14, 2021 5:57 PM To: dev(a)openeuler.org Subject: [Dev] Compiler SIG双周例会您好！ openEuler Compiler SIG 邀请您参加 2021-05-18 10:00 召开的ZOOM会议(自动录制) 会议主题：Compiler SIG双周例会会议内容：1. bishengjdk发行介绍&如何做发行 2. 构建bishengjdk rpm包常见的坑欢迎上报议题！会议链接：https://us06web.zoom.us/j/89840429300?pwd=Tk5GL3FjdFBpMTlzc1ExODJzT0tJZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Compiler SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-18 10:00, The subject of the conference is Compiler SIG双周例会, Summary: 1. bishengjdk发行介绍&如何做发行 2. 构建bishengjdk rpm包常见的坑欢迎上报议题！ You can join the meeting at https://us06web.zoom.us/j/89840429300?pwd=Tk5GL3FjdFBpMTlzc1ExODJzT0tJZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

【会议纪要】Rust安全编译选项遗留
by yanglijin 20 May '21

20 May '21

SP2版本stratovirt扫描安全编译选项有缺失，定位出来是依赖的rust工具链升级导致的。结论：stratovirt安全编译选项问题遗留，不影响SP2版本发布 1、安全编译选项实施指导规范适用于C、C++,针对rust无细则 2、升级rust后引入编译选项缺失原因未知遗留任务： 1、rust的安全编译选项细则――安全委员会 2、分析为何升级会导致缺失栈保护选项和Fortify Source两个安全编译选项问题

1 0

【会议纪要】SIG-compliance双周例会
by yangcong 19 May '21

19 May '21

SIG-compliance双周例会：时间：2021年5月18日上午10:00-11:00 与会者（请与会者在下面添加您的姓名）：杨聪、李自、郑志鹏、杨昭、王悦良 SIG-compliance组6月1日例会轮值主持人：郑志鹏议题（描述-发起人）： 1.“张飞”（license扫描工具）门禁与openeuler社区CI工具jenkins的集成流程中，非SPDX（Software Package Data Exchange，一种记录有关软件许可信息的文件格式）规范的license如何处理责任人：杨聪 2.合规SIG组例会分享的“张飞”（license扫描）工具使用责任人：杨聪 3.scantist工具与其它license扫描和漏洞扫描工具优缺点对比分享责任人：李冠庆 4.代码血缘关系分析报告确认系统试用前演示交流责任人：王小军会议纪要： 1.“张飞”（license扫描工具）门禁与openeuler社区CI工具jenkins的集成流程中，非SPDX（Software Package Data Exchange，一种记录有关软件许可信息的文件格式）规范的license如何处理责任人：杨聪 SPDX（Software Package Data Exchange）是用于传达软件物料清单信息（包括组件、许可证、版权和安全参考）的开放标准。张飞扫描工具采用 SPDX 报告许可证信息：以 SDPX 格式提供许可证信息，以尽量减少任何可能的错误，并标准化报告信息的方式。因此，扫描结果中，如果license信息错误，扫描工具不能给出SPDX格式规范或者给出unknown-license-reference。目前已经扫描openEuler仓库10+款较为典型的项目，发现对于license信息匹配不上的会提示unknown-license-reference，但均是系统误报。所以对于这种提示信息的处理分为三步：（1）门禁系统给出模糊匹配信息，判断这款license与哪款license信息最相似，然后再确认是否是license文本信息有误；（2）确认是否是系统误报，可查看该issue下是否有相关误报信息，如果没有相关误报信息，请在此issue下进行回复；（3）若license信息均不属于上述两种情况，提交issue关联compliance-sig组，由sig组分析后给出建议并添加到张飞license数据库 2.合规SIG组例会分享的“张飞”（license扫描）工具使用责任人：杨聪现在提供源码、docker镜像等形式使用工具，详细使用说明、使用链接可参考https://gitee.com/compliance-tools/com…. 另外，该系统也提供了门禁集成的功能，详细部署到Jenkins流程的代码及配置可参考https://gitee.com/compliance-bot/j… 遗留问题：由于相关责任人时间冲突，可在下次例会进行分享 1.scantist工具与其它license扫描和漏洞扫描工具优缺点对比分享责任人：李冠庆 2.代码血缘关系分析报告确认系统试用前演示交流责任人：王小军 | | yangcong | | yangcong_hit(a)163.com | 签名由网易邮箱大师定制

1 0

【会议纪要】sig-release-management双周例会
by Xuxiaosong 19 May '21

19 May '21

轮值主持人：许小松下次主持人：胡峰会议时间：2021年5月19日 14:30－16:30 会议地点：sig电话会议议题一：openEuler 20.03 LTS SP2版本进展介绍：许小松 1、openEuler 20.03 LTS SP2已完成第一轮转测试，正在进行第二轮测试； 2、第三轮转测试时间5.24日，openEuler 20.03 LTS SP2版本需求合入情况和转测试，发布计划详见： https://gitee.com/openeuler/release-management/blob/master/openEuler-20.03-… 议题二：openEuler 21.09创新版本需求搜集计划介绍：胡峰 1、openEuler 21.09创新版本需求收集时间； 2、openEuler 21.09创新版本版本计划介绍； 3、openEuler 21.09创新版本需求填写要求；议题三：为解决xfce声音控制问题引入pavucontrol包：dingwenlong 结论： 1、同意引入pavucontrol包解决声音控制bugfix； 2、代码在5月21日前完成合入验证； From: Xuxiaosong Sent: Monday, May 17, 2021 3:24 PM To: 'tc(a)openeuler.org'; 'dev(a)openeuler.org'; 'release(a)openeuler.org' Subject: [Dev] sig-release-management双周例会欢迎大家申报议题。 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, May 17, 2021 3:20 PM Subject: [Dev] sig-release-management双周例会您好！ openEuler sig-release-management SIG 邀请您参加 2021-05-19 14:30 召开的ZOOM会议会议主题：sig-release-management双周例会会议链接：https://us06web.zoom.us/j/86057315767?pwd=TTRHUTRaOUwxelhERmQvZVV1UTZ0QT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference will be held at 2021-05-19 14:30, The subject of the conference is sig-release-management双周例会, You can join the meeting at https://us06web.zoom.us/j/86057315767?pwd=TTRHUTRaOUwxelhERmQvZVV1UTZ0QT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

openEuler 20.03 LTS SP2 Test round 2转测试通知
by Xuxiaosong 18 May '21

18 May '21

转测试计划比原计划有1天延期。请相关责任人最晚于2021-5-20前完成特性进展更新为正常状态。 Test round 2版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-20.03-LTS-SP2/openeuler-2021-05-1… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 20.03-LTS-SP2-round-2）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-20.03-… 1、本轮转2个特性； no fetur 特性说明 status 1 【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 21.03，vmtop支持x86<https://gitee.com/openeuler/release-management/issues/I3NLWF?from=project-i…> 【openEuler 20.03 LTS SP2】【虚拟化】QEMU支持qemu-rbd和qemu-ssh 【openEuler 20.03 LTS SP2】【虚拟化】软件模拟超线程支持（HT）【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 20.09需求：Qemu支持IO悬挂【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 21.03，vmtop支持x86 Testing 2 openEuler 20.03 LTS SP2支持HA<https://gitee.com/openeuler/release-management/issues/I3N31O?from=project-i…> 支持HA Testing 2、新增和删除包见附件； Test round1已解决问题单40个，未解决的问题单26，详见： https://e.gitee.com/open_euler/issues/list?is%5Bmilestone_id%5D=69297&is%5B… https://e.gitee.com/open_euler/issues/list?is%5Bmilestone_id%5D=116380&is%5… Release plan Stage name Begin time End time key feature collect 2021-03-16 2021-03-31 Develop 2021-03-16 2021-04-26 Kernel freezing 2021-04-16 2021-04-16 Build 2021-04-26 2021-04-30 Test round 1 2021-05-6 2021-05-12 Test round 2（we are here） 2021-05-17 2021-05-21 Test round 3 2021-05-24 2021-05-31 Test round 4 2021-06-03 2021-06-07 Test round 5 2021-06-09 2021-06-11 release 2021-06-28 2021-06-30 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 21.03，vmtop支持x86<https://gitee.com/openeuler/release-management/issues/I3NLWF?from=project-i…> Testing 2 openEuler 20.03-LTS-SP2支持内存分级扩展特性<https://gitee.com/openeuler/release-management/issues/I2C2NI?from=project-i…> Testing storage liuzhiqiang26<https://gitee.com/liuzhiqiang26> 3 openEuler 20.03-LTS-SP2版本集成secgear组件<https://gitee.com/openeuler/release-management/issues/I3JE3U?from=project-i…> Testing sig-confidential-computing chenmaodong<https://gitee.com/chenmaodong> 4 openEuler 20.03 LTS SP2 support OpenStack Rocky discussion sig-openstack @joec88 @liksh @xiyuanwang @huangtianhua 5 openEuler 20.03 LTS SP2支持osinfo软件包<https://gitee.com/openeuler/release-management/issues/I3N30H?from=project-i…> Testing 6 openEuler 20.03 LTS SP2开源openEuler-rpm-config宏定义文件<https://gitee.com/openeuler/release-management/issues/I3N30J?from=project-i…> Testing 7 openEuler 20.03 LTS SP2 支持 compat-openssl10、libzip等<https://gitee.com/openeuler/release-management/issues/I3N30L?from=project-i…> Testing 8 openEuler 20.03 LTS SP2 支持libwbxml、hyperscan<https://gitee.com/openeuler/release-management/issues/I3N30N?from=project-i…> Testing 9 openEuler 20.03 LTS SP2支持microcode_ctl<https://gitee.com/openeuler/release-management/issues/I3N30S?from=project-i…> Testing 10 openEuler 20.03 LTS SP2支持bcc软件包<https://gitee.com/openeuler/release-management/issues/I3N30Q?from=project-i…> Testing 11 openEuler 20.03 LTS SP2支持树莓派<https://gitee.com/openeuler/release-management/issues/I3N30P?from=project-i…> Testing 12 openEuler 20.03 LTS SP2支持1822 HBA卡<https://gitee.com/openeuler/release-management/issues/I3N30V?from=project-i…> Testing 13 openEuler 20.03 LTS SP2支持飞腾2000+/64<https://gitee.com/openeuler/release-management/issues/I3N30W?from=project-i…> Testing 14 openEuler 20.03 LTS SP2支持maildrop和proftpd<https://gitee.com/openeuler/release-management/issues/I3N30X?from=project-i…> Testing 15 openEuler 20.03 LTS SP2支持 iSulad 2.0<https://gitee.com/openeuler/release-management/issues/I3N312?from=project-i…> Testing 16 openEuler 20.03 LTS SP2 A-tune 2.0<https://gitee.com/openeuler/release-management/issues/I3N314?from=project-i…> Testing 17 openEuler 20.03 LTS SP2 支持网络安装<https://gitee.com/openeuler/release-management/issues/I3N315?from=project-i…> Testing 18 openEuler 20.03 LTS SP2 支持 criu组件<https://gitee.com/openeuler/release-management/issues/I3N319?from=project-i…> Testing 19 openEuler 20.03 LTS SP2支持config_acpi_nfit<https://gitee.com/openeuler/release-management/issues/I3N31B?from=project-i…> Testing 20 openEuler 20.03 LTS SP2 虚拟化增强<https://gitee.com/openeuler/release-management/issues/I3N31E?from=project-i…> Testing 21 openEuler 20.03 LTS SP2 支持 UKUI桌面<https://gitee.com/openeuler/release-management/issues/I3N31F?from=project-i…> Testing 22 openEuler 20.03 LTS SP2 支持openGauss<https://gitee.com/openeuler/release-management/issues/I3N31I?from=project-i…> Discussion 23 openEuler 20.03 LTS SP2 支持DDE桌面<https://gitee.com/openeuler/release-management/issues/I3N31J?from=project-i…> Testing 24 openEuler 20.03 LTS SP2 编译器支持openjdk<https://gitee.com/openeuler/release-management/issues/I3N31M?from=project-i…> Testing 25 openEuler 20.03 LTS SP2支持HA<https://gitee.com/openeuler/release-management/issues/I3N31O?from=project-i…> Testing 26 openEuler 20.03 LTS SP2 加速库版本同步<https://gitee.com/openeuler/release-management/issues/I3N31Q?from=project-i…> Testing 27 openEuler 20.03 LTS SP2支持金融领域软件包<https://gitee.com/openeuler/release-management/issues/I3N311?from=project-i…> Testing 28 openEuler 20.03 LTS SP2支持kmod功能<https://gitee.com/openeuler/release-management/issues/I3N30C?from=project-i…> Testing 29 openEuler 20.03 LTS SP2支持华为多路径<https://gitee.com/openeuler/release-management/issues/I3N2XS?from=project-i…> Discussion 30 openEuler 20.03 LTS SP2 CPU核故障在线隔离解决方案<https://gitee.com/openeuler/release-management/issues/I3N36L?from=project-i…> Developing 31 openEuler 20.03 LTS SP2 支持多应用版本构建和发布<https://gitee.com/openeuler/release-management/issues/I3N36K?from=project-i…> Developing 32 openEuler 20.03 LTS SP2 内存UCE故障降级，用户数据保持一致，业务可持续运行<https://gitee.com/openeuler/release-management/issues/I3N36H?from=project-i…> Developing 33 openEuler 20.03 LTS SP2 故障预测框架<https://gitee.com/openeuler/release-management/issues/I3N36F?from=project-i…> Testing 34 openEuler 20.03 LTS SP2 IO_URING全栈使能<https://gitee.com/openeuler/release-management/issues/I3N36C?from=project-i…> Testing 35 openEuler 20.03 LTS SP2 Qemu：虚拟化可靠性和可维护性增强<https://gitee.com/openeuler/release-management/issues/I3N369?from=project-i…> Testing 36 openEuler 20.03 LTS SP2 Qemu：热迁移pro，提升热迁移性能+安全<https://gitee.com/openeuler/release-management/issues/I3N368?from=project-i…> Testing 37 openEuler 20.03 LTS SP2支持StratoVirt：下一代轻量化虚拟化平台<https://gitee.com/openeuler/release-management/issues/I3N364?from=project-i…> Testing 38 【openEuler 20.03 LTS SP2】继承xfce 4.14<https://gitee.com/openeuler/release-management/issues/I3NC3I?from=project-i…> Testing xfce @dillon_chen<https://gitee.com/dillon_chen> 39 【openEuler 20.03 LTS SP2】继承Kubernetes 1.18<https://gitee.com/openeuler/release-management/issues/I3NC5H?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 40 【openEuler 20.03 LTS SP2】继承门禁检查功能<https://gitee.com/openeuler/release-management/issues/I3O08F?from=project-i…> Testing 41 openEuler 20.03-LTS-SP2 集成 kubernetes 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I2BHF4?from=project-i…> Testing 42 openEuler 20.03-LTS-SP2 arm虚拟机支持NMI watchdog<https://gitee.com/openeuler/release-management/issues/I2B4WL?from=project-i…> Testing 43 openEuler 20.03-LTS-SP2 集成 coredns 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXLJ?from=project-i…> Testing 44 【openEuler 20.03 LTS SP2】虚拟机热迁移支持TLS<https://gitee.com/openeuler/release-management/issues/I3IE57?from=project-i…> Testing 45 【kernel-4.19】openEuler kernel nvme 驱动增强<https://gitee.com/openeuler/release-management/issues/I1WGZE?from=project-i…> Testing 46 openEuler 20.03-LTS-SP2 集成 etcd 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXGJ?from=project-i…> Testing 历史转测试版本取用链接 Test round 1版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-20.03-LTS-SP2/openeuler-2021-05-0…

1 0

openEuler第三方镜像源列表上线使用说明/openEuler Third-Party Mirror Source List
by 随心 18 May '21

18 May '21

hello all: 为方便大家下载和使用openEuler的发布件，基础设施团队拓展了openEuler的第三方镜像源，目前已经上线包括中国&俄罗斯在内的9个Repo源，大家可以在官方页面[1]查找使用，也可以在下载页面[2]点击站点选择，已20.03-LTS-SP1为例[3]，选择距离最近的镜像源下载使用；同时也欢迎大家帮助我们拓展更多的openEuler第三方镜像源。 To facilitate users to download and use openEuler release files, the infrastructure team has expanded the third-party mirror source of openEuler. Currently, nine Repo sources, including those in China and Russia, have been launched, You can search for and use the mirror source on the official page [1] or select a site on the download page [2]. For example, 20.03-LTS-SP1 [3], select the closest mirror source to download. You are also welcome to help us develop more openEuler third-party mirror sources. [1]: https://openeuler.org/zh/mirror/list/ [2]: https://openeuler.org/zh/download/ [3]: https://openeuler.org/zh/mirror/select/?version=20.03-LTS-SP1

1 0

【会议纪要】RE: [Virt] virt sig例会-20210514
by Chenqun (kuhn) 17 May '21

17 May '21

时间：2021年4月23日 14：15 - 15：45 参会人员来自：麒麟、统信、品高、华云、移动、电信、浪潮、申威、Intel、华为等居多公司成员及个人参与者（详见与会人员信息） · 2021-05-14会议纪要： * openEuler 20.03 LTS SP2需求进展介绍当前openEuler 20.03 LTS SP2版本新增Feature 9个，代码均已经合入完成，当前已开展测试过程中。各个Feature说明：https://gitee.com/openeuler/qemu/wikis/openEuler%2020.03%20LTS%… * qemu 4.2特性回合需求介绍介绍了 qemu 4.2特性回合到openEuler 社区背景：当前有部分客户已经使用Centos 8.1版本（qemu 4.2），期望切换到openEuler版本后原qemu 4.2相关Feature不丢失。 qemu 4.2相对qemu 4.1发布Feature 总计32个，其中有13个非x86及arm架构。剩余19个中，已经回合openEuler版本8个，待回合11个。针对剩余的11个待回合Feature，各个开发者可以自主认领，认领后在qemu仓库建立ISSUE，回合代码。回合需求列表：https://gitee.com/openeuler/qemu/wikis/qemu%204.2%20Feature%E5%9B%9E… * 分享了StratoVirt之快速冷启动bootloader技术视频连接：https://www.bilibili.com/video/BV1Ef4y1Y7HK 本主题视频时间：0:22:44~00:00:41:30 参会人员列表： [cid:image002.jpg@01D74B6E.2E8FA2D0] [cid:image004.jpg@01D74B6E.2E8FA2D0] From: openEuler conference via Virt [mailto:virt@openeuler.org] Sent: Wednesday, May 12, 2021 8:23 PM To: tc(a)openeuler.org; virt(a)openeuler.org; dev(a)openeuler.org Subject: [Virt] virt sig例会-20210514 您好！ openEuler Virt SIG 邀请您参加 2021-05-14 14:15 召开的ZOOM会议(自动录制) 会议主题：virt sig例会-20210514 会议内容：1、openEuler 20.03 LTS SP2需求进展介绍 2、qemu 4.2特性回合需求介绍 3、StratoVirt快速冷启动bootloader技术分享会议链接：https://us06web.zoom.us/j/85000061143?pwd=VVJVY0Qyak51TFdvdWZUMWJCM2FQQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Virt SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-14 14:15, The subject of the conference is virt sig例会-20210514, Summary: 1、openEuler 20.03 LTS SP2需求进展介绍 2、qemu 4.2特性回合需求介绍 3、StratoVirt快速冷启动bootloader技术分享 You can join the meeting at https://us06web.zoom.us/j/85000061143?pwd=VVJVY0Qyak51TFdvdWZUMWJCM2FQQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

[X-diagnosis] oom: add more info for oom
by Zhoukang (A) 17 May '21

17 May '21

From 18e0f00ea2e3e5528b4ac9671d5caa3e3110fa0e Mon Sep 17 00:00:00 2001 From: Liu Zixian <liuzixian4(a)huawei.com> Date: Sat, 15 May 2021 09:04:53 +0000 Subject: [PATCH] oom: add more info for oom kernel do not printk enough messages when OS happen oom. this module print more info when oom happen. Signed-off-by: Liu Zixian <liuzixian4(a)huawei.com> --- src/oom_debug_info/Makefile | 2 + src/oom_debug_info/oom_debug_info.c | 639 ++++++++++++++++++++++++++++ src/oom_debug_info/oom_debug_info.h | 19 + 3 files changed, 660 insertions(+) create mode 100755 src/oom_debug_info/Makefile create mode 100644 src/oom_debug_info/oom_debug_info.c create mode 100644 src/oom_debug_info/oom_debug_info.h diff --git a/src/oom_debug_info/Makefile b/src/oom_debug_info/Makefile new file mode 100755 index 0000000..b53d93e --- /dev/null +++ b/src/oom_debug_info/Makefile @@ -0,0 +1,2 @@ + +obj-m += oom_debug_info.o diff --git a/src/oom_debug_info/oom_debug_info.c b/src/oom_debug_info/oom_debug_info.c new file mode 100644 index 0000000..cba8eef --- /dev/null +++ b/src/oom_debug_info/oom_debug_info.c @@ -0,0 +1,639 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * Copyright (c) Huawei Technologies Co., Ltd. 2021-2021. ALL rights reversed. + */ + +#include <linux/delay.h> +#include <linux/fs.h> +#include <linux/hugetlb.h> +#include <linux/kallsyms.h> +#include <linux/kernel.h> +#include <linux/mman.h> +#include <linux/module.h> +#include <linux/nmi.h> +#include <linux/oom.h> +#include <linux/printk.h> +#include <linux/rwsem.h> +#include <linux/sched/signal.h> +#include <linux/sched/task.h> +#include <linux/seq_file.h> +#include <linux/swap.h> +#ifdef CONFIG_CMA +#include <linux/cma.h> +#endif +#include <../fs/mount.h> +#include <../mm/slab.h> + +#include "oom_debug_info.h" + +#define TMP_FS_ID 1 +#define FILE_PATH_BUF_SIZE 1024 +#define MAX_PRINT_STR_SIZE 1024 +#define SHOW_FILE_NUM_IN_DIR 1024 +#define RECURSE_DEPTH_LIMIT 50 +#define FILE_NUM_MDELAY_FOR_LOG 1000 +#define MAX_PRINT_FILE_INFO_BYTES (2 * 1024 * 1024UL) +#define MAX_BUF_LEN 256 + +int sysctl_oom_enhance_enable = 1; +int sysctl_oom_print_file_info = 1; +int sysctl_oom_show_file_num_in_dir = 10; + +static atomic_t console_silent_atomic = ATOMIC_INIT(0); +static atomic_t dentry_tree_running = ATOMIC_INIT(0); +static char file_path_buf[FILE_PATH_BUF_SIZE]; +static char str_print[MAX_PRINT_STR_SIZE]; +static unsigned long min_heap[SHOW_FILE_NUM_IN_DIR]; +static unsigned int fs_id; +static char *mount_path[] = { + "", + "/tmp", +}; + +static unsigned long show_file_num; +static unsigned long print_file_info_bytes; + +static const char *task_state_Array[] = { + "R (running)", /* 0 */ + "S (sleeping)", /* 1 */ + "D (disk sleep)", /* 2 */ + "T (stopped)", /* 4 */ + "T (tracing stop)", /* 8 */ + "Z (zombie)", /* 16 */ + "X (dead)" /* 32 */ +}; + +/* get_task_state() */ +#ifndef TASK_REPORT +#define TASK_REPORT (TASK_RUNNING | TASK_INTERRUPTIBLE | \ + TASK_UNINTERRUPTIBLE | __TASK_STOPPED | \ + __TASK_TRACED) +#endif + +static struct ctl_table_header *debug_table_header; + +static struct ctl_table debug_kernel_table[] = { + { + .procname = "oom_enhance_enable", + .data = &sysctl_oom_enhance_enable, + .maxlen = sizeof(int), + .mode = 0640, + .proc_handler = proc_dointvec_minmax, + }, + { + .procname = "oom_print_file_info", + .data = &sysctl_oom_print_file_info, + .maxlen = sizeof(int), + .mode = 0640, + .proc_handler = proc_dointvec_minmax, + }, + { + .procname = "oom_show_file_num_in_dir", + .data = &sysctl_oom_show_file_num_in_dir, + .maxlen = sizeof(int), + .mode = 0640, + .proc_handler = proc_dointvec_minmax, + }, + {} +}; + +static struct ctl_table debug_root_table[] = { + { + .procname = "kernel", + .mode = 0555, + .child = debug_kernel_table, + }, + {} +}; + +// TODO: compat to kernel-5.10 + +static struct rw_semaphore *k_namespace_sem = NULL; +static rwlock_t *k_tasklist_lock = NULL; + +typedef void (*show_mem_fn)(unsigned int, nodemask_t *); +show_mem_fn k_show_mem = NULL; + +typedef void (*iterate_supers_fn)(void (*)(struct super_block *, void *), void *); +iterate_supers_fn k_iterate_supers = NULL; + +typedef void (*hugetlb_report_meminfo_fn)(struct seq_file *); +hugetlb_report_meminfo_fn k_hugetlb_report_meminfo = NULL; + +static int last_console_printk = 0; +static int *k_console_printk = NULL; + +static inline void _console_silent(void) +{ + last_console_printk = *k_console_printk; + *k_console_printk = CONSOLE_LOGLEVEL_SILENT; +} + +static inline void _console_resume(void) +{ + *k_console_printk = last_console_printk; +} + +static int init_kernel_sym(void) +{ + k_namespace_sem = (struct rw_semaphore *) kallsyms_lookup_name("namespace_sem"); + + k_tasklist_lock = (rwlock_t *) kallsyms_lookup_name("tasklist_lock"); + if (!k_tasklist_lock) { + printk(KERN_WARNING "tasklist_lock is not found\n"); + return -1; + } + + k_console_printk = (int*) kallsyms_lookup_name("console_printk"); + if (!k_console_printk) { + printk(KERN_WARNING "console_printk is not found\n"); + return -1; + } + + k_show_mem = (show_mem_fn) kallsyms_lookup_name("show_mem"); + if (!k_show_mem) { + printk(KERN_WARNING "show_mem is not found\n"); + return -1; + } + + k_iterate_supers = (iterate_supers_fn) kallsyms_lookup_name("iterate_supers"); + if (!k_iterate_supers) { + printk(KERN_WARNING "iterate_supers is not found\n"); + return -1; + } + + k_hugetlb_report_meminfo = (hugetlb_report_meminfo_fn) kallsyms_lookup_name("hugetlb_report_meminfo"); + if (!k_hugetlb_report_meminfo) { + printk(KERN_WARNING "hugetlb_report_meminfo is not found\n"); + return -1; + } + + return 0; +} + +static struct dentry *get_mountpoint_from_mnt_root(struct dentry *dentry) +{ + struct mnt_namespace *ns = current->nsproxy->mnt_ns; + struct mount *mnt; + struct dentry *mount_point = NULL; + + if (IS_ERR_OR_NULL(dentry) || strncmp(dentry->d_iname, "/", sizeof("/"))) + goto out; + + if (!k_namespace_sem) { + printk(KERN_WARNING "k_namespace_sem is NULL\n"); + return NULL; + } + + if (!down_read_trylock(k_namespace_sem)) { + printk(KERN_WARNING "get namespace_sem fail when get mountpoint from mnt_root!\n"); + return NULL; + } + + list_for_each_entry(mnt, &ns->list, mnt_list) { + if (mnt->mnt.mnt_root == dentry) { + mount_point = mnt->mnt_mountpoint; + break; + } + } + up_read(k_namespace_sem); +out: + return mount_point; +} + +static int show_proc_slab_info(void) +{ +// TODO: read file /proc/slabinfo + return 0; +} + +static int show_proc_mem_info(void) +{ +// TODO: read file /proc/meminfo + return 0; +} + +/* + * get string of task status according to stat of task_struct. + */ +static inline const char *oom_get_task_state(struct task_struct *tsk) +{ + unsigned int state = (tsk->state & TASK_REPORT) | tsk->exit_state; + const char **p = &task_state_Array[0]; + + while (state) { + p++; + state >>= 1; + } + return *p; +} + +/* + * refer to ps -aux, show task info for debug. + */ +static int show_ps_aux_info(void) +{ + struct task_struct *p; + + printk(KERN_WARNING "%5s %5s %20s %8s %8s %16s\n", "PID", "PPID", "VSZ", "RSS", "STAT", "COMMAND"); + read_lock(k_tasklist_lock); + for_each_process(p) { + printk(KERN_WARNING "%5d %5d %7luK %7luK %16s %s\n", p->pid, + p->parent->pid, + (p->mm != NULL ? p->mm->total_vm : 0) * 4, + (p->mm != NULL ? get_mm_rss(p->mm) : 0) * 4, oom_get_task_state(p), p->comm); + } + read_unlock(k_tasklist_lock); + return 0; +} + +static char *get_file_path(struct dentry *dentry) +{ + /* for placing '\0' at end */ + int byte_left = FILE_PATH_BUF_SIZE - 2; + int name_len; + + memset(file_path_buf, 0, FILE_PATH_BUF_SIZE); + + while (dentry && (strncmp(dentry->d_name.name, "/", 1) != 0)) { + name_len = strlen(dentry->d_name.name); + if (byte_left <= name_len) { + printk(KERN_WARNING "file name too long ..."); + break; + } + + byte_left -= name_len; + memcpy(file_path_buf + byte_left, dentry->d_name.name, name_len); + byte_left--; + file_path_buf[byte_left] = '/'; + dentry = dentry->d_parent; + } + + return file_path_buf + byte_left; +} + +static bool is_empty_dir(struct dentry *dir) +{ + struct dentry *dentry = NULL; + + if (!d_is_dir(dir)) + return false; + + if (list_empty(&dir->d_subdirs)) + return true; + + spin_lock(&dir->d_lock); + list_for_each_entry(dentry, &dir->d_subdirs, d_child) { + if (dentry == NULL || dentry->d_inode == NULL) + continue; + if (d_is_file(dentry) && dentry->d_inode->i_size > 0) { + spin_unlock(&dir->d_lock); + return false; + } + if (d_is_dir(dentry) && !is_empty_dir(dentry)) { + spin_unlock(&dir->d_lock); + return false; + } + } + spin_unlock(&dir->d_lock); + return true; +} + +static void my_swap(unsigned long *a, int i, int j) +{ + unsigned long temp = a[i]; + + a[i] = a[j]; + a[j] = temp; +} + +static void heap_adjust(unsigned long *a, int n, int i) +{ + int j = 2 * i + 1; + + while (j < n) { + if (j + 1 < n && a[j] > a[j + 1]) + j++; + if (a[i] > a[j]) + my_swap(a, i, j); + else + break; + i = j; + j = 2 * i + 1; + } +} + +static void heap_build(unsigned long *a, int n) +{ + int i; + + for (i = n / 2 - 1; i >= 0; i--) + heap_adjust(a, n, i); +} + +static unsigned long get_topn_size_in_dir(struct dentry *dir, unsigned int *file_num) +{ + struct dentry *dentry = NULL; + unsigned long topn_size = 0; + + *file_num = 0; + memset(min_heap, 0, sizeof(min_heap)); + + spin_lock(&dir->d_lock); + list_for_each_entry(dentry, &dir->d_subdirs, d_child) { + if (dentry == NULL || dentry->d_inode == NULL) + continue; + if (d_is_file(dentry)) { + (*file_num)++; + if (*file_num < sysctl_oom_show_file_num_in_dir) { + min_heap[*file_num - 1] = dentry->d_inode->i_size; + } else if (*file_num == sysctl_oom_show_file_num_in_dir) { + min_heap[*file_num - 1] = dentry->d_inode->i_size; + heap_build(min_heap, sysctl_oom_show_file_num_in_dir); + } else if (*file_num > sysctl_oom_show_file_num_in_dir) { + if (dentry->d_inode->i_size > min_heap[0]) { + min_heap[0] = dentry->d_inode->i_size; + heap_adjust(min_heap, sysctl_oom_show_file_num_in_dir, 0); + } + } + } + } + spin_unlock(&dir->d_lock); + + if (*file_num > sysctl_oom_show_file_num_in_dir) + topn_size = min_heap[0]; + return topn_size; +} + +static unsigned long do_show_dentry_tree(struct dentry *tree, unsigned int depth) +{ + struct dentry *dentry = NULL; + unsigned long topn_size; + unsigned long dir_size = 0; + unsigned long subdir_size; + unsigned int file_num; + int num_chars; + + if (print_file_info_bytes > MAX_PRINT_FILE_INFO_BYTES) { + printk(KERN_WARNING "file info exceed %lu bytes!\n", MAX_PRINT_FILE_INFO_BYTES); + return 0; + } + + if (depth >= RECURSE_DEPTH_LIMIT) { + printk(KERN_WARNING "dir depth exceed %d!\n", RECURSE_DEPTH_LIMIT); + return 0; + } + + /* get topN file size in dir */ + topn_size = get_topn_size_in_dir(tree, &file_num); + + spin_lock(&tree->d_lock); + /* ramfs and tmpfs will "pin the dentry in core", + * so we can iterate all files in root initramfs(tmpfs) by dentry. + */ + list_for_each_entry(dentry, &tree->d_subdirs, d_child) { + if (dentry == NULL || dentry->d_inode == NULL) + continue; + if (dentry->d_inode->i_size == 0) + continue; + if (d_is_symlink(dentry)) + continue; + if (d_is_file(dentry)) { + if (dentry->d_inode->i_size >= topn_size) { + num_chars = snprintf(str_print, + MAX_PRINT_STR_SIZE, "%s:%llu\n", + dentry->d_name.name, dentry->d_inode->i_size); + if (num_chars > 0) + print_file_info_bytes += num_chars; + printk(KERN_CONT "%s", str_print); + show_file_num++; + } + if (show_file_num % FILE_NUM_MDELAY_FOR_LOG == 0) { + num_chars = snprintf(str_print, MAX_PRINT_STR_SIZE, + "already printed %lu files, will mdelay 10 ms for log system.\n", + show_file_num); + if (num_chars > 0) + print_file_info_bytes += num_chars; + printk(KERN_CONT "%s", str_print); + touch_nmi_watchdog(); + mdelay(10); + } + dir_size += dentry->d_inode->i_size; + } + } + /* second iterate list for showing subdirs after showing files */ + list_for_each_entry(dentry, &tree->d_subdirs, d_child) { + if (dentry == NULL || dentry->d_inode == NULL) + continue; + /* 1.we use d_mountpoint to skip mountpoint, but + * auditd mounted /usr/lib/modules to itself process space, + * it will lead to skip this dir in memory rootfs by mistake. + * 2.you can fix it by all inodes have same super block in same + * file system, pity that all inodes have same super block in + * root initramfs(tmpfs) when unpack, lead to it cann`t work by + * dentry iterate, although you can get distinguished + * inode->i_sb->s_dev by name lookup, refer to vfs_lstat to get + * stat.dev, but it shouldn`t sched or alloc when oom. + * 3.you also can fix it by refer to is_local_mountpoint, + * notice down_read may sleep and up_read call wake_up_process + * when hold d_lock, use down_read_trylock and call + * local_irq_save and preempt_disable preempt_enable_no_resched + * to ensure safe. + * 4.we handle it in simple way, treat as mountpoint is empty + * dir in initramfs. + */ + if (is_empty_dir(dentry)) + continue; + if (d_is_dir(dentry)) { + num_chars = snprintf(str_print, MAX_PRINT_STR_SIZE, + "%s%s\n", mount_path[fs_id], get_file_path(dentry)); + if (num_chars > 0) + print_file_info_bytes += num_chars; + printk(KERN_CONT "%s", str_print); + subdir_size = do_show_dentry_tree(dentry, depth + 1); + if (subdir_size > 0) { + num_chars = snprintf(str_print, + MAX_PRINT_STR_SIZE, "dir %s%s:%lu\n", + mount_path[fs_id], get_file_path(dentry), subdir_size); + if (num_chars > 0) + print_file_info_bytes += num_chars; + printk(KERN_CONT "%s", str_print); + dir_size += subdir_size; + } + } + } + spin_unlock(&tree->d_lock); + + if (topn_size > 0) { + num_chars = snprintf(str_print, MAX_PRINT_STR_SIZE, "...files num:%d\n", file_num); + if (num_chars > 0) + print_file_info_bytes += num_chars; + printk(KERN_CONT "%s", str_print); + } + + return dir_size; +} + +static void show_dentry_tree(struct dentry *tree) +{ + unsigned long dir_size; + + if (IS_ERR_OR_NULL(tree)) + return; + printk(KERN_WARNING "%s%s\n", mount_path[fs_id], tree->d_iname); + dir_size = do_show_dentry_tree(tree, 0); + printk(KERN_WARNING "%lu bytes in %s%s\n", dir_size, mount_path[fs_id], tree->d_iname); +} + +static void show_file_info_by_name(struct super_block *sb, void *name) +{ + struct dentry *mount_point = NULL; + + if (strncmp(sb->s_type->name, name, strlen(name))) + return; + + if (!strncmp(name, "rootfs", strlen(name))) { + fs_id = 0; + show_dentry_tree(sb->s_root); + } else if (!strncmp(name, "tmpfs", strlen(name))) { + /* get mount_point of mnt_root, I have no better way than refer + * to is_local_mountpoint, notice down_read may sleep and + * up_read call wake_up_process, use down_read_trylock and + * call preempt_disable preempt_enable_no_resched. + */ + mount_point = get_mountpoint_from_mnt_root(sb->s_root); + if (!strncmp(get_file_path(mount_point), "/tmp", sizeof("/tmp")) + && !strncmp(mount_point->d_sb->s_type->name, "rootfs", sizeof("rootfs"))) { + printk(KERN_WARNING "###################\n"); + printk(KERN_WARNING "show files in /tmp:\n"); + fs_id = TMP_FS_ID; + show_dentry_tree(sb->s_root); + } + } +} + +void show_rootfs_info(void) +{ + printk(KERN_WARNING "rootfs file info:\n"); + k_iterate_supers(show_file_info_by_name, "rootfs"); +} + +void show_tmpfs_info(void) +{ + k_iterate_supers(show_file_info_by_name, "tmpfs"); +} + +void show_memfs_info(void) +{ + if (!sysctl_oom_print_file_info) + return; + + if (atomic_cmpxchg(&dentry_tree_running, 0, 1)) + return; + print_file_info_bytes = 0; + show_file_num = 0; + show_rootfs_info(); + show_tmpfs_info(); + atomic_set(&dentry_tree_running, 0); +} + +void oom_show_debug_info(void) +{ + typedef int (*ivpfn) (void); + ivpfn show_pfn_memory_info = NULL; + + if (atomic_cmpxchg(&console_silent_atomic, 0, 1) == 1) { + mdelay(500); + return; + } + + dump_stack(); + + /* print the use info of all memory */ + show_pfn_memory_info = (ivpfn) kallsyms_lookup_name("MEM_PrintAllMemory"); + if (show_pfn_memory_info != NULL) { + printk(KERN_EMERG "\nmem trace:\n"); + show_pfn_memory_info(); + } else { + printk(KERN_EMERG "error, MEM_PrintAllMemory is NULL!\n"); + } + + /* print slab info */ + printk(KERN_EMERG "\nslab info:\n"); + show_proc_slab_info(); + + /* print mem info */ + printk(KERN_EMERG "\nmem info:\n"); + show_proc_mem_info(); + + /* silent console for console print too slow */ + _console_silent(); + /* print the info of current process */ + printk(KERN_EMERG "ps -aux:\n"); + show_ps_aux_info(); + _console_resume(); + + /* print mem */ + k_show_mem(0, NULL); + + /* silent console for console print too slow */ + _console_silent(); + show_memfs_info(); + _console_resume(); + + atomic_set(&console_silent_atomic, 0); +} + +static int debug_oom_notify(struct notifier_block *self, unsigned long notused, void *nfreed) +{ + if (sysctl_oom_enhance_enable) + oom_show_debug_info(); + return 0; +} + +static struct notifier_block debug_oom_nb = { + .notifier_call = debug_oom_notify +}; + +static int __init oom_debug_info_init(void) +{ + int ret; + + printk("oom_debug_info init\n"); + + ret = init_kernel_sym(); + if (ret) { + return ret; + } + + ret = register_oom_notifier(&debug_oom_nb); + if (ret) { + printk("register_oom_notifier fail\n"); + return ret; + } + + debug_table_header = register_sysctl_table(debug_root_table); + if (!debug_table_header) { + printk("register_sysctl_table fail\n"); + ret = -ENOMEM; + goto sysctl_fail; + } + + return 0; + +sysctl_fail: + unregister_oom_notifier(&debug_oom_nb); + return ret; +} + +static void __exit oom_debug_info_exit(void) +{ + printk("oom_debug_info exit\n"); + unregister_oom_notifier(&debug_oom_nb); + unregister_sysctl_table(debug_table_header); +} + +module_init(oom_debug_info_init) +module_exit(oom_debug_info_exit) + +MODULE_LICENSE("GPL"); diff --git a/src/oom_debug_info/oom_debug_info.h b/src/oom_debug_info/oom_debug_info.h new file mode 100644 index 0000000..d562290 --- /dev/null +++ b/src/oom_debug_info/oom_debug_info.h @@ -0,0 +1,19 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* + * Copyright (c) Huawei Technologies Co., Ltd. 2021-2021. All rights reserved. + */ +#ifndef _OOM_SHOW_INFO_H +#define _OOM_SHOW_INFO_H +#ifdef CONFIG_EULEROS_DEBUG_OOM +#include <linux/nodemask.h> +#include <linux/seq_file.h> + +extern int sysctl_oom_enhance_enable; +extern int sysctl_oom_print_file_info; +extern int sysctl_oom_show_file_num_in_dir; + +extern unsigned long kallsyms_lookup_name(const char *name); +extern void oom_show_debug_info(nodemask_t *nodemask); +extern struct dentry *get_mountpoint_from_mnt_root(struct dentry *dentry); +#endif +#endif -- 2.29.2

1 0

Fwd: openEuler Developer Day 启动大会招募环节，报名通道同步开启！
by Marketing openEuler 17 May '21

17 May '21

openEuler 社区的开发者：您好！ openEuler Developer Day 2021 将于*6**月10日*在北京举行。本次大会是由 openEuler 社区发起，主要面向签署了 CLA的核心开发者、南北向生态厂商以及核心用户的一场技术盛会，旨在推动 openEuler 社区在多样性计算、云原生全栈、全场景协同等技术方向的持续探索和创新。 *开放招募* openEuler Developer Day 正式开放招募环节：*Call for Speaker* <https://shimo.im/forms/KgXxt8JCYKYtVXHx/fill>、*Call for Sponsor* <https://shimo.im/forms/vwCC68q3pQvvR3Yc/fill>、*Call for SIG* <https://shimo.im/forms/x6vXyW8QHCGK9QJD/fill>、*Call for Demo* <https://shimo.im/forms/PQTvWKjHgg96DjD8/fill> 欢迎 openEuler 社区的开发者提交以上四个方面的材料。 [image: 截屏2021-05-13 下午8.12.43.png] *大会亮点* 这是一场大型的面向 openEuler 社区开发者的技术交流会议。在现场共同探讨*热点技术方向*和*如何参与社区贡献*，通过大会*公开接收用户需求*，*完成版本规划*。 *技术委员会*、*品牌委员会*、*用户委员会*、*20个 SIG 组*会同期举办*开放工作会议**（仅限签署社区 CLA 的开发者参加）*。技术委员会主席给大家解读 *openEuler 21.03*，发布下个社区版的*技术定位*，分享社区创新思路。来自互联网、金融、运营商的客户分享成功的应用实践经验。开源圆桌中，客户、伙伴、厂商、研究机构一同探究开源软件供应链的意义和风险，开源模式如何推动独立演进操作系统技术的发展。更有开发者心心念念的 *Party* 心动不如行动，赶紧来报名参会 <https://e-campaign.huawei.com/m/mIzQFr>吧！！！

1 0

OBS 构建优化，软件包 spec 缺少构建依赖需要补齐，请各位开发者关注
by Chenyanpan 17 May '21

17 May '21

openEuler 社区各位开发者，大家好：目前我们在 openEuler OBS 构建优化过程中，发现一些优化项需要大家一起协作完成。具体情况是这样的： OBS 每次构建软件包会创建新的构建环境（build environment），在构建环境中 preinstall 一些必备软件包，然后 install 这些必备软件包及其依赖，以及 spec 中 BuildRequires 及其依赖。当前 preinstall 预安装一些多余软件包，部分软件包存在多余安装依赖，导致每次创建构建环境至少需要安装 300+ 个 rpm，占用空间 1.2GB，耗时 60+ 秒。需要对 Project Config 及软件包的依赖进行优化，减少构建过程安装的 rpm 数量，避免 IO 资源浪费，缩短构建时间。去除软件包多余依赖，不仅对构建过程有收益，对实际使用环境也有好处，在实际使用环境中避免安装时间、空间浪费，也可以减少安装多余 rpm 引入不必要的安全漏洞。前期我们做了初步分析，对 openEuler 整个版本每个包起到较好的效果。优化方案在 2021.05.12 TC 例会上汇报过，TC 同意优化方案落地实施。议题及结论如下： [cid:image001.png@01D74B12.BE6C92C0] 由于优化需要从构建环境去掉了一些依赖，有些软件包本来自身需要的构建依赖如果没在 spec 中明确指定，那么当前构建会缺少依赖导致构建失败，目前遇到的软件包有 317 个，已经提了 issue 跟踪，软件包列表见邮件附件。当前需要大家共同完成的工作是：对这些构建失败的软件包，整改 spec 文件，补齐各自需要的构建依赖。为了尽量缩小影响范围，我们从 openEuler:Mainline 复制了一个工程 openEuler-Mainline-copy，请大家基于 openEuler-Mainline-copy 开发验证，代码提交到 src-openeuler 各自的代码仓。软件包 spec 整改后我们再将优化的 Project Config 应用到 openEuler:Mainline 工程（由于复制的工程跟 Mainline 工程的代码未能及时同步，如果应用后个别软件包构建失败再进一步整改）。为了减少大家的工作量，我们对构建失败的这些软件包的日志进行初步分析，其中大部分包列出失败的关键日志，以及可能缺失的依赖，大家可以参考，或者对比 openEuler:Mainline 工程中同一软件的构建日志，可以判断缺少的构建依赖，具体信息请查看相关issue。请各位软件包责任人在 2021.05.31 前完成该项任务。开发验证过程中如有疑问，请与我联系。谢谢！ -- 陈燕潘 (@chenyanpanHW)

1 0

sig-release-management双周例会
by openEuler conference 17 May '21

17 May '21

1 0

sig-CN双周会议
by openEuler conference 17 May '21

17 May '21

1 0

Compliance-SIG 双周例会
by openEuler conference 17 May '21

17 May '21

1 0

测试结论////答复: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知
by liyongqiang (H) 14 May '21

14 May '21

本次update测试策略： 1、发布软件包的安装升级管理操作验证验证本次发布软件包的升级正确性符合用户实际使用场景 1)从LTS升级到SP1的update 2)从LTS升级到LTS的某个update，然后再升级到SP1本次发布的update 3)从SP1版本直接升级到此次update 4)选取SP1的中间发布update进行升级发布软件包管理验证升级后的卸载与回退 2、本次发布软件包提供服务的管理操作验证(启动/停止/重启等) 3、软件包升级后操作系统的基本集成功能验证/重启 2、测试结论发布软件包安装升级无问题升级后，系统重启正常，软件包可以正常卸载软件包提供命令和服务完成验证测试过程中发现问题已解决同意update版本发布发件人: xiasenlin 发送时间: 2021年5月14日 18:15 收件人: release(a)openeuler.org; qa(a)openeuler.org; sa-announce(a)openeuler.org; dev(a)openeuler.org 抄送: Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com> 主题: 【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知 openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月15日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210515 代码冻结： 20210512 转测试时间：20210514 版本发布： 20210515 本次更新主要涉及：golang、xstream等；修复cve：25个 CVE清单： CVE-2021-29425 次要 src-openEuler/apache-commons-io CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-27506 次要 src-openEuler/clamav CVE-2021-3448 不重要 src-openEuler/dnsmasq CVE-2021-29470 次要 src-openEuler/exiv2 CVE-2021-29457 主要 src-openEuler/exiv2 CVE-2021-29458 次要 src-openEuler/exiv2 CVE-2021-28650 次要 src-openEuler/gnome-autoar CVE-2021-27918 主要 src-openEuler/golang CVE-2021-28168 次要 src-openEuler/jersey CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-15169 次要 src-openEuler/rubygem-actionview CVE-2021-21349 主要 src-openEuler/xstream CVE-2021-21350 严重 src-openEuler/xstream CVE-2021-21348 主要 src-openEuler/xstream CVE-2021-21351 严重 src-openEuler/xstream CVE-2021-21341 主要 src-openEuler/xstream CVE-2021-21342 严重 src-openEuler/xstream CVE-2021-21343 主要 src-openEuler/xstream CVE-2021-21344 严重 src-openEuler/xstream CVE-2021-21345 严重 src-openEuler/xstream CVE-2021-21346 严重 src-openEuler/xstream CVE-2021-21347 严重 src-openEuler/xstream From: guoxiaoqi Sent: Friday, May 14, 2021 9:34 AM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>>; xiasenlin <xiasenlin1(a)huawei.com<mailto:xiasenlin1@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试新增依赖软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler src-openEuler/mxparser 依赖 SP1 不涉及 openEuler src-openEuler/xmlpull 依赖 SP1 不涉及 openEuler From: guoxiaoqi Sent: Thursday, May 13, 2021 9:10 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试更新，xstream不涉及接口变更。thrift涉及变更，本次版本暂时不发布软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… From: guoxiaoqi Sent: Thursday, May 13, 2021 3:39 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; guoxiaoqi <guoxiaoqi2(a)huawei.com<mailto:guoxiaoqi2@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: 【20.03-LTS-SP1 512 update周版本】启动测试请启动openEuler-20.03-LTS-SP1 2021年512 周版本测试软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 涉及接口变更 openEuler src-openEuler/thrift CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base…

1 0

【CVE update】openEuler 20.03 LTS SP1 CVE Update 2021/5/14 release评审通知
by xiasenlin 14 May '21

14 May '21

openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时邮件通知我们，2021年5月15日结束发布流程。版本目标：CVE修复版本计划：例行CVE冻结（本次为周例行版本）：20210515 代码冻结： 20210512 转测试时间：20210514 版本发布： 20210515 本次更新主要涉及：golang、xstream等；修复cve：25个 CVE清单： CVE-2021-29425 次要 src-openEuler/apache-commons-io CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-3487 次要 src-openEuler/binutils CVE-2021-27506 次要 src-openEuler/clamav CVE-2021-3448 不重要 src-openEuler/dnsmasq CVE-2021-29470 次要 src-openEuler/exiv2 CVE-2021-29457 主要 src-openEuler/exiv2 CVE-2021-29458 次要 src-openEuler/exiv2 CVE-2021-28650 次要 src-openEuler/gnome-autoar CVE-2021-27918 主要 src-openEuler/golang CVE-2021-28168 次要 src-openEuler/jersey CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-28493 次要 src-openEuler/python-jinja2 CVE-2020-15169 次要 src-openEuler/rubygem-actionview CVE-2021-21349 主要 src-openEuler/xstream CVE-2021-21350 严重 src-openEuler/xstream CVE-2021-21348 主要 src-openEuler/xstream CVE-2021-21351 严重 src-openEuler/xstream CVE-2021-21341 主要 src-openEuler/xstream CVE-2021-21342 严重 src-openEuler/xstream CVE-2021-21343 主要 src-openEuler/xstream CVE-2021-21344 严重 src-openEuler/xstream CVE-2021-21345 严重 src-openEuler/xstream CVE-2021-21346 严重 src-openEuler/xstream CVE-2021-21347 严重 src-openEuler/xstream From: guoxiaoqi Sent: Friday, May 14, 2021 9:34 AM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com> Cc: Yanxiaobing <yanxiaobing(a)huawei.com>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com>; wangchong (J) <wangchong56(a)huawei.com>; yaokai (G) <yaokai13(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; xiasenlin <xiasenlin1(a)huawei.com> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试新增依赖软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler src-openEuler/mxparser 依赖 SP1 不涉及 openEuler src-openEuler/xmlpull 依赖 SP1 不涉及 openEuler From: guoxiaoqi Sent: Thursday, May 13, 2021 9:10 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: RE: 【20.03-LTS-SP1 512 update周版本】启动测试更新，xstream不涉及接口变更。thrift涉及变更，本次版本暂时不发布软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base… From: guoxiaoqi Sent: Thursday, May 13, 2021 3:39 PM To: Hufeng (Solar, Euler) <solar.hu(a)huawei.com<mailto:solar.hu@huawei.com>>; liyongqiang (H) <liyongqiang10(a)huawei.com<mailto:liyongqiang10@huawei.com>>; chenyaqiang <chenyaqiang(a)huawei.com<mailto:chenyaqiang@huawei.com>> Cc: Yanxiaobing <yanxiaobing(a)huawei.com<mailto:yanxiaobing@huawei.com>>; Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com>>; Liujingang (Bob) <liujingang09(a)huawei.com<mailto:liujingang09@huawei.com>>; guoxiaoqi <guoxiaoqi2(a)huawei.com<mailto:guoxiaoqi2@huawei.com>>; fanjiachen (A) <fanjiachen3(a)huawei.com<mailto:fanjiachen3@huawei.com>>; Zhangtao (zhangtao, AX) <zhangtao221(a)huawei.com<mailto:zhangtao221@huawei.com>>; Miaokaibo (miao_kaibo) <miaokaibo(a)huawei.com<mailto:miaokaibo@huawei.com>>; wangchong (J) <wangchong56(a)huawei.com<mailto:wangchong56@huawei.com>>; yaokai (G) <yaokai13(a)huawei.com<mailto:yaokai13@huawei.com>>; Xuxiaosong <xuxiaosong(a)huawei.com<mailto:xuxiaosong@huawei.com>> Subject: 【20.03-LTS-SP1 512 update周版本】启动测试请启动openEuler-20.03-LTS-SP1 2021年512 周版本测试软件包类别所属分支接口变更责任田 src-openEuler/apache-commons-io CVE SP1 不涉及 openEuler src-openEuler/binutils CVE SP1 不涉及基础服务 src-openEuler/dnsmasq CVE SP1 不涉及网络组 src-openEuler/exiv2 CVE SP1 不涉及网络组 src-openEuler/gnome-autoar CVE SP1 不涉及网络组 src-openEuler/golang CVE SP1 不涉及容器组 src-openEuler/jersey CVE SP1 不涉及 openEuler src-openEuler/python-jinja2 CVE SP1 不涉及基础服务 src-openEuler/rubygem-actionview CVE SP1 不涉及 openEuler src-openEuler/velocity CVE SP1 不涉及 openEuler src-openEuler/xstream CVE SP1 涉及接口变更 openEuler src-openEuler/thrift CVE SP1 不涉及 openEuler 测试repo： SP1：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/update_… SP1 EPOL：http://121.36.84.172/repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/u… 请测试同时挂载发布源everything和update repo： SP1 everything: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/$basearch SP1 update: https://repo.openeuler.org/openEuler-20.03-LTS-SP1/update/$basearch EPOL：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/$basearch EPOL update：https://repo.openeuler.org/openEuler-20.03-LTS-SP1/EPOL/update/$base…

1 0

Compiler SIG双周例会
by openEuler conference 14 May '21

14 May '21

1 0

OS-Builder 例会
by openEuler conference 14 May '21

14 May '21

1 0

会议纪要：安全委员会&安全sig例会
by yanglijin 14 May '21

14 May '21

��ˣ�� ʱ�䣺2021/5/13 16:00��17:30 ��ˣ��գ�κ�գ��콡ΰ��ס�ͳ��-gaochong��ͳ��-zhangshaoning��-��Ρ��-�� ⡿ 1. ©��֪��߽�չ �� ־ȫ 1��ݾۺ��Ż� 100% 2��ֶΣ��ϵͳ�״θ�֪ʱ��ֶΣ� 100% 3��Ż� 95% 4��Ż� 50% 5��ʱЧ�Ա�� 10% 2. ��©��չ �� 1�� ©��֪��˫�ܣ�4��28��-5��12�գ��©��67��7��©��42��Ҫ�漰Compiler��rust 8��Networking��unbound 11��kernel��4��52��©��֪��ߣ�ռ��78% 2�� ޸��5��6��ѷ��¶Ȱ汾��32��SA��74��CVE 3�� ޸��ǰ��99��©��δ�޸��7��ϴ��޸�©��39�� 4�� 5��12��ܰ汾��壬��CVE 30�� 3. ��openEuler��Դ��ȫ�� κ�� Ŀ�ģ��Ӳ��ƽ̨��ȫ��֮�� ܣ��ռ��ֲ��䡢��Ƽ��ϵĸ��ֻ��ȫ��Լ��ȫ�м��ʹ��ȫ�� Ҫ��ԣ�Զ��֤��û��ȡĿ��ϵͳ��Ӳ��״̬ ��ۣ�ͬ��openEuler��֣��security-facility�� 4. ��audit��Ӱ�� Ϊ��ʹaudit��ں˽ӿ�ƥ��ø��ã��ҪOSV��audit��Ӱ�� audit �ӿڱ��issue : https://gitee.com/src-openeuler/audit/issues/I3R0Q8?from=project-issue ��⣺��ǰOSV��audit��Ӱ�� 5. CVE�� giflib CVE-2020-23922 ��ۣ��Ҫ��һ��н�� ´λ��ʱ�䣺5��19�գ� ��ˣ�� 00511953 ��Ʒ��-��ƽ̨��ĿȺ Mobile��15168350853 Email��yanglijin(a)huawei.com <mailto:yanglijin@huawei.com%20>

1 0

ROS-sig 例会会议纪要
by 安传旭 13 May '21

13 May '21

您好： ROS-sig组23th双周例会会议纪要如下：上阶段计划完成的任务： 1. 验证提交到对应分支后，CI是否可以识别并通过对应分支代码； 2. 开始适配20.03spce文件，进行sp2入源包的修改和检查，并提交入源交付物 DONE 1. 维护ROS打包工作汇总表； 2. 验证提交到对应分支后，CI是否可以识别并通过对应分支代码； 3. 开始适配20.03 spce文件，进行sp2入源包的修改和检查，并提交入源交付物，共计36个PR被merge。注意事项催促release-sig组尽快审核PR，将ROS组件加入到版本测试； Hello: The meeting minutes of 23th biweekly regular meeting of ROS-SIG Group are as follows: Tasks planned to be completed in the previous stage: 1. Verify whether CI can identify and pass the corresponding branch code after submitting to the corresponding branch; 2. Begin to adapt the 20.03 SPCE file, modify and check the SP2 incoming source package, and submit incoming source deliverables DONE 1. Maintain the ROS packaging summary table; 2. Verify whether CI can identify and pass the corresponding branch code after submitting to the corresponding branch; 3. Start to adapt the 20.03 SPCE file, modify and check the SP2 incoming source package, and submit incoming source deliverables, a total of 36 PR were merged. Matters needing attention Urge the release-sig team to review the PR as soon as possible and add the ROS component to the release test;

1 0

etcd使用的简单介绍
by openEuler conference 13 May '21

13 May '21

1 0

ROS例会
by 安传旭 13 May '21

13 May '21

您好！ openEuler ROS SIG 邀请您参加 2021-05-13 19:00 召开的腾讯会议会议主题：ROS例会会议内容： 1. openEuler ROS组件的移植情况； 2. ROS组件对openEuler 20.03 LTS SP2的适配。点击链接入会，或添加至会议列表：https://meeting.tencent.com/s/2fogPapxXLsg <https://meeting.tencent.com/s/2fogPapxXLsg> 会议 ID：969 2960 5954 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com <http://gitee.com/>的ID 更多资讯尽在：https://openeuler.org/zh/ <https://openeuler.org/zh/> Hello! Openeuler Ros SIG invites you to attend the Tencent conference at 2021-05-13 19:00 Conference Theme: ROS Regular Meeting Content of the Conference: 1. Migration of OpenEuler ROS components; 2. Adaptation of the ROS component to OpenEuler 20.03 LTS SP2. Click on the links to membership, or add to the meeting list: https://meeting.tencent.com/s/2fogPapxXLsg <https://meeting.tencent.com/s/2fogPapxXLsg> Conference ID: 969 2960 5954 Warm Reminder: It is recommended to change the participant's name after accessing the conference, or you can use your ID at gitee.com <http://gitee.com/> More information on: https://openeuler.org/zh/ <https://openeuler.org/zh/>

1 0

ROS例会
by 安传旭 13 May '21

13 May '21

您好！ openEuler ROS SIG 邀请您参加 2021-05-14 19:00 召开的腾讯会议会议主题：ROS例会会议内容： 1. openEuler ROS组件的移植情况； 2. ROS组件对openEuler 20.03 LTS SP2的适配。点击链接入会，或添加至会议列表：https://meeting.tencent.com/s/2fogPapxXLsg 会议 ID：969 2960 5954 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com <http://gitee.com/>的ID 更多资讯尽在：https://openeuler.org/zh/ <https://openeuler.org/zh/> Hello! Openeuler Ros SIG invites you to attend the Tencent conference at 2021-05-14 19:00 Conference Theme: ROS Regular Meeting Content of the Conference: 1. Migration of OpenEuler ROS components; 2. Adaptation of the ROS component to OpenEuler 20.03 LTS SP2. Click on the links to membership, or add to the meeting list: https://meeting.tencent.com/s/2fogPapxXLsg Conference ID: 969 2960 5954 Warm Reminder: It is recommended to change the participant's name after accessing the conference, or you can use your ID at gitee.com More information on: https://openeuler.org/zh/

1 0

Firefly-RK3399 开发板的 openEuler 内测镜像发布
by 方亚芬 12 May '21

12 May '21

Hi，大家好。我是 openEuler 社区树莓派 SIG 组的 maintainer。我们发布了适配到 Firefly-RK3399 开发板的 openEuler 内测镜像，详见：https://gitee.com/openeuler/rockchip。欢迎大家试用，有问题或需求欢迎提 issue。祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

1 0

RaspberryPi例会
by openEuler conference 12 May '21

12 May '21

2 1

virt sig例会-20210514
by openEuler conference 12 May '21

12 May '21

1 0

品牌委员会理会
by openEuler conference 12 May '21

12 May '21

1 0

sig-bio双周例会
by openEuler conference 11 May '21

11 May '21

2 1

由于5月12日与TC例会冲突，会议时间调整到5月19日//sig-release-management双周例会
by Xuxiaosong 11 May '21

11 May '21

欢迎大家申报议题。 From: openEuler conference [mailto:public@openeuler.io] Sent: Tuesday, May 11, 2021 10:22 AM Subject: [Dev] sig-release-management双周例会您好！ openEuler sig-release-management SIG 邀请您参加 2021-05-19 10:00 召开的ZOOM会议会议主题：sig-release-management双周例会会议链接：https://us06web.zoom.us/j/86347500013?pwd=cjYydXVaUGE1czdFVE11bU5sY0tHdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference will be held at 2021-05-19 10:00, The subject of the conference is sig-release-management双周例会, You can join the meeting at https://us06web.zoom.us/j/86347500013?pwd=cjYydXVaUGE1czdFVE11bU5sY0tHdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

sig-release-management双周例会
by openEuler conference 11 May '21

11 May '21

1 0

openEuler安全委员会例会
by openEuler conference 11 May '21

11 May '21

1 0

TC双周例会
by openEuler conference 10 May '21

10 May '21

3 2

sig-release-management双周例会
by openEuler conference 10 May '21

10 May '21

2 1

【Meeting Notice】openEuler kernel 技术分享第五期 & 双周例会 Time: 2021-05-14 14:00-18:00
by Meeting Book 10 May '21

10 May '21

1 0

sig-confidential-computing双周例会
by openEuler conference 10 May '21

10 May '21

1 0

申报议题 RE: [Tc] Re: TC双周例会
by Chenyanpan 10 May '21

10 May '21

议题： openEuler OBS 构建 Project Config 及 spec 优化内容： OBS 每次构建软件包会创建新的构建环境（build environment），在构建环境中 preinstall 一些必备软件包，然后 install 这些必备软件包及其依赖，以及 spec 中指定的 BuildRequires 及其依赖。当前 preinstall 安装多余软件包，部分软件包 spec 存在多余依赖，导致每次创建构建环境至少需要安装 300+ 个 rpm，占用空间 1.2GB，耗时 60+ 秒。需要对 Project Config 及 spec 进行优化，减少构建过程安装的 rpm 数量，避免 IO 资源浪费，缩短构建时间。同时去掉软件包 spec 多余依赖，避免安装时间、空间浪费，也避免安装多余 rpm 引入的安全风险。 From: Liujingang (Bob) [mailto:liujingang09@huawei.com] Sent: Monday, May 10, 2021 9:26 AM To: tc(a)openeuler.org; dev(a)openeuler.org Subject: [Tc] Re: TC双周例会欢迎大家上报议题，当前议题如下： 1、遗留问题跟踪： 2、SIG运作情况分享：（1）sig-OKD运作情况介绍杨昭（2）sig-ONL运作情况介绍栾建海（3）Storage运作情况介绍刘志强 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, May 10, 2021 9:11 AM To: tc(a)openeuler.org<mailto:tc@openeuler.org>; dev(a)openeuler.org<mailto:dev@openeuler.org> Subject: [Tc] TC双周例会您好！ openEuler TC SIG 邀请您参加 2021-05-12 10:00 召开的ZOOM会议(自动录制) 会议主题：TC双周例会会议链接：https://us06web.zoom.us/j/83802136408?pwd=NWVzQStkM1V6bEpkTzFqdEc5cFZidz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-12 10:00, The subject of the conference is TC双周例会, You can join the meeting at https://us06web.zoom.us/j/83802136408?pwd=NWVzQStkM1V6bEpkTzFqdEc5cFZidz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

【Infra】邮件列表故障通知
by 随心 08 May '21

08 May '21

Hey openEuler developers: Due to a physical hardware failure on the cloud instance, the delivering functionality of the mailing list became abnormal between 09:00 and 10:00 on May 8, 2021, now the service is online now. If you use the mailing list service during this period, you need to resend the mail again. To avoid similar problems in the future, the Infrastructure team plan to refactor the deloyment architecture to guarantee service SLA. If you still have other problems, please contact us in the following ways: [1]: https://gitee.com/openeuler/infrastructure/issues [2]: infra(a)openeuler.org Gaohechao openEuler Infrastructure Team --------------------------------------------------------------------------------------------------------------------------- openEuler社区的开发者: 由于云主机物理硬件故障，在2021年5月8日9:00-10:00期间邮件列表收发邮件功能出现异常，当前系统已经恢复，如果有在此时间段使用邮件列表服务，需要重新发送。为避免后续类似问题，基础设施小组已经计划对邮件列表做HA改造，保障服务的SLA，如果您在服务使用中还遇到其他问题，请通过以下途径联系我们： [1]: https://gitee.com/openeuler/infrastructure/issues [2]: infra(a)openeuler.org 高鹤超 openEuler 基础设施团队

1 0

openEuler 20.03 LTS SP2 Test round 1转测试通知
by Xuxiaosong 08 May '21

08 May '21

转测试计划比原计划有2天延期。请相关责任人最晚于2021-5-10前完成特性进展更新为正常状态。 Test round 1版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-20.03-LTS-SP2/openeuler-2021-05-0… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 20.03-LTS-SP2-round-1）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-20.03-… 1、本轮转41个特性，详见附件； 2、本轮新增和删除包列表详见附件； Release plan Stage name Begin time End time key feature collect 2021-03-16 2021-03-31 Develop 2021-03-16 2021-04-26 Kernel freezing 2021-04-16 2021-04-16 Build 2021-04-26 2021-04-30 Test round 1（we are here） 2021-05-6 2021-05-12 Test round 2 2021-05-17 2021-05-21 Test round 3 2021-05-24 2021-05-31 Test round 4 2021-06-03 2021-06-07 Test round 5 2021-06-09 2021-06-11 release 2021-06-28 2021-06-30 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 openEuler 20.03-LTS-SP2版本支持内核热升级<https://gitee.com/openeuler/release-management/issues/I3JDU8?from=project-i…> Testing ops anatas<https://gitee.com/anatas> 2 openEuler 20.03-LTS-SP2支持内存分级扩展特性<https://gitee.com/openeuler/release-management/issues/I2C2NI?from=project-i…> Testing storage liuzhiqiang26<https://gitee.com/liuzhiqiang26> 3 openEuler 20.03-LTS-SP2版本集成secgear组件<https://gitee.com/openeuler/release-management/issues/I3JE3U?from=project-i…> Testing sig-confidential-computing chenmaodong<https://gitee.com/chenmaodong> 4 openEuler 20.03 LTS SP2 support OpenStack Rocky Discussion sig-openstack @joec88 @liksh @xiyuanwang @huangtianhua 5 openEuler 20.03 LTS SP2支持osinfo软件包<https://gitee.com/openeuler/release-management/issues/I3N30H?from=project-i…> Testing 6 openEuler 20.03 LTS SP2开源openEuler-rpm-config宏定义文件<https://gitee.com/openeuler/release-management/issues/I3N30J?from=project-i…> Testing 7 openEuler 20.03 LTS SP2 支持 compat-openssl10、libzip等<https://gitee.com/openeuler/release-management/issues/I3N30L?from=project-i…> Testing 8 openEuler 20.03 LTS SP2 支持libwbxml、hyperscan<https://gitee.com/openeuler/release-management/issues/I3N30N?from=project-i…> Testing 9 openEuler 20.03 LTS SP2支持microcode_ctl<https://gitee.com/openeuler/release-management/issues/I3N30S?from=project-i…> Testing 10 openEuler 20.03 LTS SP2支持bcc软件包<https://gitee.com/openeuler/release-management/issues/I3N30Q?from=project-i…> Testing 11 openEuler 20.03 LTS SP2支持树莓派<https://gitee.com/openeuler/release-management/issues/I3N30P?from=project-i…> Testing 12 openEuler 20.03 LTS SP2支持1822 HBA卡<https://gitee.com/openeuler/release-management/issues/I3N30V?from=project-i…> Testing 13 openEuler 20.03 LTS SP2支持飞腾2000+/64<https://gitee.com/openeuler/release-management/issues/I3N30W?from=project-i…> Testing 14 openEuler 20.03 LTS SP2支持maildrop和proftpd<https://gitee.com/openeuler/release-management/issues/I3N30X?from=project-i…> Testing 15 openEuler 20.03 LTS SP2支持 iSulad 2.0<https://gitee.com/openeuler/release-management/issues/I3N312?from=project-i…> Testing 16 openEuler 20.03 LTS SP2 A-tune 2.0<https://gitee.com/openeuler/release-management/issues/I3N314?from=project-i…> Testing 17 openEuler 20.03 LTS SP2 支持网络安装<https://gitee.com/openeuler/release-management/issues/I3N315?from=project-i…> Testing 18 openEuler 20.03 LTS SP2 支持 criu组件<https://gitee.com/openeuler/release-management/issues/I3N319?from=project-i…> Testing 19 openEuler 20.03 LTS SP2支持config_acpi_nfit<https://gitee.com/openeuler/release-management/issues/I3N31B?from=project-i…> Testing 20 openEuler 20.03 LTS SP2 虚拟化增强<https://gitee.com/openeuler/release-management/issues/I3N31E?from=project-i…> Testing 21 openEuler 20.03 LTS SP2 支持 UKUI桌面<https://gitee.com/openeuler/release-management/issues/I3N31F?from=project-i…> Testing 22 openEuler 20.03 LTS SP2 支持openGauss<https://gitee.com/openeuler/release-management/issues/I3N31I?from=project-i…> Testing 23 openEuler 20.03 LTS SP2 支持DDE桌面<https://gitee.com/openeuler/release-management/issues/I3N31J?from=project-i…> Testing 24 openEuler 20.03 LTS SP2 编译器支持openjdk<https://gitee.com/openeuler/release-management/issues/I3N31M?from=project-i…> Testing 25 openEuler 20.03 LTS SP2支持HA<https://gitee.com/openeuler/release-management/issues/I3N31O?from=project-i…> Developing 26 openEuler 20.03 LTS SP2 加速库版本同步<https://gitee.com/openeuler/release-management/issues/I3N31Q?from=project-i…> Testing 27 openEuler 20.03 LTS SP2支持金融领域软件包<https://gitee.com/openeuler/release-management/issues/I3N311?from=project-i…> Testing 28 openEuler 20.03 LTS SP2支持kmod功能<https://gitee.com/openeuler/release-management/issues/I3N30C?from=project-i…> Testing 29 openEuler 20.03 LTS SP2支持华为多路径<https://gitee.com/openeuler/release-management/issues/I3N2XS?from=project-i…> Testing 30 openEuler 20.03 LTS SP2 CPU核故障在线隔离解决方案<https://gitee.com/openeuler/release-management/issues/I3N36L?from=project-i…> Developing 31 openEuler 20.03 LTS SP2 支持多应用版本构建和发布<https://gitee.com/openeuler/release-management/issues/I3N36K?from=project-i…> Developing 32 openEuler 20.03 LTS SP2 内存UCE故障降级，用户数据保持一致，业务可持续运行<https://gitee.com/openeuler/release-management/issues/I3N36H?from=project-i…> Testing 33 openEuler 20.03 LTS SP2 故障预测框架<https://gitee.com/openeuler/release-management/issues/I3N36F?from=project-i…> Developing 34 openEuler 20.03 LTS SP2 IO_URING全栈使能<https://gitee.com/openeuler/release-management/issues/I3N36C?from=project-i…> Testing 35 openEuler 20.03 LTS SP2 Qemu：虚拟化可靠性和可维护性增强<https://gitee.com/openeuler/release-management/issues/I3N369?from=project-i…> Testing 36 openEuler 20.03 LTS SP2 Qemu：热迁移pro，提升热迁移性能+安全<https://gitee.com/openeuler/release-management/issues/I3N368?from=project-i…> Testing 37 openEuler 20.03 LTS SP2支持StratoVirt：下一代轻量化虚拟化平台<https://gitee.com/openeuler/release-management/issues/I3N364?from=project-i…> Testing 38 【openEuler 20.03 LTS SP2】继承xfce 4.14<https://gitee.com/openeuler/release-management/issues/I3NC3I?from=project-i…> Discussion xfce @dillon_chen<https://gitee.com/dillon_chen> 39 【openEuler 20.03 LTS SP2】继承Kubernetes 1.18<https://gitee.com/openeuler/release-management/issues/I3NC5H?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 40 【openEuler 20.03 LTS SP2】继承门禁检查功能<https://gitee.com/openeuler/release-management/issues/I3O08F?from=project-i…> Testing 41 openEuler 20.03-LTS-SP2 集成 kubernetes 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I2BHF4?from=project-i…> Testing 42 openEuler 20.03-LTS-SP2 arm虚拟机支持NMI watchdog<https://gitee.com/openeuler/release-management/issues/I2B4WL?from=project-i…> Testing 43 openEuler 20.03-LTS-SP2 集成 coredns 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXLJ?from=project-i…> Testing 44 【openEuler 20.03 LTS SP2】虚拟机热迁移支持TLS<https://gitee.com/openeuler/release-management/issues/I3IE57?from=project-i…> Testing 45 【kernel-4.19】openEuler kernel nvme 驱动增强<https://gitee.com/openeuler/release-management/issues/I1WGZE?from=project-i…> Testing 46 openEuler 20.03-LTS-SP2 集成 etcd 及其依赖组件<https://gitee.com/openeuler/release-management/issues/I3MXGJ?from=project-i…> Testing 47 【openEuler 20.03 LTS SP2】【虚拟化】回合openEuler 21.03，vmtop支持x86<https://gitee.com/openeuler/release-management/issues/I3NLWF?from=project-i…> Testing

1 0

openEuler Repository Issues
by George 07 May '21

07 May '21

大家好，我是openEuler社区Infra-Sig组maintainer，近期对openEuler在Gitee上的代码仓库进行梳理，发现一些不符合预期的代码仓库，需要整改，现将相关事宜知会如下： 1、openEuler社区目前的代码仓库结构：    openEuler社区在Gitee平台有一个对应的Enterprise，名为open_euler    其下有三个组织：        openeuler：用于管理源码仓库，通过https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml配置文件管理        src-openeuler：用于管理二进制仓库，通过https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.yaml配置文件管理        openEuler-competition：用于管理社区竞赛相关代码仓库，通常由相关委员会成员通知Infra-Sig组添加或删除。    2、扫描发现部分社区成员在open_euler Enterprise下创建、Fork了部分仓库，这些仓库不属于三个组织中的任何一个，具体仓库信息见附件。    这部分仓库通常是误操作导致，创建者在创建后又无权限删除，导致仓库残留。后续会禁用直接在企业下创建和Fork仓库的权限。    所以Infra-Sig近期（1周后）将对上述仓库做清理，删除这些直接归属在Enterprise下的仓库。 3、清理原因：仓库占用社区资源且仓库路径容易引起混淆。     4、如何确认是否有自己涉及的仓库：下载附件，在附件中搜索自己的giteeId（注意是giteeId不是Gitee名称）。     如果没有搜索到即不涉及。如果搜索到，但确认不需要该仓库，则无需特殊处理，由Infra-Sig统一清理。 5、如有特殊需求需要保留上述仓库，请联系infra(a)openeuler.xn--org,-t35f38cpymo8g1mtcurqv3bu6ciw0h.    ------------------------------------------------------------------------------------------------------------------------------------------------------------------- Hi, I am the maintainer of Infra-Sig of openEuler community. I recently reviewed the code repository of OpenEuler on the Giitee, Some code repositories that do not meet expectations are found and need to be rectified. The following issues are notified: 1. The code repository structure of the openEuler community is as follows:     The openEuler community has an enterprise named open_euler on the Gitee platform.     There are three organizations under it:            openeuler: manages the source code repository through the https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml configuration file.            src-openeuler: manages the binary repository through the https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.… configuration file.            openEuler-competition: It is used to manage the code repository related to community competitions. Generally, the relevant committee members notify the Infra-Sig to add or delete the code repository. 2. The scan shows that some community members have created and fork some repositories under open_euler Enterprise. These repositories do not belong to any of the three organizations. For details about the repositories, see the attachment.     These repositories are usually caused by misoperations. After being created, the creator does not have the permission to delete them. As a result, the repositories are residual. The permission to create and fork repositories in the enterprise will be disabled later.     Therefore, Infra-Sig will clean up these repositories in the near future (one week later) and delete these repositories directly belonging to Enterprise. 3. Handling reason: The repository occupies community resources and the repository path is easy to confuse. 4. How to check whether your repository is involved: Download the attachment and search for your giteeId in the attachment (giteeId，not the name).     If no search result is found, this issue is not involved. If the repository is found but is not need, the Infra-Sig deletes the warehouse in a unified manner. 5. If there is a special need to retain the above repositories, please contact infra(a)openeuler.org and explain the reason for retaining the repository.

1 0

【DISCUSS】Impala 3.3.0版本在openEuler ARM64架构下的支持
by Peng Lei 07 May '21

07 May '21

Hi devs：我们目前有在openEuler 20.03 LTS arm64平台上使用Impala v3.3.0的使用诉求，但是遗憾的是目前openEuler 20.03并没有提供Impala v3.3.0的软件包或者Impala v3.3.0从x86 到arm的迁移指导。*我们正在尝试做这项工作* *目前的进展：* 1、Impala v3.3.0已经编译完成其依赖的*20+*个软件包（cctz orc1.4 libev breakpad flatbuffers re2 libunwind-1.3-rc1等） 2、剩余5个模块尚未完成迁移（ kudu-1.10.0-cdh6.x-SNAPSHOT llma-minikdc-1.1.0 hive-2.1.1-cdh6.x-SNAPSHOT hbase-2.1.0-cdh6.x-SNAPSHOT sentry-2.1.0-cdh6.x-SNAPSHOT） * 希望有更多的开源爱好者，可以关注和参与到我们的工作中。* 后续我们也会用邮件的方式，同步我们的关键进展，最终提供 Impala v3.3.0的arm 软件包提供给openEuler社区。 Thanks 彭磊

3 3

[DB SIG MEETUP] DB SIG HangZhou meetup Invitation.
by bo zhaobo 06 May '21

06 May '21

各位openEuler开发者，大家好： openEuler DB SIG将于5.9日在杭州举行首次线下meetup，本次Meetup现已邀请到来自openEuler DB SIG、MariaDB Foundation、沃趣科技、openGauss社区、openLooKeng社区等重量级嘉宾进行技术分享。详情请看： https://openeuler.org/zh/interaction/salon-list/detail/?id=43&isMini=1 欢迎各位专家、开发者到场参与。感谢。 --------------------------------------------------------------------------------------------------------------------------- Hi openEuler contributors: openEuler DB SIG will raise a meetup in HangZhou on 9th May, we had invited the high guests from openEuler DB SIG members, MariaDB Foundation, Woqu Tech, openGauss community and openLooKeng community. For more details, please see: https://openeuler.org/zh/interaction/salon-list/detail/?id=43&isMini=1 We are welcome and excited that your attendance. Thank you. BR Bo Zhao [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> 04/30/21, 12:00:00 PM

2 1

【月度update】openEuler 20.03 LTS SP1 Update 2021/4/30 release评审通知
by xiasenlin 06 May '21

06 May '21

openEuler 20.03 LTS SP1 Update 20210430 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年5月7日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I3INM4?from=project-i… 版本目标：CVE、大数据多版本软件包特性和Bugfix修复版本计划：例行CVE冻结（本次为月度例行版本）：20210420 代码冻结： 20210420 转测试时间：20210427 版本发布： 20210430 本次更新主要涉及：python-pillow、netty等；修复cve：66个修复bug：6个新增软件包：3个 SP1：发布源码包 40个； arm二进制包 371个; x86二进制包 374个； SP1:EPOL：发布源码包：EPOL：6个；arm二进制包 15个; x86二进制包 15个； CVE清单： CVE 组件 CVE-2021-20197 binutils CVE-2021-28831 busybox CVE-2020-35492 cairo CVE-2021-27506 clamav CVE-2021-22890 curl CVE-2021-22876 curl CVE-2021-21381 flatpak CVE-2019-8308 flatpak CVE-2021-28153 glib2 CVE-2020-17489 gnome-shell CVE-2020-25666 ImageMagick CVE-2020-25675 ImageMagick CVE-2020-25676 ImageMagick CVE-2020-27757 ImageMagick CVE-2020-27758 ImageMagick CVE-2020-27771 ImageMagick CVE-2020-27772 ImageMagick CVE-2020-27774 ImageMagick CVE-2020-27775 ImageMagick CVE-2020-27751 ImageMagick CVE-2019-18853 ImageMagick CVE-2020-27755 ImageMagick CVE-2020-27223 jetty CVE-2021-28165 jetty CVE-2019-2708 libdb CVE-2020-35523 libtiff CVE-2020-35524 libtiff CVE-2021-20305 nettle CVE-2021-21295 netty CVE-2021-21409 netty CVE-2021-23362 nodejs-hosted-git-info CVE-2021-23358 nodejs-underscore CVE-2021-3474 OpenEXR CVE-2021-3477 OpenEXR CVE-2021-3475 OpenEXR CVE-2021-20296 OpenEXR CVE-2021-3476 OpenEXR CVE-2021-3479 OpenEXR CVE-2021-3449 openssl CVE-2021-27906 pdfbox CVE-2021-27807 pdfbox CVE-2021-28957 python-lxml CVE-2021-25293 python-pillow CVE-2021-25290 python-pillow CVE-2021-25292 python-pillow CVE-2021-27291 python-pygments CVE-2021-20270 python-pygments CVE-2020-26137 python-urllib3 CVE-2019-18281 qt5-qtbase CVE-2021-3470 redis CVE-2021-20289 resteasy CVE-2021-20271 rpm CVE-2021-28834 rubygem-kramdown CVE-2019-13574 rubygem-mini_magick CVE-2020-11076 rubygem-puma CVE-2020-11077 rubygem-puma CVE-2020-26298 rubygem-redcarpet CVE-2020-12866 sane-backends CVE-2020-25097 squid CVE-2021-20193 tar CVE-2021-29136 umoci CVE-2020-13936 velocity CVE-2018-1311 xerces-c 修复bug清单：【20.03-LTS-SP1】【arm/x86】clamav包下的 clamdtop 命令执行报错 https://gitee.com/open_euler/dashboard?issue_id=I3OUAN 【20.03 LTS-SP1版本】redis-server帮助信息内容错误 https://gitee.com/open_euler/dashboard?issue_id=I3OT6A sp1升级tpm2-tools后，直接执行tpm2命令会出现segfault https://gitee.com/open_euler/dashboard?issue_id=I3OSZ3 【20.03-LTS-SP1】【arm/x86】clamav包下的clamconf、clamdscan、clamdtop 命令执行报错，缺少配置文件 https://gitee.com/open_euler/dashboard?issue_id=I3OMTU 【20.03-SP1】【arm】报错无文件 https://gitee.com/open_euler/dashboard?issue_id=I3OMJH 【20.03-LTS-SP1】【arm/x86】clamav包下的clambc命令执行报错 https://gitee.com/open_euler/dashboard?issue_id=I3OLQM 涉及软件仓清单： binutils busybox cairo clamav criu curl etmem flatpak gcc glib2 glibc gnome-shell ima-evm-utils ImageMagick jetty libboundscheck libdb libtiff nettle netty nodejs-hosted-git-info nodejs-underscore OpenEXR openssl openvswitch pdfbox python-lxml python-pillow python-pygments python-urllib3 qt5-qtbase redis resteasy rpm ruby rubygem-kramdown rubygem-mini_magick rubygem-puma rubygem-redcarpet sane-backends squid tar tpm2-tools tpm2-tss umoci velocity

1 0

【Meeting Notice】openEuler kernel 技术分享第四期 & 双周例会 Time: 2021-04-30 14:00-18:00
by chengjian (D) 29 Apr '21

29 Apr '21

-------- Forwarded Message -------- Subject: 【Meeting Notice】openEuler kernel 技术分享第四期 & 双周例会 Time: 2021-04-30 14:00-18:00 Date: Thu, 29 Apr 2021 17:52:38 +0800 From: Meeting Book <uMeeting(a)huawei.com> To: cj.chengjian(a)huawei.com Topic openEuler kernel 技术分享第四期 & 双周例会 Time 2021-04-30 14:00-18:00((UTC+08:00)Beijing) Join Conference Join (External) >> <https://welink-meeting.zoom.us/j/795275194> Meeting ID 795 275 194 Convener 唐嘉远 Agenda 14:00 ~ 15:30 openEuler kernel 技术分享第四期(openEuler内核的PCI子系统介绍-汪雄峰) Tips: Dial the access number to join conference <http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载 <https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download <https://zoom.us/download>

1 0

【Meeting Notice】openEuler kernel 技术分享第四期 & 双周例会 Time: 2021-04-30 14:00-18:00
by Meeting Book 29 Apr '21

29 Apr '21

1 0

Rust Sig和Compiler SIG是否有支持musl工具链计划
by Xufei (VF) 29 Apr '21

29 Apr '21

背景：当前openEuler社区的Rust语言安装包只支持gnu工具链（动态链接）的安装，并不支持musl工具链（静态链接）；业界中Rust语言开发的虚拟化开源软件均使用musl版本进行构建，例如Firecracker、Cloud Hypervisor，因此建议能尽快补齐musl工具链的能力意义： 1、 musl 版本的静态链接支持可让编译出的二进制可移植性更强，不依赖于动态库，提升应用程序可部署能力。 2、 musl 版本的静态链接支持可减少动态链接中的启动时间和内存开销。社区musl工具链支持现状： 1、 musl基础编译工具链在openEuler社区还未支持（例如musl-gcc等等），CentOs、Fedora系统均已支持。 2、 musl版本的libc库的支持，musl的libc库虽然已经引入openEuler社区，但是尝试安装时却无法使用详见https://gitee.com/src-openeuler/musl/issues/I3OICZ?from=project-issue 3、Rust语言安装包的src-openEuler仓库需要适配，实现Rust语言安装包musl工具链支持。请问Rust SIG和Compiler SIG是否有支持musl工具链相关计划?

1 0

安全委员会例会
by openEuler conference 28 Apr '21

28 Apr '21

2 1

OpenStack SIG 例会
by openEuler conference 28 Apr '21

28 Apr '21

2 1

QA-SIG 双周例会
by openEuler conference 27 Apr '21

27 Apr '21

1 0

【重要】openEuler src-openeuler/kernel 仓库已完成瘦身（涉及 force push）
by chengjian (D) 27 Apr '21

27 Apr '21

一句话总结：为了解决仓库太大的问题，src-openeuler/kernel 仓库于今天 2021/04/27 下午 17:30 左右进行了*force push* 因此大家之前 fork 和 clone 的私人仓库建议*强制同步*。 1. 个人 fork 的仓库，可以使用 gitee 的*一键同步功能*，强制拉取。 2. 个人本地 clone 的仓库，建议 *删除掉仓库后重新下载*（如果 clone 的是自己 fork 的仓库，待 1 完成后再进行 2 操作）。 # 1 问题背景 ------- 仓库地址：https://gitee.com/src-openeuler/kernel src-openEuler/kernel 仓库通过 PR 方式来合入补丁。但是 gitee 限制私人仓库不能超过 1G，超过 1G 之后仓库将被封禁，停止访问，禁止提交。个人 fork 的 src-openEuler/kernel 私人仓库无法正常 push，因此无法向 openEuler 主仓提交 PR。 # 2 问题分析 ------- 检索 git/objects 信息发现：历史提交中有一些内核源代码 TAR 包，该文件大小接近 1G，导致仓库较大涉及的历史提交如下：即使大文件已经在历史提交中被删除，但是仍然存在于 git 历史记录中，方便查找历史提交和回滚版本。 # 3 问题解决 ------- 通过 git filter-branch 强制删除了历史上的大文件的提交，并重建了 commit 记录。最后仓库进行了强制 push 本次瘦身清理的历史文件包括： 1. linux-4.19.90.tar.gz 内核源代码 TAR 包 2. patches.tar.bz2 patch 文件 TAR 包此次清理的历史都是早期仓库创建初期的一些提交，已在后面提交中被清理。现在当前仓库使用 PR 方式合入，经过 CI 门禁和 Committer 检视，不会再发生此类问题。清理前，仓库大小 1.1G 清理后，仓库大小 3.1M # 4 影响以及建议操作 ------- 由于仓库进行了强制 push，因此大家之前 fork 和 clone 的私人仓库建议强制同步。 1. fork 的仓库，可以使用 gitee 的一键同步功能，强制拉取。点击红色框中的刷新按钮即可。 2. 自己本地 clone 的仓库，建议删除仓库后重新下载。谢谢 ---- 成坚

1 0

回复：CloudNative SIG双周例会
by gwei3 27 Apr '21

27 Apr '21

代表安全委员会申请增加一个议题： 2. 讨论sig安全联络员的设置魏刚 ---原始邮件--- 发件人: "openEuler conference"<public(a)openeuler.io> 发送时间: 2021年4月27日(周二) 中午11:07 收件人: "cloudnative"<cloudnative(a)openeuler.org>;"dev"<dev(a)openeuler.org>; 主题: [Dev] CloudNative SIG双周例会您好！ openEuler sig-CloudNative SIG 邀请您参加 2021-04-27 16:00 召开的ZOOM会议(自动录制) 会议主题：CloudNative SIG双周例会会议内容：1.各项工作进展同步 2.议题待收集会议链接：https://us06web.zoom.us/j/87445971925?pwd=bDNJVVdFb1llM29CY21zM1k0Ykx2QT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-04-27 16:00, The subject of the conference is CloudNative SIG双周例会, Summary: 1.各项工作进展同步 2.议题待收集 You can join the meeting at https://us06web.zoom.us/j/87445971925?pwd=bDNJVVdFb1llM29CY21zM1k0Ykx2QT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

2 1

答复: [Buildteam] 对openEuler for risc-v grub2 补丁的添加
by zhangxuzhou 27 Apr '21

27 Apr '21

Hi GUI：很好的工作！看了一下你的pr，包含一个patch，没有对spec文件进行修改； src-openEuler/grub2 用于构建openEuler的软件包，由上游社区发行版+patch组成，你的提交需要确保能够构建成功软件包，然后才能由maintainer/commiter 审核之后合入；建议在本地环境上先将利用src-openEuler/grub2 下的spec文件作出rpm包的过程验证完成再提交pr。另外src-openEuler/grub2 仓中包含300+ 个patch，结构确实有些复杂，已将此邮件转发至dev mailist，还请负责维护grub2 的开发者审视pr，协助完成补丁的合入。十分感谢。 BR Whoisxxx(张旭舟) 发件人: GUI [mailto:2991707448@qq.com] 发送时间: 2021年4月26日 8:40 收件人: buildteam <buildteam(a)openeuler.org> 主题: [Buildteam] 对openEuler for risc-v grub2 补丁的添加 RISC-V SIG的前辈们大家好，我前段时间完成了openEuler kernel 5.12rc riscv的grub2 启动测试，前天完成了稳定版OLK-5.10的测试。仓库地址是：5-GuEe Studio: XBook and GNL forever! (gitee.com)<https://gitee.com/openeuler2020/team-1375238611> 仓库里有非常详细的实现步骤以及补丁。昨天基于最新master分支向src-openEuler/grub2 (gitee.com)<https://gitee.com/src-openeuler/grub2>提交了补丁PR，第一次向OpenEuler社区提交补丁，因此格式可能还不符合OpenEuler社区的要求，欢迎大家使用和提出改进建议。 Hello, RISC-V SIG, I completed the test of grub2 startup for openEuler kernel 5.12rc riscv before, and completed the test of the release version of OLK-5.10 in the day before yesterday. The depository address is: 5-GuEe Studio: XBook and GNL forever! (gitee.com)<https://gitee.com/openeuler2020/team-1375238611> There are some implementation ways and patches in there. I based on the new master branch hand in a patch PR to src-openEuler/grub2 (gitee.com)<https://gitee.com/src-openeuler/grub2> This is my first time to hand in a patch to the OpenEuler community. So my PR's format may not meet the requirements of the OpenEuler community. You are welcome to use the tool and give suggestion.

1 0

CloudNative SIG双周例会
by openEuler conference 27 Apr '21

27 Apr '21

1 0

CloudNative SIG双周例会
by openEuler conference 27 Apr '21

27 Apr '21

1 0

sig-release-management双周例会
by Xuxiaosong 25 Apr '21

25 Apr '21

欢迎大家申报议题。 From: openEuler conference [mailto:public@openeuler.io] Sent: Friday, April 23, 2021 8:16 PM Subject: [Dev] sig-release-management例会您好！ openEuler sig-release-management SIG 邀请您参加 2021-04-28 10:00 召开的ZOOM会议会议主题：sig-release-management例会会议链接：https://us06web.zoom.us/j/88081424194?pwd=UU4vZTZDd3FndnlETHlHTU5BOVh0Zz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference will be held at 2021-04-28 10:00, The subject of the conference is sig-release-management例会, You can join the meeting at https://us06web.zoom.us/j/88081424194?pwd=UU4vZTZDd3FndnlETHlHTU5BOVh0Zz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

2 1

openEuler支持多版本遗留问题讨论
by openEuler conference 25 Apr '21

25 Apr '21

1 0

【会议纪要】RE: [Virt] virt sig例会0423
by Chenqun (kuhn) 24 Apr '21

24 Apr '21

时间：2021年4月23日 14：15 - 15：45 参会人员来自：麒麟、移动、Intel、浪潮、蚂蚁、华为、飞腾等居多公司成员及个人参与者（详见与会人员信息） * 分享了StratoVirt 之 balloon特性技术原理 * 分享了StratoVirt之hydropper测试套 * virt sig组commiter及maintainer运作机制（初稿）： · 社区关键成员（maintainer和commiter）晋升及退出主要从三个维度评判：社区代码贡献度，社区事务参与度，社区成员认同度。 · maintainer晋升条件（同时满足）： · 1、贡献关键组件patch 20+个或最少2个核心组件贡献patch超过5个； · 2、连续参与社区virt sig会议超过2个月； · 3、最少3名关键社区成员（最少2名Maintainer）提名认同； · 4、virt sig组例会同意(关键成员60%赞同）； · commiter晋升条件（同时满足）： · 1、贡献关键组件patch 10+个或最少2个核心组件均有贡献或关键组件ISSUE 20+个； · 2、连续参与社区virt sig会议超过1月； · 3、最少2名关键社区成员（最少1名Maintainer）提名认同； · 4、virt sig组例会同意(关键成员60%赞同）； · maintainer和commiter退出机制（任意条件）： · 1、自愿退出； · 2、超过6个月未参与virt sig会议或超过6个月未贡献patch； · 参与openEuler社区卓越贡献者，可长期担任maintainer不受规则限制，卓越贡献者定义（任意条件）： · 1、核心组件创始者； · 2、核心组件代码贡献超过3000行； · 3、核心组件upstream社区的maintainer； · virt sig组关键组件定义： · stratovirt，qemu，kvm，libvirt，libcareplus, vmtop · virt sig组核心组件定义： · stratovirt, qemu, kvm · 社区主要沟通方式： · 公共需求或问题讨论：virt(a)openeuler.org /release-management(a)openeuler.org · 临时问题或需求：virt sig 微信群 · 各个组件ISSUE讨论： · 各个虚拟化组件ISSUE； · https://gitee.com/openeuler/release-management/issues 与会人员信息： [cid:image001.jpg@01D73879.FA445720] [cid:image002.jpg@01D73879.FA445720] From: openEuler conference via Virt [mailto:virt@openeuler.org] Sent: Wednesday, April 21, 2021 10:38 PM To: dev(a)openeuler.org; virt(a)openeuler.org Subject: [Virt] virt sig例会0423 您好！ openEuler Virt SIG 邀请您参加 2021-04-23 14:15 召开的ZOOM会议(自动录制) 会议主题：virt sig例会0423 会议内容： 1、stratovirt之virtio-balloon技术分享 2、stratovirt之hydropper测试套分享 3、commiter 及maintainer运作机制讨论会议链接：https://us06web.zoom.us/j/82229489518?pwd=enNxc0l6WVoyR1JXRmhCUjdFbDVodz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Virt SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-04-23 14:15, The subject of the conference is virt sig例会0423, Summary: 1、stratovirt之virtio-balloon技术分享 2、stratovirt之hydropper测试套分享 3、commiter 及maintainer运作机制讨论 You can join the meeting at https://us06web.zoom.us/j/82229489518?pwd=enNxc0l6WVoyR1JXRmhCUjdFbDVodz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

sig-release-management例会
by openEuler conference 23 Apr '21

23 Apr '21

1 0

virt sig例会0423
by openEuler conference 21 Apr '21

21 Apr '21

1 0

安全委员会例会
by openEuler conference 21 Apr '21

21 Apr '21

1 0

RaspberryPi例会
by openEuler conference 21 Apr '21

21 Apr '21

2 3

安全委员会例会
by openEuler conference 21 Apr '21

21 Apr '21

1 0

RaspberryPi例会
by openEuler conference 21 Apr '21

21 Apr '21

1 0

RaspberryPi例会
by 方亚芬 21 Apr '21

21 Apr '21

t2 您好！ openEuler sig-RaspberryPi SIG 邀请您参加 2021-04-21 20:00 召开的ZOOM会议会议主题：RaspberryPi例会会议内容：1. openEuler 树莓派镜像更新和测试情况 2. raspi-config 移植到 openEuler 3. openEuler移植到 RK3399 的工作进展会议链接：https://us06web.zoom.us/j/88479573928?pwd=RzJCbm5kNjkySVh3T21XTlg2QmpVUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-RaspberryPi SIG invites you to attend the ZOOM conference will be held at 2021-04-21 20:00, The subject of the conference is RaspberryPi例会, Summary: 1. openEuler 树莓派镜像更新和测试情况 2. raspi-config 移植到 openEuler 3. openEuler 移植到 RK3399 的工作进展 You can join the meeting at https://us06web.zoom.us/j/88479573928?pwd=RzJCbm5kNjkySVh3T21XTlg2QmpVUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

virt sig例会
by openEuler conference 21 Apr '21

21 Apr '21

1 0

sig-bio双周例会
by openEuler conference 21 Apr '21

21 Apr '21

3 4

Re: 【月度update补发】openEuler 20.03 LTS SP1 Update 2021/4/10 release评审通知
by xiasenlin 20 Apr '21

20 Apr '21

openEuler 20.03 LTS SP1 Update 2021/4/10 release issue地址更新： https://gitee.com/openeuler/release-management/issues/I3N2HA?from=project-i… From: xiasenlin Sent: Tuesday, April 20, 2021 3:33 PM To: 'tc(a)openeuler.org' <tc(a)openeuler.org>; 'release(a)openeuler.org' <release(a)openeuler.org>; 'qa(a)openeuler.org' <qa(a)openeuler.org>; 'sa-announce(a)openeuler.org' <sa-announce(a)openeuler.org>; 'dev(a)openeuler.org' <dev(a)openeuler.org> Cc: Jiangzhenhua (Ronnie, Kunpeng Computing) <zhenhua.jiang(a)huawei.com>; Guoge(JVM) <ge.guo(a)huawei.com>; chenyaqiang <chenyaqiang(a)huawei.com>; liyongqiang (H) <liyongqiang10(a)huawei.com>; Chenzhendong (alex) <alex.chen(a)huawei.com>; Liyiting <liyiting(a)huawei.com>; Mingpei <mingpei(a)huawei.com>; Xuxiaosong <xuxiaosong(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com>; Yanxiaobing <yanxiaobing(a)huawei.com>; Liujingang (Bob) <liujingang09(a)huawei.com>; fanjiachen (A) <fanjiachen3(a)huawei.com>; guoxiaoqi <guoxiaoqi2(a)huawei.com> Subject: 【月度update补发】openEuler 20.03 LTS SP1 Update 2021/4/10 release评审通知 openEuler 20.03 LTS SP1 Update 20210410 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年4月20日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I393RJ?from=project-i… 版本目标：CVE、软件包引入升级和Bugfix修复版本计划：例行CVE冻结（本次为月度补发版本）：20210410 代码冻结： 20210410 转测试时间：20210413 版本发布： 20210420 本次更新主要涉及：anaconda、grub2、golang等本次新增特性主要涉及： digest-list-tools i40e iavf lwip python-invoke watchdog hadoop hadoop-3.1 python-pycdlib 修复cve：8个修复bug：12个 SP1：发布源码包：42个； arm二进制包188个; x86二进制包205个； CVE清单： CVE score CVE-2020-25632 7.5 CVE-2020-25647 7.6 CVE-2020-27749 7.5 CVE-2021-20225 7.5 CVE-2021-20233 7.5 CVE-2020-27779 7.5 CVE-2020-14372 7.5 CVE-2021-3449 5.9 bugfix清单： 1、anaconda https://e.gitee.com/open_euler/repos/src-openeuler/netty/pulls/21?issue=I3B… https://gitee.com/src-openeuler/anaconda/pulls/84 2、grub2 修复高分CVE与回合社区补丁 #I38CMV:从 20.03-LTS 升级到 20.03-LTS-SP1，导致启动失败<https://gitee.com/open_euler/dashboard?issue_id=I38CMV>?from=project-issue 3、firewalld #I38VCX:LTS版本 firewalld运行依赖kernel, 影响systemd编译效率，firewalld需要优化安装依赖<https://gitee.com/open_euler/dashboard?issue_id=I38VCX>?from=project-issue 4、其他issue I3B5TJ I3AZ9M I3AZBJ I3AZOR I3AZR4 I3B0LV I3B1KE I3B1MQ I3B1O5 I3B5FS I3B5GY I3B5I2 涉及软件仓清单： anaconda apr-util assimp bcc courier-unicode dejavu-fonts digest-list-tools firewalld golang grub2 gstreamer1 gtk2 i40e iavf isula-build kata_integration kata-containers libimagequant libnotify lwip maildrop mesa mutt obs-bundled-gems openEuler-latest-release openjfx11 openjfx8 openssl proftpd python-dns python-invoke python-munch python-paramiko rhash syscontainer-tools syslinux tzdata watchdog hadoop hadoop-3.1 lorax python-pycdlib

1 0

【议题申报】TC双周例会
by xiasenlin 20 Apr '21

20 Apr '21

议题申报 3）openEuler支持多版本软件包方案及分支命名规范变更说明为了支持openEuler集成多版本软件包，我们在前期调研了红帽系的appstream概念，并为之设计了大体方案。后面在吴峰光大牛的建议下，又分析了debian/Ubuntu的支持多版本的做法，特别是其中对于soname的约束以及多repo的形式，更加符合openEuler当前构建和发布的状态，因此我们又设计了新的方案。相比appstream，新方案大大弱化对OBS构建系统的改造要求，但是对社区开发者有一些新的规则需要遵守申报人：夏森林发件人: Jiangzhenhua (Ronnie, Kunpeng Computing) [mailto:zhenhua.jiang@huawei.com] 发送时间: 2021年4月19日 11:33 收件人: tc(a)openeuler.org<mailto:tc@openeuler.org>; dev(a)openeuler.org<mailto:dev@openeuler.org>; release(a)openeuler.org<mailto:release@openeuler.org> 主题: [Dev] TC双周例会欢迎大家申报议题。 Best Regards Ronnie Jiang 姜振华华为鲲鹏计算产品部 Mobile: 17052280688 E-mail: zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com> 杭州市滨江区江虹路410号华为杭州研发中心 Z4-2-B Z4-2-B, NO.410,Jianghong Road,Binjiang District, Hangzhou 310052,P.R.China www.huawei.com<../../../../../z00124665/Desktop/enterprise.huawei.com> 发件人: openEuler conference [mailto:public@openeuler.io] 发送时间: 2021年4月19日 11:28 主题: [Dev] TC双周例会您好！ openEuler TC SIG 邀请您参加 2021-04-21 10:00 召开的ZOOM会议(自动录制) 会议主题：TC双周例会会议链接：https://us06web.zoom.us/j/84944088720?pwd=ZmIxd0tyenZheVlZVE90WXFjTmdqUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-04-21 10:00, The subject of the conference is TC双周例会, You can join the meeting at https://us06web.zoom.us/j/84944088720?pwd=ZmIxd0tyenZheVlZVE90WXFjTmdqUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

3 2

QA-sig双周例会
by openEuler conference 20 Apr '21

20 Apr '21

1 0

TC双周例会
by openEuler conference 20 Apr '21

20 Apr '21

3 2

How to support OpenStack old versions？
by Tianhua huang 19 Apr '21

19 Apr '21

基于厂商诉求和OpenStack SIG PTG的讨论结论，结合openEuler当前多版本支持能力现状，OpenStack SIG计划在openEuler-20.03-LTS-SP2版本优先支持OpenStack的R版本，在后续SP版本中补齐OpenStack Q/S/T版本，但是OpenStack在T版本之前只支持python2，这就意味着支持OpenStack的R、Q、S等老版本需要在openEuler-20.03里面引入python2的软件包，请问社区对于在20.03-LTS-SP2/SP3版本中引入新的python2软件包的策略是什么？OpenStack SIG组希望将OpenStack的R版本软件包引入到openEuler-20.03-LTS-SP2的EPOL，策略上是否可行？谢谢大家！ =========================================================== Based on vendor requirements,OpenStack SIG PTG discussion conclusions, and current support capabilities of OpenEuler multiple versions, OpenStack SIG plans to preferentially support OpenStack R version in openEuler-20.03-LTS-SP2. OpenStack Q/S/T will be supplemented in later SP versions. However, OpenStack earlier than T supports only python2. This means that the python2 software packages need to be introduced to openEuler-20.03 for R, Q, and S. What is the community's strategy for introducing the new python2 software packages in 20.03-LTS-SP2/SP3? The OpenStack SIG team hopes to introduce the OpenStack R version to the openEuler-20.03-LTS-SP2 EPOL. Is it feasible? Thank you.

3 2

[OpenStack-SIG] OpenStack openEuler 上下游软件包版本比对面板
by Rui Chen 19 Apr '21

19 Apr '21

SIG的朋友们大家好，我们平时在SIG组的工作中需要对大量的OpenStack软件包和依赖包进行构建和验证，OpenStack社区上游发布的软件包就有200多个[1]，引入openEuler时需要的关联构建依赖和运行依赖就更多了，相信大家在检查软件包版本的时候都花费了不少精力和时间。我做了一个小工具可以对比OpenStack上游软件包和openEuler软件仓库中的软件包版本，可以在线查看 https://kiwik.github.io/os-version-checker/ ，支持PC和移动端，是基于Debian OpenStack team的开源工具os-version-checker开发的，并在github上开源[3]，工具使用github action的cron job，每天早上生成最新数据，与 OpenStack软件包的版本差异会用不同颜色表示，欢迎大家使用和提出改进建议。 Hello, SIG friends, we need to build and verify a large number of OpenStack software packages and dependency packages in the SIG team. The OpenStack community has more than 200 software packages in one release [1]. When we build openEuler packages, there are more associated build dependencies and running dependencies. I believe you should spend a lot of effort and time checking the software package version. I have made a tool to compare the OpenStack upstream packages with the packages version in the OpenEuler software repository. You can view https://kiwik.github.io/os-version-checker/ online. It supports PC and mobile devices. It is developed based on the open-source tool os-version-checker of the Debian OpenStack team. My tool os-version-checker for openEuler is hosted in Github [3] and open source again. The tool uses the cron job of Github action to generate the latest data every morning. The version differences between the tool and the OpenStack software package are displayed in different colors. You are welcome to use the tool and give suggestion. [1]: https://releases.openstack.org/wallaby/index.html [2]: https://kiwik.github.io/os-version-checker/ [3]: https://github.com/kiwik/os-version-checker

2 1

openEuler kernel Meetup 4月9号北京站圆满结束
by Xie XiuQi 17 Apr '21

17 Apr '21

openEuler kernel Meetup 4月9号北京站圆满结束 openEuler kernel SIG组于2021年4月9日在北京成功举办了kernel meetup。本次活动云集了来自华为、麒麟、PingCAP、申威、飞腾、万里红、armChina、兆芯、美团、复旦的行业领袖、业界资深专家、高校教授、社区maintainer、开发者，吸引了现场30人+，线上约300人参与。会上就内核技术、SIG组后续运作规划进行了充分研讨，收集了各厂商的诉求并进行答疑，对SIG组后续的工作开展和技术合作有着重大意义。来自麒麟软件的孙立明老师，对ARM64 KVM 虚拟化架构做了介绍，增进了大家对ARM64 架构虚拟化的理解。麒麟软件的郭皓老师提出了openEuler kernel 支持PREEMPT_RT 的想法和思路。期待openEuler 具备更高的实时性，促进其在嵌入式领域的应用。孙立明老师郭皓老师来自兆芯的张伟老师，对兆芯CPU的演进、特性，以及兆芯补丁合入openEuler kernel 的过程做了介绍。目前兆芯的补丁已经合入openEuler 4.19 内核，预计6 月底发布的 openEuler 20.03 LTS SP2 将支持兆芯CPU。兆芯与openEuler社区的紧密合作促成了 openEuler 对兆芯CPU的快速支持，张伟老师对此表示了称赞。张伟老师来自申威的崔巍老师就处理器接口、虚拟化支持、安全增强等话题与飞腾、兆芯专家进行了现场交流，并表达了积极参与openEuler 的愿望，期待openEuler 尽快支持申威全自主指令集架构，促进openEuler社区和申威生态的共同繁荣。崔巍老师来自华为的缪勰介绍了华为针对SCM介质研发的文件系统。该文件系统的原理基于华为OS内核实验室主任陈海波老师的论文Soft Updates Made Simple and Fast on Non-volatile Memory <https://www.usenix.org/system/files/conference/atc17/atc17-dong.pdf> 采用软更新（soft-update) 提供一致性保证，采用哈希表目录结构，消除循环依赖，提供的字节级读写能力显著降低了SoupFS的复杂性等技术。性能相比业界其他SCM 文件系统有显著的提升。来自华为的杨基鸿，介绍了性能调优的常用方法、工具和思路，并通过实际案例讲解工具的应用及性能分析的思路。线上与会同学表达了对TOP-down性能分析工具的强烈兴趣，我们后续会通过专题分享介绍更多技术细节。杨基鸿来自复旦大学计算机学院的张亮教授，针对如何推动高校参与openEuler提出了建设性意见，我们后续也会持续开展面向高校的交流合作活动。张亮教授 openEuler kernel SIG 的Maintainer 谢秀奇介绍了kernel SIG一年多以来的进展以及后续的运作、规划等。与会专家老师进行了充分的研讨，提出了在kernel SIG 建立committer 机制的想法，以Committer 为核心对openEuler 内核进行规划、开发和治理。谢秀奇本次meetup的成功举办，对kernel SIG的后续工作和发展有重大意义。期待各厂商、各单位、各开发者在openEuler 开源社区这个大平台下，共建、共享、共治，让 openEuler kernel走进千行百业，成为信息产业的基石。 openEuler kernel SIG openEuler kernel 源代码仓库： https://gitee.com/openeuler/kernel 欢迎大家多多star、fork，多多参与社区开发，多多贡献补丁。关于贡献补丁请参考：如何参与 openEuler 内核开发 <https://mp.weixin.qq.com/s/a42a5VfayFeJgWitqbI8Qw> openEuler kernel SIG 微信技术交流群请扫描下方二维码添加小助手微信，备注“交流群”或“技术交流”，加入 openEuler kernel SIG 技术交流群。

1 0

Compiler SIG双周例会&技术分享
by openEuler conference 17 Apr '21

17 Apr '21

2 1

OS-Builder例会
by openEuler conference 17 Apr '21

17 Apr '21

2 1

openEuler in WSL by Wang Haitao
by 海涛 16 Apr '21

16 Apr '21

Hello guys, I am a new intern in Huawei OpenEuler, my name is Wang Haitao I can use openEuler in WSL in my computer now. Here is my gitee repo, I store everthing in here https://gitee.com/ouyanghaitao/open-euler-in-wsl I have tryed two ways: 1. import openEuler docker image in wsl, so I can start it from wsl command shell. 2. develop a WSL launcher project, so I can start openEuler on the windows start menu. I will share my dev doc, written in Chinese and English. you can see it in my email or gitee repo. If you can follow my document, try to start OpenEuler in WSL, and put forward some issues, I would be very grateful! ======================= 大家好呀, 我是华为openEuler下刚来的实习生，我叫王海涛我现在可以在我的计算机上使用openEuler的WSL。这是我的gitee repo，我帮相关的东西都放这里了 https://gitee.com/ouyanghaitao/open-euler-in-wsl 我尝试了两种方法: 1. 在wsl中导入openEuler docker映像，这样我就可以从wsl命令shell启动它。 2. 开发一个WSL启动程序项目，这样我就可以在windows开始菜单上启动openEuler。我将分享我的中英文开发文档。你可以在我的邮件或gitee repo中看到它。如果你能跟着我的文档，尝试在WSL中启动启动openEuler，并提一些issue，我会感激不尽的！

3 4

【Meeting Notice】openEuler kernel 技术分享第三期 & 双周例会 Time: 2021-04-16 14:00-18:00
by Meeting Book 16 Apr '21

16 Apr '21

1 0

kibana的日志查看/生命周期管理
by openEuler conference 15 Apr '21

15 Apr '21

1 0

双周例会
by openEuler conference 14 Apr '21

14 Apr '21

1 0

双周例会
by openEuler conference 14 Apr '21

14 Apr '21

1 0

请阅【sig-release-management 例会会议纪要_20210414】//sig-release-management 例会，欢迎申报议题，欢迎与会
by Jiangzhenhua (Ronnie, Kunpeng Computing) 14 Apr '21

14 Apr '21

轮值主持人：姜振华下次主持人：许小松与会人：jiangzhenhua、hufeng、zhuyanpeng、chenyaqiang、liyongqiang、xuxiaosong、程鑫鑫、CL-iphone、麒麟软件-白光磊、赵鹏辉、Kouwq、qingzheng、麒麟软件-崔雷、刘金刚、颜小兵、dolphin-M、kouwenqi、杨晓东、李永强、kongzizaixian、麒麟软件-杨昭、麒麟软件-郭建兴、罗飞、潘晨博、wangxiaojun、麒麟软件-王子亮、Erik Yuan、詹年科、统信-叶青龙、沙文娜、侯健、csj、张鹏会议时间：2021年4月14日 10:00－12:00 会议地点：sig电话会议议题一：为openEuler社区部署开源片段引用扫描工具SCANOSS 议题责任人：颜小兵议题背景：为openEuler社区部署开源片段引用扫描工具SCANOSS，计划在两个场景下使用：1）提交PR时，在门禁中集成该扫描；2）版本发布前，进行全量扫描；对于版本发布前全量扫描这个场景，合规SIG例会讨论后，建议到 release-SIG 组会议上讨论明确一下必要性。议题结论： 1、同意将SCANOSS引入openEuler社区； 2、考虑到SCANOSS的使用率还不是很高，可能存在误报率和使用体验上的问题，建议先定两个SIG组做试点，不做强制项，只做建议参考； 3、openEuler社区基础设施需要支持 “扫描出问题，自动提issue给Compliance SIG组的特性” ，由Compliance SIG组管理issue，并依此优化和监控SCANOSS的准确性和体验，待时机成熟，再决策是否将SCANOSS在社区正式 “转正” ； 4、openEuler社区基础设施要开放扫描接口，方便开发者在开发阶段就可以快速识别是否存在合规性问题，而不是等到提交PR时，通过门禁才发现有大量问题需要整改；议题二：关于软件生态的若干问题：议题责任人：潘晨博议题背景：目前操作系统软件生态已经成为一个很关键的要素，尤其对于openEuler这种新版本来说，软件生态尤为重要。从目前的openEuler版本发布来看，都是通过上报特性的方式来决定版本的发布内容，因此有如下三个问题： 1、讨论下openEuler对各个软件领域生态扩充计划，包括且不限于数据库，中间件，人工智能，大数据，高可用等方面？ 2、对于软件生态最迫切的应该是LTS分支，OSV基本都是基于该分支的，因此开源软件生态第一优先级是否考虑在LTS版本？后续的LTS SP版本是否规划更多的软件生态丰富？ 3、对于appstream的支持已经有oemodule来支持，那么对于开发工具集，是否考虑引入redaht的scl+Developer Toolset方案？议题结论： 1、openEuler社区高度重视生态的发展，会持续完善南北向生态。在软件领域生态方面，openEuler今年主动规划新增引入2800+软件包，覆盖了主流的企业应用场景，包括与OSV对齐的软件，以及数据库、大数据、分布式存储、虚拟化&云、WEB主流的水平场景的主流多版本。其他软件支持，case by case的解决； 2、这些软件包的引入不仅仅是引入到Master分支，而是会直接纳入到LTS/SP版本； 3、scl+Developer Toolset是一个很不错的选择，会后胡峰针对该方案做详细分析，并提供引入建议，在下次例会上讨论；议题三：openEuler 20.03 LTS SP2版本计划议题责任人：胡峰议题结论： 1、本议题介绍了openEuler 20.03 LTS SP2版本的整体计划，和关键特性需求； 2、需求冻结日期，是一个牵引日期，建议各SIG组按照该计划执行，如有个别需求没有赶得上提的，可以case by case的审视；议题四：openEuler社区版本生命周期介绍议题责任人：姜振华议题结论： 1、会上针对openEuler社区版本的生命周期做了交流与讨论，具体生命周期建议如下，会上与会人员未提出其他方案建议： a、20.03 LTS、22.03 LTS 生命周期一年； b、20.03 LTS SP1、22.03 LTS SP2 生命周期两年； c、20.03 LTS SP3、22.03 LTS SP4到LTS生命周期结束； d、20.03 LTS SP2、22.03 LTS SP1、22.03 LTS SP3生命周期9个月（6+3）； e、创新版本生命周期6个月，轻量级维护。遗留问题：序号遗留问题描述完成时间责任人 1 openEuler社区基础设施需要支持如下特性： 1、扫描出问题，自动提issue给Compliance SIG组；2、开放扫描接口，方便开发者在开发阶段就可以快速识别是否存在合规性问题 TBD（待与基础设施团队分析讨论工作量）颜小兵 2 scl+Developer Toolset是一个很不错的选择，会后胡峰针对该方案做详细分析，并提供引入建议，在下次例会上讨论； 2021.04.28 胡峰 Best Regards Ronnie Jiang 姜振华华为鲲鹏计算产品部 Mobile: 17052280688 E-mail: zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com> 杭州市滨江区江虹路410号华为杭州研发中心 Z4-2-B Z4-2-B, NO.410,Jianghong Road,Binjiang District, Hangzhou 310052,P.R.China www.huawei.com<../../../../../z00124665/Desktop/enterprise.huawei.com> 发件人: Jiangzhenhua (Ronnie, Kunpeng Computing) [mailto:zhenhua.jiang@huawei.com] 发送时间: 2021年4月13日 14:23 收件人: dev(a)openeuler.org; tc(a)openeuler.org; release(a)openeuler.org 主题: [Dev] sig-release-management 例会，欢迎申报议题，欢迎与会 Best Regards Ronnie Jiang 姜振华您好！ openEuler sig-release-management SIG 邀请您参加 2021-04-14 10:00 召开的ZOOM会议会议主题：sig-release-management 例会会议链接：https://us06web.zoom.us/j/86389194548?pwd=NGNIZTZzcnZwQjkraEZYVlVvcXVjdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference will be held at 2021-04-14 10:00, The subject of the conference is sig-release-management 例会, You can join the meeting at https://us06web.zoom.us/j/86389194548?pwd=NGNIZTZzcnZwQjkraEZYVlVvcXVjdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

sig-release-management 例会，欢迎申报议题，欢迎与会
by Jiangzhenhua (Ronnie, Kunpeng Computing) 14 Apr '21

14 Apr '21

Best Regards Ronnie Jiang 姜振华您好！ openEuler sig-release-management SIG 邀请您参加 2021-04-14 10:00 召开的ZOOM会议会议主题：sig-release-management 例会会议链接：https://us06web.zoom.us/j/86389194548?pwd=NGNIZTZzcnZwQjkraEZYVlVvcXVjdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference will be held at 2021-04-14 10:00, The subject of the conference is sig-release-management 例会, You can join the meeting at https://us06web.zoom.us/j/86389194548?pwd=NGNIZTZzcnZwQjkraEZYVlVvcXVjdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

4 4

Re: 咨询 openeuler 的 ceph sig 的微信群
by Liyongle (Fred) 14 Apr '21

14 Apr '21

Hi Ceph SIG team Please help this engineer to join Ceph. Thanks in advance. Fred 李永乐 From: shao [mailto:shaoll_xt@teamsun.com.cn] Sent: Wednesday, April 14, 2021 9:25 AM To: dev(a)openeuler.org Subject: 咨询 openeuler 的 ceph sig 的微信群您好，我是一名 Ceph 爱好者，开发者，希望跟进基于Ceph项目丰富openeuler生态圈，请问我怎么才能加入ceph sig 的微信群，方便我及时了解动态和参加会议。 ________________________________ 邵丽拉 Shao Lila 研发工程师华胜天成集团云计算事业部 R & D Engineer Teamsun Group Cloud Computing Department Mobile：18810583260 E-mail：shaoll_xt(a)teamsun.com.cn<mailto:shaoll_xt@teamsun.com.cn> Web：www.teamsun.com.cn<http://www.teamsun.com.cn> 北京市海淀区西北旺西路软件园二期华胜天成科研大楼 No.23 Building,10 East Block XiBeiWang East Road,HaiDian District,Beijing [cid:image001.png@01D73111.32B2E970] 本邮件（包括任何附件）包含机密信息，并受法律保护。此信息意在使收件人明确以下内容：如果您并非该收件人或错收此邮件，请联系发件人并退还此邮件，请不要向任何人泄露邮件内容，请立即删除所有邮件及其附件。严禁任何使用，传播或复制此邮件的行为，这些行为可能违反法律。The information (including any attachments) contained in this e-mail is confidential and may be legally privileged . The message is intended solely for the addressee(s). If this e-mail is not originally intended for you, or received by you in error,please contact the sender by return e-mail and do not disclose its content to anyone and destroy all copies of the original message immediately. If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful.

1 0

gatekeeper双周例会
by openEuler conference 13 Apr '21

13 Apr '21

1 0

sig-release-management 例会
by openEuler conference 13 Apr '21

13 Apr '21

1 0

DB SIG Bi-weekly meeting
by openEuler conference 13 Apr '21

13 Apr '21

1 0

Summary of OpenStack SIG PTG
by Tianhua huang 12 Apr '21

12 Apr '21

大家好， openEuler OpenStack SIG组于2021.4.10在北京成功举办了PTG（Project Team Gathering，意为开发者见面会，从OpenStack社区的PTG继承而来）开发者会议，就OpenStack SIG组的运作和规划进行了充分的讨论，也收集了到场各厂商包括联通数科、中国电信、天津卓朗科技、华胜天成、烽火通信、浪潮、统信软件、Intel、中软、Linaro、Arm、同方有云、EasyStack、建信金融科技、九州云、赛迪对openEuler&OpenStack的需求，对SIG组后续的工作非常有指导意义。 PTG会议总结：运作规范： 1. 秉承OpenStack社区4个Open的原则，SIG组规范开源运作方式： - 使用邮件列表openstack(a)openeuler.xn--orgsig,-sr4kq2g500ad3v8wimzpl4d544a2z2d014bjjap52ozel - 周三下午15:00点举行SIG组双周例会，议题申报和会议纪要使用etherpad： https://etherpad.openeuler.org/p/sig-openstack-meetings - 微信群'openEuler sig-openstack'作为日常问题讨论平台 2. 以官方releases.openstack.org为标准，选取最新openstack组件版。 3. 参考openEuler RPM规范，输出OpenStack相关RPM spec模板（比如格式要求，是否需要加UT测试内容等）。 4. 在openEuler社区中建立OpenStack SIG统一入口仓库，集中issue收集，关闭各子项目issue功能。刷新相关Doc说明。 *技术讨论：* 1. 由Linaro、华为牵头，在OpenStack社区推动openEuler 20.03 LTS的ARM CI支持。涉及项目包含DevStack、diskimage-builder、system-config等。并从社区沟通层面，在4月19的OpenStack PTG中，与QA、Infra团队积极交流，获取积极反馈。 2. 在openEuler社区推动20.03LTS SP2中Libvirt/QEMU软件包的版本升级，满足OpenStack的依赖要求。 3. 通过公开投票，将在openEuler 20.03 LTS SP2中优先支持OpenStack的R版本，后续openEuler多版本能力实现后，补齐OpenStack Q/R/S/T多版本支持。 4. 建立OpenStack在openEuler LTS版本升级的路径，支持OpenStack 1个版本重叠。考虑到OpenStack T之前的版本支持python2，T及之后的版本支持python3，暂定OpenStack T版本作为openEuler 20.03 LTS到openEuler 22.03 LTS的重叠版本。 *需求收集：* 1. 希望引入更多OpenStack服务，包括：Kolla、Octavia、Cyborg、Trove。 2. 希望引入更多OpenStack测试场景，包括： Neutron OVN、OpenvSwitch、LinuxBridge、Ceph以及X86+ARM64混合架构。 3. 希望提供Packstack、OpenStack-Ansible等类似工具，以yum源安装方式，快速部署OpenStack。 *SIG组未来规划：* 1. 吸引更多开发者、厂商参与openEuler OpenStack社区工作。积极收集更多用户、厂商诉求。规划下一次PTG举办时间/地点。 2. 2021年Q2聚焦OpenStack R版在openEuler 20.03 LTS SP2的支持工作。在多版本支持的前提下，再引入OpenStack Q/S/T版本。 3. 2021年Q3聚焦openEuler 21.09创新版本支持OpenStack W版本工作，挑战在openEuler 21.09中支持OpenStack X版本。 4. 2021年Q4完成22.03 LTS OpenStack适配先期调研工作，聚焦openEuler 20.03 LTS SP3 OpenStack更多版本支持。 =================================================================================================================== Hi all, The openEuler OpenStack SIG successfully held the PTG (Project Team Gathering is inherited from the PTG of the OpenStack community) conference at Beijing on April 10, 2021. We fully discussed the operation specifications and planning of the OpenStack SIG team, and collected information from vendors including Wo Cloud, China Telecom, Troila Technology, TEAMSUN, FiberHome, Inspur, UnionTech Software Technology, Intel, ChinaSoft International, Linaro, Arm, TFCloud, EasyStack, CCB Fintech, 99Cloud and CCID TECHNICAL INNOVATION's requirements for OpenEuler&OpenStack. It is very instructive for the follow-up work of the SIG team. Meeting summary: *Operation specifications* 1. Adhering to the four open principles of the OpenStack community, the SIG team standardizes the open-source operation mode. - Use the mailing list openstack(a)openeuler.org to discuss SIG group technical issues for archiving and backtracking. - Hold the bi-weekly meeting of the SIG team at 15:00 on Wednesday. Use etherpad https://etherpad.openeuler.org/p/sig-openstack-meetings for topic collecting and meeting minutes. - WeChat group 'openEuler sig-openstack' as a platform for daily discussion. 2. Select the latest OpenStack component version based on https://releases.openstack.org/ 3. Output OpenStack RPM spec templates based on the OpenEuler RPM specifications. For example, format requirements and whether to add UT test content. 4. Establish a unified portal repository for OpenStack SIG in the openEuler community, collect issues in a centralized manner, and disable the issue function of each sub-project. To update the description of related Docs. *Technical Discussion* 1. Linaro and Huawei take the lead to promote ARM CI support for openEuler 20.03 LTS in the OpenStack community. Involved projects include DevStack, Diskimage-builder, and system-config. In the OpenStack PTG on April 19, we'll actively communicate with QA and Infra teams to obtain positive feedback. 2. Promote the version upgrade of the Libvirt/QEMU software package of 20.03 LTS SP2 in the openEuler community to meet the dependency requirements of OpenStack. 3. After public voting, openEuler 20.03 LTS SP2 will preferentially support the R version of OpenStack. After the multi-version capability of openEuler is supplemented, the Q, R, S, and T versions of OpenStack will be supported. 4. Establish an upgrade path for OpenStack in openEuler LTS and allow one version of OpenStack to overlap. Considering that OpenStack versions earlier than T support python2 and OpenStack T and later versions support python3, we selected OpenStack T as the overlapping version from openEuler 20.03 LTS to openEuler 22.03 LTS. *Requirements collection* 1. More OpenStack services are expected to be introduced, including Kolla, Octavia, Cyborg, and Trove. 2. More OpenStack test scenarios are expected, including Neutron OVN, OpenvSwitch, LinuxBridge, Ceph, and x86+ARM64 hybrid architecture. 3. Hope to provide tools such as Packstack and OpenStack-Ansible to quickly deploy OpenStack using yum source installation. *Future Plan* 1. Attract more developers and vendors to participate in the openEuler OpenStack community. Actively collect more requirements from users and vendors. Plan the time/location of the next PTG. 2. In 2021 Q2, SIG will focus on supporting OpenStack Rocky release on openEuler 20.03 LTS SP2. OpenStack Q, S, and T versions will be introduced when multiple versions feature are supported in openEuler community. 3. In 2021 Q3, SIG will focus on supporting OpenStack Wallaby release on openEuler 21.09, and will try our best to add OpenStack Xena release support as well. 4. In 2021 Q4, SIG will first complete the preliminary survey about OpenStack on openEuler 22.03 LTS. And then focus on openEuler 20.03 LTS SP3 stuff.

3 2

OpenStack SIG 例会
by openEuler conference 12 Apr '21

12 Apr '21

1 0

sig-Compliance双周会
by openEuler conference 12 Apr '21

12 Apr '21

1 0

Re: [Community] Re: [Infra] Jira 服务使用推荐
by George 12 Apr '21

12 Apr '21

Hi Fred, Thank you for your attention. I'll try to answer the two questions : 1. Currently, Infra-sg is preparing an SSO system. After the system is released, the account communication between multiple systems can be resolved, including Gitee, Jira, and Bugzilla. 2. After the first issue above is successfully resolved, the Issue and PR link functions need to be developed. Our preliminary judgment is that it can be achieved.     This requirement also exists in the bugzilla system. So we want to choose a better system from Bugzilla and Jira to develop and make it available to you. Best regards George ------------------ 原始邮件 ------------------ 发件人: "Liyongle (Fred)" <liyongle(a)huawei.com>; 发送时间: 2021年4月9日(星期五) 上午10:21 收件人: "George"<caozhi1214(a)qq.com>;"infra(a)openeuler.org"<infra(a)openeuler.org>;"dev"<dev(a)openeuler.org>;"community(a)openeuler.org"<community(a)openeuler.org>;"tc(a)openeuler.org"<tc(a)openeuler.org>; 主题: [Community] Re: [Infra] Jira 服务使用推荐 Hi George,   English email could help more. Thanks.   May I have a couple of questions?   1. Is there a solution to link the accounts between Jira and Gitee? I am wondering whether I can identify the same gay in Jira who I know in openEuler Gitee.   2. Is there a way to link the issues and PRs in Gitee with the items in Jira? I am afraid that I will have to re-create the items in Jira which already exist in openEuler Gitee.     Fred 李永乐   From: George [mailto:caozhi1214@qq.com] Sent: Wednesday, April 7, 2021 4:13 PM To: Meeting&nbsp;Book&nbsp;via&nbsp;Infra <infra(a)openeuler.org>; dev <dev(a)openeuler.org>; community(a)openeuler.org; tc(a)openeuler.org Subject: [Infra] Jira 服务使用推荐   Hi，我是openEuler社区Infra Sig组maintainer，我们Sig组近期以社区名义向Atlassian申请了Jira的免费账号。如果您以前使用过Jira做任务管理或对Jira感兴趣，现在可以申请免费使用Jira来管理openEuler社区事务啦。您只需要提供Jira账号的邮箱地址给我们，由我们将您加入openEuler团队，即可使用。 Jira 对事务跟踪、事务分析、统计、生成报告等方面都有很好的支撑。   您可以通过 infra(a)openeuler.org 或 caozhi1214(a)qq.com 告知我们您的邮箱地址。       附 Jira账号注册： 1. 进入Jira官网：https://www.atlassian.com/zh/software/jira 2. 通过右上角【My account】—》【login】     3. 如果已有账户可直接登录，如果无账号可以登录页面找到【Sign up】进入注册页面：         4. 注册后Jira会发验证邮件，到相应邮箱下 verify your email 即可完成。            

1 0

sig-confidential-computing双周例会
by openEuler conference 11 Apr '21

11 Apr '21

1 0

Jira 服务使用推荐
by George 09 Apr '21

09 Apr '21

Hi，我是openEuler社区Infra Sig组maintainer，我们Sig组近期以社区名义向Atlassian申请了Jira的免费账号。如果您以前使用过Jira做任务管理或对Jira感兴趣，现在可以申请免费使用Jira来管理openEuler社区事务啦。您只需要提供Jira账号的邮箱地址给我们，由我们将您加入openEuler团队，即可使用。 Jira 对事务跟踪、事务分析、统计、生成报告等方面都有很好的支撑。您可以通过 infra(a)openeuler.org 或 caozhi1214(a)qq.com 告知我们您的邮箱地址。附 Jira账号注册： 1. 进入Jira官网：https://www.atlassian.com/zh/software/jira 2. 通过右上角【My account】—》【login】     3. 如果已有账户可直接登录，如果无账号可以登录页面找到【Sign up】进入注册页面：       4. 注册后Jira会发验证邮件，到相应邮箱下 verify your email 即可完成。          

2 1

[DB SIG] The first launch up of DB SIG
by bo zhaobo 08 Apr '21

08 Apr '21

Hi DB SIG members，为了方便大家能够查阅和后续任务认领及分配。准备了几个大家平时主要用的etherpad，如果错过SIG例会，我们也会在这里同步进展。 1. SIG介绍及路标 https://etherpad.openeuler.org/p/DB-SIG 2. SIG当前工作，关乎PR，issue以及求助信息等等 https://etherpad.openeuler.org/p/DB-SIG-worklist 3. SIG组织内部事务及投票等等 https://etherpad.openeuler.org/p/DB-SIG-inside 期望大家尽快确认DB SIG例会时间，咱们好安排后续会议，多谢。同时，期望在dev maillist里面的关注DB的同学同样能够参与DB SIG，共同繁荣openEuler DB生态。 ================================================================== Hi DB SIG members, In order to ease for everyone to consult and follow-up task claim and allocation.We have prepared several etherpads that we mainly use at ordinary times. If we miss the regular meeting of SIG, we will also keep up with the progress here. 1. SIG introduction and roadmap https://etherpad.openeuler.org/p/DB-SIG 2. Current jobs of SIG, PRs, issues, help requests, etc https://etherpad.openeuler.org/p/DB-SIG-worklist 3. SIG organizes internal affairs and votes, etc https://etherpad.openeuler.org/p/DB-SIG-inside We hope you can confirm the regular meeting time of DB SIG as soon as possible, so that we can schdule the follow-up meeting. Thank you. At the same time, the people who pay attention to DB in Dev Maillist can also participate in DB Sig and prosper the Openeuler DB ecology together. BR, Bo Zhao [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> 04/08/21, 08:56:54 PM

1 0

【月度例行update】openEuler 20.03 LTS SP1 Update 2021/3/31 release评审再次通知
by xiasenlin 07 Apr '21

07 Apr '21

openEuler 20.03 LTS SP1 Update 20210331 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年4月9日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I3EUQF?from=project-i… 版本目标：CVE、大数据多版本软件包特性和Bugfix修复版本计划：例行CVE冻结（本次为月度例行版本）：20210331 代码冻结： 20210420 转测试时间：20210326 版本发布： 20210407 本次更新主要涉及：gnutls、qemu、kernel、docker；本次新增特性主要涉及多版本软件包：kafka、redis等修复cve：120个修复bug：15个 SP1：发布源码包：61个； arm二进制包347个; x86二进制包347个； SP1:EPOL：发布源码包：EPOL：14个；arm二进制包35个; x86二进制包35个； CVE清单： CVE score status CVE-2017-12613 7.1 完成 CVE-2020-11987 5.3 完成 CVE-2020-16592 5.5 完成 CVE-2020-8277 7.5 完成 CVE-2020-25678 4.9 完成 CVE-2020-35512 7.8 完成 CVE-2021-21284 6.8 完成 CVE-2021-21285 6.5 完成 CVE-2020-15969 8.8 完成 CVE-2020-15999 6.5 完成 CVE-2021-21300 8 完成 CVE-2021-27218 7.5 完成 CVE-2021-27219 7.5 完成 CVE-2020-36241 5.5 完成 CVE-2021-20231 9.8 完成 CVE-2021-20232 9.8 完成 CVE-2019-14900 6.5 完成 CVE-2019-14900 6.5 完成 CVE-2019-14900 6.5 完成 CVE-2020-10693 5.3 完成 CVE-2021-20176 7.8 完成 CVE-2020-27773 3.3 完成 CVE-2020-27763 3.3 完成 CVE-2020-27768 3.3 完成 CVE-2020-25665 5.5 完成 CVE-2020-25674 5.5 完成 CVE-2020-27750 5.5 完成 CVE-2021-20241 5.5 完成 CVE-2021-20243 5.5 完成 CVE-2021-20244 5.5 完成 CVE-2017-15089 8.8 完成 CVE-2016-0750 8.8 完成 CVE-2020-28491 7.5 完成 CVE-2020-25669 4.1 完成 CVE-2020-27815 7.4 完成 CVE-2020-27830 5.5 完成 CVE-2020-25668 0 完成 CVE-2021-20177 4.4 完成 CVE-2021-3178 6.5 完成 CVE-2021-26931 5.5 完成 CVE-2021-26930 7.8 完成 CVE-2021-26932 5.5 完成 CVE-2015-7837 5.5 完成 CVE-2021-28038 6.5 完成 CVE-2021-27363 3.6 完成 CVE-2021-27364 6.3 完成 CVE-2021-27365 7 完成 CVE-2019-12779 7.1 完成 CVE-2020-13848 7.5 完成 CVE-2021-2024 6.5 完成 CVE-2021-2036 4.9 完成 CVE-2021-2056 4.4 完成 CVE-2021-2021 4.9 完成 CVE-2021-2046 6.8 完成 CVE-2021-2038 4.4 完成 CVE-2021-2061 4.4 完成 CVE-2021-2070 4.9 完成 CVE-2021-2002 4.9 完成 CVE-2021-2081 4.9 完成 CVE-2021-2072 4.9 完成 CVE-2021-2031 4.9 完成 CVE-2021-2028 4.9 完成 CVE-2021-2122 4.9 完成 CVE-2021-2048 5 完成 CVE-2021-2088 4.4 完成 CVE-2021-2058 4.9 完成 CVE-2021-2076 4.9 完成 CVE-2021-2065 4.9 完成 CVE-2021-2087 4.4 完成 CVE-2021-2010 4.2 完成 CVE-2021-2011 5.9 完成 CVE-2021-2060 4.9 完成 CVE-2021-2022 4.4 完成 CVE-2021-2032 4.3 完成 CVE-2021-21290 5.5 完成 CVE-2021-22883 7.5 完成 CVE-2021-22884 7.5 完成 CVE-2020-12403 6.8 完成 CVE-2020-27814 7.8 完成 CVE-2020-27841 5.5 完成 CVE-2020-27843 5.5 完成 CVE-2020-27845 5.5 完成 CVE-2021-27212 7.5 完成 CVE-2020-14145 5.9 完成 CVE-2021-23841 7.5 完成 CVE-2021-23840 7.5 完成 CVE-2021-20188 7 完成 CVE-2021-20229 4.3 完成 CVE-2021-23336 7.1 完成 CVE-2021-21240 7.5 完成 CVE-2020-35655 5.4 完成 CVE-2021-27921 7.5 完成 CVE-2021-27922 7.5 完成 CVE-2021-27923 7.5 完成 CVE-2020-29443 6.5 完成 CVE-2021-20203 3.2 完成 CVE-2020-26247 4.3 完成 CVE-2020-8165 9.8 完成 CVE-2020-8162 7.5 完成 CVE-2020-15810 6.5 完成 CVE-2020-15811 6.5 完成 CVE-2020-24606 7.5 完成 CVE-2020-14058 7.5 完成 CVE-2020-15049 8.8 完成 CVE-2020-17525 7.5 完成 CVE-2021-25329 7 完成 CVE-2021-25122 7.5 完成 CVE-2021-27097 7.8 完成 CVE-2021-27138 7.8 完成 CVE-2020-13959 6.1 完成 CVE-2020-35738 6.1 完成 CVE-2020-9431 7.5 完成 CVE-2020-9428 7.5 完成 CVE-2019-19553 7.5 完成 CVE-2019-13619 7.5 完成 CVE-2021-27803 7.5 完成 CVE-2019-20916 8.5 完成大数据特性清单： redis5 redis6 storm hadoop hadoop-3.1 protobuf2 kafka flink spdk zookeeper spark hyperscan bugfix清单： #I3DUEK:wildfly-core包作为infinispan包的编译依赖，未发布，导致infinispan本地编译失败。<https://gitee.com/open_euler/dashboard?issue_id=I3DUEK> #I3DUG2:【SP1】安装python3-pexpect缺少依赖<https://gitee.com/open_euler/dashboard?issue_id=I3DUG2> #I3DUSK:libraqm包作为python-pillow包的编译依赖，未发布，导致python-pillow本地编译失败。<https://gitee.com/open_euler/dashboard?issue_id=I3DUSK> #I3E27G:【SP1】第一次安装storm失败，再次安装可以成功<https://gitee.com/open_euler/dashboard?issue_id=I3E27G> #I3E3F6:redis5在openEuler aarch64环境下服务启动失败<https://gitee.com/open_euler/dashboard?issue_id=I3E3F6> #I3E3GA:redis6在openEuler aarch64环境下服务启动失败<https://gitee.com/open_euler/dashboard?issue_id=I3E3GA> #I3E3PV:[20.03-sp1]执行命令slideshow /usr/share/batik/samples/mines.svg报错<https://gitee.com/open_euler/dashboard?issue_id=I3E3PV> #I3E4ZB:【20.03-SP1】【arm/x86】update版本测试服务重启失败<https://gitee.com/open_euler/dashboard?issue_id=I3E4ZB> #I3EAPZ:[update-sp1] arm和x86执行podman run -it alpine后exit退出时报错<https://gitee.com/open_euler/dashboard?issue_id=I3EAPZ> #I3EBIY:【20.03-SP1】【arm/x86】kafka连接yum源的zk服务timeout<https://gitee.com/open_euler/dashboard?issue_id=I3EBIY> 涉及软件仓清单： apr batik binutils c-ares ceph dbus docker firefox flink git glib2 gnome-autoar gnutls grpc hibernate hibernate3 hibernate4 hibernate-validator hyperscan ImageMagick infinispan jackson-dataformats-binary kafka kernel libqb libupnp mysql netty nodejs nss openjpeg2 openldap openssh openssl podman postgresql protobuf2 python3 python-httplib2 python-pexpect python-pillow python-ptyprocess python-pycryptodome qemu redis5 redis6 rubygem-actioncable rubygem-actionmailer rubygem-actionpack rubygem-actionview rubygem-activejob rubygem-activemodel rubygem-activerecord rubygem-activestorage rubygem-activesupport rubygem-nokogiri rubygem-rack rubygem-rails rubygem-railties selinux-policy spark spdk squid storm subversion tomcat uboot-tools velocity-tools wavpack wildfly-core wireshark wpa_supplicant zookeeper libraqm openEuler-latest-release

1 0

virt sig例会0409
by openEuler conference 07 Apr '21

07 Apr '21

1 0

virt sig例会
by openEuler conference 07 Apr '21

07 Apr '21

1 0

回复：[Tc] 回复：sig-bio双周例会
by zhouzhongyuan96 07 Apr '21

07 Apr '21

议题： BIGC生物信息绘图工具用户体验及需求 ——荣誉 GCTA软件对接KML适配aarch64架构进展 ——周中元 | | 周中元开源软件工程师 | | 华为技术有限公司 18673967233 zhouzhongyuan96(a)163.com | 签名由网易邮箱大师定制在2021年4月6日 18:21，狼<853793837(a)qq.com> 写道：你好，BIGC荣誉想就绘图工具类的用户体验及需求大概说一下 ------------------ 原始邮件 ------------------ 发件人: "openEuler conference" <public(a)openeuler.io>; 发送时间: 2021年4月6日(星期二) 上午9:27 收件人: "tc"<tc(a)openeuler.org>;"dev"<dev(a)openeuler.org>;"community"<community(a)openeuler.com>; 主题: [Tc] sig-bio双周例会您好！ openEuler sig-bio SIG 邀请您参加 2021-04-08 10:00 召开的ZOOM会议(自动录制) 会议主题：sig-bio双周例会会议内容：sig-bio双周例会，欢迎申报议题。会议链接：https://us06web.zoom.us/j/81442755975?pwd=M0RUVnY0ZEVZK0UyMGw0R3lRYTRQQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-bio SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-04-08 10:00, The subject of the conference is sig-bio双周例会, Summary: sig-bio双周例会，欢迎申报议题。 You can join the meeting at https://us06web.zoom.us/j/81442755975?pwd=M0RUVnY0ZEVZK0UyMGw0R3lRYTRQQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

CloudNative SIG 双周例会
by openEuler conference 06 Apr '21

06 Apr '21

1 0

社区安全sig例会
by openEuler conference 06 Apr '21

06 Apr '21

1 0

CloudNative SIG 双周例会
by openEuler conference 06 Apr '21

06 Apr '21

1 0

ROS sig提交pr cibot测试无法通过
by 韩昊旻 06 Apr '21

06 Apr '21

问题描述：以laser_assembler为例，提交链接： https://gitee.com/src-openeuler/laser_assembler/pulls/1 laser_assembler目标能在openeuler 20.03 LTS上编译通过，但是提交pr之后cibot测试的却是在master分支。想请教的问题是：如何才能改变cibot的测试环境，使得提交的包在openeuler 20.03的环境上编译？寻求您的帮助，期待您的回信. 韩昊旻 15021888297

2 1

Re: [Tc] 4月7日上午 TC 例会议题收集
by 袁德俊 06 Apr '21

06 Apr '21

大家好：以下两个分享，可不占用议题讨论时间，谢谢大家 :pray: 1，上周参加 KERNEL 测试会议，结合 sig-minzuchess 和 sig-raspPI 的需求。第三方交付的测试是否需要统一个社区认证，也是社区基础建设的一部分，openEuler Inside(tm) 2，另外，在社区宣传活动，需求一个SIG中文名称，是否需要社区统一规范？如：树莓派的民族棋私有云方案，我们两个SIG组取名为，石榴派，民族团结的意思。 minzuchess组现在和 RISC-V sig组合作做青少年科普，灵感来自公号宣传中的一段话，加强南向的推广，未来几年，将是各种 RISC-V 硬件百花齐放的时代，openEuler RISC-V SIG 将致力于丰富 RISC-V 的北向软件生态，联合 RISC-V 的南向硬件生态，将 openEuler RISC-V 打造成一个开源的基础软件平台。欢迎大家关注 RISC-V SIG。特取了两个名字：minzuchess组为 “北战” 组，RISC-V 组为 “南征” 组，合并的青少年科普活动为 “南征北战” ，以介绍 openEuler 整个社区为题，出一期专刊介绍。下面是最新的一期样刊，《SIGer 兴趣小组》青少年开源文化期刊，是一个小小的阵地。https://gitee.com/flame-ai/siger Better RISC-V For Better Life sig-minzuchess Maintainer FLAME-AI, 火焰棋实验室 https://gitee.com/flame-ai 袁德俊 yuandj1972(a)163.com 在 2021-04-06 07:38:05，"Huxinwei" <huxinwei(a)huawei.com> 写道：大家好： 4月7日周三上午是例行TC会议。请大家反馈议题。谢谢 Regards Xinwei 发件人: openEuler conference [mailto:public@openeuler.io] 发送时间: 2021年4月5日 19:29 收件人: Huxinwei <huxinwei(a)huawei.com>; tc(a)openeuler.org 主题: TC 例会您好！ openEuler TC SIG 邀请您参加 2021-04-07 10:00 召开的ZOOM会议(自动录制) 会议主题：TC 例会会议内容：技术委员会例会会议链接：https://us06web.zoom.us/j/81039466641?pwd=a2haTFFoRmhqL2c1NGdJV2dZdHUrdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-04-07 10:00, The subject of the conference is TC 例会, Summary: 技术委员会例会 You can join the meeting at https://us06web.zoom.us/j/81039466641?pwd=a2haTFFoRmhqL2c1NGdJV2dZdHUrdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

sig-bio双周例会
by openEuler conference 06 Apr '21

06 Apr '21

1 0

品牌宣传委员会例会
by openEuler conference 06 Apr '21

06 Apr '21

1 0

TC 例会
by openEuler conference 05 Apr '21

05 Apr '21

1 0

maven仓库项目
by openEuler conference 03 Apr '21

03 Apr '21

1 0

【月度例行update】openEuler 20.03 LTS SP1 Update 2021/3/31 release评审通知
by xiasenlin 02 Apr '21

02 Apr '21

openEuler 20.03 LTS SP1 Update 20210331 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年4月9日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I3EUQF?from=project-i… 版本目标：CVE、大数据多版本软件包特性和Bugfix修复版本计划：例行CVE冻结（本次为月度例行版本）：20210331 代码冻结： 20210420 转测试时间：20210326 版本发布： 20210402 本次更新主要涉及：gnutls、qemu、kernel、docker；本次新增特性主要涉及：hadoop、redis等修复cve：120个修复bug：15个 SP1：发布源码包：62个； arm二进制包376个; x86二进制包376个； SP1:EPOL：发布源码包：EPOL：15个；arm二进制包36个; x86二进制包36个； CVE清单： CVE score status CVE-2017-12613 7.1 完成 CVE-2020-11987 5.3 完成 CVE-2020-16592 5.5 完成 CVE-2020-8277 7.5 完成 CVE-2020-25678 4.9 完成 CVE-2020-35512 7.8 完成 CVE-2021-21284 6.8 完成 CVE-2021-21285 6.5 完成 CVE-2020-15969 8.8 完成 CVE-2020-15999 6.5 完成 CVE-2021-21300 8 完成 CVE-2021-27218 7.5 完成 CVE-2021-27219 7.5 完成 CVE-2020-36241 5.5 完成 CVE-2021-20231 9.8 完成 CVE-2021-20232 9.8 完成 CVE-2019-14900 6.5 完成 CVE-2019-14900 6.5 完成 CVE-2019-14900 6.5 完成 CVE-2020-10693 5.3 完成 CVE-2021-20176 7.8 完成 CVE-2020-27773 3.3 完成 CVE-2020-27763 3.3 完成 CVE-2020-27768 3.3 完成 CVE-2020-25665 5.5 完成 CVE-2020-25674 5.5 完成 CVE-2020-27750 5.5 完成 CVE-2021-20241 5.5 完成 CVE-2021-20243 5.5 完成 CVE-2021-20244 5.5 完成 CVE-2017-15089 8.8 完成 CVE-2016-0750 8.8 完成 CVE-2020-28491 7.5 完成 CVE-2020-25669 4.1 完成 CVE-2020-27815 7.4 完成 CVE-2020-27830 5.5 完成 CVE-2020-25668 0 完成 CVE-2021-20177 4.4 完成 CVE-2021-3178 6.5 完成 CVE-2021-26931 5.5 完成 CVE-2021-26930 7.8 完成 CVE-2021-26932 5.5 完成 CVE-2015-7837 5.5 完成 CVE-2021-28038 6.5 完成 CVE-2021-27363 3.6 完成 CVE-2021-27364 6.3 完成 CVE-2021-27365 7 完成 CVE-2019-12779 7.1 完成 CVE-2020-13848 7.5 完成 CVE-2021-2024 6.5 完成 CVE-2021-2036 4.9 完成 CVE-2021-2056 4.4 完成 CVE-2021-2021 4.9 完成 CVE-2021-2046 6.8 完成 CVE-2021-2038 4.4 完成 CVE-2021-2061 4.4 完成 CVE-2021-2070 4.9 完成 CVE-2021-2002 4.9 完成 CVE-2021-2081 4.9 完成 CVE-2021-2072 4.9 完成 CVE-2021-2031 4.9 完成 CVE-2021-2028 4.9 完成 CVE-2021-2122 4.9 完成 CVE-2021-2048 5 完成 CVE-2021-2088 4.4 完成 CVE-2021-2058 4.9 完成 CVE-2021-2076 4.9 完成 CVE-2021-2065 4.9 完成 CVE-2021-2087 4.4 完成 CVE-2021-2010 4.2 完成 CVE-2021-2011 5.9 完成 CVE-2021-2060 4.9 完成 CVE-2021-2022 4.4 完成 CVE-2021-2032 4.3 完成 CVE-2021-21290 5.5 完成 CVE-2021-22883 7.5 完成 CVE-2021-22884 7.5 完成 CVE-2020-12403 6.8 完成 CVE-2020-27814 7.8 完成 CVE-2020-27841 5.5 完成 CVE-2020-27843 5.5 完成 CVE-2020-27845 5.5 完成 CVE-2021-27212 7.5 完成 CVE-2020-14145 5.9 完成 CVE-2021-23841 7.5 完成 CVE-2021-23840 7.5 完成 CVE-2021-20188 7 完成 CVE-2021-20229 4.3 完成 CVE-2021-23336 7.1 完成 CVE-2021-21240 7.5 完成 CVE-2020-35655 5.4 完成 CVE-2021-27921 7.5 完成 CVE-2021-27922 7.5 完成 CVE-2021-27923 7.5 完成 CVE-2020-29443 6.5 完成 CVE-2021-20203 3.2 完成 CVE-2020-26247 4.3 完成 CVE-2020-8165 9.8 完成 CVE-2020-8162 7.5 完成 CVE-2020-15810 6.5 完成 CVE-2020-15811 6.5 完成 CVE-2020-24606 7.5 完成 CVE-2020-14058 7.5 完成 CVE-2020-15049 8.8 完成 CVE-2020-17525 7.5 完成 CVE-2021-25329 7 完成 CVE-2021-25122 7.5 完成 CVE-2021-27097 7.8 完成 CVE-2021-27138 7.8 完成 CVE-2020-13959 6.1 完成 CVE-2020-35738 6.1 完成 CVE-2020-9431 7.5 完成 CVE-2020-9428 7.5 完成 CVE-2019-19553 7.5 完成 CVE-2019-13619 7.5 完成 CVE-2021-27803 7.5 完成 CVE-2019-20916 8.5 完成大数据特性清单： redis5 redis6 storm hadoop hadoop-3.1 protobuf2 kafka flink spdk zookeeper spark hyperscan bugfix清单： #I3DUD7:【SP1】安装hadoop-httpfs缺少依赖<https://gitee.com/open_euler/dashboard?issue_id=I3DUD7> #I3DUEB:【SP1】安装hadoop-3.1-httpfs缺少依赖<https://gitee.com/open_euler/dashboard?issue_id=I3DUEB> #I3DUEK:wildfly-core包作为infinispan包的编译依赖，未发布，导致infinispan本地编译失败。<https://gitee.com/open_euler/dashboard?issue_id=I3DUEK> #I3DUG2:【SP1】安装python3-pexpect缺少依赖<https://gitee.com/open_euler/dashboard?issue_id=I3DUG2> #I3DUSK:libraqm包作为python-pillow包的编译依赖，未发布，导致python-pillow本地编译失败。<https://gitee.com/open_euler/dashboard?issue_id=I3DUSK> #I3E27G:【SP1】第一次安装storm失败，再次安装可以成功<https://gitee.com/open_euler/dashboard?issue_id=I3E27G> #I3E3F6:redis5在openEuler aarch64环境下服务启动失败<https://gitee.com/open_euler/dashboard?issue_id=I3E3F6> #I3E3GA:redis6在openEuler aarch64环境下服务启动失败<https://gitee.com/open_euler/dashboard?issue_id=I3E3GA> #I3E3OV:【20.03 LTS-SP1版本】hadoop两个版本安装后，使用报错<https://gitee.com/open_euler/dashboard?issue_id=I3E3OV> #I3E3PV:[20.03-sp1]执行命令slideshow /usr/share/batik/samples/mines.svg报错<https://gitee.com/open_euler/dashboard?issue_id=I3E3PV> #I3E4ZB:【20.03-SP1】【arm/x86】update版本测试服务重启失败<https://gitee.com/open_euler/dashboard?issue_id=I3E4ZB> #I3E5C1:【20.03-SP1】【arm/x86】服务启动失败<https://gitee.com/open_euler/dashboard?issue_id=I3E5C1> #I3EAPZ:[update-sp1] arm和x86执行podman run -it alpine后exit退出时报错<https://gitee.com/open_euler/dashboard?issue_id=I3EAPZ> #I3EBIY:【20.03-SP1】【arm/x86】kafka连接yum源的zk服务timeout<https://gitee.com/open_euler/dashboard?issue_id=I3EBIY> 涉及软件仓清单： apr batik binutils c-ares ceph dbus docker firefox flink git glib2 gnome-autoar gnutls grpc hadoop hadoop-3.1 hibernate hibernate3 hibernate4 hibernate-validator hyperscan ImageMagick infinispan jackson-dataformats-binary kafka kernel libqb libupnp mysql netty nodejs nss openjpeg2 openldap openssh openssl open podman postgresql protobuf2 python3 python-httplib2 python-pexpect python-pillow python-ptyprocess python-pycryptodome qemu redis5 redis6 rubygem-actioncable rubygem-actionmailer rubygem-actionpack rubygem-actionview rubygem-activejob rubygem-activemodel rubygem-activerecord rubygem-activestorage rubygem-activesupport rubygem-nokogiri rubygem-rack rubygem-rails rubygem-railties selinux-policy spark spdk squid storm subversion tomcat uboot-tools velocity-tools wavpack wildfly-core wireshark wpa_supplicant zookeeper libraqm openEuler-latest-release

1 0

【月度例行update】openEuler 20.03 LTS Update 2021/3/31 release评审通知
by guoxiaoqi 02 Apr '21

02 Apr '21

openEuler 20.03 LTS Update 20210331 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年4月9日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I3EUNF?from=project-i… 版本目标：CVE和Bugfix修复版本计划：例行CVE冻结（本次为月度例行版本）：20210331 代码冻结： 20210420 转测试时间：20210326 版本发布： 20210402 本次更新主要涉及，gnutls、qemu、kernel、docker。修复cve：98个修复bug：3个发布源码包35个 arm二进制包279个 x86二进制包278个 CVE清单： CVE score status CVE-2017-12613 7.1 完成 CVE-2020-16592 5.5 完成 CVE-2020-0551 5.6 完成 CVE-2020-8277 7.5 完成 CVE-2020-25678 4.9 完成 CVE-2020-35512 7.8 完成 CVE-2021-21284 6.8 完成 CVE-2021-21285 6.5 完成 CVE-2020-15969 8.8 完成 CVE-2020-15999 6.5 完成 CVE-2020-25690 8.8 完成 CVE-2021-21300 8.0 完成 CVE-2020-35457 7.8 完成 CVE-2021-27218 7.5 完成 CVE-2021-27219 7.5 完成 CVE-2020-36241 5.5 完成 CVE-2021-20231 9.8 完成 CVE-2021-20232 9.8 完成 CVE-2021-20176 7.8 完成 CVE-2020-27773 3.3 完成 CVE-2020-27763 3.3 完成 CVE-2020-27768 3.3 完成 CVE-2020-25665 5.5 完成 CVE-2020-25674 5.5 完成 CVE-2020-27750 5.5 完成 CVE-2021-20241 5.5 完成 CVE-2021-20243 5.5 完成 CVE-2021-20244 5.5 完成 CVE-2021-20246 5.5 完成 CVE-2021-26931 5.5 完成 CVE-2021-26930 7.8 完成 CVE-2021-26932 5.5 完成 CVE-2015-7837 5.5 完成 CVE-2021-28038 6.5 完成 CVE-2021-27363 3.6 完成 CVE-2021-27364 6.3 完成 CVE-2021-27365 7.0 完成 CVE-2020-35521 5.5 完成 CVE-2020-35522 5.5 完成 CVE-2020-35523 7.8 完成 CVE-2020-35524 7.8 完成 CVE-2021-2024 6.5 完成 CVE-2021-2036 4.9 完成 CVE-2021-2056 4.4 完成 CVE-2021-2021 4.9 完成 CVE-2021-2046 6.8 完成 CVE-2021-2038 4.4 完成 CVE-2021-2061 4.4 完成 CVE-2021-2070 4.9 完成 CVE-2021-2002 4.9 完成 CVE-2021-2081 4.9 完成 CVE-2021-2072 4.9 完成 CVE-2021-2031 4.9 完成 CVE-2021-2028 4.9 完成 CVE-2021-2122 4.9 完成 CVE-2021-2048 5.0 完成 CVE-2021-2088 4.4 完成 CVE-2021-2058 4.9 完成 CVE-2021-2076 4.9 完成 CVE-2021-2065 4.9 完成 CVE-2021-2087 4.4 完成 CVE-2021-2010 4.2 完成 CVE-2021-2011 5.9 完成 CVE-2021-2060 4.9 完成 CVE-2021-2022 4.4 完成 CVE-2021-2032 4.3 完成 CVE-2021-22883 7.5 完成 CVE-2021-22884 7.5 完成 CVE-2019-17007 7.5 完成 CVE-2020-12403 6.8 完成 CVE-2020-25648 7.5 完成 CVE-2020-8020 6.1 完成 CVE-2020-8021 5.3 完成 CVE-2020-27814 7.8 完成 CVE-2020-27841 5.5 完成 CVE-2020-27843 5.5 完成 CVE-2020-27845 5.5 完成 CVE-2021-27212 7.5 完成 CVE-2020-14145 5.9 完成 CVE-2021-23841 7.5 完成 CVE-2021-23840 7.5 完成 CVE-2020-35498 7.5 完成 CVE-2021-20188 7.0 完成 CVE-2021-20229 4.3 完成 CVE-2021-23336 7.1 完成 CVE-2021-21240 7.5 完成 CVE-2020-35655 5.4 完成 CVE-2021-27921 7.5 完成 CVE-2021-27922 7.5 完成 CVE-2021-27923 7.5 完成 CVE-2020-29443 6.5 完成 CVE-2021-20203 3.2 完成 CVE-2020-17525 7.5 完成 CVE-2021-27097 7.8 完成 CVE-2021-27138 7.8 完成 CVE-2020-35738 6.1 完成 CVE-2020-9431 7.5 完成 CVE-2020-9428 7.5 完成 CVE-2019-19553 7.5 完成 CVE-2019-13619 7.5 完成 CVE-2021-27803 7.5 完成 bugfix清单： #I3DU23:LTS update验证安装fontforge缺少安装依赖<https://gitee.com/open_euler/dashboard?issue_id=I3DU23> #I3E0A0:fontforge自编译失败，缺少编译依赖libuninameslist-devel<https://gitee.com/open_euler/dashboard?issue_id=I3E0A0> #I3EAPZ:[update-sp1] arm和x86执行podman run -it alpine后exit退出时报错<https://gitee.com/open_euler/dashboard?issue_id=I3EAPZ> 涉及软件仓清单 src-openEuler/apr src-openEuler/binutils src-openEuler/c-ares src-openEuler/ceph src-openEuler/dbus src-openEuler/docker src-openEuler/firefox src-openEuler/fontforge src-openEuler/git src-openEuler/glib2 src-openEuler/gnome-autoar src-openEuler/gnutls src-openEuler/ImageMagick src-openEuler/kernel src-openEuler/libtiff src-openEuler/mysql src-openEuler/nodejs src-openEuler/nss src-openEuler/obs-server src-openEuler/openjpeg2 src-openEuler/openldap src-openEuler/openssh src-openEuler/openssl src-openEuler/openvswitch src-openEuler/podman src-openEuler/postgresql src-openEuler/python3 src-openEuler/python-httplib2 src-openEuler/python-pillow src-openEuler/qemu src-openEuler/subversion src-openEuler/uboot-tools src-openEuler/wavpack src-openEuler/wireshark src-openEuler/wpa_supplicant

1 0

云原生专题分享：WebAssembly 在云原生领域的应用
by openEuler conference 02 Apr '21

02 Apr '21

2 1

Re: 答复 : 答复 : 答复 : [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会
by Wang Jianmin 02 Apr '21

02 Apr '21

或许还有一个方案，我们用主仓库的 markdown 方案来做文档，不用 wiki 。因为 https://gitee.com/openeuler/cloudnative/ 本身就是 SIG 的主要入口仓库，并不是有明确的代码承载目标吧？ ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of leizhongkai <leizhongkai(a)huawei.com> Date: Thursday, 1 April 2021 at 10:40 AM To: Wang Jianmin <jianmin(a)iscas.ac.cn>, "Zhoukang (A)" <zhoukang7(a)huawei.com>, "dev(a)openeuler.org" <dev(a)openeuler.org>, "cloudnative(a)openeuler.org" <cloudnative(a)openeuler.org> Subject: [Dev] 答复: 答复: 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会似乎不行。我找了gitee的帮助文档：https://gitee.com/help，没看到wiki的协同方式目前了解到只能maintainer直接git push，或者网页直接编辑其他人有熟悉的也可以指导指导发件人: Wang Jianmin [mailto:jianmin@iscas.ac.cn] 发送时间: 2021年4月1日 9:41 收件人: leizhongkai <leizhongkai(a)huawei.com>; Zhoukang (A) <zhoukang7(a)huawei.com>; dev(a)openeuler.org; cloudnative(a)openeuler.org 主题: Re: [Dev] 答复: 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会那么 wiki 仓库可以用提交 PR 的方式协同吗？ From: <dev-bounces(a)openeuler.org> on behalf of leizhongkai <leizhongkai(a)huawei.com> Date: Thursday, 1 April 2021 at 9:35 AM To: "Zhoukang (A)" <zhoukang7(a)huawei.com>, "dev(a)openeuler.org" <dev(a)openeuler.org>, "cloudnative(a)openeuler.org" <cloudnative(a)openeuler.org> Subject: [Dev] 答复: 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会是的，我找caozhi确认，这个git仓库跟主仓权限保持一致，目前规则只能maintainer级别权限发件人: Zhoukang (A) 发送时间: 2021年3月31日 11:16 收件人: leizhongkai <leizhongkai(a)huawei.com>; dev(a)openeuler.org; cloudnative(a)openeuler.org 主题: RE: [Dev] 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会 Wiki应该是后台有个隐藏的git仓库; 那个仓库没权限吗? From: leizhongkai [mailto:leizhongkai@huawei.com] Sent: Wednesday, March 31, 2021 11:11 AM To: dev(a)openeuler.org; cloudnative(a)openeuler.org Subject: [Dev] 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会协调开放 wiki 的编辑权限至 SIG 组成员 @zhongkai //昨天找infra SIG同学了解到，咱们gitee仓库里的wiki权限跟SIG是强绑定的，只能由maintainer推送，committer也不行所以后续咱们的wiki文档也许只能先自己准备好，发给maintainer提交。文档写上作者gitee账号。讨论issue：https://gitee.com/openeuler/cloudnative/issues/I3ECN7?from=project-… 发件人: Wang Jianmin [mailto:jianmin@iscas.ac.cn] 发送时间: 2021年3月30日 17:31 收件人: dev(a)openeuler.org; cloudnative(a)openeuler.org 主题: [Dev] [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: [Dev] CloudNative SIG 双周例会会议日期2021/03/30 轮值：王建民与会人：杨昭、郭峰、卞乃猛、薛晋泽、王悦良、陈锐、李翔、雷钟凯、邢为政，王伟、曹睿东、李元戎、林晓旭会议纪要： 1. 遗留问题闭环 - Ceph 存储等相关镜像推动进展 @钟凯 - 已联系Ceph 的负责人，第一阶段目标 Ceph 作为容器存储后端的默认选项，输出解决方案到 CloudNative Wiki 中。 @钟凯 2. Kubernetes基础镜像构建及发布讨论 @lixiang @jingxiaolu 基础镜像构建初步验证，镜像大小的优化可后续迭代，初步讨论了后续工作： 1) Wiki: SIG 组制定发布镜像的流程(暂行) @lixiang 2) Wiki: k8s 镜像本地测试调试的方法 @lixiang 3) 协调分配 CloudNative SIG 组成员的 oepkgs 成员账号 @jianmin 4) etcd 镜像的制作并提交到 oepkgs 个人仓 @yangzhao 3. 镜像仓库（hub.oepkgs.net）界面美化讨论 @lixiang @jingxiaolu 目标尽快着手开展镜像仓库的社区试用，后续工作：建立 issue 用于 SIG 内讨论确定待定项，预期 deadline： 4/1 日 @lixiang 4. cloudnative主仓的使用后续工作： 1) 建立 issue 讨论如何使用 @zhongkai 2) 协调开放 wiki 的编辑权限至 SIG 组成员 @zhongkai 5. KubeOS介绍 @曹睿东 6. 下一次会议安排 - 时间：2021/4/13 16:00 - 轮值主持：pixiake@pixiake ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of openEuler conference <public(a)openeuler.io> Date: Wednesday, 24 March 2021 at 10:15 AM To: <jianmin(a)iscas.ac.cn> Subject: [Dev] CloudNative SIG 双周例会您好！ openEuler sig-CloudNative SIG 邀请您参加 2021-03-30 16:00 召开的ZOOM会议(自动录制) 会议主题：CloudNative SIG 双周例会会议内容： 1. Ceph存储等相关镜像推动进展 2. 更多议题会议链接：https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-30 16:00, The subject of the conference is CloudNative SIG 双周例会, Summary: 1. Ceph存储等相关镜像推动进展 2. 更多议题 You can join the meeting at https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

4 3

Compiler SIG双周例会
by openEuler conference 02 Apr '21

02 Apr '21

1 0

[Release] openEuler 21.03 release评审通知
by Xuxiaosong 01 Apr '21

01 Apr '21

openEuler 21.03 2021-4-1 release已经测试完成。请TC委员，Release委员，QA委员在issue内答复评审意见，欢迎广大开发者对本次发布发表意见，您的每条意见我们都会认真对待，并加以改进。如果您发现了版本的致命问题请及时在issue内回复或者邮件通知我们，2021年4月1日关闭该发布电子流。 https://gitee.com/openeuler/release-management/issues/I3EP9T?from=project-i… openEuler 21.03版本作为2021年首个创新版本，发布范围主要如下： 1、内核版本升级到5.10 2、新增组件OpenStack/xfce/Kubernetes 3、竞争力特性：StratoVirt轻量级虚拟化功能增强和优化/etmem/内核热升级/secGear机密计算安全应用开发套件 4、删除python2 5、补齐/优化社区软件包生态 6、修复bug和cve 本次版本需求特性：详见：https://gitee.com/openeuler/release-management/blob/master/openEuler-21.… no fetur 1 openEuler 21.03 support openStack 2 openEuler 21.03 support virtualization live migration pro 3 openEuler 21.03 support StratoVirt function enhancement 4 openEuler 21.03 support Risc-v virt live migration 5 openEuler 21.03 support DDE 6 openEuler 21.03 kernel update to version 5.10 7 openEuler 21.03 remove python 2 from release 8 openEuler 21.03 support xfce 4.14 9 openEuler 21.03 support memig 10 openEuler 21.03 support nvwa 11 openEuler 21.03 support secGear 12 openEuler 21.03 support RaspberryPi 13 openEuler 21.03 support UKUI 14 openEuler 21.03 support HA 15 openEuler 21.03 support StratoVirt microvm image 16 openEuler 21.03 support Kubernetes 17 openEuler 21.03 update SPDK 28 openEuler 21.03 update some software 29 openEuler 21.03 slim container base image openEuler 21.03版本共发现问题单266个，有效问题253个，其中修复问题单247个，回归均通过，另外转需求问题单2个，遗留问题单6个，遗留问题详见链接测试报告： https://gitee.com/openeuler/QA/blob/master/Test_Result/openEuler_21.03/open… 本次版本修复cve 743个。 <javascript:void(0)>

1 0

openEuler 21.03创新版本发布评审
by openEuler conference 01 Apr '21

01 Apr '21

1 0

sparrow流程分析/os_mount与rootfs讲解
by openEuler conference 01 Apr '21

01 Apr '21

1 0

sig-compilance 双周例会
by openEuler conference 01 Apr '21

01 Apr '21

2 2

Re: 答复 : 答复 : [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会
by Wang Jianmin 01 Apr '21

01 Apr '21

那么 wiki 仓库可以用提交 PR 的方式协同吗？ From: <dev-bounces(a)openeuler.org> on behalf of leizhongkai <leizhongkai(a)huawei.com> Date: Thursday, 1 April 2021 at 9:35 AM To: "Zhoukang (A)" <zhoukang7(a)huawei.com>, "dev(a)openeuler.org" <dev(a)openeuler.org>, "cloudnative(a)openeuler.org" <cloudnative(a)openeuler.org> Subject: [Dev] 答复: 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会是的，我找caozhi确认，这个git仓库跟主仓权限保持一致，目前规则只能maintainer级别权限发件人: Zhoukang (A) 发送时间: 2021年3月31日 11:16 收件人: leizhongkai <leizhongkai(a)huawei.com>; dev(a)openeuler.org; cloudnative(a)openeuler.org 主题: RE: [Dev] 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会 Wiki应该是后台有个隐藏的git仓库; 那个仓库没权限吗? From: leizhongkai [mailto:leizhongkai@huawei.com] Sent: Wednesday, March 31, 2021 11:11 AM To: dev(a)openeuler.org; cloudnative(a)openeuler.org Subject: [Dev] 答复: [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: CloudNative SIG 双周例会协调开放 wiki 的编辑权限至 SIG 组成员 @zhongkai //昨天找infra SIG同学了解到，咱们gitee仓库里的wiki权限跟SIG是强绑定的，只能由maintainer推送，committer也不行所以后续咱们的wiki文档也许只能先自己准备好，发给maintainer提交。文档写上作者gitee账号。讨论issue：https://gitee.com/openeuler/cloudnative/issues/I3ECN7?from=project-… 发件人: Wang Jianmin [mailto:jianmin@iscas.ac.cn] 发送时间: 2021年3月30日 17:31 收件人: dev(a)openeuler.org; cloudnative(a)openeuler.org 主题: [Dev] [ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: [Dev] CloudNative SIG 双周例会会议日期2021/03/30 轮值：王建民与会人：杨昭、郭峰、卞乃猛、薛晋泽、王悦良、陈锐、李翔、雷钟凯、邢为政，王伟、曹睿东、李元戎、林晓旭会议纪要： 1. 遗留问题闭环 - Ceph 存储等相关镜像推动进展 @钟凯 - 已联系Ceph 的负责人，第一阶段目标 Ceph 作为容器存储后端的默认选项，输出解决方案到 CloudNative Wiki 中。 @钟凯 2. Kubernetes基础镜像构建及发布讨论 @lixiang @jingxiaolu 基础镜像构建初步验证，镜像大小的优化可后续迭代，初步讨论了后续工作： 1) Wiki: SIG 组制定发布镜像的流程(暂行) @lixiang 2) Wiki: k8s 镜像本地测试调试的方法 @lixiang 3) 协调分配 CloudNative SIG 组成员的 oepkgs 成员账号 @jianmin 4) etcd 镜像的制作并提交到 oepkgs 个人仓 @yangzhao 3. 镜像仓库（hub.oepkgs.net）界面美化讨论 @lixiang @jingxiaolu 目标尽快着手开展镜像仓库的社区试用，后续工作：建立 issue 用于 SIG 内讨论确定待定项，预期 deadline： 4/1 日 @lixiang 4. cloudnative主仓的使用后续工作： 1) 建立 issue 讨论如何使用 @zhongkai 2) 协调开放 wiki 的编辑权限至 SIG 组成员 @zhongkai 5. KubeOS介绍 @曹睿东 6. 下一次会议安排 - 时间：2021/4/13 16:00 - 轮值主持：pixiake@pixiake ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of openEuler conference <public(a)openeuler.io> Date: Wednesday, 24 March 2021 at 10:15 AM To: <jianmin(a)iscas.ac.cn> Subject: [Dev] CloudNative SIG 双周例会您好！ openEuler sig-CloudNative SIG 邀请您参加 2021-03-30 16:00 召开的ZOOM会议(自动录制) 会议主题：CloudNative SIG 双周例会会议内容： 1. Ceph存储等相关镜像推动进展 2. 更多议题会议链接：https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-30 16:00, The subject of the conference is CloudNative SIG 双周例会, Summary: 1. Ceph存储等相关镜像推动进展 2. 更多议题 You can join the meeting at https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

3 2

[ 会议纪要 ] CloudNative SIG 双周例会 0330 Re: [Dev] CloudNative SIG 双周例会
by Wang Jianmin 01 Apr '21

01 Apr '21

会议日期2021/03/30 轮值：王建民与会人：杨昭、郭峰、卞乃猛、薛晋泽、王悦良、陈锐、李翔、雷钟凯、邢为政，王伟、曹睿东、李元戎、林晓旭会议纪要： 1. 遗留问题闭环 - Ceph 存储等相关镜像推动进展 @钟凯 - 已联系Ceph 的负责人，第一阶段目标 Ceph 作为容器存储后端的默认选项，输出解决方案到 CloudNative Wiki 中。 @钟凯 2. Kubernetes基础镜像构建及发布讨论 @lixiang @jingxiaolu 基础镜像构建初步验证，镜像大小的优化可后续迭代，初步讨论了后续工作： 1) Wiki: SIG 组制定发布镜像的流程(暂行) @lixiang 2) Wiki: k8s 镜像本地测试调试的方法 @lixiang 3) 协调分配 CloudNative SIG 组成员的 oepkgs 成员账号 @jianmin 4) etcd 镜像的制作并提交到 oepkgs 个人仓 @yangzhao 3. 镜像仓库（hub.oepkgs.net）界面美化讨论 @lixiang @jingxiaolu 目标尽快着手开展镜像仓库的社区试用，后续工作：建立 issue 用于 SIG 内讨论确定待定项，预期 deadline： 4/1 日 @lixiang 4. cloudnative主仓的使用后续工作： 1) 建立 issue 讨论如何使用 @zhongkai 2) 协调开放 wiki 的编辑权限至 SIG 组成员 @zhongkai 5. KubeOS介绍 @曹睿东 6. 下一次会议安排 - 时间：2021/4/13 16:00 - 轮值主持：pixiake@pixiake ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of openEuler conference <public(a)openeuler.io> Date: Wednesday, 24 March 2021 at 10:15 AM To: <jianmin(a)iscas.ac.cn> Subject: [Dev] CloudNative SIG 双周例会您好！ openEuler sig-CloudNative SIG 邀请您参加 2021-03-30 16:00 召开的ZOOM会议(自动录制) 会议主题：CloudNative SIG 双周例会会议内容： 1. Ceph存储等相关镜像推动进展 2. 更多议题会议链接：https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-30 16:00, The subject of the conference is CloudNative SIG 双周例会, Summary: 1. Ceph存储等相关镜像推动进展 2. 更多议题 You can join the meeting at https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

3 3

release sig例会
by openEuler conference 31 Mar '21

31 Mar '21

2 1

【议题收集】【Meeting Notice】openEuler kernel sig meeting Time: 2021-04-02 14:00-16:00
by Xie XiuQi 30 Mar '21

30 Mar '21

kernel sig meeting，欢迎申报议题。 On 2021/3/30 11:09, Meeting Book wrote: > Topic > openEuler kernel sig meeting > Time > 2021-04-02 14:00-16:00((UTC+08:00)Beijing) > > > > Join Conference > Join (External) >> <https://welink-meeting.zoom.us/j/170346906> > Meeting ID > 170 346 906 > > > > Convener > 谢秀奇 > > > > Tips: > Dial the access number to join conference <http://app.huawei.com/eshare/voiceMeetings> > 注：仅支持部分国家和地区。( Only some countries and regions are supported.) > 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载 <https://zoom.us/download> > If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download <https://zoom.us/download> > > > _______________________________________________ > Kernel mailing list -- kernel(a)openeuler.org > To unsubscribe send an email to kernel-leave(a)openeuler.org

1 0

【Meeting Notice】openEuler kernel sig meeting Time: 2021-04-02 14:00-16:00
by Meeting Book 30 Mar '21

30 Mar '21

1 0

Re: OpenJDK RISC-V port is coming!
by Guoge(JVM) 29 Mar '21

29 Mar '21

Congrats! It will be the first JIT available JDK in the world. From: jiangfeilong Sent: Monday, March 29, 2021 9:29 AM To: tc(a)openeuler.org; dev(a)openeuler.org Cc: Guoge(JVM) <ge.guo(a)huawei.com>; wangyadong (E) <yadonn.wang(a)huawei.com>; Chenshanyao <chenshanyao(a)huawei.com>; Chengwentao (Vintorcheng) <chengwentao(a)huawei.com>; xuwei (AU) <xuwei43(a)huawei.com> Subject: OpenJDK RISC-V port is coming! OpenJDK RISC-V port brings the template interpreter and backends of C1/C2 compiler to the RISC-V world. We supports RV64G (G used to be represent the IMAFD base and extensions of RISC-V ISA) for now and with BV (bit-manipulation and vector extensions) on the way . We have set up a repo request[1] in openEuler. [1]: https://gitee.com/openeuler/community/pulls/1694

1 0

Re: CloudNative SIG双周例会议题申报
by Wang Jianmin 28 Mar '21

28 Mar '21

谢谢申报议题。目前 CloudNative SIG 双周例会已有议题如下，欢迎大家继续申报议题。 1. Ceph存储等相关镜像推动进展 @钟凯 2. CNOS介绍 @曹睿东 3. Kubernetes基础镜像构建及发布讨论 @lixiang 4. 镜像仓库（hub.oepkgs.net）界面美化讨论 @lixiang 会议时间：2021-03-30 16:00 会议链接：https://zoom.us/j/93306108174?pwd=blgvazNYcEdpNmUyRjRoYWx6YVo1dz09 会议笔记：https://etherpad.openeuler.org/p/sig-CloudNative-meetings ——王建民 From: <dev-bounces(a)openeuler.org> on behalf of "lixiang (CH)" <lixiang172(a)huawei.com> Date: Saturday, 27 March 2021 at 11:17 AM To: "cloudnative(a)openeuler.org" <cloudnative(a)openeuler.org> Cc: "dev(a)openeuler.org" <dev(a)openeuler.org> Subject: [Dev] CloudNative SIG双周例会议题申报 CloudNative SIG双周例会议题申报： 1． Kubernetes基础镜像构建及发布讨论申报人：李翔、卢景晓 2．镜像仓库（hub.oepkgs.net）界面美化讨论申报人：李翔、卢景晓李翔（LI XIANG）华为技术有限公司 Tel : +86 15651111331 Email : lixiang172(a)huawei.com _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

1 0

[SIG OpenStack] Welcome to OpenStack SIG Meetup Beijing
by Zheng Zhenyu 27 Mar '21

27 Mar '21

Dear Contributors, The OpenStack SIG is going to arrange an F2F Meetup in 10th April at Beijing, the meetup will be divided into two parts: 1. In the morning, we will arrange a PTG(Project Team Gathering), during the PTG, the SIG members will gather together to make plans for the SIG for the next few months, contributors and users can bring up ideas and questions for discussion. All the topics are listed here: https://etherpad.openeuler.org/p/openstack-sig-ptg-bj please feel free to amend the list with the content you are intrested. 2. In the afternoon, we will arrange sessions from users of OpenStack in different areas like Telco, Cloud Providers and Hardware Vendors, to share their experiences of using OpenStack with openEuler and Arm, for more details on the sessions, please checkout: https://www.oschina.net/event/2321805 See you at the Meetup! 各位贡献者大家好， OpenStack SIG将于4月10日于北京举办线下Meetup活动，本次活动将分为两个部分： 1. 10日上午，将举办PTG(Project Team Gathering)活动，在PTG中，OpenStack SIG成员将收集开发者、用户诉求，制定未来几个月的SIG工作方向。开发者与用户可以将自己所关心的议题追加到以下协作文档上：https://etherp… PTG会议中将按顺序对议题进行讨论。 2. 10日下午，将举办开放分享活动，我们收集到了来自包括运营商、云提供商、硬件厂商等领域OpenStack用户的分享议题，将为参与者提供OpenStack… Meetup现场见！

1 0

CloudNative SIG双周例会议题申报
by lixiang (CH) 27 Mar '21

27 Mar '21

CloudNative SIG双周例会议题申报： 1． Kubernetes基础镜像构建及发布讨论申报人：李翔、卢景晓 2．镜像仓库（hub.oepkgs.net）界面美化讨论申报人：李翔、卢景晓李翔（LI XIANG）华为技术有限公司 Tel : +86 15651111331 Email : lixiang172(a)huawei.com<mailto:lixiang172@huawei.com> [cid:image006.png@01D5FE96.F9F76FF0]

1 0

会议纪要 // [Sig-ai-bigdata] sig-ai-bigdata regular meeting
by Hubble_Zhu 26 Mar '21

26 Mar '21

与会人：sinever，hubble_zhu，hao，coding，chengxinxin，yikun，统信-魏东，PL-HW，zhengzhenyu，常涛，麒麟软件-杨昭，统信-杨绍兴，王玺源感谢大家的参与！会议纪要：议题一：sig-ai-bigdata AI/大数据组件支持进展 hubble_zhu:   master分支，20.03LTS-SP1分支新增支持hadoop3.1.4，hadoop3.2.1，Spark3.0.1，Flink1.12.0，Kafka2.4.1，Storm1.2.3，Zookeeper3.6.1 议题二: openEuler上对于大数据组件做了哪些功能的测试统信-魏东：      很关注openEuler现在对这些大数据组件做了哪些功能的测试 hubble_zhu:   目前只做了wordCount测试 wangxiyuan:   现在openEuler构建arm，x86的环境是啥样的 yikun:            现在构建arm，x86都是在华为云的虚拟机上 chengxinxin:   如果需要验证在其他硬件上的功能的话，可以向社区提看看是否能提供一些基础设施（比如兆芯） wangxiyuan：很关心下游在使用AI/大数据组件时遇到了哪些问题，到时可以提issue给相关包统信-魏东：      下周很关注多个AI/大数据组件包之间的版本配套关系议题三：openEuler developer day展示demo召集 chenxinxin：     openEuler社区在5/20，5/21会在北京举行developer day活动，如果有一些有意思的demo可以到时展示下 zhengzhenyu：建议可以考虑给submarine，bigtop等新项目一个展示的平台 zhengzhenyu：如果有其他有意思的idea也可以提议题四：其他 1、后面ZhengZhenyu会参与sig运作，帮助sig-ai-bigdata运营 2、希望可以报个bigtop议题给大家分享下，期待 ——hao 3、希望可以把在openEuler上部署多个大数据组件的实践给大家分享下，期待 ——coding 4、希望可以介绍下submarine，期待 ——tangzhankun 欢迎大家将想要了解的内容或者讨论的议题发送到 sig-ai-bigdata(a)openeuler.xn--org !-5g7zf65p 欢迎大家添加小助手进群交流！ ------------------ 原始邮件 ------------------ 发件人: "openEuler conference" <public(a)openeuler.io>; 发送时间: 2021年3月23日(星期二) 上午7:38 收件人: "sig-ai-bigdata"<sig-ai-bigdata(a)openeuler.org>;"tc"<tc(a)openeuler.org>;"dev"<dev(a)openeuler.org>; 主题: [Sig-ai-bigdata] sig-ai-bigdata regular meeting 您好！ openEuler sig-ai-bigdata SIG 邀请您参加 2021-03-25 19:00 召开的ZOOM会议会议主题：sig-ai-bigdata regular meeting 会议内容：1、sig相关软件包引入进展 2、下一步分工与计划会议链接：https://zoom.us/j/99124965310?pwd=eVV5SFk2QWJnT3JpUE5FQ05oNUhudz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-ai-bigdata SIG invites you to attend the ZOOM conference will be held at 2021-03-25 19:00, The subject of the conference is sig-ai-bigdata regular meeting, Summary: 1、sig相关软件包引入进展 2、下一步分工与计划 You can join the meeting at https://zoom.us/j/99124965310?pwd=eVV5SFk2QWJnT3JpUE5FQ05oNUhudz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

A-Tune sig meeting Time: 2021-03-26 10:00-12:00
by hanxinke 25 Mar '21

25 Mar '21

您好！ openEuler A-Tune SIG 邀请您参加 2021-03-26 10:00 召开的ZOOM会议(自动录制) 会议主题：A-Tune sig meeting 会议内容： 1、2021年社区比赛信息与A-Tune课题介绍 2、业界性能调优论文分享会议链接：https://zoom.us/j/98151178845?pwd=TTFUR0c3UjNrUUh0ZW0vbU9DL0pTdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler A-Tune SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-26 10:00, The subject of the conference is A-Tune sig meeting, Summary: 1、2021年社区比赛信息与A-Tune课题介绍 2、业界性能调优论文分享 You can join the meeting at https://zoom.us/j/98151178845?pwd=TTFUR0c3UjNrUUh0ZW0vbU9DL0pTdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

A-Tune sig meeting
by openEuler conference 25 Mar '21

25 Mar '21

1 0

[openeuler-security] openEuler安全委员会例会纪要20210324
by Yanxiaobing 25 Mar '21

25 Mar '21

安全委员会例会纪要会议时间：2021-3-24 与会人：刘金刚、统信-张绍宁、麒麟-崔雷、中科微澜-闫志全、朱建伟、魏刚、颜小兵、郭晓琪、杨丽锦、汪奕如、朱俊豪纪要人：颜小兵【会议议题】一、漏洞感知工具进展主讲人：闫志全 1、介绍了漏洞感知工具当前的优化进展，包括灾备方案的实施进展和漏洞推送时效性优化的进展； 2、感知工具漏洞数据推送前的人工审核改造成自动化审核，需要在3月31日上线。如果无法达成，则要求每天进行两次人工审核后推送，以保证漏洞推送的时效要求。二、社区漏洞处理进展主讲人：颜小兵 1. 漏洞感知：本周新增漏洞29个（严重2个，主要的15个），其中19个源自感知工具，占比65%，贡献者提交的10个漏洞，其中有效漏洞28个，感知工具漏报率：35%。 2. 漏洞修复： 1）待修复：当前社区还有152个漏洞未修复（严重7个、主要62个，其它79个），其中146个代码已修改，待出版本，6个待修改。需要尽快出补丁版本。 2）严重漏洞计划3月26日发布单包补丁，其它漏洞计划3月31日发布月度补丁。三、21.03创新版本CVE清零进展主讲人：杨丽锦 1、本次使用二进制扫描工具共扫描到cve 761个，已确认在21.03分支修复完成。从Vtopic推送的漏洞中过滤出影响21.03版本的CVE除CVE-2021-28116，其余均已修复。 2、CVE-2021-28116 是squid的漏洞，启用WCCP协议时受影响，当前默认未启用WCCP协议，同时上游社区无修复方案，安全委员会同意报备，暂不解决，继续跟踪社区的解决进展。 4.CVRF格式SA对接分享；主讲人：崔雷 1）介绍麒麟软件漏洞管理工具与openEuler CVRF对接的优秀实践； 2）由麒麟软件崔雷作为openEuler社区CVRF格式模板维护的owner； 5.openEuler漏洞指标看板进展；主讲人：汪奕如 1）介绍openEuler漏洞指标看板的开发进展。 2）建议漏洞指标的单位要做统一，漏洞指标的命名要清晰，建议后续增加统计报表；遗留问题： 1、Vtopic 3月22日推送的漏洞，感知时长大于24小时的CVE，需要分析原因。-- 闫志全 2、漏洞处理进展议题每次需要主讲人提前人工整理统计CVE数据，考虑工具化生成方案。-- 颜小兵、张建均 3、建议增加统计报表 --- 刘金刚、汪奕如 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, March 22, 2021 8:35 PM To: dev(a)openEuler.org; openEuler-security(a)openEuler.org; tc(a)openEuler.org Subject: [openeuler-security] openEuler安全委员会例会您好！ openEuler security-committee SIG 邀请您参加 2021-03-24 16:00 召开的ZOOM会议会议主题：openEuler安全委员会例会会议内容：1. 漏洞感知优化进展； 2.社区漏洞处理进展；有其它议题，欢迎申报。会议链接：https://zoom.us/j/98230650603?pwd=cGNOZ3hwSzNoTWZCV3VYZ3RmL3A3UT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler security-committee SIG invites you to attend the ZOOM conference will be held at 2021-03-24 16:00, The subject of the conference is openEuler安全委员会例会, Summary: 1. 漏洞感知优化进展； 2.社区漏洞处理进展；有其它议题，欢迎申报。 You can join the meeting at https://zoom.us/j/98230650603?pwd=cGNOZ3hwSzNoTWZCV3VYZ3RmL3A3UT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

virt sig例会0326
by openEuler conference 25 Mar '21

25 Mar '21

1 0

Re: [Community] Compiler SIG双周例会【会议纪要】
by hedongbo 24 Mar '21

24 Mar '21

会议纪要 MEETING MINUTES 主题 Subject Compiler SIG双周例会时间 Date & Time 2021年03月23日星期二 10:00-11:00 地点 Location 线上会议与会者 Attendees jianningsheng(ARM)、gongxiaohong(ARM)、Eric(ARM)、李兵（保兰德）、郭杰（保兰德）、詹年科（保兰德）、郭建兴（麒麟），刘老师（麒麟）、程鑫鑫、彭成寒、王篁、张高峰、艾佳明、贺东博纪要者 Note Taker 贺东博议题一：SVE开发进展(jianningsheng, gongxiaohong, 王篁) 1. Extract和剩下的cast类型已全部完成，并将代码提交至openjdk社区. 详见JDK-8263001，JDK-8263348 ，JDK-8263417，JDK-8263644 2. 讨论接下来要做的内容，以及开发过程中遇到的问题 3．SVE代码进JDK17问题：由于在社区进行reivew和测试时间较长，可能有一部分代码无法进入jdk17，但SVE后端和目前Huawei 进行的工作可以进入jdk17 议题二：KAE Provider开发进展（李兵、彭成寒、张高峰、贺东博） 1．第一阶段代码已提交至码云，包括功能和测试代码，详见https://gitee.com/openeuler/bishengjdk-8/pulls/27/… Huawei 方面介绍了KAE Provider的代码框架以及如何使用 2．探讨接下来要完成的内容：譬如通过开关来控制是否写日志，在手册中说明如何对java.security进行改性等议题三：版本发布（贺东博） 1．此版本相关feature和优化已全部提交至码云，详见https://gitee.com/openeuler/bishengjdk-8/pulls?… https://gitee.com/openeuler/bishengjdk-11/pulls?assignee_id=&author_id=&lab… 2．二进制会在月底前发布。议题四：和麒麟同事讨论如何集成BiSheng JDK (郭老师，刘老师，彭成寒，贺东博) 1．讨论在麒麟上集成BiSheng JDK后，用户如何安装其他版本JDK 2．介绍openeuler上怎么管理BiSheng JDK相关的patch 待跟进问题： 1．二进制发布后，需要将优化和feature更新到Bisheng JDK的release note中。--东博 2．确认为什么src-openeuler中的包名为openjdk，而不命名为Bisheng. –东博会议录屏已自动上传至B站: https://www.bilibili.com/video/BV1964y1U7pY?from=search&seid=67129390060176… From: openEuler conference [mailto:public@openeuler.io] Sent: Friday, March 19, 2021 12:52 PM To: dev(a)openeuler.org; wanghuang <wanghuang3(a)huawei.com>; pengchenghan <pengchenghan(a)huawei.com>; zhanggaofeng (C) <zhanggaofeng9(a)huawei.com> Subject: [Community] Compiler SIG双周例会您好！ openEuler Compiler SIG 邀请您参加 2021-03-23 10:00 召开的ZOOM会议(自动录制) 会议主题：Compiler SIG双周例会会议内容：1:SVE开发进展 2:KAEProvider开发进展 3:版本发布欢迎上报议题。新增议题直接回复邮件即可！会议链接：https://zoom.us/j/99363855954?pwd=Qm9pZ2VqcllWSnI5R1daUlVCL3NHdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Compiler SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-23 10:00, The subject of the conference is Compiler SIG双周例会, Summary: 1:SVE开发进展 2:KAEProvider开发进展 3:版本发布欢迎上报议题。新增议题直接回复邮件即可！ You can join the meeting at https://zoom.us/j/99363855954?pwd=Qm9pZ2VqcllWSnI5R1daUlVCL3NHdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

sig-Bio 例会议题征集回复：[Tc] 回复：sig-BIO双周例会
by zhouzhongyuan96 24 Mar '21

24 Mar '21

在2021年3月23日 12:48，Shao-Jie Zhang<1993zsj123(a)163.com> 写道：申报议题：生物信息在群体遗传上的应用及具体课题成果分享张少杰在 2021-03-23 11:38:36，"zhouzhongyuan96" <zhouzhongyuan96(a)163.com> 写道：申报议题： GCTA软件技术分享，以及适配arm64架构的问题讨论 ——杨剑、周中元在2021年3月23日 10:34，openEuler conference<public(a)openeuler.io> 写道：您好！ openEuler sig-bio SIG 邀请您参加 2021-03-25 10:00 召开的ZOOM会议(自动录制) 会议主题：sig-BIO双周例会会议内容：sig-BIO双周例会，欢迎申报议题。会议链接：https://zoom.us/j/97645198641?pwd=K01IUDBrSEpTNVZoMzVVZUQzVk1BQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-bio SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-25 10:00, The subject of the conference is sig-BIO双周例会, Summary: sig-BIO双周例会，欢迎申报议题。 You can join the meeting at https://zoom.us/j/97645198641?pwd=K01IUDBrSEpTNVZoMzVVZUQzVk1BQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information

1 0

Re: [Tc] openEuler安全委员会例会
by Yanxiaobing 24 Mar '21

24 Mar '21

议题刷新: 1.漏洞感知优化进展；软件所-闫志全 2.社区漏洞处理进展；华为-颜小兵 3.CVE报备评审；华为-杨丽锦 4.CVRF格式SA对接分享；麒麟-崔雷 5.openEuler漏洞指标看板进展；华为-汪奕如 From: Liujingang (Bob) Sent: Tuesday, March 23, 2021 9:31 AM To: 崔雷 <cuilei(a)kylinos.cn>; Yanxiaobing <yanxiaobing(a)huawei.com> Cc: openEuler conference <public(a)openeuler.io>; dev(a)openEuler.org; openEuler-security(a)openEuler.org; tc(a)openEuler.org Subject: RE: [Tc] openEuler安全委员会例会申报一个议题： cvrf格式SA对接情况分享麒麟-崔雷 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, March 22, 2021 8:35 PM To: dev(a)openEuler.org<mailto:dev@openEuler.org>; openEuler-security(a)openEuler.org<mailto:openEuler-security@openEuler.org>; tc(a)openEuler.org<mailto:tc@openEuler.org> Subject: [Tc] openEuler安全委员会例会您好！ openEuler security-committee SIG 邀请您参加 2021-03-24 16:00 召开的ZOOM会议会议主题：openEuler安全委员会例会会议内容：1. 漏洞感知优化进展； 2.社区漏洞处理进展；有其它议题，欢迎申报。会议链接：https://zoom.us/j/98230650603?pwd=cGNOZ3hwSzNoTWZCV3VYZ3RmL3A3UT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler security-committee SIG invites you to attend the ZOOM conference will be held at 2021-03-24 16:00, The subject of the conference is openEuler安全委员会例会, Summary: 1. 漏洞感知优化进展； 2.社区漏洞处理进展；有其它议题，欢迎申报。 You can join the meeting at https://zoom.us/j/98230650603?pwd=cGNOZ3hwSzNoTWZCV3VYZ3RmL3A3UT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

Re: 【会议纪要】[Community] sig-confidential-computing双周例会
by chenmaodong 24 Mar '21

24 Mar '21

会议纪要： 1、介绍当前21.03版本中secGear软件包结构； 2、介绍21年路标TLS特性的能力、合入情况和上游社区反馈情况； 3、兰州大学网络空间安全研究院团队介绍团队情况； 4、全国信息安全竞赛队伍介绍参赛题目，讨论用机密计算保护关键数据的策略； a) 建议在sig下建立repo仓单独跟踪竞赛事项。 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, March 22, 2021 2:34 PM To: dev(a)openeuler.org; xinl(a)lzu.edu.cn Subject: [Community] sig-confidential-computing双周例会您好！ openEuler sig-confidential-computing SIG 邀请您参加 2021-03-23 16:00 召开的ZOOM会议(自动录制) 会议主题：sig-confidential-computing双周例会会议内容：1、21.03版本集成secgear进度及特性介绍 2、兰州大学团队基于机密计算的项目研究介绍会议链接：https://zoom.us/j/98670858010?pwd=QTBraTUzd2NkaDRGbXJpeEpJbGZYUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-confidential-computing SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-23 16:00, The subject of the conference is sig-confidential-computing双周例会, Summary: 1、21.03版本集成secgear进度及特性介绍 2、兰州大学团队基于机密计算的项目研究介绍 You can join the meeting at https://zoom.us/j/98670858010?pwd=QTBraTUzd2NkaDRGbXJpeEpJbGZYUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

CloudNative SIG 双周例会
by openEuler conference 24 Mar '21

24 Mar '21

1 0

QA-sig双周例会
by openEuler conference 23 Mar '21

23 Mar '21

1 0

sig-BIO双周例会
by openEuler conference 23 Mar '21

23 Mar '21

2 1

sig-ai-bigdata regular meeting
by openEuler conference 23 Mar '21

23 Mar '21

1 0

openEuler安全委员会例会
by openEuler conference 22 Mar '21

22 Mar '21

1 0

openEuler社区双周例会
by openEuler conference 22 Mar '21

22 Mar '21

1 0

Infra-Sig双周例会
by openEuler conference 22 Mar '21

22 Mar '21

1 0

sig-confidential-computing双周例会
by openEuler conference 22 Mar '21

22 Mar '21

1 0

openEuler 21.03创新版本 RC4转测试通知
by Xuxiaosong 21 Mar '21

21 Mar '21

转测试计划比原计划有1天延期。请相关责任人最晚于2021-3-22前完成特性进展更新为正常状态。 RC4版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-21-06-55-… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 21.03-RC4）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-21.03/… RC4已解决问题单70个，有4 issue待办，详见： https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&milest… https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&issue_… https://gitee.com/open_euler/dashboard/issues?issue_type_id=118738&sort=cre… Release plan Stange name Begin time End time Kernel update 5.10 2020-10-20 2020-10-30 Key feature collect 2020-10-10 2020-12-15 Kernel freezing 2020-12-21 2020-12-30 Key feature freezing 2021-1-22 2021-1-22 Build beta branch 2021-2-1 2022-2-22 Beta test round 1 2021-2-24 2021-3-2 Beta test round 2 2021-3-5 2021-3-11 Beta test round 3 2021-3-15 2021-3-19 Beta test round 4（we are here） 2021-3-20 2021-3-20 release 2021-3-25 2021-3-26 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 openEuler 21.03 support openStack<https://gitee.com/openeuler/release-management/issues/I25Y6B?from=project-i…> Testing sig-openstack @joec88<https://gitee.com/joec88> @liksh<https://gitee.com/liksh> 2 openEuler 21.03 support virtualization live migration pro<https://gitee.com/openeuler/release-management/issues/I25ZB1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 3 openEuler 21.03 support StratoVirt function enhancement<https://gitee.com/openeuler/release-management/issues/I25ZH0?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 4 openEuler 21.03 support Risc-v virt live migration<https://gitee.com/openeuler/release-management/issues/I25ZF1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 5 openEuler 21.03 support DDE<https://gitee.com/openeuler/release-management/issues/I27TT4?from=project-i…> Testing sig-DDE @panchenbo<https://gitee.com/panchenbo> 6 openEuler 21.03 kernel update to version 5.10<https://gitee.com/openeuler/release-management/issues/I27YGU?from=project-i…> Testing sig-kernel @XieXiuQi<https://gitee.com/xiexiuqi> 7 openEuler 21.03 remove python 2 from release<https://gitee.com/openeuler/release-management/issues/I29EV9?from=project-i…> Testing sig-python-modules @yaqiangchen<https://gitee.com/yaqiangchen> 8 openEuler 21.03 support xfce 4.14<https://gitee.com/openeuler/release-management/issues/I29LTB?from=project-i…> Testing xfce @dillon_chen<https://gitee.com/dillon_chen> 9 openEuler 21.03 support GNOME 3.38.1<https://gitee.com/openeuler/release-management/issues/I29LTT?from=project-i…> Reject GNOME @dillon_chen<https://gitee.com/dillon_chen> 10 openEuler 21.03 Increase the dependency library of ROS-base<https://gitee.com/openeuler/release-management/issues/I2D19V?from=project-i…> Reject sig-ROS @anchuanxu<https://gitee.com/anchuanxu> 11 openEuler 21.03 support memig<https://gitee.com/openeuler/release-management/issues/I2C2NY?from=project-i…> Testing memig @liuzhiqiang26<https://gitee.com/liuzhiqiang26> 12 openEuler 21.03 support replace vender info<https://gitee.com/openeuler/release-management/issues/I2C2JJ?from=project-i…> Testing Builder @t.feng<https://gitee.com/t.feng> 13 openEuler 21.03 support nvwa<https://gitee.com/openeuler/release-management/issues/I2B057?from=project-i…> Testing sig-ops @EulerOSWander<https://gitee.com/EulerOSWander> 14 openEuler 21.03 support secGear<https://gitee.com/openeuler/release-management/issues/I2B0KY?from=project-i…> Testing sig-confidential-computing @chenmaodong<https://gitee.com/chenmaodong> 15 openEuler 21.03 support RaspberryPi<https://gitee.com/openeuler/release-management/issues/I2CVE3> Testing sig-RaspberryPi @woqidaideshi<https://gitee.com/woqidaideshi> 16 openEuler 21.03 support UKUI<https://gitee.com/openeuler/release-management/issues/I2E61C> Testing sig-UKUI @dou33<https://gitee.com/dou33> 17 openEuler 21.03 support HA<https://gitee.com/openeuler/release-management/issues/I2E5R3?from=project-i…> Testing sig-HA @yangzhao_kl<https://gitee.com/yangzhao_kl> 18 openEuler 21.03 support StratoVirt microvm image<https://gitee.com/openeuler/release-management/issues/I2P83D?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 19 openEuler 21.03 support Kubernetes<https://gitee.com/openeuler/release-management/issues/I2CMA0?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 20 openEuler 21.03 support KubeSphere<https://gitee.com/openeuler/release-management/issues/I34L4L> Reject sig-kubesphere @feynmanzhou<https://gitee.com/feynmanzhou> 21 openEuler 21.03 update SPDK<https://gitee.com/openeuler/release-management/issues/I35A62> Testing Storage @liuzhiqiang<https://gitee.com/liuzhiqiang26> 22 openEuler 21.03 update some software<https://gitee.com/openeuler/release-management/issues/I35BTA> Testing release-management @chenyaqiang<https://gitee.com/yaqiangchen> 23 openEuler 21.03 slim container base image<https://gitee.com/openeuler/release-management/issues/I35D25> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 历史转测试版本取用链接 RC3版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-14-07-55-…

1 0

[X-diagnosis][PATCH] cpu: add cpuload for debug cpu usage
by Zhoukang (A) 20 Mar '21

20 Mar '21

From 40fbbe466f421bc8534325e60b4369dcff7626ac Mon Sep 17 00:00:00 2001 From: zhoukang <zhoukang7(a)huawei.com> Date: Sat, 20 Mar 2021 07:07:58 +0000 Subject: [PATCH] cpu: add cpuload for debug cpu usage cpuload calculates the cpu usage, showing which tasks run out of cpu resource. It display top N tasks when the cpu usage exceeds more than P% and calculates every T ms. This works by tracing the sched switch events using tracepoints. Since this uses BPF, only the root user can use this tool. optional arguments: -h, --help show this help message and exit -t TIME, --time TIME interval to calculate, default 1000 -n NUMBER, --number NUMBER maximum tasks to print, default 3 -p PERCENT, --percent PERCENT minimum percent to print, default 30 example: [root@localhost ~]# ./cpuload.py -p 50 -n 2 -t 100 Tracing task switch. Output when cpu is overload. Ctrl-C to end. DATE COMM PID CPU TIME(ms) %CPU 2021-01-27 10:40:39 stress-ng-cpu 33179 1 100.529 96.68% 2021-01-27 10:40:39 cpuload.py 395575 1 3.363 03.23% 2021-01-27 10:40:39 stress-ng-cpu 33175 3 107.704 99.73% 2021-01-27 10:40:39 sshd 2259 3 0.226 00.21% 2021-01-27 10:40:39 stress-ng-cpu 33176 0 131.978 99.99% 2021-01-27 10:40:39 kworker/0:0 388650 0 0.017 00.01% 2021-01-27 10:40:39 stress-ng-cpu 33178 2 183.987 99.99% 2021-01-27 10:40:39 kworker/2:0 391880 2 0.011 00.01% Signed-off-by: Liu Chao <liuchao173(a)huawei.com> --- doc/cpuload.en.md | 43 ++++++++++ doc/cpuload.md | 13 +++ src/cpu/cpuload.py | 197 +++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 253 insertions(+) create mode 100644 doc/cpuload.en.md create mode 100644 doc/cpuload.md create mode 100755 src/cpu/cpuload.py diff --git a/doc/cpuload.en.md b/doc/cpuload.en.md new file mode 100644 index 0000000..2c37567 --- /dev/null +++ b/doc/cpuload.en.md @@ -0,0 +1,43 @@ +# cpuload + +The CPU usage detection tool cpuload can be used to print processes with high CPU usage. +Implementation principle: Use the bcc tool to accurately trace scheduling tracks and collect statistics on processes with high CPU usage. +python /usr/share/bcc/tools/cpuload +-t Interval for calculating the CPU usage. The value ranges from 0 to 60000, in milliseconds. If the value is 0, thread information is printed each time a scheduling occurs. The default value is 1000. +-n Displays the top CPU usage. The default value is 3. +-p Sets the CPU usage threshold. When the CPU usage exceeds the threshold, the system displays information. The value ranges from 0 to 100. The default value is 90. +-m Sets the size of the circular buffer for recording scheduling tracks. 1000 to 1000000. The default value is 10000. + + +cpuload calculates the cpu usage, showing which tasks run out of cpu resource. + +It display top N tasks when the cpu usage exceeds more than P% and calculates +every T ms. + +This works by tracing the sched switch events using tracepoints. + +Since this uses BPF, only the root user can use this tool. + +optional arguments: + -h, --help show this help message and exit + -t TIME, --time TIME interval to calculate, default 1000 + -n NUMBER, --number NUMBER + maximum tasks to print, default 3 + -p PERCENT, --percent PERCENT + minimum percent to print, default 30 + +example: +[root@localhost ~]# ./cpuload.py -p 50 -n 2 -t 100 +Tracing task switch. Output when cpu is overload. Ctrl-C to end. +DATE COMM PID CPU TIME(ms) %CPU +2021-01-27 10:40:39 stress-ng-cpu 33179 1 100.529 96.68% +2021-01-27 10:40:39 cpuload.py 395575 1 3.363 03.23% +2021-01-27 10:40:39 stress-ng-cpu 33175 3 107.704 99.73% +2021-01-27 10:40:39 sshd 2259 3 0.226 00.21% +2021-01-27 10:40:39 stress-ng-cpu 33176 0 131.978 99.99% +2021-01-27 10:40:39 kworker/0:0 388650 0 0.017 00.01% +2021-01-27 10:40:39 stress-ng-cpu 33178 2 183.987 99.99% +2021-01-27 10:40:39 kworker/2:0 391880 2 0.011 00.01% + + + diff --git a/doc/cpuload.md b/doc/cpuload.md new file mode 100644 index 0000000..c56af1f --- /dev/null +++ b/doc/cpuload.md @@ -0,0 +1,13 @@ +# cpuload + +CPU冲高检测工具cpuload，使用该工具能够将CPU使用率高的进程打印出来。 +实现原理, 通过bcc工具精确trace调度轨迹, 统计分析CPU占用率高的进程; + +```shell +python /usr/share/bcc/tools/cpuload +-t 计算CPU使用率的周期。单位为毫秒，取值为0~60000，取0则每次发生调度都会打印出线程的信息，默认值为1000。 +-n 打印CPU使用率top。默认值为3。 +-p 设置CPU使用率的水线，超过时打印。0~100，默认值为90。 +-m 设置记录调度轨迹的循环缓冲区大小。1000~1000000，默认值为10000。 +``` + diff --git a/src/cpu/cpuload.py b/src/cpu/cpuload.py new file mode 100755 index 0000000..47062e9 --- /dev/null +++ b/src/cpu/cpuload.py @@ -0,0 +1,197 @@ +#!/usr/bin/python +# @lint-avoid-python-3-compatibility-imports +# +# cpuload Display top N tasks use more than U percent cpu resource when +# the cpu doesn't enter idle state for more than T ms. +# +# USAGE: cpuload [-h] [-t time] [-n number] [-p percent_limit] [-m max_entry] +# +# This uses in-kernel eBPF maps to cache task details (PID and comm) by +# sched_switch, as well as a running time for calculating cpu usage. + +from __future__ import print_function +from bcc import BPF +from bcc.utils import printb +import argparse +from datetime import datetime + +# arguments +examples = """examples: + ./cpuload # display tasks when cpu overload + ./cpuload -t 100 # calculate cpu usage every 100 ms + ./cpuload -n 5 # display top 5 tasks details + ./cpuload -p 30 # display tasks when cpu usage exceeds 30% + ./cpuload -m 10000 # set the maximum number of entry to 10,000 +""" +parser = argparse.ArgumentParser( + description="display tasks when cpu overload", + formatter_class=argparse.RawDescriptionHelpFormatter, + epilog=examples) +parser.add_argument("-t", "--time", default=1000, + help="interval for calculating the CPU usage, in milliseconds(0 - 60000), default 1000") +parser.add_argument("-n", "--number", default=3, + help="display top n tasks with high cpu usage, default 3") +parser.add_argument("-p", "--percent_limit", default=90, + help="display when the usage of a cpu exceeds percent_limit(0 - 100), default 90") +parser.add_argument("-m", "--max_entry", default=10000, + help="size of the cyclic buffer for recording the scheduling track(1000 - 1000000), default 10000") +parser.add_argument("--ebpf", action="store_true", + help=argparse.SUPPRESS) +args = parser.parse_args() +time_ms = int(args.time) +time_ns = time_ms * 1000000 +number = int(args.number) +percent_limit = int(args.percent_limit) +max_entry = int(args.max_entry) +debug = 0 + +if time_ms > 60000 or time_ms < 0: + print("time invalid") + exit(1) + +if percent_limit > 100 or percent_limit < 0: + print("percent_limit invalid") + exit(1) + +if max_entry > 1000000 or max_entry < 1000: + print("max_entry invalid") + exit(1) + +# define BPF program +bpf_text = """ +#include <linux/sched.h> + +#define MAX_TIME """ + str(time_ns) + """ +#define THRESHOLD """ + str(percent_limit) + """ +#define MAX_ENTRY """ + str(max_entry) + """ + +struct cpu_data_t { + u32 index; + u32 number; + u64 prev_time; + u64 busy_time; + u64 total_time; +}; + +struct task_data_t { + u32 pid; + char comm[TASK_COMM_LEN]; + u64 delta; +}; + +struct data_t { + u32 index; + u32 number; + u64 total_time; +}; + +BPF_PERCPU_ARRAY(cpu_data, struct cpu_data_t, 1); + +BPF_PERCPU_ARRAY(task_data, struct task_data_t, MAX_ENTRY); + +BPF_PERF_OUTPUT(events); +TRACEPOINT_PROBE(sched, sched_switch) { + u32 index = 0; + u64 now = bpf_ktime_get_ns(), delta; + struct data_t data = {}; + struct cpu_data_t *cpu = cpu_data.lookup(&index); + struct task_data_t *task; + + if (cpu == NULL) + return 0; + + if (cpu->prev_time == 0) { + cpu->prev_time = now; + return 0; + } + + index = (cpu->index + cpu->number) % MAX_ENTRY; + task = task_data.lookup(&index); + if (task == NULL) + return 0; + + delta = now - cpu->prev_time; + if (args->prev_pid != 0) { + cpu->busy_time += delta; + task->pid = args->prev_pid; + __builtin_memcpy(&task->comm, &args->prev_comm, sizeof(task->comm)); + task->delta = now - cpu->prev_time; + cpu->number++; + } + + cpu->prev_time = now; + cpu->total_time += delta; + + if (cpu->total_time > MAX_TIME || cpu->number == MAX_ENTRY) { + if (cpu->busy_time * 100 > cpu->total_time * THRESHOLD) { + data.index = cpu->index; + data.number = cpu->number; + data.total_time = cpu->total_time; + events.perf_submit(args, &data, sizeof(data)); + cpu->index = (index + 1) % MAX_ENTRY; + } + cpu->number = 0; + cpu->busy_time = 0; + cpu->total_time = 0; + cpu->prev_time = now; + } + + return 0; +} +""" + +if debug or args.ebpf: + print(bpf_text) + if args.ebpf: + exit() + +# initialize BPF +b = BPF(text=bpf_text) + +print("Tracing task switch. Output when cpu is overload. Ctrl-C to end.") + +print("%-19s %-14s %-7s %-4s %-8s %-5s" % + ("DATE", "COMM", "PID", "CPU", "TIME(ms)", "%CPU")) + +# process event +def print_event(cpu, data, size): + date = datetime.now().strftime('%Y-%m-%d %H:%M:%S') + data = b["events"].event(data) + dic = {} + tasks = b["task_data"] + if data.total_time < time_ns: + print("max_entry is too small, please set more than %d" % + (max_entry * time_ns / data.total_time)) + for i in range(data.index, data.number + data.index): + task = tasks[i % max_entry][cpu] + entry = dic.get(task.pid) + if entry is not None: + entry.delta += task.delta + else: + dic[task.pid] = task + + count = 0 + for item in sorted(dic.items(), key=lambda x: x[1].delta, reverse=True): + if count >= number: + break + task = item[1] + u = task.delta * 100 / data.total_time + print("%s %-14.14s %-7s %-4s %-8.3f %05.2f%%" % ( + date, + task.comm.decode("utf-8", "replace"), + task.pid, + cpu, + float(task.delta) / 1000000, + u)) + count += 1 + dic.clear() + print("---------------------------------------------------------------") + +# loop with callback to print_event +b["events"].open_perf_buffer(print_event) +while 1: + try: + b.perf_buffer_poll() + except KeyboardInterrupt: + exit() + -- 2.29.2

1 0

Compiler SIG双周例会
by openEuler conference 19 Mar '21

19 Mar '21

1 0

安全技术sig组例会
by openEuler conference 19 Mar '21

19 Mar '21

1 0

openEuler21.03系统诊断会
by openEuler conference 18 Mar '21

18 Mar '21

1 0

openEuler kernel sig meeting
by openEuler conference 17 Mar '21

17 Mar '21

1 0

Progress of openEuler supporting OpenStack Victoria
by Tianhua huang 17 Mar '21

17 Mar '21

Hi all, The openstack sig was working on supporting OpenStack Victoria in openEuler 21.03, and has introduced more than 200 packages into openEuler to support the core projects of OpenStack, such as nova, cinder, neutron, keystone, glance, placement, ironic and horizon. Now we are on beta round test 3 of openEuler 21.03, the openstack sig has already took function and tempest tests for it, the latest daily build version is available here http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-16-18-45-… , you can find the OpenStack packages in EPOL, please have a try if you are interested and contact us if there is any problems. The openstack sig also plans to support several releases of OpenStack in openEuler 20.03-LTS, the top 2 expected releases are Rocky and Train for SP2, hope more discussion and suggestion about this. Please feel free to reply or contact us if you have any suggestions or requirements. Thanks. Regards.

3 2

openEuler release conference
by openEuler conference 17 Mar '21

17 Mar '21

2 1

openEuler release conference
by openEuler conference 17 Mar '21

17 Mar '21

2 1

3/16会议纪要 //RE: CloudNative SIG双周例会
by lujingxiao 17 Mar '21

17 Mar '21

2021/03/16 轮值：caihaomin（jingxiaolu代理）与会人：jingxiaolu、杨昭、叶青龙、统信_gaochong、xingweizheng、wang_wei4、郭峰、zhangke、reganhe、李翔、liuhao、guoxiaoqi、chenyanpan、zhangsong、Eric Yuan、wangfengtu、统信——王策、gaohuatao、侯健 1. 遗留问题闭环 1）基础镜像裁剪完需要跟release SIG进行讨论，争取合入版本（景晓）已与release SIG讨论，整体技术方案和版本节奏上问题不大，需发公告邮件给dev/tc/cloudnative sig；公告已发送，收到一个反馈（王策），会上已沟通。 2）CloudNative 主仓建设推动（钟凯） https://gitee.com/openeuler/cloudnative 已完成建立 3）ceph存储等相关镜像推动，有必要的话看是否需要上TC会议决策(钟凯) 继续遗留 2. 议题 1）21.03版本特性——kubernetes集成&测试进展同步 -- 李翔本地集成测试已完成；测试报告已提供，QA组review中；文档开发中 2）21.03版本特性——etcd集成&测试进展同步 -- 杨昭测试报告已提供。钟凯跟踪下，是否已经可以进入版本？ 3）21.03版本特性——openEuler容器基础镜像裁剪 -- xingweizheng 裁剪之后的PR：https://gitee.com/openeuler/openeuler-os-build/pulls/26 PR待合入 4）集群部署工具介绍 -- liuhao 需要讲清楚场景，以及跟现有开源工具的差异（kubekey/ansible/...） 5）src-openeuler上go语言软件包的vendor库的CVE跟踪方案讨论 -- yanxiaobing/guoxiaoqi src-openeuler 上go 语言开发的开源软件，引用的上游开源软件如果有漏洞，该怎么发现和处理？方案：在 repo根目录下，人工维护依赖包列表文件。安全委员会的漏洞处理工具增加特性去识别依赖包列表文件感知漏洞和提交issue跟踪。 3. 遗留事项 4. 下一次会议安排 - 时间：2021/3/30 16:00 - 轮值主持：jianminw@jianminw 谢谢， jingxiaolu From: Yanxiaobing [mailto:yanxiaobing@huawei.com] Sent: Monday, March 15, 2021 9:47 AM To: cloudnative(a)openeuler.org Cc: dev(a)openeuler.org Subject: [Cloudnative] Re: [Dev] CloudNative SIG双周例会你好，申请新增一个议题，讨论下面这个问题。 src-openeuler 上go 语言开发的开源软件，往往会引用一些其它的上游开源软件，如通过 go.mod 文件申明引入。这些上游开源软件，如果有漏洞发现，对引用它的软件可能有影响，同样需要有ISSUE单跟踪，加于分析并解决。需要讨论一下，如何记录go 语言类软件的对上游软件的依赖关系，并维护好这个关系，以便漏洞感知系统根据这个关系，来推送相关的CVE单。 From: openEuler conference [mailto:public@openeuler.io] Sent: Monday, March 15, 2021 9:23 AM To: dev(a)openeuler.org<mailto:dev@openeuler.org>; cloudnative(a)openeuler.org<mailto:cloudnative@openeuler.org> Subject: [Dev] CloudNative SIG双周例会您好！ openEuler sig-CloudNative SIG 邀请您参加 2021-03-16 16:00 召开的ZOOM会议会议主题：CloudNative SIG双周例会会议内容：1.例行过进展 2.安装部署工具规划和介绍会议链接：https://zoom.us/j/99563455187?pwd=d0lQTUlwN2pKOFdDS3ByaVo5RDJCQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference will be held at 2021-03-16 16:00, The subject of the conference is CloudNative SIG双周例会, Summary: 1.例行过进展 2.安装部署工具规划和介绍 You can join the meeting at https://zoom.us/j/99563455187?pwd=d0lQTUlwN2pKOFdDS3ByaVo5RDJCQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

CLA签署检查规则变更说明
by George 17 Mar '21

17 Mar '21

Hi all: 我们是openEuler社区基础设施团队，根据讨论并参考其他社区实现，特对openEuler社区CLA检查做了如下调整：     1. 之前在Gitee平台合入代码，会检查PR源仓作者在Gitee注册的邮箱是否已签署CLA；   2. 现在改为检查该PR中所包含的所有commit的作者的邮箱；   3. 如果PR包含多位commit作者，需要检查所有的commit作者，任何一位未签署都会打CLA失败标签；   4. 针对合入上游社区patch包（如CVE）场景,由于不能修改commit作者，CLA检查commit提交人；【上述调整的原因】：    因为CLA作为代码贡献者协议，检查对象使用commit作者比使用PR源仓作者更准确；   【如有不一致处理方案】：   建议保持本地git配置的邮箱和Gitee平台上注册的邮箱一致；   因commit作者为本地git配置，若本地git邮箱未签署CLA，可重新使用该邮箱注册Gitee再完成签署；   也可以通过git命令修改git本地配置的邮箱地址为Gitee平台的注册邮箱。   【补充说明】   常见FAQ（https://github.com/opensourceways/test-infra/blob/sync-5-22/prow/gite…

2 1

sig-RaspberryPi例会
by openEuler conference 16 Mar '21

16 Mar '21

2 1

openeuler安全委员会例会
by openEuler conference 16 Mar '21

16 Mar '21

1 0

[X-diagnosis][PATCH] memory: add memtool.sh for glibc memory debug
by Zhoukang (A) 15 Mar '21

15 Mar '21

From b5d0dbaa6bba0f01e24634886fbd06264aad016f Mon Sep 17 00:00:00 2001 From: wangshuo <wangshuo47(a)huawei.com> Date: Mon, 15 Mar 2021 11:37:13 +0000 Subject: [PATCH] memory: add memtool.sh for glibc memory debug glibc memory debug The memory management of the glibc is widely used, but the methods for fault locating are limited. A command-line tool is provided to detect memory leakage of user-mode processes and collect memory distribution information about user-mode processes. Obtains the memory distribution information of user-mode processes. The implementation principle is to use the gcore to save the memory copy of the process, and then analyze the memory allocation of the memory copy. memtool show -p -e -f Detects memory leaks of user-mode processes within a period of time. The implementation principle is to enable the memory trace mechanism of the glibc through the gdb, and then disable the trace function after a period of time. memtool trace -p -t -f --- doc/memtool.en.md | 13 ++ doc/memtool.md | 13 ++ src/memory/memtool.sh | 415 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 441 insertions(+) create mode 100644 doc/memtool.en.md create mode 100644 doc/memtool.md create mode 100755 src/memory/memtool.sh diff --git a/doc/memtool.en.md b/doc/memtool.en.md new file mode 100644 index 0000000..ab6eb43 --- /dev/null +++ b/doc/memtool.en.md @@ -0,0 +1,13 @@ +# memtool + +glibc memory debug +The memory management of the glibc is widely used, but the methods for fault locating are limited. A command-line tool is provided to detect memory leakage of user-mode processes and collect memory distribution information about user-mode processes. + +Obtains the memory distribution information of user-mode processes. +The implementation principle is to use the gcore to save the memory copy of the process, and then analyze the memory allocation of the memory copy. +memtool show -p -e -f + +Detects memory leaks of user-mode processes within a period of time. +The implementation principle is to enable the memory trace mechanism of the glibc through the gdb, and then disable the trace function after a period of time. +memtool trace -p -t -f + diff --git a/doc/memtool.md b/doc/memtool.md new file mode 100644 index 0000000..992ede6 --- /dev/null +++ b/doc/memtool.md @@ -0,0 +1,13 @@ +# memtool + +glibc内存调测 +glibc的内存管理被广泛使用，但调测定位手段有限。现提供一个命令行工具，工具可以检测用户态进程内存泄漏，收集用户态进程内存分布信息。 + +获取用户态进程内存分布信息。 +实现原理是通过gcore保存进程的内存副本, 然后分析内存副本的内存分配情况; +memtool show -p -e -f + +检测用户态进程内存一段时间内的内存泄漏情况。 +实现原理是通过gdb开启glibc的内存trace机制, 然后间隔一段时间后关闭trace; +memtool trace -p -t -f + diff --git a/src/memory/memtool.sh b/src/memory/memtool.sh new file mode 100755 index 0000000..12070b3 --- /dev/null +++ b/src/memory/memtool.sh @@ -0,0 +1,415 @@ +#!/bin/bash + +#Print the usage. +function usage() +{ + echo "This is a debug tool for glibc memory manage, Usage:" + echo " memtool show [options] Show the running process memory distribution" + echo " memtool trace [options] Trace the running process memory leaks" + echo "Selection of options:" + echo " --process, -p Process ID" + echo " --files, -f Path of record files" + echo " --exe, -e Exe filename with its path" + echo " --time, -t Time of trace (sec)" + echo " --help, -h Print this message and then exit" + echo "Examples:" + echo " memtool show -p PID -f path -e filename" + echo " memtool trace -p PID -f path -t time" +} + +function trace() +{ + local process_id=$1 + local limit_time=$2 + local file=$3 + + gdb attach $process_id &> /dev/null << EOF +call setenv("MALLOC_TRACE","$file",1) +call mtrace() +EOF + + if [ $? -eq 0 ];then + echo "start trace sucessed" + else + echo "start trace failed" + return 1 + fi + + while true + do + if [ $limit_time -gt 0 ];then + echo -n "$limit_time sec remaining" + sleep 1 + tput rc + tput ed + let limit_time-- + if [ ! -d /proc/${process_id} ];then + echo "Process does not exist." + return 1 + fi + else + break + fi + done + + gdb attach $process_id &> /dev/null << EOF +call muntrace() +call unsetenv("MALLOC_TRACE") +EOF + + if [ $? -eq 0 ];then + echo "stop trace sucessed" + return 0 + else + echo "stop trace failed" + return 1 + fi +} + +function mm_trace() +{ + local process_id=-1 + local limit_time=-1 + local file="" + + while [ $# -gt 0 ] + do + case "$1" in + -p|--process) + shift + if [ $# -gt 0 ];then + if [ -d /proc/$1 ];then + process_id=$1 + shift + else + echo "Invalid process id" + usage + exit 1 + fi + else + echo "Missing parameters" + usage + exit 1 + fi + ;; + -t|--time) + shift + if [ $# -gt 0 ];then + if [ "$1" -gt 0 ] 2>/dev/null ;then + limit_time=$1 + shift + else + echo "Invalid trace time" + usage + exit 1 + fi + else + echo "Missing parameters" + usage + exit 1 + fi + ;; + -f|--file) + shift + if [ $# -gt 0 ];then + file=$1 + shift + else + echo "Missing parameters" + usage + exit 1 + fi + ;; + + *) + echo "Unrecognized parameters!" + usage + exit 1 + ;; + esac + done + + if [ $process_id -eq -1 ];then + echo "Missing Process ID" + usage + exit 1 + fi + + if [ $limit_time -eq -1 ];then + echo "Missing trace time" + usage + exit 1 + fi + + if [ -z $file ];then + echo "Missing trace file" + usage + exit 1 + else + if [ ! -d ${file%/*} ];then + echo "invalid file path" + exit 1 + fi + fi + + trace $process_id $limit_time ${file}-tmp + + if [ -f ${file}-tmp ];then + touch ${file} + chmod 600 ${file} + mtrace ${file}-tmp > $file + rm -rf ${file}-tmp + fi + + return 0 +} + +#Show the running process memory distribution +function show_mm_distribution +{ + local process_id=$1 + local record_path=$2 + local exe_file=$3 + + gcore -o $record_path/memtool_show_core $process_id &> /dev/null + gdb -q $exe_file $record_path/memtool_show_core* >> $record_path/mm_show_result.txt << EOF +set pagination off +set \$gdb_size_bits = 7 +set \$gdb_malloc_align_mask = 15 +set \$gdb_heap_max_size = 2 * 4 * 1024 * 1024 * sizeof(long) +set \$gdb_loop = 1 +set \$gdb_prev_inuse = 0x0000000000000001 +define print_arena_distribution + if \$argc != 1 + help print_arena_distribution + else + set \$gdb_arena_addr = (mstate)(\$arg0 + 1) + if \$gdb_arena_addr == &main_arena + set \$gdb_top = \$gdb_arena_addr->top + set \$gdb_top_size = \$gdb_arena_addr->top->mchunk_size &~ \$gdb_size_bits + set \$gdb_ptr = (unsigned long)\$gdb_top - \$gdb_arena_addr->system_mem + (unsigned long)\$gdb_top_size + else + set \$gdb_top = \$arg0->ar_ptr->top + if \$arg0->ar_ptr != (mstate) (\$arg0 + 1) + set \$gdb_ptr = (unsigned long)(\$arg0 + 1) + else + set \$gdb_ptr = (unsigned long)((mstate)(\$arg0 + 1) + 1) + end + end + set \$gdb_p = (mchunkptr)((\$gdb_ptr + \$gdb_malloc_align_mask) &~ \$gdb_malloc_align_mask) + set \$loop_stop_flag = 0 + while \$gdb_loop == 1 + if \$loop_stop_flag == 1 + loop_break + end + set \$gdb_start_addr = \$gdb_p + set \$gdb_next_addr = (mchunkptr)((unsigned long)\$gdb_start_addr + \$gdb_start_addr->mchunk_size &~ \$gdb_size_bits) + set \$gdb_end_addr = \$gdb_start_addr + set \$gdb_original_use_flag = \$gdb_next_addr->mchunk_size & \$gdb_prev_inuse + set \$gdb_now_use_flag = \$gdb_next_addr->mchunk_size & \$gdb_prev_inuse + set \$gdb_chunk_num = 0 + set \$gdb_all_chunk_size = 0 + while \$gdb_now_use_flag == \$gdb_original_use_flag + set \$gdb_chunk_num = \$gdb_chunk_num + 1 + set \$gdb_all_chunk_size = \$gdb_all_chunk_size + \$gdb_end_addr->mchunk_size &~ \$gdb_size_bits + set \$gdb_end_addr = \$gdb_next_addr + if \$gdb_end_addr == \$gdb_top + set \$loop_stop_flag = 1 + loop_break + end + if \$gdb_end_addr->mchunk_size == \$gdb_prev_inuse + set \$loop_stop_flag = 1 + loop_break + end + set \$gdb_next_addr = (mchunkptr)((unsigned long)\$gdb_next_addr + \$gdb_next_addr->mchunk_size &~ \$gdb_size_bits) + set \$gdb_now_use_flag = \$gdb_next_addr->mchunk_size & \$gdb_prev_inuse + end + printf "%#lx%#20lx%20ld%20ld%10d\n", \$gdb_start_addr, \$gdb_end_addr, \$gdb_chunk_num, \$gdb_all_chunk_size, \$gdb_original_use_flag + set \$gdb_p = \$gdb_end_addr + end + end +end +document print_arena_distribution +Syntax: print_arena_distribution arena_addr +| Print the arena memory distribution. +end + +define print_mm_distribution + if \$argc != 0 + help print_mm_distribution + else + set \$gdb_heap = (heap_info*)&main_arena - 1 + set \$gdb_thread_num = 1 + printf "\n" + printf "\n" + printf "start addr" + printf " end addr" + printf " chunk num" + printf " all chunk size" + printf " is use\n" + print_arena_distribution \$gdb_heap + set \$gdb_ar_ptr = main_arena.next + while \$gdb_ar_ptr != &main_arena + set \$gdb_thread_num = \$gdb_thread_num + 1 + set \$gdb_heap_ptr = (heap_info *)((unsigned long)\$gdb_ar_ptr->top &~ (\$gdb_heap_max_size - 1)) + while \$gdb_heap_ptr->ar_ptr != (mstate) (\$gdb_heap_ptr + 1) + print_arena_distribution \$gdb_heap_ptr + set \$gdb_heap_ptr = \$gdb_heap_ptr->prev + end + print_arena_distribution \$gdb_heap_ptr + set \$gdb_ar_ptr = \$gdb_ar_ptr->next + end + printf "Printf memory distribution Successfully !" + end +end +document print_mm_distribution +Syntax: print_mm_distribution option + 0 -- Print the help message + nothing -- Print the distribution of memory +end +print_mm_distribution +EOF + rm -f $record_path/memtool_show_core* +} + +function mm_show +{ + local process_id=-1 + local record_path="" + local exe_file="" + + while [ $# -gt 0 ] + do + case "$1" in + -p|--process) + shift + if [ $# -eq 0 ]; then + echo "Missing process id" + usage + exit 1 + else + if [ "$1" -gt 0 ] 2>/dev/null; then + process_id=$1 + shift + else + echo "Invalid process id!" + usage + exit 1 + fi + if [ ! -d /proc/$process_id ]; then + echo "Process do not exist!" + exit 1 + fi + fi + ;; + -f|--files) + shift + if [ $# -eq 0 ]; then + echo "Missing record path" + exit 1 + else + record_path=$1 + if [ ! -d $record_path ]; then + echo "$record_path do not exists, please create it" + usage + exit 1 + fi + record_path=`echo $record_path | sed "s/\/$//g"` + shift + fi + ;; + -e|--exe) + shift + if [ $# -eq 0 ]; then + echo "Missing exe filename" + usage + exit 1 + else + exe_file=$1 + if [ ! -f $exe_file ]; then + echo "Invalid exe filename" + usage + exit 1 + fi + shift + fi + ;; + *) + echo "Unrecognized parameters!" + usage + exit 1 + ;; + esac + done + + if [ $process_id -eq -1 ];then + echo "Missing Process ID" + usage + exit 1 + fi + + if [ "$record_path" == "" ];then + echo "Record path can not be empty!" + usage + exit 1 + fi + + if [ "$exe_file" == "" ];then + echo "Exe filename can not be empty!" + usage + exit 1 + fi + + show_mm_distribution $process_id $record_path $exe_file + + return 0 +} + +#judge whether gdb is installed +which gdb &> /dev/null +if [ $? -ne 0 ]; then + echo "Can not find gdb on this environment" + exit 1 +fi + +#judge whether glibc-debuginfo is installed +ls /usr/lib/debug/sbin/ldconfig.debug &> /dev/null +if [ $? -ne 0 ]; then + echo "Can not find glibc-debuginfo on this environment" + exit 1 +fi + +#judge whether glibc-debugutils is installed +ls /usr/bin/mtrace &> /dev/null +if [ $? -ne 0 ]; then + echo "Can not find glibc-utils on this environment" + exit 1 +fi + +if [ $# -lt 1 ] || [ $# -gt 7 ]; then + usage + exit 1 +fi + +case "$1" in + show) + shift + mm_show "$@" + exit 0 + ;; + trace) + shift + mm_trace "$@" + exit 0 + ;; + -h|--help) + usage + exit 0 + ;; + *) + echo "Unrecognized options!" + usage + exit 1 + ;; +esac + -- 2.29.2

1 0

品牌宣传委员会会议
by openEuler conference 15 Mar '21

15 Mar '21

1 0

openEuler 21.03创新版本 RC3转测试通知
by Xuxiaosong 15 Mar '21

15 Mar '21

请相关责任人最晚于2021-3-17前完成特性进展更新为正常状态。 RC3版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-14-07-55-… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 21.03-RC3）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-21.03/… RC3已解决问题单71个，未解决的问题单78，详见： https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&milest… https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&issue_… Release plan Stange name Begin time End time Kernel update 5.10 2020-10-20 2020-10-30 Key feature collect 2020-10-10 2020-12-15 Kernel freezing 2020-12-21 2020-12-30 Key feature freezing 2021-1-22 2021-1-22 Build beta branch 2021-2-1 2022-2-22 Beta test round 1 2021-2-24 2021-3-2 Beta test round 2 2021-3-5 2021-3-11 Beta test round 3（we are here） 2021-3-15 2021-3-19 Beta test round 4 2021-3-20 2021-3-20 release 2021-3-25 2021-3-26 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 openEuler 21.03 support openStack<https://gitee.com/openeuler/release-management/issues/I25Y6B?from=project-i…> Testing sig-openstack @joec88<https://gitee.com/joec88> @liksh<https://gitee.com/liksh> 2 openEuler 21.03 support virtualization live migration pro<https://gitee.com/openeuler/release-management/issues/I25ZB1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 3 openEuler 21.03 support StratoVirt function enhancement<https://gitee.com/openeuler/release-management/issues/I25ZH0?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 4 openEuler 21.03 support Risc-v virt live migration<https://gitee.com/openeuler/release-management/issues/I25ZF1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 5 openEuler 21.03 support DDE<https://gitee.com/openeuler/release-management/issues/I27TT4?from=project-i…> Testing sig-DDE @panchenbo<https://gitee.com/panchenbo> 6 openEuler 21.03 kernel update to version 5.10<https://gitee.com/openeuler/release-management/issues/I27YGU?from=project-i…> Testing sig-kernel @XieXiuQi<https://gitee.com/xiexiuqi> 7 openEuler 21.03 remove python 2 from release<https://gitee.com/openeuler/release-management/issues/I29EV9?from=project-i…> Testing sig-python-modules @yaqiangchen<https://gitee.com/yaqiangchen> 8 openEuler 21.03 support xfce 4.14<https://gitee.com/openeuler/release-management/issues/I29LTB?from=project-i…> Testing xfce @dillon_chen<https://gitee.com/dillon_chen> 9 openEuler 21.03 support GNOME 3.38.1<https://gitee.com/openeuler/release-management/issues/I29LTT?from=project-i…> Reject GNOME @dillon_chen<https://gitee.com/dillon_chen> 10 openEuler 21.03 Increase the dependency library of ROS-base<https://gitee.com/openeuler/release-management/issues/I2D19V?from=project-i…> Reject sig-ROS @anchuanxu<https://gitee.com/anchuanxu> 11 openEuler 21.03 support memig<https://gitee.com/openeuler/release-management/issues/I2C2NY?from=project-i…> Testing memig @liuzhiqiang26<https://gitee.com/liuzhiqiang26> 12 openEuler 21.03 support replace vender info<https://gitee.com/openeuler/release-management/issues/I2C2JJ?from=project-i…> Testing Builder @t.feng<https://gitee.com/t.feng> 13 openEuler 21.03 support nvwa<https://gitee.com/openeuler/release-management/issues/I2B057?from=project-i…> Testing sig-ops @EulerOSWander<https://gitee.com/EulerOSWander> 14 openEuler 21.03 support secGear<https://gitee.com/openeuler/release-management/issues/I2B0KY?from=project-i…> Testing sig-confidential-computing @chenmaodong<https://gitee.com/chenmaodong> 15 openEuler 21.03 support RaspberryPi<https://gitee.com/openeuler/release-management/issues/I2CVE3> Testing sig-RaspberryPi @woqidaideshi<https://gitee.com/woqidaideshi> 16 openEuler 21.03 support UKUI<https://gitee.com/openeuler/release-management/issues/I2E61C> Testing sig-UKUI @dou33<https://gitee.com/dou33> 17 openEuler 21.03 support HA<https://gitee.com/openeuler/release-management/issues/I2E5R3?from=project-i…> Testing sig-HA @yangzhao_kl<https://gitee.com/yangzhao_kl> 18 openEuler 21.03 support StratoVirt microvm image<https://gitee.com/openeuler/release-management/issues/I2P83D?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 19 openEuler 21.03 support Kubernetes<https://gitee.com/openeuler/release-management/issues/I2CMA0?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 20 openEuler 21.03 support KubeSphere<https://gitee.com/openeuler/release-management/issues/I34L4L> Reject sig-kubesphere @feynmanzhou<https://gitee.com/feynmanzhou> 21 openEuler 21.03 update SPDK<https://gitee.com/openeuler/release-management/issues/I35A62> Testing Storage @liuzhiqiang<https://gitee.com/liuzhiqiang26> 22 openEuler 21.03 update some software<https://gitee.com/openeuler/release-management/issues/I35BTA> Testing release-management @chenyaqiang<https://gitee.com/yaqiangchen> 23 openEuler 21.03 slim container base image<https://gitee.com/openeuler/release-management/issues/I35D25> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 历史转测试版本取用链接 RC2版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-04-21-04-…

1 0

openEuler 21.03创新版本 RC3转测试通知
by Xuxiaosong 15 Mar '21

15 Mar '21

请相关责任人最晚于2021-3-17前完成特性进展更新为正常状态。 RC1版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-14-07-55-… 欢迎感兴趣的开发者提前获取验证，对于发现的问题请及时以issue的方式反馈给openEuler社区（里程碑选择openEuler 21.03-RC3）。由本次为发布前测试环节，软件版本可能存在重大问题，不建议大规模使用。 Release计划路径 https://gitee.com/openeuler/release-management/blob/master/openEuler-21.03/… RC1已解决问题单71个，未解决的问题单78，详见： https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&milest… https://gitee.com/open_euler/dashboard/issues?sort=created_at%20desc&issue_… Release plan Stange name Begin time End time Kernel update 5.10 2020-10-20 2020-10-30 Key feature collect 2020-10-10 2020-12-15 Kernel freezing 2020-12-21 2020-12-30 Key feature freezing 2021-1-22 2021-1-22 Build beta branch 2021-2-1 2022-2-22 Beta test round 1 2021-2-24 2021-3-2 Beta test round 2 2021-3-5 2021-3-11 Beta test round 3（we are here） 2021-3-15 2021-3-19 Beta test round 4 2021-3-20 2021-3-20 release 2021-3-25 2021-3-26 Feture list 状态说明：discussion(方案讨论，需求未接受)，developing(开发中)，Testing(测试中)，Reject(未纳入版本) no fetur status sig owner 1 openEuler 21.03 support openStack<https://gitee.com/openeuler/release-management/issues/I25Y6B?from=project-i…> developing sig-openstack @joec88<https://gitee.com/joec88> @liksh<https://gitee.com/liksh> 2 openEuler 21.03 support virtualization live migration pro<https://gitee.com/openeuler/release-management/issues/I25ZB1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 3 openEuler 21.03 support StratoVirt function enhancement<https://gitee.com/openeuler/release-management/issues/I25ZH0?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 4 openEuler 21.03 support Risc-v virt live migration<https://gitee.com/openeuler/release-management/issues/I25ZF1?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 5 openEuler 21.03 support DDE<https://gitee.com/openeuler/release-management/issues/I27TT4?from=project-i…> developing sig-DDE @panchenbo<https://gitee.com/panchenbo> 6 openEuler 21.03 kernel update to version 5.10<https://gitee.com/openeuler/release-management/issues/I27YGU?from=project-i…> Testing sig-kernel @XieXiuQi<https://gitee.com/xiexiuqi> 7 openEuler 21.03 remove python 2 from release<https://gitee.com/openeuler/release-management/issues/I29EV9?from=project-i…> Testing sig-python-modules @yaqiangchen<https://gitee.com/yaqiangchen> 8 openEuler 21.03 support xfce 4.14<https://gitee.com/openeuler/release-management/issues/I29LTB?from=project-i…> developing xfce @dillon_chen<https://gitee.com/dillon_chen> 9 openEuler 21.03 support GNOME 3.38.1<https://gitee.com/openeuler/release-management/issues/I29LTT?from=project-i…> Reject GNOME @dillon_chen<https://gitee.com/dillon_chen> 10 openEuler 21.03 Increase the dependency library of ROS-base<https://gitee.com/openeuler/release-management/issues/I2D19V?from=project-i…> Reject sig-ROS @anchuanxu<https://gitee.com/anchuanxu> 11 openEuler 21.03 support memig<https://gitee.com/openeuler/release-management/issues/I2C2NY?from=project-i…> Testing memig @liuzhiqiang26<https://gitee.com/liuzhiqiang26> 12 openEuler 21.03 support replace vender info<https://gitee.com/openeuler/release-management/issues/I2C2JJ?from=project-i…> Testing Builder @t.feng<https://gitee.com/t.feng> 13 openEuler 21.03 support nvwa<https://gitee.com/openeuler/release-management/issues/I2B057?from=project-i…> Testing sig-ops @EulerOSWander<https://gitee.com/EulerOSWander> 14 openEuler 21.03 support secGear<https://gitee.com/openeuler/release-management/issues/I2B0KY?from=project-i…> Testing sig-confidential-computing @chenmaodong<https://gitee.com/chenmaodong> 15 openEuler 21.03 support RaspberryPi<https://gitee.com/openeuler/release-management/issues/I2CVE3> developing sig-RaspberryPi @woqidaideshi<https://gitee.com/woqidaideshi> 16 openEuler 21.03 support UKUI<https://gitee.com/openeuler/release-management/issues/I2E61C> developing sig-UKUI @dou33<https://gitee.com/dou33> 17 openEuler 21.03 support HA<https://gitee.com/openeuler/release-management/issues/I2E5R3?from=project-i…> developing sig-HA @yangzhao_kl<https://gitee.com/yangzhao_kl> 18 openEuler 21.03 support StratoVirt microvm image<https://gitee.com/openeuler/release-management/issues/I2P83D?from=project-i…> Testing sig-virt @alexchen<https://gitee.com/zhendongchen> 19 openEuler 21.03 support Kubernetes<https://gitee.com/openeuler/release-management/issues/I2CMA0?from=project-i…> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 20 openEuler 21.03 support KubeSphere<https://gitee.com/openeuler/release-management/issues/I34L4L> Reject sig-kubesphere @feynmanzhou<https://gitee.com/feynmanzhou> 21 openEuler 21.03 update SPDK<https://gitee.com/openeuler/release-management/issues/I35A62> Testing Storage @liuzhiqiang<https://gitee.com/liuzhiqiang26> 22 openEuler 21.03 update some software<https://gitee.com/openeuler/release-management/issues/I35BTA> Testing release-management @chenyaqiang<https://gitee.com/yaqiangchen> 23 openEuler 21.03 slim container base image<https://gitee.com/openeuler/release-management/issues/I35D25> Testing sig-cloudnative @jingxiaolu<https://gitee.com/jingxiaolu> 历史转测试版本取用链接 RC2版本取用路径如下： http://121.36.84.172/dailybuild/openEuler-21.03/openeuler-2021-03-04-21-04-…

1 0

合规组例会
by openEuler conference 15 Mar '21

15 Mar '21

1 0

CloudNative SIG双周例会
by openEuler conference 15 Mar '21

15 Mar '21

2 1

会议纪要//答复: A-Tune sig meeting Time: 2021-03-12 10:00-12:00
by hanxinke 12 Mar '21

12 Mar '21

本次sig会议议程： 1、A-Tune 新一年开发路标梳理 2、业界调优技术调研与分享与会人：A-Tune sig组成员（与会人数36人）感谢与各位的线上交流！会议纪要： hanxinke： 1、介绍了A-Tune的开发计划，包括在采集工具、WebUI、调优算法等方面的能力增强 2、梳理了社区伙伴可以加入的参与点，包括新的调优场景、新的调优点、其他OS适配等 3、进行了《ConfAdvisor-云原生线上配置调优框架》论文的分享与交流问题交流以及下一步计划： 1、A-Tune当前还是主要针对物理机和虚拟机的调优，后期会加强对容器场景的调优 2、A-Tune已经支持x86架构，每个版本发布都会做对应的兼容验证 3、外部社区可以参与对新增场景的调优，一方面可以熟悉A-Tune工具的使用，另一方面也可以对A-Tune工具做进一步的优化。遇到问题可以共同探讨 4、A-Tune的应用识别主要还是针对性能比拼场景，因此采集的大多还是高负载压力场景下的数据 5、增加A-Tune-UI的开发指导文档，便于社区开发者参与UI开发 6、针对gcc的编译参数场景，增加重要参数选择的例子 7、WebUI上期待增加各个配置参数对性能影响的曲线图下次sig会议议程：（预计时间：2020-3-26 10:00-12:00）欢迎大家将想要了解的内容或者讨论的议题发送到a-tune(a)openeuler.xn--org-l86ho90g<mailto:欢迎大家将想要了解的内容或者讨论的议题发送到a-tune@openeuler.org邮箱>！敬请期待发件人: hanxinke 发送时间: 2021年3月11日 11:02 主题: A-Tune sig meeting Time: 2021-03-12 10:00-12:00 您好！ openEuler A-Tune SIG 邀请您参加 2021-03-12 10:00 召开的ZOOM会议(自动录制) 会议主题：A-Tune sig meeting 会议内容： 1、A-Tune 新一年开发路标梳理 2、业界调优技术调研与分享会议链接：https://zoom.us/j/99594812311?pwd=Y2FMUURZdHFRTVI4OFdWV2Fpa1RmQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler A-Tune SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-12 10:00, The subject of the conference is A-Tune sig meeting, Summary: 1、A-Tune 新一年开发路标梳理 2、业界调优技术调研与分享 You can join the meeting at https://zoom.us/j/99594812311?pwd=Y2FMUURZdHFRTVI4OFdWV2Fpa1RmQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

openEuler21.03系统诊断会议 2021-03-15 16:00~17:00
by Xuxiaosong 12 Mar '21

12 Mar '21

您好！ openEuler sig-release-management SIG 邀请您参加 2021-03-15 16:00 召开的ZOOM会议会议主题：openEuler21.03系统诊断会会议链接：https://zoom.us/j/98047435816?pwd=Znd3djVJK0VJQUh5bk8xM1ZNNGoxUT09 请大家以邮件的方式反馈议题

1 0

openEuler21.03系统诊断会
by openEuler conference 12 Mar '21

12 Mar '21

1 0

Compiler SIG双周例会
by openEuler conference 12 Mar '21

12 Mar '21

3 2

21.03版本容器基础镜像变更知会/Notification for container base image update on 21.03
by lujingxiao 11 Mar '21

11 Mar '21

Hi all, 当前版本里的容器基础镜像（openEuler-docker.x86_64.tar.xz）规格较大，不便于分发，我们Cloud Native SIG决定对它进行裁剪。裁剪之后的大小是209M（解压后），我们计划将它应用到本月的创新版本21.03。 The base image for container (openEuler-docker.x86_64.tar.xz) on our version is too big for delivery, so we Cloud Native SIG decided to tailor it. After tailoring, the size of base image for container is 209M (uncompressed) and we’re planning to delivery it on the Innovation version of 21.03 this month. 相比较于20.03-SP1，本次裁剪了NetworkManager, net-tools, iproute, systemd等229个软件包裁剪之后的容器基础镜像主要保留了 yum 和procps-ng/vim-minimal/tar 等最常用的129个软件包。只要有yum，大家就可以基于它定制出符合您的场景的应用镜像。这也是主流OS厂商在容器基础镜像上的组建思路。 Compares to 20.03-SP1, 229 rpm packages were tailored including NetworkManager, net-tools, iproute, system, etc. 129 rpm packages including yum and the most popular packages of procps-ng/vim-minimal/tar are saved in the slim version. We believed that, if there is yum and yum repo, you can DIY your own application images base on it. And this is also the main logic for OSVs on constructing there container base images. 如果大家有疑问，请于3/17前联系我们Cloud Native SIG：cloudnative(a)openeuler.org<mailto:cloudnative@openeuler.org> If there’re any doubts, please feel free to contact us before 17th Mar. with: cloudnative(a)openeuler.org<mailto:cloudnative@openeuler.org> 谢谢， Best Regards, 卢景晓/jingxiaolu

1 0

sig-HA双周例会
by openEuler conference 11 Mar '21

11 Mar '21

1 0

A-Tune sig meeting Time: 2021-03-12 10:00-12:00
by hanxinke 11 Mar '21

11 Mar '21

您好！ openEuler A-Tune SIG 邀请您参加 2021-03-12 10:00 召开的ZOOM会议(自动录制) 会议主题：A-Tune sig meeting 会议内容： 1、A-Tune 新一年开发路标梳理 2、业界调优技术调研与分享会议链接：https://zoom.us/j/99594812311?pwd=Y2FMUURZdHFRTVI4OFdWV2Fpa1RmQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler A-Tune SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-03-12 10:00, The subject of the conference is A-Tune sig meeting, Summary: 1、A-Tune 新一年开发路标梳理 2、业界调优技术调研与分享 You can join the meeting at https://zoom.us/j/99594812311?pwd=Y2FMUURZdHFRTVI4OFdWV2Fpa1RmQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information<https://openeuler.org/zh/>

1 0

openEuler21.03系统诊断会议 2021-03-10 17:15~18：15
by Xuxiaosong 10 Mar '21

10 Mar '21

您好！ openEuler sig-release-management SIG 邀请您参加 2021-03-10 17:15 召开的ZOOM会议会议主题：openEuler21.03系统诊断会议会议链接：https://zoom.us/j/95500989253?pwd=dUpkUW85dUZsQ2hPNmhreWx5SlVwZz09 请大家以邮件的方式反馈议题

1 1

openEuler21.03系统诊断会议 2021-03-11 16:00~17：00
by Xuxiaosong 10 Mar '21

10 Mar '21

您好！ openEuler sig-release-management SIG 邀请您参加 2021-03-11 16:00 召开的ZOOM会议(自动录制) 会议主题：openEuler21.03系统诊断会会议链接：https://zoom.us/j/95960590405?pwd=Ty9WcUZwK3pwYlNwb1RJSS9OS3YvUT09 请大家以邮件的方式反馈议题

1 0