Thank you,
would it be possible to consolidate all the info in the thread in a
"call for volunteers" that could then be posted in mailing lists/IRCs/etc?
Best regards
Francesco
On 2026-03-10 10:00, Alfredo Moralejo Alonso via dev wrote:
On Tue, Mar 10, 2026 at 9:24 AM Francesco Di Nucci
<[email protected]> wrote:
Why not, I'd like to try, at least with the call for volunteers.
Just to have an idea, how much time roughly is required? I'd have
to get a couple of authorizations
The required time will depend on the intended scope. Let me briefly
describe the set of activities of RDO which will likely make easier to
define the future of the new OpenStack RPMs.
RDO used to cover two sets of RPM repositories:
- RDO Trunk repositories built automatically by DLRN tool for each
merged patch (or update in upper-constraints) for each supported
OpenStack release and master branch. These were non-officially signed
packages served directly from RDO infra servers.
- RDO "official" CloudSIG builds for supported releases, built and
shipped using the CentOS Cloud SIG tool chain and repos infra. These
repos were the ones used when installing
"centos-release-openstack-<release>".
For each set of repositories there is some automation to trigger
builds on each commit or when a change is merged upstream in the
openstack releases or requirements project (i.e. a new tag-release is
created or a library version is updated in upper-constraints.txt).
Also, there were CI jobs to validate new builds using deployment jobs
based on puppet-openstack, packstack and openstack-k8s-operators. This
automation and CI was mostly done in RDO infra (using gerrit,
zuul/nodepool)
About numbers, in Epoxy RDO had 248 OpenStack packages and around 400
dependencies (dependencies are usually not rebuilt on each release)
In addition to that, openstack clients are maintained in Fedora and
some dependencies (the policy in RDO was that non-openstack
dependencies required for OpenStack and not available in RHEL/CentOS
where built using Fedora specs, so packages need to be maintained
there too).
The process can be probably streamlined and the scope reduced based on
the interest and time availability of the contributors. Also, the
required time will depend on the experience on RPMs and package
maintenance.
Best regards,
Alfredo
Francesco
On 09/03/26 22:37, Amy Marrich wrote:
If you all are willing to volunteer, and/or help find other
volunteers, I will try to find folks to mentor you to get you
started to keep the RPMs going. Unfortunately, I have already
spoken to folks in both Alma and Rocky, a year ago and again this
weekend at a conference, to see if they could assist and they do
not have the resources.
There was previously a small team of 2-3 engineers working on RDO
but as mentioned in the release announcement email they moved on
to other positions.
Amy
On Mon, Mar 9, 2026 at 2:42 PM Francesco Di Nucci
<[email protected]> wrote:
Thank you,
is it possible to try again to search for volunteers before
abandoning definitively the RPM packages? Less diversity is a
loss for everyone, and maybe people did not fully realize the
situation (me including, didn't read the announcement email
as I'm still running Caracal 😅). Cross-posting with other
mailing lists/IRC/ops meetings could be useful, and if the
alternative is RPM discontinuation, more people might be
interested.
If I can ask, how many people would (ideally) be
necessary/how many RPMs are around?
Francesco
On 06/03/26 17:14, Amy Marrich wrote:
Francesco, Massimo, Jose,
We would love help from the other communities to continue
creating the RPMS. We put a call out for volunteers over a
year ago[0]. and while folks replied that they wanted to
help or attended a meeting no one actually started helping.
As a result, we added an important note to the bottom of the
Epoxy release announcement[1] explaining that internal
developers had moved on and we again said we needed help and
to reach out if interested.
Amy
0 -
https://lists.rdoproject.org/archives/list/[email protected]/thread/6X5DTJG5ZLKV5LZC5BVQY7ROQBV55XTV/
1 -
https://lists.rdoproject.org/archives/list/[email protected]/message/2O4U2QL5WLAMPW2B225MLYQEEYQCREP2/
I'll also send this to the OpenStack list but respecting
Jeremy's decoupling of lists.
On Fri, Mar 6, 2026 at 8:12 AM Francesco Di Nucci
<[email protected]> wrote:
Hi all,
given that RDO will soon stop releasing RPMs of
OpenStack, it has been
suggested on IRC etc that AlmaLinux and Rocky Linux
communities might be
interested in building the RPMs instead, is there
already a discussion
about it?
Best regards
Francesco Di Nucci
--
Francesco Di Nucci
System Administrator
Compute & Networking Service, INFN Naples
Email: [email protected]
_______________________________________________
users mailing list [email protected]
To unsubscribe send an email [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
_______________________________________________
dev mailing list [email protected]
To unsubscribe send an email [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
_______________________________________________
dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
_______________________________________________
dev mailing list [email protected]
To unsubscribe send an email [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
--
Francesco Di Nucci
System Administrator
Compute & Networking Service, INFN Naples
Email:[email protected]
_______________________________________________
dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
