devel

devel@lists.centos.org

3 participants
4613 discussions

Re: [CentOS-devel] Balancing the needs around the CentOS platform
by Chris Mair 20 Dec '20

20 Dec '20

To: centos-devel(a)centos.org To: centos-questions(a)redhat.com Hi, Re: https://blog.centos.org/2020/12/balancing-the-needs-around-the-centos-platf… you can spin this to the moon and back. The fact remains you just killed CentOS Linux and your users' trust by moving the EOL of CentOS Linux 8 from 2029 to 2021. You've alienated a few hunderd thousand sysadmins that started upgrading to 8 this year and you've thrown the scientific Linux community under a bus. You do realize Scientific Linux was discontinued because CERN and FermiLab decided to standardize on CentOS 8? This trickled down to a load of labs and research institutions. Nobody forced you to buy out CentOS or offer a gratis distribution. But everybody expected you to stick to the EOL dates you committed to. You boast about being the "Enterprise" Linux distributor. Then, don't act like a freaking start-up that announces stuff today and vanishes a year later. The correct way to handle this would have been to kill the future CentOS 9, giving everybody the time to cope with the changes. I've earned my RHCE in 2003 (yes that's seventeen years ago). Since then, many times, I've recommended RHEL or CentOS to the clients I do free lance work for. Just a few weeks ago I was asked to give an opinion on six CentOS 7 boxes about to be deployed into a research system to be upgraded to 8. I gave my go. Well, that didn't last long. What do you expect me to recommend now? Buying RHEL licenses? That may or may be not have a certain cost per year and may or may be not supported until a given date? Once you grant yourself the freedom to retract whatever published information, how can I trust you? What added values do I get over any of the community supported distributions (given I can support myself)? And no, CentOS Stream cannot "cover 95% (or so) of current user workloads". Stream was introduces as "a rolling preview of what's next in RHEL". I'm not interested at all in a "a rolling preview of what's next in RHEL". I'm interested in a stable distribution I can trust to get updates until the given EOL date. You've made me look elsewhere for that. -- Chris

1 0

Can the CentOS Stream FAQ be updated
by Troy Dawson 17 Dec '20

17 Dec '20

Hi, There has been some confusion around the new CentOS Stream timeframe. Through the past year we've been told that when CentOS Stream 9 comes out, CentOS Stream 8 will be phased out in a short period of time. With the new announcement we have been told that the CentOS Stream 8 (and any future version) will be available during the maintenance phase of that release. [1] This means that CentOS Stream 8 will be around for 5 years. I've been trying to send people to the CentOS Stream FAQ [2] because it's easier to find. But the question [3] related to this hasn't been updated and says it will be a year at most. So, thus my question. Can the CentOS Stream FAQ be updated with the new policy? Thanks Troy Dawson [1] - https://centos.org/distro-faq/#q6-will-there-be-separateparallelsimultaneou… [2] - https://wiki.centos.org/FAQ/CentOSStream [3] - https://wiki.centos.org/FAQ/CentOSStream#What_happens_when_CentOS_Stream_sw…

6 8

Virtualization SIG meeting minutes - 2020-12-16
by Sandro Bonazzola 16 Dec '20

16 Dec '20

=================================== #centos-meeting: Virtualization SIG =================================== Meeting started by sbonazzo at 16:03:35 UTC. The full logs are available athttps://www.centos.org/minutes/2020/December/centos-meeting.2020-12-16-16… Meeting summary --------------- * Xen updates (anthonyper, 16:06:08) * ACTION: anthonyper to repackage Xen with XSA from yesterday (sbonazzo, 16:08:53) * Advanced Virtualization (etrunko, 16:10:33) * AV-8.3.0 packages have been built, currently on testing (etrunko, 16:11:04) * oVirt (sbonazzo, 16:14:02) * finalizing oVirt 4.4.4, waiting for Advanced Virtualization to be released and for ansible 2.9.16 released upstream recently (sbonazzo, 16:14:35) * we got some issues from CEntOS 8.3 release but they have been quickly solved by the CentOS team (sbonazzo, 16:15:15) * still some issue due to Anaconda rebase in CentOS 8.3 for oVirt Node (sbonazzo, 16:15:41) * LINK: https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/K7XF3CW5BHNZHI… (sbonazzo, 16:15:52) * oVirt 4.4.5 development started, rebasing on CentOS Stream. oVirt appliance will go first (sbonazzo, 16:16:32) * LINK: https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/NXZ7WJACAST5DK… (sbonazzo, 16:16:43) * AoB (sbonazzo, 16:18:36) * AGREED: skipping next meeting. We'll meet in new year on Jan 13th 2021 (sbonazzo, 16:22:24) Meeting ended at 16:23:50 UTC. Action Items ------------ * anthonyper to repackage Xen with XSA from yesterday Action Items, by person ----------------------- * anthonyper * anthonyper to repackage Xen with XSA from yesterday * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sbonazzo (40) * etrunko (10) * centbot (8) * gwd (4) * dholler (3) * anthonyper (3) * amoralej (1) * tfherbert (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

NFV SIG meeting minutes - 2020-12-16
by Thomas F Herbert 16 Dec '20

16 Dec '20

======================== #centos-meeting: NFV SIG ======================== Meeting started by tfherbert at 15:03:23 UTC. The full logs are available at https://www.centos.org/minutes/2020/December/centos-meeting.2020-12-16-15.0… . Meeting summary --------------- * Agenda items? (tfherbert, 15:04:14) * LINK: https://hackmd.io/oRe_HVJiTteDI4H332ApMw?both (amoralej, 15:07:55) * Rupdate to FDP 20.I (amoralej, 15:08:53) * Rebuilds of ovn/ovs 2.11 and 2.13 from FDP 20.I have been tested and published. (amoralej, 15:09:03) * CentOS Stream and impact on NFV SIG (tfherbert, 15:11:37) * https://blog.centos.org/2020/12/future-is-centos-stream/ (tfherbert, 15:11:54) * Wait and see what direction NFV SIG should take WRT C8 and C8s. (tfherbert, 15:35:43) * next meeting (tfherbert, 15:39:12) * next mtg is on January 13th. (tfherbert, 15:39:26) Meeting ended at 15:45:07 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (62) * tfherbert (31) * dholler (9) * ykarel (5) * centbot (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- *Thomas F Herbert* CTO Office Networking Group *Red Hat* he/him/his

1 0

Christmas gift from SantaOS.
by Thomas Stephen Lee 16 Dec '20

16 Dec '20

Hi, I am a grown-up kid :p. As a Christmas gift from CentOS, we would like CentOS core developers to show us how they build a release from RedHat sources whenever RedHat releases a version or an rpm. The documentation, scripts, and setup are what we are looking for. This is not for me personally, but for people interested in cloning CentOS. Christmas cheers :) Thanks --- Lee

5 5

centos stream container image
by Ken Dreyer 15 Dec '20

15 Dec '20

Hi folks, https://centos.org/centos-linux/ has some "Containers" links (that point to Docker Hub). https://centos.org/centos-stream/ has the word "Containers", but it's not linked to anything. Is there a ticket (Mantis, Pagure or Bugzilla, etc) that tracks the work of publishing a CentOS Stream container image? - Ken

2 2

C8 minimal (fwd)
by Marko Bevc 15 Dec '20

15 Dec '20

Hi everyone! QQ unrelated to all current discussions around C8; is minimal ISO in progress or is it not being produced anymore as part of 8.3 release? Cheers, Marko

5 11

centos-release-openstack-victoria is missing
by Marcin Juszkiewicz 15 Dec '20

15 Dec '20

Hi "centos-release-openstack-victoria" package was built on 3rd November 2020: https://koji.mbox.centos.org/koji/buildinfo?buildID=14699 In Kolla project we started using it on 12th November. Now it is gone. CI broke. Firefighting started instead of doing development. Can we get this package back?

2 1

GitLab AMA Topic Follow Up: Branches
by Aoife Moloney 14 Dec '20

14 Dec '20

Hi everyone, I know there's a lot going on in CentOS right now, but I still wanted to share with you all the follow up on the GItLab AMA session on Branches, in case you wished to read about it. So below are some links to the original documents and chat logs from the IRC session, and the main body of this mail is the questions and answers pulled directly from the Q&A sheet that specifically relate to branches. * 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/me-0oLN-Qtmff1qMX2S-DA?view ## Topic: Branches Force pushing - Protected Branches - Question: Fedora forbids force-push in the main projects but allows them in forks. Would this be feasible in GitLab in a way that people cannot revert? - Answer: This can be done with Protected branches, basically (https://docs.gitlab.com/ee/user/project/protected_branches.html#protected-b…) Archived branches - Protected Branches - Question: Fedora supports the concept of retired git `branch` (ie: archived) that no-one can commit. Does GitLab have an equivalent concept? (The retired status is not something project admins can change) - Answer: Yes this is possible with Protected Branches https://docs.gitlab.com/ee/user/project/protected_branches.html#protected-b… - Question: Extending to above question, the sla's or eol dates are coming from a 3rd party service, when a user pushes to git branch, it will check the eol in that service and rejects it if it is already eol'd. Is this possible in GitLab? - Answer: Instead of this we would probably use the Protected Branches in GitLab. We could leverage the APIs to mass configure the branches on eol dates. That would mean that for each git push we don’t need to look at a 3rd party service to know if we can push or not. - Question: It is not allowed for users to delete the branches, only certain people with certain access levels are allowed to perform this operation. Is this possible in GitLab? - Answer: Yes protected branches can be used here https://docs.gitlab.com/ee/user/project/protected_branches.html#protected-b… Push permissions - Question: In CentOS, members of a group (say: storage-sig) can push to any branch starting with c<int>-<sig-name>-* (so for example, they can push to : c8-storage-sig-v2.0 or c7-storage-sig), but they cannot push to any other branches, like: c8, c7 or any of the branches starting with c8-kernel-sig and so on. Would this be doable in GitLab? (in a way that project owner/maintainer cannot edit?) - Answer: A Custom Push Rule and server hook (pre-recieve Git hooks behind the scenes) could help with this. - Question: Can we set permissions at branch level? Esp can we set them with some regex matching? - Answer: permissions accept wildcards, but not regexes. Regex can be used with custom push rules. See https://docs.gitlab.com/ee/push_rules/push_rules.html and https://docs.gitlab.com/ee/user/project/protected_branches.html#configuring…. Hiding branches - Question: Is it possible to hide these retired branches from the UI? Say, hide branch names with f30 or lower? - Answer: This is not possible currently - Question: Currently a user is not allowed to rewrite the history. Is it possible? It would be nice to allow only certain people to do so. Although we might not use this, but its good to have just in case if we ever need it. - Answer: by default, only the `master` branch is protected against force push and deletion. It’s possible to configure other branches to be protected and who has permission to override. https://docs.gitlab.com/ee/user/project/protected_branches.html#configuring… Branch level orphaning - Question: Orphaning a package or repo? A maintainer (owner) of the package can decide to orphan a package, the maintainer should only be able to assign the package to the `orphan` user or any of the other maintainers of the package only. Is this possible to set this branch level as well? - Answer: Yes, in the sense that who is allowed to push or merge to a specific branch is controllable at the user or group level. This can be at the specific branch level or based on a wildcard match based on branch name. See configuring protected branches for more details. There is one more topic from the AMA session on Naming issues with `+` and I will include any other Q&A's from the sheet that have not been posted yet. This will be out next week. I hope you have been finding this concentrated topic email useful and informative. This has been an extremely different year for everyone & we as a team have found ourselves with very little time to give to this project since the initial announcement, but I hope to engage with the community much more directly in 2021 as I work through this GitLab project formally to make sure we are making the best choices for everyone, straight through from end user to sys-admin, and everyone in between. Have a lovely weekend everyone and thank you again for your engagement and patience! Kindest regards, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

4 5

CentOS 8 Stream Migration from CentOS 8 Linux
by Agarwal, Swati 14 Dec '20

14 Dec '20

Dear CentOS Team, This is regarding latest notification released for CentOS 8 stream replacement from CentOS 8 Linux. We have some queries in which we need your inputs as we have many Clients using CentOS 8 Linux on their production environments: * The packages which are available in Centos 8, will the same packages be available in Centos stream 8 ? * RHEL is doing some CVE fixes for Centos 8 and they have given temporary fixes so RHEL will push those fixes in Centos Stream 8 and what will be their impacts ? * We have upgraded from Centos 8 to Centos stream 8 by following the steps below. a.) dnf install centos-release-stream b.) dnf swap centos-{linux,stream}-repos c.) dnf distro-sync d.) cat /etc/centos-releas Expected output : CentOS Stream release 8. Did we miss anything ? * Suppose if RHEL is developing a package so it won't be available in CentOS Stream 8 and if it is available then what will be the impact ? * After upgrading from Centos8 Linux to CentOS Stream release 8, can we compare the versions of packages before & after and see which got updated * using # rpm -qa * After CentOS stream, what will vault.centos.org show ? Also, will it be same as shown in access.redhat.com/downloads/packages from RedHat ? * https://access.redhat.com/downloads/content/69/ver=/rhel---7/7.9/x86_64/pac… * https://vault.centos.org/7.7.1908/os/Source/SPackages/ * The Packages that are currently shown in access.redhat.com/downloads/packages or vault.centos.org are officially released ones. After CentOS Stream for CentOS8, the Packages shown in access.redhat.com/downloads/packages or vault.centos.org would be Beta releases or Officially released ones ? Please help us to answer above questions. -Br Swati

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel