- Dev - mailweb.openeuler.org

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

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

10 Mar '21

1 0

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

10 Mar '21

1 0

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

10 Mar '21

1 0

TC双周例会
by openEuler conference 09 Mar '21

09 Mar '21

1 0