devel August 2022

devel@lists.centos.org

34 participants
20 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redactions, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

Opensourcing the CentOS brand creative work, licensing thoughts
by Alain Reguera Delgado 03 Sep '22

03 Sep '22

Dear community, I would like to bring up this topic once again because it is relevant for the well-being of CentOS visual identity, and its future improvements on the long-term. This mail is probably for Red Hat Liaison, considering the legalities involved in relation to CentOS branding matters. Nevertheless, I would like to keep the discussion open to collect the vast majority of opinions possible about it. Considering the CentOS brand is presently a registered trademark of Red Hat, the exact questions are: 1. Related to CentOS brand changes, and design improvements: What does Red Hat allow the CentOS community to do, and not to do? Here, please, consider the legal and not-legal matters. 2. Would it be possible for Red Hat to explicitly set the license under which the CentOS brand (creative/design) work is released, so to grantee its openness inside the CentOS community? If not, please, elaborate why, and share the expected process to follow in order to keep the brand design relevant through time. I deliberately have collected some thoughts[1] about the recent CentOS brand actualization process but am not sure if they are aligned with Red Hat needs and expectations. The goal here would be to make a very clean and simple statement about how much autonomy does the CentOS community have over its own brand. Also, complement the CentOS Trademark Guidelines[2] document with such information, since there isn't mention of it at the moment. [1] https://gitlab.com/areguera/centos-brand [2] https://www.centos.org/legal/trademarks/ Appreciate your comments. Best regards. -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 4

What to do with wiki.centos.org ? (let's discuss it)
by Fabian Arrotin 30 Aug '22

30 Aug '22

Some time ago, we started to suffer from spammers/load/etc against wiki.centos.org We tried to implement various techniques , found on the moin wiki or elsewhere but we have to face it : moin (http://moinmo.in/) then underlying app for wiki.centos.org, is now unmaintained. Latest version (that we run) is python 2.7 compatible but no plan for python 3, etc, etc For that reason, some SIGs (including Infra SIG), moved already their doc to markdown format, easy to write/review through PR and automatically rendered. The question is so : do we want/need to keep wiki.centos.org running ? Most of the content (if not almost 99%) is outdated/unmaintained at this stage, and deciding what to do about content , and how/where to migrate it would make sense. That's tied to an old infra ticket open a long time ago (https://pagure.io/centos-infra/issue/793) when we had to enabled mod_qos, and other workarounds to just try to keep it running and functional. Let's start a thread/discussion ! @Shaun : as Docs leader, your voice/opinion/feedback would be greatly appreciated ;-) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

13 16

Network Issue on CentOS Infra/services
by Fabian Arrotin 29 Aug '22

29 Aug '22

Hi, We are currently suffering from a flapping network connectivity to the main DC where majority of the CentOS Infra is hosted. After some internal discussion, we confirmed that upstream link provider is aware of the issue and they are looking for a fix (but no ETA) Impacted services: - centos ci - git.centos.org - cbs.centos.org - mirror.centos.org (downstream consumer and having issues pulling content) - mirror.stream.centos.org (downstream consumer and having issues pulling content) - buildlogs.centos.org (same reason) We'll post an update when this will be finally resolved -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

CPE Weekly Update - Week 34 2022
by Michal Konecny 27 Aug '22

27 Aug '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-34-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

2 1

glibc internal ABI changes and CentOS 8 Stream updates on busy systems
by Florian Weimer 26 Aug '22

26 Aug '22

We have recently been made aware that the internal ABI changes due to LD_AUDIT fixes cause processes launched concurrently during the update to crash: glibc: Upgrading to glibc-2.28-209.el8.x86_64 causes segfaults during concurrent process launch <https://bugzilla.redhat.com/show_bug.cgi?id=2119304> In glibc-2.28-211.el8, we have made the ABI changes more compatible with *older* versions (before -208), but this might cause yet another bumpy update from -209 or -210 to -211 or later. (The version ranges are slightly different for s390x; see the bug. ppc64le has a different issue caused by RPM file writing order, but no crashes.) CentOS 9 Stream should be less sensitive to these issues due to the merged libpthread/libdl. We are putting some checks into place to catch this earlier. In general, it might not be possible to avoid such issues completely, particularly on CentOS 8 Stream. The workaround is to do updates in quasi-single-user mode, with as little running on the system as possible. Thanks, Florian

2 1

RabbitMQ eats 1.6GB ram on CentOS Stream 9
by Marcin Juszkiewicz 24 Aug '22

24 Aug '22

As part of OpenStack deployments we deploy RabbitMQ. During current cycle I looked at moving from CentOS Stream 8 to 9. And RabbitMQ is a problem. When I boot CentOS Stream 9 system and then use just built 'rabbitmq' container memory use of "/usr/lib64/erlang/erts-12.3.2.2/bin/beam.smp" process goes up to 1.6GB ram: (rabbitmq)[root@kolla-cs9 /]# rabbitmq-diagnostics memory_breakdown Reporting memory breakdown on node rabbit@kolla-cs9... other_system: 1.6233 gb (68.59%) allocated_unused: 0.5164 gb (21.82%) binary: 0.1551 gb (6.55%) code: 0.0356 gb (1.51%) other_proc: 0.0184 gb (0.78%) connection_other: 0.0037 gb (0.16%) other_ets: 0.0036 gb (0.15%) queue_procs: 0.0021 gb (0.09%) plugins: 0.0021 gb (0.09%) connection_readers: 0.0021 gb (0.09%) atom: 0.0014 gb (0.06%) mgmt_db: 0.001 gb (0.04%) metrics: 8.0e-4 gb (0.03%) connection_writers: 4.0e-4 gb (0.02%) connection_channels: 4.0e-4 gb (0.02%) mnesia: 3.0e-4 gb (0.01%) msg_index: 0.0 gb (0.0%) quorum_ets: 0.0 gb (0.0%) stream_queue_procs: 0.0 gb (0.0%) stream_queue_replica_reader_procs: 0.0 gb (0.0%) queue_slave_procs: 0.0 gb (0.0%) quorum_queue_procs: 0.0 gb (0.0%) stream_queue_coordinator_procs: 0.0 gb (0.0%) reserved_unallocated: 0.0 gb (0.0%) If I boot the same container on Debian host then same process uses 0.2GB ram: (rabbitmq)[root@debian /]# rabbitmq-diagnostics memory_breakdown Reporting memory breakdown on node rabbit@debian... binary: 0.2787 gb (70.2%) code: 0.0355 gb (8.93%) other_system: 0.0255 gb (6.44%) other_proc: 0.0209 gb (5.26%) connection_other: 0.0108 gb (2.72%) mgmt_db: 0.0073 gb (1.84%) plugins: 0.0048 gb (1.2%) other_ets: 0.0037 gb (0.93%) connection_readers: 0.003 gb (0.75%) queue_procs: 0.0028 gb (0.7%) atom: 0.0015 gb (0.37%) metrics: 0.0011 gb (0.28%) connection_channels: 8.0e-4 gb (0.21%) mnesia: 4.0e-4 gb (0.1%) connection_writers: 2.0e-4 gb (0.05%) msg_index: 0.0 gb (0.01%) quorum_ets: 0.0 gb (0.01%) stream_queue_procs: 0.0 gb (0.0%) stream_queue_replica_reader_procs: 0.0 gb (0.0%) queue_slave_procs: 0.0 gb (0.0%) quorum_queue_procs: 0.0 gb (0.0%) stream_queue_coordinator_procs: 0.0 gb (0.0%) allocated_unused: 0.0 gb (0.0%) reserved_unallocated: 0.0 gb (0.0%) So I started checking. Maybe it is a problem of Erlang/RabbitMQ packages provided by RabbitMQ team? Booted CS9 system and deployed OpenStack using Debian based containers. Again 1.6GB memory use. So let build CS9 based containers using Erlang/RabbitMQ from CentOS Stream 9 "messaging/rabbitmq-38" repository. Again 1.6GB memory use. I am wondering what is a reason? And what is proper solution? For now I only know not-acceptable solution: deploy OpenStack using Debian or Ubuntu and forget about CentOS Stream 9 and rest of RHEL 9 family.

4 6

CentOS Cloud SIG meeting minutes (2022-08-11)
by Alfredo Moralejo Alonso 24 Aug '22

24 Aug '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-08-11) ====================================================== Meeting started by amoralej at 15:01:25 UTC. The full logs are available athttps://www.centos.org/minutes/2022/August/centos-meeting.2022-08-11-15.0… . Meeting summary --------------- * OKD/SCOS Update (amoralej, 15:04:38) * OKD (OpenShift community edition) team is working in a new variant that runs on CentOS Stream 9 CoreOS (amoralej, 15:07:25) * OKD team is looking for the best way to provide scos images so that users can use them to run OpenShift community edition or other things (amoralej, 15:17:35) * LINK: https://wiki.centos.org/Events/Dojo/DevConfUS2022 (mcraychee, 15:24:22) * LINK: http://mirror.stream.centos.org/9-stream/NFV/ (aleskandro, 15:38:19) * LINK: http://mirror.stream.centos.org/9-stream/NFV/ (amoralej, 15:42:09) * AGREED: SCOS team will join CloudSIG, welcome! (amoralej, 15:45:02) * ACTION: someone from the CoreOS team should be designated as CloudSIG co-chair (amoralej, 15:45:53) * LINK: https://pbs.twimg.com/profile_images/1455901978194690048/f1_Z6llN_400x400.j… (lorbus, 15:55:45) Meeting ended at 16:00:40 UTC. Action Items ------------ * someone from the CoreOS team should be designated as CloudSIG co-chair Action Items, by person ----------------------- * **UNASSIGNED** * someone from the CoreOS team should be designated as CloudSIG co-chair People Present (lines said) --------------------------- * amoralej (68) * lorbus (56) * travier (23) * spotz84 (22) * aleskandro (9) * mcraychee (9) * centguard (6) * davdunc[m (2) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

3 2

CPE Weekly Update – Week 33 2022
by Michal Konecny 19 Aug '22

19 Aug '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) Week: 15th August - 19th August 2022 If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update---week-33-2022/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-08-17.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * Mass update/reboot cycle this week (stg/nonoutage done, outage later today) * Freeze for f37 beta starts next week ### CentOS Infra including CentOS CI * Discussion around the CentOS Stream infra hand over * New tasks for the CI infra migration * S3 bucket for the Stream CoreOS effort * Some infra projects moved from gitea to gitlab ### Release Engineering * Openh264 composes fo f36,37,38 send to cisco * Package retirement issues after the branching, thanks to human error ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Face to face meeting in Boston. * Penultimate parts of Module process sync. Between el8 and el9. ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 is up to 7339 (+106) packages from 3278 (+71) source packages * Found the bloaty package was uninstallable because of a libre2 soname fix, rebuilding it fixed the issue. ## FMN replacement Goal of this initiative ----------------------- FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC. The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper. Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether. Updates ------- * Frontend * Use CoreUI components * Set up i18n * Initial version of a “New Rule” page * Authentication integration FE/BE (ongoing) * Backend: SQLAlchemy integration (ongoing)) Kindest regards, CPE Team

1 0

Changes to CentOS CI: reminder of Phase 1 and 2
by Camila Granella 16 Aug '22

16 Aug '22

Hello everyone, This is a friendly reminder of the current and upcoming status of CentOS CI changes (check [1]). Projects that opted-in for continuing on CentOS CI have been migrated, and the new Duffy API is available. With that, *phase 0 has been completed*. Regarding *phase 1*, we are still working on a permanent fix for the DB Concurrency issues [2]. Also, as for our OpenShift new deployment, we have a staging environment up and running, and it should be available at the beginning of September 2022. In October 2022 we begin *phase 2* when we will work through the following items (these were also previously communicated in [1]): - legacy/compatibility API endpoint will handover EC2 instances instead of local seamicro nodes (VMs vs bare metal) - bare-metal options will be available through the new API only - legacy seamicro and aarch64/ThunderX hardware are decommissioned - only remaining "on-premises" option is ppc64le (local cloud)Feel free to reach out if you have any questions or concerns The final deadline for decommissioning the old infrastructure (*phase 3*) is *December 2022*. We will be communicating further until then, and meanwhile, reach out to any of us in case you have any questions. Regards, [1] [ci-users] Changes on CentOS CI and next steps: https://lists.centos.org/pipermail/ci-users/2022-June/004547.html [2] DB Concurrency issues: https://github.com/CentOS/duffy/issues/523 -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

1 0

August board meeting recording and office hours
by Shaun McCance 15 Aug '22

15 Aug '22

Hi folks, I've uploaded the recording of last week's board meeting: https://youtu.be/C0Xv33ml3Xo If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, August 18, at 14:00 UTC. https://meet.google.com/hsn-sher-use Email me directly if you need dial-in info instead. This is the day after the Dojo, so many of us will be at DevConf. But I'll run the office hours anyway. I just don't know what the turnout will be. Thanks, Shaun

1 0

CPE Weekly Update – Week 32 2022
by Lenka Segura 12 Aug '22

12 Aug '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) Week: 8th - 12th August 2022 If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/?p=11316 # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-08-10.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * Some great nest talks and discussions, check them out on replay! * Debugging instability in 32bit arm builders again. ;( * Rebalanced the s390x builders. * Business as usual ### CentOS Infra including CentOS CI * koji/cbs.centos.org upgrade complete * Kick off for Stream infra handover to I&R * Adapted ansible baseline role to include workaround for Rsync issue on CentOS Stream 8 * Enabled RHEL9 Buildroots on cbs/koji for SIGs ### Release Engineering * Mass branching yesterday (f37 split off rawhide, which is now f38) ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Git source moved from git.centos.org to gitlab, for c8s modules. ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 is up to 7233 (+106) packages from 3207 (+27) source packages * “State of EPEL” presentation at Nest conference, recording will be posted to YouTube at a later date * EPEL Survey has launched and is available through the end of August https://tinyurl.com/epelsurvey2022 * epel-release has been improved with a recommends on dnf-command(config-manager) to ensure crb enabling script can work out of the box * KDE Plasma updated from 5.23 to 5.24 (LTS release) in epel8-next and epel9-next ## FMN replacement Goal of this initiative ----------------------- FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC. The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper. Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether. Updates ------- * Unit tests/coverage tests on frontend (Vue.js) * Auth/OIDC work on both frontend and backend * Initial backend connection via SQLAlchemy/fastAPI * Basic functionality of connecting to FASJSON * CI improvements and fixes Kindest regards, CPE Team

1 0

nodejs version regression cs8 vs c8
by Leon Fauster 11 Aug '22

11 Aug '22

C8 has nodejs-10.24.0-1.module_el8.3.0+717+fa496f1d.x86_64 CS8 has nodejs-10.23.1-1.module_el8.4.0+645+9ce14ba2 should CentOS Stream 8's package version not be at least == C8? -- Thanks Leon

8 15

infra outage : Stream 9 builsystem
by Fabian Arrotin 11 Aug '22

11 Aug '22

Hi, We got some monitoring alerts that CentOS Stream 9 build infra is actually unreachable. We have an internal ticket open at Red Hat to investigate the issue (seems network related) If you're directly consuming pkgs from that infra (like https://kojihub.stream.centos.org) it's actually unreachable. That means that it also impacts downstream buildsystems, like https://cbs.centos.org, but only if you asked to consume directly pkgs from teh CentOS Stream 9 buildroot. For SIGs only building against content from mirror.stream.centos.org, builds should continue to work. We'll update this thread when we'll have more information. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

[Infra] - Planned outage : cbs.centos.org
by Fabian Arrotin 08 Aug '22

08 Aug '22

We recently received some RFEs for new features for our Community Build System (aka https://cbs.centos.org) on our tracker (https://pagure.io/centos-infra/issues) and some were added in upstream koji projects. So we'll upgrade our koji build environment to latest koji version 1.29.1 (and get same version deployed after for Stream build env too) to then be able to track/test new features for SIGs. Migration is scheduled for """"Monday August 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-08-08 07:00 UTC') The expected "downtime" is estimated to ~5 minutes , time needed for ansible to shutdown kojid builders, upgrade kojihub (cbs.centos.org) run db schema upgrade, restart kojihub and then kojid builders. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

CPE Weekly Update – Week 31 2022
by Lenka Segura 05 Aug '22

05 Aug '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) Week: 1st - 5th August 2022 If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-31-2022 # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-08-03.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * Unblocked osbuild in production, should be working now. (Uses script to keep api ip updated in the firewalls) * Ocp4 cluster api uses valid cert not (for webhooks/external oc) * Disabled systemd-oomd in some places (koji hubs in particular) * Barcamp at nest on saturday: https://hackmd.io/MiWdaZXCRDi4LEO1jmyLDg * Some sysadmin-main additions: Nils, Michal, Ryan ### CentOS Infra including CentOS CI * Duffy CI is now live (so hotfixes are also coming, thanks to Nils) * Preparing CBS/koji upgrade to 1.29 (would unblock other RFEs on tracker) ### Release Engineering * FTBFS bugs filed on failing to build packages * Containers: rawhide fixed/updating, updated f35/f36 ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Meetings about and started code, to move module source from git.centos to gitlab. * New ISOs for CentOS Linux 7 for installation that fixes libtimezonemap (and other) issues. * Rewrote the errata announcement scripts for CentOS Linux 7 to use new endpoints after the decommissioning of the API search/rs/ on access.redhat.com. ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 is up to 7127 (+141) packages from 3180 (+97) source packages * Prepared EPEL survey, it will be promoted on FedoraNest * Provided a fix to nagios-plugins-check-updates to improve distro compatibility ## FMN replacement Goal of this initiative ----------------------- FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC. The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper. Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether. Updates ------- * Frontend auth being developed * Access token and refresh token * Making pages require auth, if user is not authenticated, redirect to login * Backend auth still being developed (tests) * Mockups for UI - bootstrap/HTML/CSS * Agile ceremonies being planned Kindest regards, CPE Team

1 0

Alternate Images - Proposed SIG
by Troy Dawson 04 Aug '22

04 Aug '22

Following the CentOS "Setting up a new SIG"[1] instructions I am opening a new topic about creating a new CentOS SIG. I have initially filled out several sections that are in other SIG pages. These are all open for discussion. Goals: The Alternate Images SIG's goal will be to build and provide alternate iso images for CentOS Stream. What is in Scope: - Live Images (Previously known as LiveDVD, LiveCD) -- Examples: --- Live Desktops (KDE / GNOME / XFCE / Mate ) --- Live Rescue - Alternate Install Images -- Examples: --- Minimum install iso (doesn't need the network, but almost as small as the boot.iso) --- KDE install iso (has epel enabled, and packages to install a working kde desktop) - Repo's that are compatible with CentOS Stream, and follow the Fedora licensing policy. What is not in Scope: - Containers - Raw / QCow / AWS - Iso images that are bigger than 4 Gig. (This number can be adjusted after the SIG is formed) - Repo's that are not compatible with CentOS Stream, or do not follow the Fedora licensing policy. Collaboration: We plan on working with various Desktop SIG's, the Fedora minimization team, and any other group that wants custom iso's. Deliverables: - Documentation along with configuration (kickstarts and scripts) that will allow members to create their alternate images. - Alternate images in a publically downloadable area -- Images will be rebuilt, or retired, a minimum of every three months. Leadership: I (Troy Dawson) will be the initial Lead of the SIG. After (or while) the SIG is formed we will decide if we want a co-chair leadership and/or how often the leadership is elected. Troy Dawson [1] - https://wiki.centos.org/SpecialInterestGroup#Setting_up_a_new_SIG

8 15

Happy Anniversary, CentOS Automotive SIG!
by Jeffrey Osier-Mixon 03 Aug '22

03 Aug '22

Todays' monthly meeting was lightly attended as expected, and we didn't have a lot of technical topics to update, but I did want to send out the one thing we did cover. August marks the 1st anniversary of the CentOS Automotive SIG, and we have accomplished quite a lot over this first year. The first meeting was August 19, 2021, at which time there was no infrastructure at all and the group had just been voted into existence by the CentOS board. Now, one year later, we have a robust repository within the CentOS domain, open to contributions by the public - and indeed we had our first contributor from outside Red Hat over the past month, which is a great example of the value we hope we are bringing to automotive Linux development. In addition to the repositories, we have a strong nightly build structure providing a continuous stream of images that are easy to download and get running via QEMU or on a Raspberry Pi 4. The image uses Stream 9 components with a customized (real time) kernel, a good example of CentOS Stream based development, and a fun and interesting project. Congratulations to everyone involved with the SIG, and thanks again to CentOS for hosting it! Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2022