devel

devel@lists.centos.org

4 participants
4640 discussions

[NFV SIG] NFV SIG meeting minutes - 2021-06-02
by Alfredo Moralejo Alonso 02 Jun '21

02 Jun '21

============================================= #centos-meeting: NFV SIG meeting - 2021-06-02 ============================================= Meeting started by amoralej at 15:06:15 UTC. The full logs are available athttps://www.centos.org/minutes/2021/June/centos-meeting.2021-06-02-15.06.… . Meeting summary --------------- * roll call (amoralej, 15:07:01) * remember that now centos IRC channels are in libera chat, meetings are in #centos-meeting (amoralej, 15:08:19) * status of OpenvSwitch and OVN 2.15 (amoralej, 15:09:01) * package ovn-2021 is compatible with openvswitch 2.15 (amoralej, 15:09:27) * ovn-2021 has been built for CentOS Stream 8 and it's available in testing repo https://buildlogs.centos.org/centos/8-stream/nfv/x86_64/openvswitch-2/ (amoralej, 15:10:18) * ovn-2021 has virtual provides on openvswitch2.13-ovn what can produce conflicts between ovn2.13 and ovn-2021 if the virtual provides is used to install (amoralej, 15:11:27) * gating jobs with openstack are being added to gate promotions of ovs2.15 and ovn-2021 (amoralej, 15:12:17) * once the jobs are set and can be used ovn-2021 will be promoted to the release repository (amoralej, 15:12:35) Meeting ended at 15:17:19 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (10) * centbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Stream ISO retention
by Lance Albertson 01 Jun '21

01 Jun '21

What is the current policy for Stream ISO's? It seems that it's currently only one week which is problematic when trying to maintain your own packer templates and having to constantly update the filename and checksums. It seems as though long term, this method doesn't bode well for maintainability. Would it be possible to do one of the following? 1. Offer a filename symlink to the "current" build? 2. Offer an ISO that exists longer than a week? 3. Host archived ISOs on vault (or somewhere else) with some saner retention Thanks- -- Lance Albertson Director Oregon State University | Open Source Lab

3 10

CentOS Stream Feature SIG Meeting - Today @ 1600 UTC+1
by Aoife Moloney 01 Jun '21

01 Jun '21

Hi Everyone, Just as an fyi, the CentOS Stream Feature SIG will be meeting today @ 1600 UTC+1 on #centos-meeting. This will be the groups first meeting and is expected to focus on establishing the SIGs policies a little more. On the agenda is currently: - Identify chair(s) - Review meeting cadences and time are doable - How to expand membership - Verify feature process flow is in place and assign tasks to members to action if there are gaps - Establish an immediate goal (and longer term goals if there is time) You are all most welcome to join the meeting and I look forward to seeing you there over time! Kindest regards, Aoife, on behalf of the CentOS Stream Feature SIG -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

1 0

[Cloud SiG] RDO IRC Information
by Amy Marrich 26 May '21

26 May '21

Dear Cloud SiG and CentOS Community Members, As many of you know, there have been changes in Freenode which affect the RDO channel, OpenInfra channels, and the channels of many other communities we work closely with. After careful consideration, the OpenDev team has chosen to move the Open Infrastructure Foundation IRC related infrastructure to OFTC[0]. As of Monday, May 31st, OFTC will become the primary home of RDO (#rdo) including where we host our meeting. The Fedora and CentOS Communities have chosen to move to Libera[1] and due to our close relationship with these projects RDO will have a presence on this system as well also in #rdo. Our channel is already created on both systems and are ready for you to join them and it is recommended you register your Nick[2][3] on both these systems. While not a total solution, we would like to mention Matrix[4] which we hope in the future will be able to bridge OFTC and Libera.chat into one location. Thanks, Amy Marrich (spotz) 0 - https://www.oftc.net/ 1 - https://libera.chat/ 2 - https://www.oftc.net/Services/#register-your-account 3 - https://libera.chat/guides/registration 4 - https://matrix.org *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/>

3 2

Enabling PowerTools by default? (and proof-of-concept alternative)
by Michel Alexandre Salim 26 May '21

26 May '21

At the Hyperscale SIG, one of the repos we ship (centos-release- hyperscale-hotfixes, which we use to override modular content we need to fix as MBS is not available to SIGs) depends on EPEL (because the packages there, for example libvirt, needs dependencies in EPEL). EPEL's Quickstart recommends enabling codeready-builder on RHEL8, and the corresponding powertools repo on CentOS 8: https://fedoraproject.org/wiki/EPEL#Quickstart Could we possibly just enable powertools by default? CRB is on by default in RHEL8 UBI containers (but weirdly not in the related CentOS Stream containers!). There are multiple unactionable bugs in Bugzilla for EPEL about uninstallable packages, e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1890414 that ends up with the maintainer telling the reporter to just enable powertools. A proof-of-concept we tested in Hyperscale is to just enable PowerTools in %posttrans: https://git.centos.org/rpms/centos-release-hyperscale/c/03b6fd490be2571efa6… That way we can make sure that Powertools is already enabled for future transactions installing packages from our repos, but not potentially break the transaction itself by changing the set of packages available. (note: not shipped yet) But we'd rather not have to do this, and just have Powertools enabled to begin with. Failing that, have this kludge in epel-release so we get it for free for our packages that depend on EPEL. Looking at PowerTools, there's a lot of packages there, esp. in the Python stack, that I could imagine many Python library or application shipped in EPEL would be uninstallable if the repo is disabled. Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/michel@michel-slm.name

8 11

Infra SIG Bi-Weekly Meeting Cancellation Today
by Aoife Moloney 24 May '21

24 May '21

Hi Everyone, Between a mix of people having some time off today, people (me!) not having moved their account to Libera.chat yet, and no agenda to discuss today, please note the Infra SIG bi-weeklyt meeting is cancelled. It will resume as normal on the #centos-meeting channel on libera.chat, at 1500 UTC +1 on Monday 7th June. Issues can be filed and found here https://pagure.io/centos-infra/issues Have a lovely week everyone! Aoife, on behalf of the Infra SIG. -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

1 0

SIG feedback - Summary and actions
by Rich Bowen 21 May '21

21 May '21

Two weeks ago I asked this list for feedback on Special Interest Groups. I got a *LOT* of feedback, both on-list, and off-list. There were, of course, some common themes, and you've seem some of that in the on-list replies. I have summarized all of the feedback here - https://blog.centos.org/2021/05/sig-experience-feeback/ - because there was so much of it. In the coming weeks, I'll be working on the SIG Guide, and related documentation, to address the comments regarding lack of information and clarity of instructions. I'm also taking the process complaints/suggestions to the board and to the Infra team to see if, and how, we can address those complaints. Note that some of them have already been answered/addressed, and I'll be documenting those items. This will all be a public process, so that I can get your continued feedback on proposed changes and clarifications, so that I don't show up with something rewritten that doesn't actually address everyone's needs. Thank you to everyone who responded. This was very helpful. I want to specifically call out Fabian Arrotin, since several people mentioned that without Fabian, they would never have figured out how to do what they were supposed to do around SIG setup.

1 0

CentOS IRC channels moving to irc.libera.chat
by Rich Bowen 20 May '21

20 May '21

TL;DR: #centos and #centos-* are moving to libera.chat Over the past few days, there has been some upheaval on the Frenode IRC network, resulting in a number of the staff members quitting and starting a new IRC network. I wont attempt to explain all the details here, but you can read more at https://kline.sh which also links to other sources. The various ops have discussed the situation, and we intend to migrate all of the various #centos-* channels from Freenode over to irc.libera.chat over the coming days. This will take time, since libera is still spinning up, and some servers are moving from one network to the other. As libera is still in the early stages of setup, you may have significantly more timeouts/disconnects, netsplits and other issues for now. Until the new network is fully stable, we'll all continue to be present in the Freenode chanels. Please bring further questions to the IRC channels (on either network).

8 10

RFC: Stream Kernel SIG Proposal
by redbaronbrowser 19 May '21

19 May '21

There are four main goals of this SIG: First, break down changes in the Stream version 4.18.0 kernel into individual patches. When possible, document the source the patch is from and the purpose of the patch. Moving forward also document which Stream kernel package revision introduced the patch. Second, build CentOS Plus kernel for Stream. Third, package newer LTS kernels during the LTS lifespan. These would be available as alternative kernels for Stream similar to the CentOS Plus kernel. Fourth, work on tools for better delivery of live security patches to be applied via kpatch. The reasoning for this SIG is to improve the openness of kernels available through Stream. Normally a distribution upstream would have access to which patch or commit each addition to the kernel belongs to. The patch name or commit comment would also give information as to the purpose of the patch. Stream's kernel reports to be 4.18.0 but uses a tar that is 110% the size of a true 4.18.0 tar. A breakdown of the additional 10% is not provided. Hence Stream's kernel still functions similar to a downstream rather than providing what is expected for a successful upstream project. This SIG would help close the kernel openness gap by documenting the changes. Stream users would then be in a better position to track down individual patches that cause regressions or bugs. This SIG would also help smooth the adoption of Stream for users that depend on CentOS Plus kernel features. Next, this SIG should help improve feedback to the LTS kernel developers. Tracking LTS kernel changes may also help with documenting some changes in the primary Stream kernel. Lastly, this SIG should help improve kernel security by promoting methods to enable kernel security updates even when a reboot of the system is not possible.

12 42

[Artwork] CentOS Stream logo?
by Rich Bowen 18 May '21

18 May '21

Hi, Artwork/Design folks, I am getting asked several times a week, by various people, where they can get the CentOS Stream logo. Since there isn't such a thing, I generally say "we just have one logo." I wonder if it would be possible to get a CentOS Stream logo - presumably just the CentOS logo with "CentOS Stream" wordmark in the right font? There's a mockup of that at https://git.centos.org/centos/Artwork/issue/1 but having high-res/scalable versions would be nice. Is that a thing that someone is willing to do? --Rich

3 5

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