November 2020 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

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

Reminder: CentOS 6 EOL on 30 November 2020
by Johnny Hughes 03 Dec '20

03 Dec '20

All, This is a friendly reminder. CentOS 6.10 will EOL at the end of November 2020. During the first week in December 2020, the 6.10 directory will move to vault.centos.org Packages will still be available at: http://vault.centos.org/centos/6.10/ However, once moved, there will be no more updates pushed to vault.centos.org. Therefore, security issues will no longer be fixed, etc. You should take the rest of the month to either move to a newer versoin of CentOS Linux ... or to procure Extended el6 support from Red Hat (EUS RHEL 6). Thanks, Johnny Hughes

13 27

Reminder: CFP for FOSDEM Dojo
by Rich Bowen 25 Nov '20

25 Nov '20

Reminder: The CFP for the FOSDEM CentOS Dojo is now open - https://wiki.centos.org/Events/Dojo/FOSDEM2021 - and closes on December 20th. We are tentatively planning for February 4th and 5th, but will scale back to just the 5th if we don't get sufficient submissions. We are looking for talks about: CentOS Linux CentOS Stream and the RHEL contribution workflow Anything that you are doing in the CentOS ecosystem (including, but not limited to: SIG activity, CentOS infra, governance, community, etc) Anything you're doing *on* CentOS - stuff you're running on CentOS, interesting research projects, useful CentOS tools/utilities/techniques. Larger ecosystem topics - Linux, Cloud, Open Source, etc. I encourage you to look at previous event schedules for further inspiration: https://wiki.centos.org/Events/Dojo/Brussels2020 https://wiki.centos.org/Events/Dojo/ORNL2019 https://wiki.centos.org/Events/Dojo/Brussels2019 Thanks! --Rich

1 0

Re: [CentOS-devel] NFS Ganesha (Storage SIG) node fails to boot after fencing
by Strahil Nikolov 24 Nov '20

24 Nov '20

Hi Vit, the generated policy fixes the issue. I've opened an issue at https://github.com/ClusterLabs/fence-agents/issues/368 @Kaleb Keithley , It's already in the previous e-mail and in the issue I just created. Best Regards, Strahil Nikolov В понеделник, 23 ноември 2020 г., 16:28:01 Гринуич+2, Vit Mojzis <vmojzis(a)redhat.com> написа: Hi, based on the policy module generated by audit2allow it seems that this is an issue in the base policy (selinux-policy package). Init_t is only allowed to access files and directories labeled var_lib_nfs_t (and not link_files). But I believe "getattr" permission was added in rhel-8.3. Does the generated policy module (my-systemd) resolve the issue? Vit On 11/23/20 2:54 PM, Kaleb Keithley wrote: > Can you collect any AVC messages from /var/log/audit/audit.log or /var/log/messsages, or dmesg on the host that would only boot after setting enforcing=0? Thanks On Mon, Nov 23, 2020 at 7:55 AM Kaleb Keithley <kkeithle(a)redhat.com> wrote: > > > > > > > > On Sat, Nov 21, 2020 at 4:48 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > >> Hi All, >> >> I have been testing EL8 + NFS Ganesha 3 (from CentOS Storage SIG) and Gluster v8 (tested both Storage SIG rpms and built from source ) and I have noticed a bug in the SELINUX policy causing the system to fail to boot after the node is fenced until a kernel parameter 'enforcing=0' is passed. >> >> The reason seems to be the link "/var/lib/nfs" pointing to the shared storage.When the cluster software is stopped gracefully, no issues are observed,as the nfs_setup resource restores /var/lib/nfs . >> >> Should I open a bug to bugzilla.redhat.com or it's specific to CentOS only ? >> > > > > > Off hand I don't think that's a bug in the nfs-ganesha-selinux package. I've asked the cluster (pacemaker, etc.) devs and the selinux devs what they think. You asked about opening a BZ in bugzilla.redhat.com; but https://github.com/gluster/glusterfs/issues is the correct place to report gluster issues. > > > > > For this though I suggest opening an issue in https://github.com/ClusterLabs/ somewhere, maybe https://github.com/ClusterLabs/fence-agents/issues?? So it doesn't get lost. > > > >> >> More details: >> [root@glustere ~]# rpm -qa | grep ganesha | sort >> centos-release-nfs-ganesha30-1.0-2.el8.noarch >> glusterfs-ganesha-8.2-0.5.git77eb5e838.el8.x86_64 >> nfs-ganesha-3.3-2.el8.x86_64 >> nfs-ganesha-gluster-3.3-2.el8.x86_64 >> nfs-ganesha-selinux-3.3-2.el8.noarch >> >> [root@glustere ~]# dmesg | grep -e type=1300 -e type=1400 >> [ 14.414782] audit: type=1400 audit(1605994499.985:3): avc: denied { getattr } for pid=1 comm="systemd" path="/var/lib/nfs" dev="dm-0" ino=33596932 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_lib_nfs_t:s0 tclass=lnk_file permissive=1 >> >> [root@glustere ~]# dmesg | grep -e type=1300 -e type=1400 | audit2allow -M my-systemd >> ******************** IMPORTANT *********************** >> To make this policy package active, execute: >> >> >> semodule -i my-systemd.pp >> >> >> [root@glustere ~]# cat my-systemd.te >> >> >> module my-systemd 1.0; >> >> >> require { >> type var_lib_nfs_t; >> type init_t; >> class lnk_file getattr; >> } >> >> >> #============= init_t ============== >> allow init_t var_lib_nfs_t:lnk_file getattr; >> >> >> Best Regards, >> Strahil Nikolov >> >> > > >

