Let's chat about centos mailing lists !
https://lists.centos.org is powered by mailman package, available in
CentOS 7 , itself going EOL next year.
There is no packaged (yet) mailman3 stack (more components than simple
mailman 2 stack).
Options :
# use mailman2 package from RHEL8
That means (in theory) that we can just reinstall the machine with
RHEL8, and use the package that is available in AppStream repository:
mailman.x86_64
3:2.1.29-12.module+el8.5.0+13466+327eb9f3.2
Normally that should be more or less (to be tested though) transparent
migration, but as that module is still relying on python2 itself, we
don't know when it will itself go EOL in RHEL8 (BaseOS should be 10y but
apps in AppStream can have a shorter TTL)
# migrate to mailman3
Clearly much more work to do including see if the mailman3 stack
maintainer can branch to epel9 and then we can reuse it.
Also time to investigate how to import previous archives from mailman2
to mailman3 but should be doable (needs time to investigate and a PoC)
# something else ?
All comments, opinions are welcome and let's discuss it in advance and
not wait next year when machine will be powered off
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi Everyone,
Our next board meeting will take place at 20:00 UTC tomorrow:
`date -d "2023-05-10 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 Zoom 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/SkDqdm_En
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.
Sorry for the late announcement.
thanks,
--
Thomas 'alphacc' Oulevey
CentOS Board of Directors Secretary
alphacc(a)centosproject.org
CentOS Stream 8 and CentOS Linux 7 will both come to an end in about a
year. CentOS Stream 8 will reach end of builds on May 31, 2024. CentOS
Linux 7 will reach end of life on June 30, 2024.
More information is available on the CentOS blog:
https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an…
Please help us spread the word by linking to the blog post. Nobody
likes getting caught off guard on these things.
Thanks,
Shaun McCance
CentOS Community Architect
Red Hat Open Source Program Office
===================================
#centos-meeting: Virtualization SIG
===================================
Meeting started by sbonazzo at 16:02:28 UTC. The full logs are available
athttps://www.centos.org/minutes/2023/May/centos-meeting.2023-05-03-16.02.l…
.
Meeting summary
---------------
* kata-containers (sbonazzo, 16:03:22)
* no updates this week (sbonazzo, 16:03:29)
* oVirt updates (sbonazzo, 16:04:30)
* upstream developers are suggesting users to swithch to nightly
builds as there are no regular releases planned (sbonazzo,
16:04:42)
* LINK:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/DMCC5QCHL6ECXN…
(sbonazzo, 16:04:49)
* Automotive SIG collaboration (sbonazzo, 16:05:55)
* working with qemu upstream adding virtio-multitouch and enable GTK3
to use it (sbonazzo, 16:06:06)
* LINK:
https://lists.nongnu.org/archive/html/qemu-devel/2023-04/msg01961.html
(sbonazzo, 16:06:14)
* working with qemu upstream adding virtio shared dma-buf (sbonazzo,
16:06:34)
* LINK:
https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg00598.html
(sbonazzo, 16:06:44)
* working with qemu upstream adding Pipewire audio backend for QEMU
(sbonazzo, 16:06:55)
* LINK:
https://lists.nongnu.org/archive/html/qemu-devel/2023-04/msg02287.html
(sbonazzo, 16:07:03)
Meeting ended at 16:11:06 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* sbonazzo (23)
* centguard (4)
* etrunko (4)
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
The CentOS password reset procedure email is sent from:
Fedora Account System <fas(a)fedoraproject.org>
Does this mean that the password reset affects FAS as well?
Thanks,
Florian
Until today, we were using old ThunderX1 aarch64 machines as kojid
builders but today I replaced two (out of three) aarch64 with ThunderX2
machines (decommissioned from old koji.mbox setup used for stream 8
builds, now merged with stream 9 build infra), so clearly faster (not as
fast as $currently available aarch64 builders but better than what we
had previously)
See ticket : https://pagure.io/centos-infra/issue/1135
FWIW, we directly saw a faster build for samba today (see details in
ticket).
Should you encounter any issue, feel free to raise an infra ticket at
usual place (https://pagure.io/centos-infra/issues)
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack 2023.1 Antelope for RPM-based distributions, CentOS
Stream and Red Hat Enterprise Linux. RDO is suitable for building private,
public, and hybrid clouds. Antelope is the 27th 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-antelo…
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.
The highlights of the broader upstream OpenStack project may be read via
https://releases.openstack.org/antelope/highlights.html but here are some
highlights:
- The continuation of SRBAC and FIPS to make OpenStack a more secure
platform across various services, along with additional support in images.
- Additional drivers and features for Block Storage to support more
technologies from vendors such as Dell, Hitachi and NetApp, among others.
- DNS Zones that can now be shared with other tenants (projects)
allowing them to create and manage recordsets within the Zone.
- Networking port forwarding was added to the dashboard for Floating IPs.
- Additional networking features to support OVN.
- Compute now allows PCI devices to be scheduled via the Placement API
and power consumption can be managed for dedicated CPUs.
- Load balancing now allows users to enable cpu-pinning.
- Community testing of compatibility between non-adjacent upstream
versions.
OpenStack Antelope is the first release 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 be supported between these (SLURP) releases,
in addition to between adjacent major releases.
*TripleO removal in the RDO Antelope release:* During the Antelope cycle,
The TripleO team communicated the decision of abandoning the development of
the project and deprecating the master branches. According to that upstream
decision, TripleO packages have been removed from the RDO distribution and
will not be included in the Antelope release.
*Contributors* During the Zed cycle, we saw the following new RDO
contributors:
- Adrian Fusco Arnejo
- Bhagyashri Shewale
- Eduardo Olivares
- Elvira Garcia Ruiz
- Enrique Vallespí
- Jason Paroly
- Juan Badia Payno
- Karthik Sundaravel
- Roberto Alfieri
- Tom Weininger
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 *52* contributors who participated in
producing this release. This list includes commits to rdo-packages,
rdo-infra, and rdo-website repositories:
- Adrian Fusco Arnejo
- Alan Pevec
- Alfredo Moralejo Alonso
- Amol Kahat
- Amy Marrich
- Ananya Banerjee
- Artom Lifshitz
- Arx Cruz
- Bhagyashri Shewale
- Cédric Jeanneret
- Chandan Kumar
- Daniel Pawlik
- Dariusz Smigiel
- Dmitry Tantsur
- Douglas Viroel
- Eduardo Olivares
- Elvira Garcia Ruiz
- Emma Foley
- Eric Harney
- Enrique Vallespí
- Fabien Boucher
- Harald Jensas
- Jakob Meng
- Jason Paroly
- Jesse Pretorius
- Jiří Podivín
- Joel Capitao
- Juan Badia Payno
- Julia Kreger
- Karolina Kula
- Karthik Sundaravel
- Leif Madsen
- Luigi Toscano
- Luis Tomas Bolivar
- Marios Andreou
- Martin Kopec
- Matthias Runge
- Matthieu Huin
- Nicolas Hicher
- Pooja Jadhav
- Rabi Mishra
- Riccardo Pittau
- Roberto Alfieri
- Ronelle Landy
- Sandeep Yadav
- Sean Mooney
- Slawomir Kaplonski
- Steve Baker
- Takashi Kajinami
- Tobias Urdin
- Tom Weininger
- Yatin Karel
*The Next Release Cycle*
At the end of one release, focus shifts immediately to the next release i.e
Bobcat.
*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 IRC channels (#centos, #centos-cloud, and #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 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/>