devel October 2021

devel@lists.centos.org

27 participants
26 discussions

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

CPE to staff EPEL work
by Rich Bowen 17 Dec '21

17 Dec '21

We are pleased to announce that Red Hat is establishing a small team directly responsible for participating in EPEL activities. Their job isn't to displace the EPEL community, but rather to support it full-time. We expect many beneficial effects, among those better EPEL readiness for a RHEL major release. The EPEL team will be part of the wider Community Platform Engineering group, or CPE for short. As a reminder, CPE is the Red Hat team combining IT and release engineering from Fedora and CentOS. Right now we are staffing up the team and expect to see us begin this work from October 2021. Keep an eye on the EPEL mailing list[1] and the associated tracker as we begin this exciting journey with the EPEL community. [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… [2] https://pagure.io/epel/issues

9 11

Outdated ca-certificates in CentOS 7 Vagrant box
by Alex Pircher 16 Dec '21

16 Dec '21

Hello all, the CentOS 7 Vagrant box (https://app.vagrantup.com/centos/boxes/7) uses outdated ca-certificates, which leads to errors. Can you please update ca-certificates. Thanks, Alex # wget https://www.centos.org/ --2021-10-15 15:46:38-- https://www.centos.org/ Resolving www.centos.org (www.centos.org)... 81.171.33.201, 81.171.33.202, 35.178.203.231 Connecting to www.centos.org (www.centos.org)|81.171.33.201|:443... connected. ERROR: cannot verify www.centos.org's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=R3’: Issued certificate has expired. To connect to www.centos.org insecurely, use `--no-check-certificate'. # yum update -y ca-certificates # wget https://www.centos.org/ --2021-10-15 15:51:09-- https://www.centos.org/ Resolving www.centos.org (www.centos.org)... 81.171.33.201, 81.171.33.202, 35.178.203.231 Connecting to www.centos.org (www.centos.org)|81.171.33.201|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 24837 (24K) [text/html] Saving to: ‘index.html’ 100%[==================================================================================================>] 24,837 --.-K/s in 0.02s 2021-10-15 15:51:09 (1.16 MB/s) - ‘index.html’ saved [24837/24837]

2 2

CentOS Stream 9 content available for cbs.centos.org : start your builds !
by Fabian Arrotin 30 Nov '21

30 Nov '21

Hi, Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 ! I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues) Worth knowing that the following repositories are enabled by default for all newly created 9s tags: - BaseOS - AppStream - CRB What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags. It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed. Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s. What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already). Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags Stay tuned for more information about that soon. Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

6 11

Thank you to Karanbir Singh
by Rich Bowen 03 Nov '21

03 Nov '21

On behalf of the CentOS Board of Directors, and the whole CentOS community, I want to thank KB for his years of service as project leader and chair of the board. KB has shaped the project for almost 2 decades, and has made the world a better place by his work over the years. KB, it's been a privilege to work with you for the past few years. Thank you for your trust and respect as I've become part of that story. I wish you much joy in your future endeavors, and will always appreciate the chance to work alongside you on this great project. Please join me in thanking KB, and in telling your KB stories. Context, in case you missed it: https://karan.org/posts/stepping-down/ -- Rich Bowen: CentOS Community Manager rbowen(a)redhat.com @rbowen // @CentOSProject 1 859 351 9166

7 7

Centos9 - systemd with no tpm2
by lejeczek 30 Oct '21

30 Oct '21

Hi. fiddling with Stream 9 - is this a fluke or intentional, -> $ systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. and why if the latter , would anybody know? many thanks, L.

6 13

Announcing centos-plus repo for 8-stream
by Fabian Arrotin 29 Oct '21

29 Oct '21

We used to have a "plus" repository for CentOS 7 and 8, that contained packages from OS, but rebuilt differently. Most known examples in CentOS 8 plus repository are the kernel-plus and thunderbird (with openpgp support). As CentOS 8 is going EOL end of this year, and that some us still need to rely on that specific thunderbird package, we agreed to just use the SIG process for the plus repository, instead of having such packages being built through the distro builders. So if you're already on CentOS Stream 8 , you can just install (like for other SIGs) a specific package containing both the .repo file *and* needed gpg key used to sign the packages. How to enable/use it ? : sudo dnf install centos-release-plus -y As stated in /etc/yum.repos.d/CentOS-Stream-Plus.repo, you can now enable it (remember that it can overwrite base packages, reason why we also ship it as disabled) sudo dnf config-manager --enable centos-stream-plus You can now install pkg from it, like thunderbird : sudo dnf install thunderbird Tip: if you want to just use some pkgs from one specific repo, you can also just use excludepkgs/includepkgs statements in your .repo configuration (see https://dnf.readthedocs.io/en/latest/conf_ref.html#options-for-both-main-an…) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Missing thunderbird 91.2.0-1 "plus"
by Chris Schanzle 28 Oct '21

28 Oct '21

Just noticed thunderbird 91.2.0-1.el8.plus is not available in the "plus" repo for CentOS 8. It does exist for CentOS 7. The plus release keeps encrypted email functional in the new 91.x ESR release by not removing a library RHEL doesn't want to ship/support. If there are other workarounds/things to install to make the non-plus version work, I would appreciate the info. Thanks!

3 3

CPE Weekly Update – Week of October 25th – 29th
by Akashdeep Dhar 28 Oct '21

28 Oct '21

Hello, 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/). If you wish to read in a well-formatted blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-october-2… # 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. Updates ------- ### Fedora Infra * Freeze breaks: added regions to aws fedimg uploads and fixed a caching issue with upgrade json * Rebooted: proxy34 and bvmhost-x86-07 * Tried to fix move of wiki talk pages, ended up creating PR to disable all talk pages. * At 66 tickets, but many should be closable after freeze ### CentOS Infra including CentOS CI * Kicked some migration for tenants on legacy cluster (nfs-ganesha) * Rebased cico-workspace container to 8-stream (staging) (Ref https://quay.io/repository/centosci/cico-workspace/build/b197513b-0105-4774… ) * Pushed some new ciphers in prod through ansible role to get A+ cert on Qualys (Ref https://www.ssllabs.com/ssltest/analyze.html?d=git.centos.org&hideResults=on ) * Mirrormanager tuning with Adrian for 9-stream inside CI infra (Ref https://admin.fedoraproject.org/mirrormanager/host/2751) * Added/announced aarch64 as covered architecture for CI infra tenants ### Release Engineering * F35 RC-1.2 is out and can be found at https://dl.fedoraproject.org/pub/alt/stage/35_RC-1.2/ * Business as usual ## 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 ------- * Basic Stream/RHEL Buildroot reporting is in place, thanks James! * Open discussion on pruning older packages from what we publish to the mirrors * Open discussion on the impact of consolidating the Stream 8 and Stream 9 workflows for maintainers * Business as usual ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates ------- * Set up a boilerplate with a skeleton application * Set up the CI in the repository with tests and coverage * Created a CLI for configuring parameters * Discussed workflows and methods for implementing models ## FCOS OpenShift migration Goal of this Initiative ----------------------- Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly deployed fedora infra OCP4 cluster. Updates ------- * Obtaining access on the cluster * Creating playbook to create OpenShift resources * Got the cluster updated and ready Thanks and regards, Akashdeep Dhar t0xic0der(a)fedoraproject.org akashdeep(a)redhat.com

1 0

Xena RDO Release Announcement
by Amy Marrich 27 Oct '21

27 Oct '21

If you're having trouble with the formatting, this release announcement is available online at https://blogs.rdoproject.org/2021/10/rdo-xena-released/ ---- *RDO Xena Released* The RDO community is pleased to announce the general availability of the RDO build for OpenStack Xena for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Xena is the 24th 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-stream/cloud/x86_64/openstack-xena/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS 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 Xena provides packages for CentOS Stream 8 only. Please use the Victoria release for CentOS Linux 8 which will reach End Of Life (EOL) on December 31st, 2021 (https://www.centos.org/centos-linux-eol/). *Interesting things in the Xena release include:* - The python-oslo-limit package has been added to RDO. This is the limit enforcement library which assists with quota calculation. Its aim is to provide support for quota enforcement across all OpenStack services. - The glance-tempest-plugin package has been added to RDO. This package provides a set of functional tests to validate Glance using the Tempest framework. - TripleO has been moved to an independend release model (see section TripleO in the RDO Xena release) The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/xena/highlights.html *TripleO in the RDO Xena release:* - In the Xena development cycle, TripleO has moved to an Independent release model( https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde… ) and will only maintain branches for selected OpenStack releases. In the case of Xena, TripleO will not support the Xena release. For TripleO users in RDO, this means that: - RDO Xena will include packages for TripleO tested at OpenStack Xena GA time. - Those packages will not be updated during the entire Xena maintenance cycle. - RDO will not be able to included patches required to fix bugs in TripleO on RDO Xena. - The lifecycle for the non-TripleO packages will follow the code merged and tested in upstream stable/xena branches. - There will not be any tripleoxena container images built/pushed, so interested users will have to do their own container builds when deploying xena. You can find details about this [in RDO webpage](https://www.rdoproject.org/documentation/tripleo-in-xena/) *Contributors* During the Xena cycle, we saw the following new RDO contributors: - Chris Sibbitt - Gregory Thiemonge - Julia Kreger - Leif Madsen 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 41 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: - Alan Bishop - Alan Pevec - Alex Schultz - Alfredo Moralejo - Amy Marrich (spotz) - Bogdan Dobrelya - Chandan Kumar - Chris Sibbitt - Damien Ciabrini - Dmitry Tantsur - Eric Harney - Gaël Chamoulaud - Giulio Fidente - Goutham Pacha Ravi - Gregory Thiemonge - Grzegorz Grasza - Harald Jensas - James Slagle - Javier Peña - Jiri Podivin - Joel Capitao - Jon Schlueter - Julia Kreger - Lee Yarwood - Leif Madsen - Luigi Toscano - Marios Andreou - Mark McClain - Martin Kopec - Mathieu Bultel - Matthias Runge - Michele Baldessari - Pranali Deore - Rabi Mishra - Riccardo Pittau - Sagi Shnaidman - Sławek Kapłoński - Steve Baker - Takashi Kajinami - Wes Hayutin - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Yoga. *Get Started* 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. 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 OFTC 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 in Libera.Chat network, and #tripleo on OFTC), 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 OFTC 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2021