1 0

NFS Ganesha (Storage SIG) node fails to boot after fencing
by Strahil Nikolov 23 Nov '20

23 Nov '20

Hi All, I have been testing EL8 + NFS Ganesha 3 (from CentOS Storage SIG) and Gluster v8 (tested both Storage SIG rpms and built from source ) and I have noticed a bug in the SELINUX policy causing the system to fail to boot after the node is fenced until a kernel parameter 'enforcing=0' is passed. The reason seems to be the link "/var/lib/nfs" pointing to the shared storage.When the cluster software is stopped gracefully, no issues are observed,as the nfs_setup resource restores /var/lib/nfs . Should I open a bug to bugzilla.redhat.com or it's specific to CentOS only ? More details: [root@glustere ~]# rpm -qa | grep ganesha | sort centos-release-nfs-ganesha30-1.0-2.el8.noarch glusterfs-ganesha-8.2-0.5.git77eb5e838.el8.x86_64 nfs-ganesha-3.3-2.el8.x86_64 nfs-ganesha-gluster-3.3-2.el8.x86_64 nfs-ganesha-selinux-3.3-2.el8.noarch [root@glustere ~]# dmesg | grep -e type=1300 -e type=1400 [ 14.414782] audit: type=1400 audit(1605994499.985:3): avc: denied { getattr } for pid=1 comm="systemd" path="/var/lib/nfs" dev="dm-0" ino=33596932 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_lib_nfs_t:s0 tclass=lnk_file permissive=1 [root@glustere ~]# dmesg | grep -e type=1300 -e type=1400 | audit2allow -M my-systemd ******************** IMPORTANT *********************** To make this policy package active, execute: semodule -i my-systemd.pp [root@glustere ~]# cat my-systemd.te module my-systemd 1.0; require { type var_lib_nfs_t; type init_t; class lnk_file getattr; } #============= init_t ============== allow init_t var_lib_nfs_t:lnk_file getattr; Best Regards, Strahil Nikolov

2 4

CPE Weekly: 2020-11-22
by Aoife Moloney 23 Nov '20

23 Nov '20

Hi Everyone, Below is this week's CPE weekly for week ending 2020-11-22 for both Fedora & CentOS, and if you want to visit the hackmd link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view you can then use the header bar on your left to skip to Fedora or CentOS updates that interest you. ## General Project Updates Final project submission date for consideration in Q1 is Friday 27th November. If you have an initiative that may take weeks/months and multiple people to work on and want to request it to CPE, please follow the steps outlined in our initiatives repo and create your issue before 27th November https://pagure.io/cpe/initiatives-proposal Our updated initative timetable can be viewed here for 2021 https://docs.fedoraproject.org/en-US/cpe/time_tables/ Below are the projects the CPE team are currently working on for the months of October, November & December: * CentOS Stream Phase 4 - Build system services * Noggin Phase 4 - Data Migration of Fedora & CentOS Accounts, Community testing * OSBS for aarch64 - this will begin in November * Fedora Messaging Schemas - this work is continuing from Q3 and is being worked on part-time ### Misc #### GitLab New GitLab topic sent to devel-announce(a)lists.fedoraproject.org & centos-devel(a)centos.org on Message Bus is out. See email in hackmd here https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view ## Project Updates *The below updates are pulled directly from our CPE team call we have every week.* ## CentOS Updates ### CentOS * CentOS 6 is EOL 30th November * CFP for FOSDEM Dojo - https://wiki.centos.org/Events/Dojo/FOSDEM2021 * Updated CentOS CI Openshift staging cluster to latest 4.6.4, Waiting for stable release in the 4.6 branch before rolling out to production. * CentOS 7.9.2009 is released! (for x86_64, i386, ppc64, ppc64le, armhfp and aarch64 architectures) * Lot of work done for Noggin/AAA ### CentOS Stream * Use centos-stream-release package to convert from CentOS 6 to CentOS Stream before 30th November * Working on integrating ODCS in Stream * Curating out t_functional suite https://github.com/centos/sig-core-t_functional * Refining our testing for finding issues at distro-level ### Fedora ### Staging Environment * Completed - any issues you find please report them in fedora infra https://pagure.io/fedora-infrastructure/issues ### Noggin/AAA * Testing team owned apps in staging with Noggin * We will be requesting community member testing before December so keep an eye out for an announcement! * The teams kanban board where they track their work can be found here https://github.com/orgs/fedora-infra/projects/6 * And we have a project tracker available to be viewed here https://github.com/fedora-infra/aaa-tracker ### OSBS for aarch64 * Basic OKD 3.11 working on aarm64 with F31 * Working on repeating that install with F33 * Next step will be to ### Fedora Messaging Schemas * This project is worked on on a part time basis as we are prioritizing completing Noggin first before fully committing to its completion * There is a list of applications that require messaging schemas can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * There is a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ## Team Info ### CPE Product Owner Office Hours IRC office hours are now once per month.Below are the logs from the most recent meetings and dates for the next ones. #### #fedora-meeting-1 * Next Meeting: 2020-12-17 @ 1300 UTC on #fedora-meeting-1 #### #centos-meeting * Next Meeting: 2020-12-15 @ 1500 UTC on #centos-meeting ## Background: The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford ReplyForward

1 0

GitLab AMA Topic Follow Up: Namespace & Issue Tracking
by Aoife Moloney 23 Nov '20

23 Nov '20

Hi everyone, I've posted this to devel-announce(a)lists.fedoraproject.org but I will always post this over here too in case there are interested people on this mailing list that may not see it on the Fedora one. Thanks again for your involvement in the GitLab AMA session on IRC in September. This email discussion thread is on Namespace & Issue Tracking. I have pulled the relevant questions and answers from the original hackmd doc into one email and if you would like to discuss this topic specifically, here might be a good place to do so so your conversations don't go down a 'rabbit hole' :) Here are some links to resources as well: * Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w * Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_w… * AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 * Here is this email in hackmd if you wish to view it there: https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view ## Namespace & Issue Tracking - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: It may need to be checked again, but it appears you can turn on/off the issue tracker at the project level. - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: You can turn the GitLab issue tracker on and off by project. See https://docs.gitlab.com/ee/user/project/settings/#sharing-and-permissions Namespaces map to “group” in GitLab. Here’s more info about them: https://docs.gitlab.com/ee/api/namespaces.html - Question: Fedora, as far as I understand, still plan on using bugzilla as issue tracker. Currently default assignee and the CC are gathered using the ``main admin`` (ie: the ``owner`` for GitLab iiuc), the other maintainers (who did not ``unwatch issues`` in the project - mechanism for them to opt-out of being in the CC list) and the people having enabled ``Issue watching`` for the project (mechanism for them to opt-in into being in the CC list). Would this work in a GitLab world? - Answer: There are a number of options related to that. For one, users can control their notifications globally and by name space in a fine grained way (see GitLab Notification Emails). - Question: Fedora is part of GitLab’s Open Source program and we have a migration tracker issue that we are using to keep track of feature requests, bugs, etc that are important to Fedora. The Fedora migration team has been working with us at GitLab to maintain that and community members can add relevant issues there so we can track them. It’s also helpful for our product managers to hear about why particular issues are important for the Fedora use case, and to have upvotes, so doing that will help! Where can you submit requests/bugs/report issues? - Answer: Fedora Migration Tracker: https://gitlab.com/gitlab-org/gitlab/-/issues/217350 Feature template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature… Bug template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Bug Please do review the original questions doc in case I have missed any that relate to namespace and issue tracking and thank you again for your engagement with these emails! The next email topic will be on 'Branches'. Have a good week! Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

mirror.centos.org/centos-7/7.9.2009 missing?
by Giedrius Rekašius 19 Nov '20

19 Nov '20

Hello, I don't see the 7.9.2009 release directory in http://mirror.centos.org/centos-7/. Up until now each minor release used to have it's own directory with the latest minor having same contents as the major release. Did something change recently and those minor release directories won't be provided going forward? Regards, Giedrius

3 2

SIGs Building Against CentOS Stream
by Johnny Hughes 18 Nov '20

18 Nov '20

All, Currently, here is a list of tags in the CBS who can build against CentOS Stream. https://cbs.centos.org/koji/search?match=glob&type=tag&terms=*8s-* If your SIG is interested in building against CentOS Stream, you can ask on this list to get a new tag created. The CentOS Project would be happy to enable building against CentOS Stream, so just let us know. Thanks, Johnny Hughes

1 0

[NFVSIG] NFV SIG meeting minutes - 2020-11-18
by Alfredo Moralejo Alonso 18 Nov '20

18 Nov '20

============================================= #centos-meeting: NFV SIG meeting - 2020-11-18 ============================================= Meeting started by amoralej at 15:08:57 UTC. The full logs are available athttps://www.centos.org/minutes/2020/November/centos-meeting.2020-11-18-15… . Meeting summary --------------- * ovs/ovn update to FDP 20.H (amoralej, 15:12:02) * ovs and ovn 2.13 from FDP 20.H have been tested and pushed to official mirrors (amoralej, 15:12:29) * ovs and ovn 2.11 from FDP 20.H have been tested and pushed to official mirrors (dholler, 15:12:45) * RDO Ussuri is also moving to OVS/OVN 2.13 from NFV SIG builds (amoralej, 15:18:54) * New centos-release-nfv pushed to mirror (amoralej, 15:20:56) * now the network-extras repo can be enabled by installing centos-release-nfv-extras (amoralej, 15:21:44) * LINK: https://pagure.io/centos-infra/issue/50 (ykarel, 15:31:55) Meeting ended at 15:34:36 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (32) * dholler (10) * ykarel (6) * centbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

7.9.2009 Live ISOs
by Ladar Levison 18 Nov '20

18 Nov '20

I noticed there is no live media in the new 7.9 ISO directory. Is that an oversight, a task that is pending, or will there be no live media for the 7.9.2009 release? The missing files are CentOS-7-x86_64-LiveGNOME-2009.iso and CentOS-7-x86_64-LiveKDE-2009.iso ... L~

3 2

7.9.2009 Live ISOs
by Ladar Levison 17 Nov '20

17 Nov '20

I noticed there is no live media in the new 7.9 ISO directory. Is that an oversight, a task that is pending, or will there be no live media for the 7.9.2009 release? The missing files are CentOS-7-x86_64-LiveGNOME-2009.iso and CentOS-7-x86_64-LiveKDE-2009.iso ... L~

1 0

Container Images & Docker Hub Rate Limiting
by Stephen Benjamin 17 Nov '20

17 Nov '20

Hi all, At the beginning of November, Docker instituted rate limiting on Docker Hub. Some builds happening in Quay are now hitting this limit[1], including those using the CentOS base images. Docker has a program to remove the rate limiting for open source projects[2]. Has anyone applied yet on behalf of the CentOS project? If not, who would be the right person to contact? We did notice that CentOS has its own registry[3], but it's currently returning 502 Bad Gateway when you hit the index page. However registry.centos.org/centos/centos:8 works -- is that a stable place for us to get the latest CentOS container images? Alternatively, would it be possible to get official builds for CentOS published to quay? Thanks - Stephen [1] https://groups.google.com/g/metal3-dev/c/6T6rMoFEOIc/m/KT68jzF5BAAJ [2] https://www.docker.com/blog/expanded-support-for-open-source-software-proje… [3] https://wiki.centos.org/ContainerPipeline

3 3

centos8 openvswitch-dpdk RPM
by Satish Patel 16 Nov '20

16 Nov '20

Folks, Recently i started playing with openvswitch on centOS for openstack SDN, and found centos8 doesn't have openvswitch with dpdk support, I was looking around RPM but didn't find any RPM also, do i need to compile openviswtch+dpdk support or rpm is available but i am not aware of it. ~S

2 10

Victoria RDO Release Announcement
by Amy Marrich 16 Nov '20

16 Nov '20

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2020/11/rdo-victoria-released/ --- RDO Victoria Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack Victoria for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Victoria is the 22nd release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. PLEASE NOTE: RDO Victoria provides packages for CentOS8 and python 3 only. Please use the Train release, for CentOS7 and python 2.7. Interesting things in the Victoria release include: - With the Victoria release, source tarballs are validated using the upstream GPG signature. This certifies that the source is identical to what is released upstream and ensures the integrity of the packaged source code. - With the Victoria release, openvswitch/ovn are not shipped as part of RDO. Instead RDO relies on builds from the CentOS NFV SIG. - Some new packages have been added to RDO during the Victoria release: - ansible-collections-openstack: This package includes OpenStack modules and plugins which are supported by the OpenStack community to help with the management of OpenStack infrastructure. - ansible-tripleo-ipa-server: This package contains Ansible for configuring the FreeIPA server for TripleO. - python-ibmcclient: This package contains the python library to communicate with HUAWEI iBMC based systems. - puppet-powerflex: This package contains the puppet module needed to deploy PowerFlex with TripleO. - The following packages have been retired from the RDO OpenStack distribution in the Victoria release: - The Congress project, an open policy framework for the cloud, has been retired upstream and from the RDO project in the Victoria release. - neutron-fwaas, the Firewall as a Service driver for neutron, is no longer maintained and has been removed from RDO. Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/victoria/highlights. Contributors During the Victoria cycle, we saw the following new RDO contributors: Amy Marrich (spotz) Daniel Pawlik Douglas Mendizábal Lance Bragstad Martin Chacon Piza Paul Leimer Pooja Jadhav Qianbiao NG Rajini Karthik Sandeep Yadav Sergii Golovatiuk Steve Baker Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 58 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: Adam Kimball Ade Lee Alan Pevec Alex Schultz Alfredo Moralejo Amol Kahat Amy Marrich (spotz) Arx Cruz Bhagyashri Shewale Bogdan Dobrelya Cédric Jeanneret Chandan Kumar Damien Ciabrini Daniel Pawlik Dmitry Tantsur Douglas Mendizábal Emilien Macchi Eric Harney Francesco Pantano Gabriele Cerami Gael Chamoulaud Gorka Eguileor Grzegorz Grasza Harald Jensås Iury Gregory Melo Ferreira Jakub Libosvar Javier Pena Joel Capitao Jon Schlueter Lance Bragstad Lon Hohberger Luigi Toscano Marios Andreou Martin Chacon Piza Mathieu Bultel Matthias Runge Michele Baldessari Mike Turek Nicolas Hicher Paul Leimer Pooja Jadhav Qianbiao.NG Rabi Mishra Rafael Folco Rain Leander Rajini Karthik Riccardo Pittau Ronelle Landy Sagi Shnaidman Sandeep Yadav Sergii Golovatiuk Slawek Kaplonski Soniya Vyas Sorin Sbarnea Steve Baker Tobias Urdin Wes Hayutin Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Wallaby. Get Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use TripleO and you’ll be running a production cloud in short order. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on Freenode IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net) however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube. *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz <https://www.redhat.com/>

1 0

404 on vault.centos.org/centos/7/updates/Source/repodata/repomd.xml
by Jan Pazdziora 13 Nov '20

13 Nov '20

Hello, /etc/yum.repos.d/CentOS-Sources.repo from centos-release-7-6.1810.2.el7.centos.x86_64 configures [updates-source] name=CentOS-$releasever - Updates Sources baseurl=http://vault.centos.org/centos/$releasever/updates/Source/ but currently http://vault.centos.org/centos/7/updates/Source/repodata/repomd.xml returns 404 Not Found. Is that an expected move of the CentOS 7 sources to some other location or is that a temporary glitch? Thank you, -- Jan Pazdziora Product Owner, Platform Security Readiness, Red Hat

2 1

EPEL-ANNOUNCE EPEL-6 is End of Life in 2020-11-30
by Troy Dawson 13 Nov '20

13 Nov '20

EPEL 6 is End Of Life (EOL) on November 30 2020. That is two weeks away EPEL 6 will be moved to archives in the first week of December 2020. That is three weeks away EPEL Steering Committee

1 0

CentOS 8.3 Release date
by Satish Patel 12 Nov '20

12 Nov '20

Folks, Redhat has released RHEL 8.3 for the general public last week so curious when CentOS 8.3 is coming out for the public? ~S

8 11

Update centos-release-openstack
by Alfredo Moralejo Alonso 12 Nov '20

12 Nov '20

Hi, Some days ago we requested to update the centos-release-openstack package to include new release OpenStack Victoria (branch c8-sig-cloud-openstack-victoria): https://git.centos.org/rpms/centos-release-openstack/c/2cdca07a1db5cf0418b2… We are waiting for it to announce the new release publicly. Is there any ETA to get it built and shipped in the extras repo? Best regards, Alfredo

2 3

[infra] Announced outage : hardware maintenance for network in main DC
by Fabian Arrotin 10 Nov '20

10 Nov '20

Due to some network switches upgrade in the DC hosting some community projects (including but not limited to CentOS), we'll have a large majority of our infra not reachable. Migration is scheduled for """"Tuesday November 10th, 2:00 am UTC time"""". You can convert to local time with $(date -d '2020-11-10 14:00 UTC') We unfortunately can't announce/give you any expected downtime as it can last for several hours (info I received through invite) but we'll try to restore all services/connectivity as soon as possible. Impacted services in that DC : - *all* Non impacted services (easier to just mention short list of things not in that DC, so items not listed below *will* be down) : - https://www.centos.org - https://forums.centos.org - https://lists.centos.org - mirrorlist.centos.org -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 4

Question about NFS Ganesha [Storage SIG]
by Strahil Nikolov 09 Nov '20

09 Nov '20

Hello All, I am trying to deploy a GlusterFS 8 on a CentOS 8.2.2004 with NFS Ganesha. It seems that Ganesha provided by centos-release-nfs-ganesha28 & centos-release-nfs-ganesha30 require resource-agents >= 4.2, but HighAvailability repo provides only 4.1 . How can I obtain resource-agents suitable for NFS Ganesha. Some output: [root@glustera ~]# yum install glusterfs-ganesha.x86_64 Последната проверка за остарялост на метаданните: преди 0:00:30 на 24.10.2020 (сб) 20:50:19 EEST. Грешка: Проблем: cannot install the best candidate for the job - nothing provides resource-agents >= 4.2.0 needed by glusterfs-ganesha-8.1-1.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Best Regards, Strahil Nikolov

3 20

NFS Ganesha on EL8 needs redesign
by Strahil Nikolov 09 Nov '20

09 Nov '20

Hello All, I have been playing around with Ganesha on CentOS 8 and I have noticed some issues so far. Could you assist me in pinpointing the correct location for tracking the issues: - 'gluster nfs-ganesha enable' builds pacemaker groups that use 'ocf:heartbeat:portblock', but that resource is relying on IPTABLES, while EL8 is using NFTABLES. - nfs-ganesha.service is starting the process via "/bin/bash -c" which SELINUX hates and of course blocks. Custom selinux policies were needed. - the glusterfs-ganesha.x86_64 rpm is deploying the following boolean 'semanage boolean -m ganesha_use_fusefs --on' but it seems that something disables it. Manual setting of 'setsebool -P ganesha_use_fusefs 1' is necessary - rpcbind is blocked by selinux, I had to enable 'rpcd_use_fusefs' - nfs-ganesha.service is starting before the shared volume is mounted locally, dependency is needed like this one: [root@glustera ~]# cat /etc/systemd/system/nfs-ganesha.service.d/01-debug.conf [Unit] After=run-gluster-shared_storage.mount Requires=run-gluster-shared_storage.mount I will rebuild my cluster to find out if I missed something. Any feedback is appreciated. P.S.: If anyone is interested , I can share the deployment procedure. Best Regards, Strahil Nikolov

1 0

CPE Weekly: 2020-11-08
by Aoife Moloney 08 Nov '20

08 Nov '20

Hi Everyone, Below is this week's CPE weekly for week ending 2020-11-08 for both Fedora & CentOS, and if you want to visit the hackmd link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view you can then use the header bar on your left to skip to Fedora or CentOS updates that interest you. ## General Project Updates We've updated our How to work with us section on our wiki https://docs.fedoraproject.org/en-US/cpe/initiatives/ Updated initative timetable can be viewed here https://docs.fedoraproject.org/en-US/cpe/time_tables/ And we have a new initiative repo live on Pagure https://pagure.io/cpe/initiatives-proposal Below are the scheduled projects the CPE team are currently working on for the months of October, November & December: * CentOS Stream Phase 4 - Build system services * Noggin Phase 4 - Data Migration of Fedora & CentOS Accounts, Community testing * OSBS for aarch64 - this will begin in November * Fedora Messaging Schemas - this work is continuing from Q3 and is being worked on part-time ### Misc #### GitLab New GitLab topic sent to devel-announce(a)lists.fedoraproject.org & centos-devel(a)centos.org on Message Bus is out. See email in hackmd here https://hackmd.io/tfOqCXNEQtqsGNLAEfZ2zg?view ## Project Updates *The below updates are pulled directly from our CPE team call we have every week.* ### CentOS * Update CentOS CI Openshift clusters to latest 4.5.16 * Storage resync completed this week. ### CentOS Stream * The team are working on developing ODCS service in the Stream build infra * Developing scripts to help automate adding artifacts to module builds * Check out the CentOS Stream page on centos.org/centos-stream for information on the latest download information and how to convert from CentOS Linux to Stream - especially if you are running on CentOS Linux 6 which is EOL on November 30th :) ### Fedora * F33 is released!!!! * F33 arm images are re-created and pushed as a point release * Testdays app up in openshift stg: https://testdays.stg.fedoraproject.org/events and may even be in production at the time of this email! * Openqa has all hardware up and running except one broken power9 box - working on resolving this ### Staging Environment * Build system nearly done - waiting on a firewall change ### Noggin/AAA * If you maintain an application that uses FAS, please test your app authentication in staging and report any issues you may find to the team in #fedora-aaa. * The team are particularly interested in if you cannot login or your user does not have the right groups/permissions/attributes, eg [cla_done] * The teams kanban board where they track their work can be found here https://github.com/orgs/fedora-infra/projects/6 * And we have a project tracker available to be viewed here https://github.com/fedora-infra/aaa-tracker ### OSBS for aarch64 * The team are tracking their work here https://pagure.io/cpe/osbs-project/issues * This project started on November 4th and the team are investigating technical approaches and requirements such as permissions & access to images. ### Fedora Messaging Schemas * This project is worked on on a part time basis as we are prioritizing completing Noggin first before fully committing to its completion * There is a list of applications that require messaging schemas can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * There is a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ## Team Info ### CPE Product Owner Office Hours IRC office hours are now once per month.Below are the logs from the most recent meetings and dates for the next ones. #### #fedora-meeting-1 * Next Meeting: 2020-11-12 @ 1300 UTC on #fedora-meeting-1 #### #centos-meeting * Next Meeting: 2020-11-10 @ 1500 UTC on #centos-meeting ## Background: The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2020