devel

devel@lists.centos.org

9 participants
4572 discussions

RDO Dalmatian 2024.2 Released
by Amy Marrich 15 Oct '24

15 Oct '24

The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2024.2 Dalmatian for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Dalmatian is the 30th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-dalmat… 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 SIG. The Cloud 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. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/dalmatian/highlights.html but here are some highlights: - New Cinder driver features were added, notably, Dell PowerStore active-active support, Dell PowerStore QoS support, NetApp added support to active/active mode in ISCSI/FC drivers, HPE Nimble replication, and StorPool added support clone-across-pools capability. - Added Glance support of new add/get location APIs which replaces the image-update (old location-add) mechanism for consumers like cinder and nova to address OSSN-0090 and OSSN-0065. - Ironic has enhanced multiple security aspects, for example it now requires rescue passwords to be hashed, it has reduced the logged nodes information during the cleaning phase to avoid showing sensitive data, and it has hardened the communication between the ironic services and the ironic agent requiring an HTTPS url by default. - All Neutron supported mechanism drivers (ML2/OVS, ML2/OVN) can now use the WSGI API module, completing the first phase of eventlet library deprecation. - Nova Instances with UEFI firmware can now be launched with stateless firmware if their image has the hw_firmware_statelessproperty and if the compute services have libvirt 8.6.0 or later. OpenStack Dalmatian is not marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Caracal 2024.1 release. RDO Dalmatian 2024.2 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation]( https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During the Dalmatian cycle, some projects have been retired or declared inactive upstream. As such, the following packages for some projects are not present in the RDO Dalmatian 2024.2 release: - python-saharaclient (https://review.rdoproject.org/r/c/rdoinfo/+/54360) - puppet-corosync (https://review.rdoproject.org/r/c/rdoinfo/+/53127) During the next release we will continue working on retiring inactive packages in order to ensure RDO content quality and security. Contributors: During the Dalmatian cycle, we saw the following new RDO contributors: - Roman Safronov - Archana Singh - pkomarov komarov - Sergii Golovatiuk - Milana Levy - Liron Kuchlani - Jaromír Wysoglad - Arnau Verdaguer - Andre Aranha 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 51 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Alfredo Moralejo Alonso - Amy Marrich - Ananya Banerjee - Andre Aranha - Archana Singh - Arnau Verdaguer - Artom Lifshitz - Arx Cruz - Bhagyashri Shewale - Bohdan Dobrelia - Cédric Jeanneret - Chandan Kumar - Daniel Pawlik - Douglas Viroel - Fabien Boucher - Fiorella Yanac - Francesco Pantano - Goutham Pacha Ravi - Gregory Thiemonge - Grzegorz Grasza - Harald Jensås - Jaromír Wysoglad - Joan Francesc Gilabert - Joel Capitao - Jon Schlueter - Karolina Kula - Karthik Sundaravel - Lewis Denny - Liron Kuchlani - Lon Hohberger - Luigi Toscano - Maor Blaustein - Marihan Girgis - Marios Andreou - Martin Kopec - Martin Magr - Michael Johnson - Milana Levy - Nicolas Hicher - Pini Komarov - Roman Safronov - Ronelle Landy - Sergii Golovatiuk - Shreshtha Joshi - Soniya Vyas - Steve Baker - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yadnesh Kulkarni - Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Epoxy. 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. For those that do not have any hardware or physical resources, there is 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://www.rdoproject.org/community/mailing-lists/. 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 IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), 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 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

1 0

TOMOYO in Red Hat kernels
by Tetsuo Handa 10 Oct '24

10 Oct '24

Hello. I hope that some of Red Hat kernel team members are subscribed to this list. I want to use TOMOYO in RHEL kernels. In accordance with Fedora -> CentOS Stream -> RHEL flow, as a first step, I opened https://bugzilla.redhat.com/show_bug.cgi?id=2303689 and am waiting for response. Regards.

2 5

Announcing s390x architecture availability for cbs.centos.org/SIGs
by Fabian Arrotin 09 Oct '24

09 Oct '24

As discussed last week (https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/S3X3… ) I reached out to openmainframeproject to see if there would be a possibility to remotely use at least one s390x VM for SIGs. I'm proud to announce that such infra is ready to be used within CBS build infra (https://cbs.centos.org/koji/hostinfo?hostID=22) # What does that mean ? If your SIG wants to start building against/for s390x architecture, please just open a infra ticket on https://pagure.io/centos-infra/issues (usual way) and for which SIG/tags you'd like to see the s390x arch being added. As usual, SIGs can build against rhel8/rhel9/CentOS Stream 9 and CentOS Stream 10, including for s390x (internal mirror is now ready too) # How to proceed There are basically multiple ways to add the s390x architecture : - when you'll create new tag, you can ask for s390x arch to be included by default for your new build tag - for existing tags, you can also ask for the s390x arch to be added, but that also means that builds you'll submit as usual will have to find all build dependencies, including for s390x. It can be that you have yourself built some BuildRequires: dependencies for your RPM packages in your tags, but so probably just for x86_64, aarch64 and eventually ppc64le. How can that specific problem be solved : - either bump nvr for your build chain/order, rebuild in order to include from now on s390x, and then it will be BAU (Business as Usual) once s390x will be at same level for all pkgs. - other possibility (what I just used for the infra tags) : it's possible to just resubmit scratch builds for same package NVR (which koji would refuse you to do as "normal" build) : cbs build --scratch --arch-override s390x <target> <src.rpm/dist-git url> After each successfully scratch build, you can use the build id and then communicate (either through ticket or irc) us the build id, so that we can use a specific (admin right required, reason why SIGs can do that themselves) koji api call, to "merge" the newly s390x build with the existing one (with same pkg NVR, so nothing to do at the src.rpm/git level at all) - other option (if you have plenty of packages in the build chain, and don't want to block other builds for your existing -release tags) : we can create a specific "bootstrap" tag, with only s390x, in which we can just do the scratch+merge dance, until it's all resolved/equal to other tag, and only then, add the s390x arch to your existing tags (that will then automatically find the s390x packages, as existing in koji) One example : I had to rebuild cvs (one of many pkgs I rebuilt), itself a dep for koji-builder (needed to bootstrap the new infra) : - scratch build : https://cbs.centos.org/koji/taskinfo?taskID=4235422 - promoted to existing build : https://cbs.centos.org/koji/buildinfo?buildID=43020 (see s390x artifacts now part of a previous build ID) # Worth knowing We'd like to thank again openmainframeproject for the VM, but also worth knowing that because it's a remote (and locked down) VM, all koji/mirror traffic goes through an encrypted tunnel , and so that has a small impact on the needed time to init a buildroot. Based on my tests, it's still pretty fast to build, but just a little bit slower to init the buildroot, when downloading all needed packages Happy building and let us know which SIG wants to be next SIG (Infra SIG started to rebuild packages for our own usage already) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 1

Planned outage , please read (Oct 8th)
by Fabian Arrotin 08 Oct '24

08 Oct '24

Due to a mandatory core switches upgrade in the DC where some services are hosted, we'll lose connectivity between some services/storage servers and some publicly available services will be impacted. Impacted services: - https://git.centos.org - https://cbs.centos.org (builders will be put on hold during maintenance window) - https://lists.centos.org - CentOS mailing lists - CentOS CI env (https://duffy.ci.centos.org api endpoint) Maintenance is scheduled for """"Tuesday September 22nd, 6:00 am UTC time"""". You can convert to local time with $(date -d '2020-09-22 06:00 UTC') The expected/communicated "downtime" was estimated to be 4h, but we'll just announce when all services will be available again. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 5

Alternative Images quarterly release
by Troy Dawson 08 Oct '24

08 Oct '24

We have finished this quarter's release for Alternative Images. We are releasing a few more things than we usually do. *Live Images:* Updated on: October 4, 2024 Update number: 202410040625 Location: https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/live/ Names: CINNAMON-Live GNOME-Live KDE-Live MATE-Live MAX-Live MIN-Live XFCE-Live *WSL Images:* Updated on: October 4, 2024 Update number: 202410041004 Location: https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/wsl/ Names: WSL-Base *WSL Docs:* https://sigs.centos.org/altimages/wsl-images/ The Windows Subsystem for Linux (WSL) lets developers install and use a Linux distribution on Windows 10 or 11. Learn how to download and run CentOS Stream 9 on WSL. *DIY Local Docs:* https://sigs.centos.org/altimages/diy-local-images/ Learn how to create your own Alternative Images locally.

1 0

2024-10-09 - CentOS Public Board Meeting
by Thomas Oulevey 08 Oct '24

08 Oct '24

Hi Everyone, Our next board meeting will take place at 20:00 UTC tomorrow `date -d "2024-10-09 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/@centosboard/B1WddHykye As a reminder we will enforce few rules : * 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/redaction, 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. I hope some of you can join. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

CentOS Stream gitlab default branch change
by Troy Dawson 04 Oct '24

04 Oct '24

As of a couple days ago, some of you might have noticed that the default branch for all RPM packages on CentOS Stream Gitlab [1] has been changed to “c10s”. This was the result of extensive discussion in CS-1985 [2] where we came to the decision that we needed to have a consistent default branch across the package set and that it should always track the latest Y-stream project. We put together the tooling for this and executed it this week. [1] https://gitlab.com/redhat/centos-stream/rpms [2] https://issues.redhat.com/browse/CS-1985

1 0

access to s390x arch for SIGs (looking for comments)
by Fabian Arrotin 27 Sep '24

27 Sep '24

It's not the first time that some SIGs members are reaching out to me to ask about s390x architecture access for CBS (https://cbs.centos.org) This time, it was on irc, in #centos-devel channel. I promised to open a public thread on devel list so that we can reach out to bigger audience (SIGs and project leaders). Myself, talking about the Infra SIG needs, I'd love to have access to s390x architecture, as my current plan includes building through local mock on a different infra, and then having to launch manual processes, as our infra packages are built / signed / distributed like every other SIG, but so lacking s390x support. During that discussion on the centos-devel irc channel earlier today, someone mentioned https://openmainframeproject.org/news/developer-resources-for-linux-on-s390… Do you think (as SIGs) that it would be beneficial to eventually engage ? But also searching for CentOS Board members' opinion/thought on this first, as I don't want to start engaging with IBM through that public process if there is another way :) That reminds me this Fedora thread about similar request : https://pagure.io/fedora-infrastructure/issue/11122 Opinions ? Thoughts ? -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

6 8

CentOS Showcase, Nov 4
by Shaun McCance 25 Sep '24

25 Sep '24

Hi folks, Since we consolidated our in-person events to the one CentOS Connect each year at FOSDEM, there's been a lot of demand to bring back virtual events to show things off throughout the year. On November 4, we're going to host our first CentOS Showcase. This is a half-day virtual event, featuring short 20-minute talks where you can show off what you've been working on in CentOS. https://cfp.fedoraproject.org/centos-showcase-2024-11/ The CFP and registration are open. We're testing out new platforms as we do this, so please let us know if there are problems. We hope to run these virtual events 2-3 times per year going forward. We're very interested in your feedback on the format so we can improve in the future. Thanks, Shaun

1 0

Red Hat Liaison role filled
by Josh Boyer 20 Sep '24

20 Sep '24

Hello CentOS community, A month ago we announced that Brian Exelbierd would be departing Red Hat and that I would be taking the Liaison role to the CentOS Board on an interim basis while Red Hat looked for a long-term candidate. I am pleased to inform you that Steve Wanless will be taking the Red Hat Liaison role, effective immediately. Steve is a Product Manager within the Red Hat Enterprise Linux Business Unit focused on infrastructure and ecosystem. He has also been looking into RISC-V and other forward looking technologies. Please give Steve a warm welcome to the project. josh

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel