April 2021 - Dev - mailweb.openeuler.org

请阅【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