RDO Epoxy 2025.1 Release - Important Note at Bottom
The RDO community is pleased to announce the general availability of RDO
builds for OpenStack 2025.1 Epoxy for RPM-based distributions, CentOS
Stream and Red Hat Enterprise Linux. RDO is suitable for building private,
public and hybrid clouds. Epoxy is the 31st release of the OpenStack
project, backed by over 1,000 contributors worldwide.
This release is already available on CentOS Stream 9 on the CentOS mirror
network:
https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-epoxy/
The RDO community project curates, packages, builds, tests, and maintains a
complete set of OpenStack components 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 on-premise,
public, or hybrid clouds.
All work on RDO and its downstream release, Red Hat OpenStack Services on
OpenShift, is 100% open source, with all code changes going into it's
related upstream first.
You can read the broader upstream OpenStack project highlights at
https://releases.openstack.org/epoxy/highlights.html, but here are some
highlights:
- Notably, active/active support for Dell PowerStore, Dell PowerStore
QoS support, NetApp adding support for active/active mode in ISCSI/FC
drivers, HPE Nimble replication, and StorPool adding support for
pool-to-pool cloning.
- To address OSSN-0090 and OSSN-0065, support was added for a new
add/get location API that replaces the image update (old location-add)
mechanism for consumers such as cinder and nova.
- Ironic includes multiple security improvements:
- All supported mechanism drivers (ML2/OVS, ML2/OVN) can now use the
WSGI API module, and the first phase of deprecation of the eventlet library
is complete.
- Instances with UEFI can now boot in stateless pending if the image has
the hw_firmware_statelessproperty and the compute service has libvirt 8.6.0
or later.
According to this model (
https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…)
upgrades will only be supported from the Caracal 2024.1 release to the next
SLURP release (phase Epoxy).
RDO Epoxy 202 5.1 has been published by the CentOS Storage SIG in the
official CentOS repository and has been built and tested with the latest
released Ceph 18.2.0 Reef version (
https://docs.ceph.com/en/latest/releases/reef/) *Note:* Follow the
instructions in the [RDO documentation](
https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack
and Ceph services on the same host.
During Epoxy cycle, some projects have been retired or declared inactive
upstream. As such, the following packages for some projects are not present
in the RDO Epoxy 2025.1 release:
- python-saharaclient (https://review.rdoproject.org/r/c/rdoinfo/+/54360)
- puppet-corosync (https://review.rdoproject.org/r/c/rdoinfo/+/53127)
- python-oauth2client (dependency
https://review.rdoproject.org/r/c/rdoinfo/+/54115)
During the next release we will continue working on retiring inactive
packages in order to ensure RDO content quality and security.
Contributors:
- During the Epoxy cycle, we saw the following new RDO contributors:
- Ashish Gupta
- Dmitriy Chubinidze
- Francisco Seruca Salgado
- Ivan Anfimov
- Lilach Avraham
- Manoj Katari
- Saurabh Agarwal
- Sofer Athlan-Guyot
- Viji Candappa
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:
- Alan Pevec
- Alfredo Moralejo
- Amy Marrich
- Ananya Banerjee
- Artom Lifshitz
- Ashish Gupta
- Bogdan Dobrelya
- Chandan Kumar
- Daniel Pawlik
- Dmitriy Chubinidze
- Douglas Viroel
- Eduardo Olivares
- Fiorella Yanac
- Francesco Pantano
- Francisco Seruca Salgado
- Harald Jensås
- Ivan Anfimov
- Jakub Libosvar
- JaromÃr Wysoglad
- Joan Francesc Gilabert
- Joel Capitao
- Karolina Kula
- Lewis Denny
- Lilach Avraham
- Luigi Toscano
- Manoj Katari
- Maor Blaustein
- Martin Kopec
- Matthias Runge
- Matthieu Huin
- Miguel Garcia
- Mikołaj Ciecierski
- Pablo RodrÃguez Nava
- Pooja Jadhav
- Rabi Mishra
- Radomir Dopieralsk
- iRodolfo Alonso
- Ronelle Landy
- Saurabh Agarwal
- Sergii Golovatiuk
- Shreshtha Joshi
- Sławek Kapłoński
- Sofer Athlan-Guyot
- Takashi Kajinami
- Tobias Urdin
- Tony Breeds
- Viji Candappa
- 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.
Join us in #rdo and on the OFTC IRC network. You can also find us on
Facebook and YouTube.
*Important Note!*
We had a thriving, if small, group of community members maintaining
packages prior to COVID and we need to return to those days of having folks
participate in this effort. The OpenStack RPM packaging effort is in need
of package maintainers in order to continue having RPMs. The current
maintainers have moved on to new opportunities, so while we have folks
continuing to contribute, we currently have no folks to build and maintain
packages. Please check out the RDO contribute pages, peruse the CentOS
Cloud SIG page, and inhale the RDO packaging documentation. Please reach
out if you can help!
*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
Due to a koji upgrade, we'll have to temporary shutdown CentOS
Community Build System (aka https://cbs.centos.org)
Migration is scheduled for """"Tuesday April 29th, 7:00 am UTC time"""".
You can convert to local time with $(date -d '2025-04-29 07:00 UTC')
The expected "downtime" is estimated to ~30 minutes , time needed to
- disable kojid hosts (eventually a little bit before to ensure running
jobs would be finished)
- upgrade kojihub to version 1.35.2 (including DB schema changes)
- upgrade and enable back koji builders
For full details, see https://pagure.io/centos-infra/issue/1639
PS : worth knowing that koji 1.35 introduces a new "on demand" repo
generation (https://docs.pagure.org/koji/repo_generation/) .
For compatibility purposes, we'll just enable the repo.auto=True setting
on existing build tags for el8/el9s/el9s/el10s build tags so that you
don't have to wait for repo to be regenerated when submitting a new build)
If you want to opt-out, feel free to ask us through infra ticket
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]
In the last Board meeting we discussed the future of git.centos.org, and
whether it would make sense to encourage SIGs to move over to GitLab, as
we already have a group at gitlab.com/centos and that's where CentOS
Stream development is happening (under gitlab.com/redhat/centos-stream)
GitLab also provides features (notably, CI integration via Pipelines and
an improved code review flow) that some SIGs would like to use and would
benefit from.
To this end, I have filed https://git.centos.org/centos/board/issue/129
to summarize the discussion and decide the next steps. We'd welcome any
comments and feedback on this. To be clear, there are no plans to sunset
git.centos.org at this time.
Cheers
Davide
Hi, folks,
we have been discussing this feature for a while, but not officially. So
let me bring this up for a wider audience:
= Overview
OpenQA is a test orchestration framework used by OpenSUSE and Fedora and
it is more or less tailored to testing distribution images.
There is a number of tests written by Fedora QA team which are being
triggered on every nightly compose, and we would like to explore the
possibility to run these tests in the CentOS project on CentOS images.
Additionally there has been an open request from CentOS Alt Images and
Hyperscale SIGs to provide the way to test their own images as well.
We would like to address this need under the umbrella of the CentOS
Integration SIG.
= Plan
1) setup a dedicated OpenQA instance as close as possible to how Fedora
OpenQA instance is deployed;
2) ensure that it can run at least one test from Fedora QA test suite on
a standard CentOS Stream compose;
3) Offer interested parties (Hyperscale, Alt Images, Installer team at
Red Hat..) to extend the functionality;
4) ..
NOT in the plan:
- To replace existing compose tests CentOS Stream.
= What has been done
Jan Scotka created a local proof-of-concept and is now ready to do the
deployment.
See details in https://gitlab.com/CentOS/Integration/general/-/issues/8
= Help needed
We have infrastructure request filed in:
https://pagure.io/centos-infra/issue/1631
And of course we would love to have more people joining, getting
familiar with OpenQA capabilities and using it for their work.
--
Aleksandra Fedorova
Matrix: @bookwar:fedora.im
Fediverse/Mastodon: @bookwar@fosstodon.org
The CentOS Alternative Images SIG[1] has updated their CentOS Stream 9 Live
images this quarter. We also added 4 new Live desktop images.[2] We now
have
* CINNAMON
* GNOME
* KDE
* MATE
* XFCE
* MAX
MAX has all the desktops listed above, plus a few others like IceWM and
Lumina.
All of these live images can be installed on your system.
If there are bugs that are specific to the live images (not just general
CentOS Stream bugs) please file an issue in our spins bug tracker.[3]
Troy
[1] - https://sigs.centos.org/altimages/
[2] - https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/live/
[3] - https://pagure.io/centos-sig-alt-images/spin-bugs/issues
Hi Everyone,
Our next board meeting will take place at 20:00 UTC on Wednesday:
`date -d "2025-04-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/H1kcOFOaJx
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
Hi all,
The CentOS Board periodically reviews SIGs to ensure they're active.
The Alternative Architectures SIG is no longer active, so we intend to
retire this SIG unless somebody from the community wants to revive it.
Thanks,
Shaun