议题: openEuler OBS 构建 Project Config 及 spec 优化
内容:
OBS 每次构建软件包会创建新的构建环境(build environment),在构建环境中 preinstall 一些必备软件包,然后 install 这些必备软件包及其依赖,以及 spec 中指定的 BuildRequires 及其依赖。当前 preinstall 安装多余软件包,部分软件包 spec 存在多余依赖,导致每次创建构建环境至少需要安装 300+ 个 rpm,占用空间 1.2GB,耗时 60+ 秒。需要对 Project Config 及 spec 进行优化,减少构建过程安装的 rpm 数量,避免 IO 资源浪费,缩短构建时间。
同时去掉软件包 spec 多余依赖,避免安装时间、空间浪费,也避免安装多余 rpm 引入的安全风险。
From: Liujingang (Bob) [mailto:liujingang09@huawei.com]
Sent: Monday, May 10, 2021 9:26 AM
To: tc(a)openeuler.org; dev(a)openeuler.org
Subject: [Tc] Re: TC双周例会
欢迎大家上报议题,当前议题如下:
1、遗留问题跟踪:
2、SIG运作情况分享:
(1)sig-OKD运作情况介绍 杨昭
(2)sig-ONL运作情况介绍 栾建海
(3)Storage运作情况介绍 刘志强
From: openEuler conference [mailto:public@openeuler.io]
Sent: Monday, May 10, 2021 9:11 AM
To: tc(a)openeuler.org<mailto:tc@openeuler.org>; dev(a)openeuler.org<mailto:dev@openeuler.org>
Subject: [Tc] TC双周例会
您好!
openEuler TC SIG 邀请您参加 2021-05-12 10:00 召开的ZOOM会议(自动录制)
会议主题:TC双周例会
会议链接:https://us06web.zoom.us/j/83802136408?pwd=NWVzQStkM1V6bEpkTzFqdEc5cFZidz09
温馨提醒:建议接入会议后修改参会人的姓名,也可以使用您在gitee.com的ID
更多资讯尽在:https://openeuler.org/zh/
Hello!
openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2021-05-12 10:00,
The subject of the conference is TC双周例会,
You can join the meeting at https://us06web.zoom.us/j/83802136408?pwd=NWVzQStkM1V6bEpkTzFqdEc5cFZidz09.
Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com.
More information<https://openeuler.org/zh/>
Hey openEuler developers:
Due to a physical hardware failure on the cloud instance, the delivering functionality of the mailing list became abnormal between 09:00 and 10:00 on May 8, 2021, now the service is online now. If you use the mailing list service during this period, you need to resend the mail again. To avoid similar problems in the future, the Infrastructure team plan to refactor the deloyment architecture to guarantee service SLA. If you still have other problems, please contact us in the following ways:
[1]: https://gitee.com/openeuler/infrastructure/issues
[2]: infra(a)openeuler.org
Gaohechao
openEuler Infrastructure Team
---------------------------------------------------------------------------------------------------------------------------
openEuler社区的开发者:
由于云主机物理硬件故障,在2021年5月8日9:00-10:00期间邮件列表收发邮件功能出现异常,当前系统已经恢复,如果有在此时间段使用邮件列表服务,需要重新发送。 为避免后续类似问题,基础设施小组已经计划对邮件列表做HA改造,保障服务的SLA,如果您在服务使用中还遇到其他问题,请通过以下途径联系我们:
[1]: https://gitee.com/openeuler/infrastructure/issues
[2]: infra(a)openeuler.org
高鹤超
openEuler 基础设施团队
大家好,
我是openEuler社区Infra-Sig组maintainer,近期对openEuler在Gitee上的代码仓库进行梳理,
发现一些不符合预期的代码仓库,需要整改,现将相关事宜知会如下:
1、openEuler社区目前的代码仓库结构:
openEuler社区在Gitee平台有一个对应的Enterprise,名为open_euler
其下有三个组织:
openeuler:用于管理源码仓库,通过https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml配置文件管理
src-openeuler:用于管理二进制仓库,通过https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.yaml配置文件管理
openEuler-competition:用于管理社区竞赛相关代码仓库,通常由相关委员会成员通知Infra-Sig组添加或删除。
2、扫描发现部分社区成员在open_euler Enterprise下创建、Fork了部分仓库,这些仓库不属于三个组织中的任何一个,具体仓库信息见附件。
这部分仓库通常是误操作导致,创建者在创建后又无权限删除,导致仓库残留。后续会禁用直接在企业下创建和Fork仓库的权限。
所以Infra-Sig近期(1周后)将对上述仓库做清理,删除这些直接归属在Enterprise下的仓库。
3、清理原因:仓库占用社区资源且仓库路径容易引起混淆。
4、如何确认是否有自己涉及的仓库:下载附件,在附件中搜索自己的giteeId(注意是giteeId不是Gitee名称)。
如果没有搜索到即不涉及。如果搜索到,但确认不需要该仓库,则无需特殊处理,由Infra-Sig统一清理。
5、如有特殊需求需要保留上述仓库,请联系infra(a)openeuler.xn--org,-t35f38cpymo8g1mtcurqv3bu6ciw0h.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi,
I am the maintainer of Infra-Sig of openEuler community. I recently reviewed the code repository of OpenEuler on the Giitee,
Some code repositories that do not meet expectations are found and need to be rectified. The following issues are notified:
1. The code repository structure of the openEuler community is as follows:
The openEuler community has an enterprise named open_euler on the Gitee platform.
There are three organizations under it:
openeuler: manages the source code repository through the https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml configuration file.
src-openeuler: manages the binary repository through the https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.… configuration file.
openEuler-competition: It is used to manage the code repository related to community competitions. Generally, the relevant committee members notify the Infra-Sig to add or delete the code repository.
2. The scan shows that some community members have created and fork some repositories under open_euler Enterprise. These repositories do not belong to any of the three organizations. For details about the repositories, see the attachment.
These repositories are usually caused by misoperations. After being created, the creator does not have the permission to delete them. As a result, the repositories are residual. The permission to create and fork repositories in the enterprise will be disabled later.
Therefore, Infra-Sig will clean up these repositories in the near future (one week later) and delete these repositories directly belonging to Enterprise.
3. Handling reason: The repository occupies community resources and the repository path is easy to confuse.
4. How to check whether your repository is involved: Download the attachment and search for your giteeId in the attachment (giteeId,not the name).
If no search result is found, this issue is not involved. If the repository is found but is not need, the Infra-Sig deletes the warehouse in a unified manner.
5. If there is a special need to retain the above repositories, please contact infra(a)openeuler.org and explain the reason for retaining the repository.