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/>
The board had its monthly meeting last week. The recording, minutes,
and recap are all available.
Recording:
https://youtu.be/-_A4Qd8tv0E
Minutes:
https://hackmd.io/@centosboard/HyfsgLsZh
Recap:
https://blog.centos.org/2023/04/centos-board-meeting-recap-april-2023/
We'll have the followup office hours this Thursday, April 20, at 14:00
UTC. Everybody is welcome to join and talk to the baord.
https://us06web.zoom.us/j/86542707135?pwd=eHlOQTNCU01vNFk4dm5Hc3NieVdXZz09
Hightlights of the recap:
* The Board discussed the x86 SIG proposal with Florian Weimer.
There's a general agreement that we want the SIG, but some differences
on the scope of work, which affects the name.
* CentOS Linux 7 and CentOS Stream 8 will both reach end of life in
2024. We're working on messaging to ensure everybody has time to
migrate. (Issue 93)
* We discussed the next steps in allowing SIGs to sign test
repositories. (Issue 92)
* We talked about our presence at Red Hat Summit, as well as plans for
events throughout the year.
======================================================
#centos-meeting: CentOS Cloud SIG meeting (2023-04-13)
======================================================
Meeting started by jcapitao[m] at 15:01:58 UTC. The full logs are
available athttps://www.centos.org/minutes/2023/April/centos-meeting.2023-04-13-15.01…
.
Meeting summary
---------------
* roll call (jcapitao[m], 15:02:48)
* RDO/OpenStack Update (jcapitao[m], 15:09:40)
* RDO Antelope is about to be released in the next couple of days
(jcapitao[m], 15:10:09)
* reminder: TripleO packages won't be provided in CloudSIG repo for
this release (jcapitao[m], 15:17:44)
* OKD update (lorbus, 15:23:10)
* new OKD/SCOS 4.12 (stable) and 4.13 (next) releases are out. The
plan is to cut releases at a 3-weekly cadence from now on (lorbus,
15:23:10)
* LINK: https://github.com/packit/packit/issues/1779 (jcapitao[m],
15:29:48)
* Open Floor (jcapitao[m], 15:42:02)
Meeting ended at 15:54:50 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jcapitao[m] (31)
* lorbus (16)
* amoralej (14)
* spotz_ (9)
* centguard (5)
* karolinku12 (1)
* karolinku (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Pythno 3.11 and some modules have appeared in CentOS Stream 8 appstream.
However I don't see python3.11-devel and the other modules that are in
CentOS Stream 9 crb in CS8 powertools. I do see them in CS9 koji.
Is this just an oversight or some kind of lag? Or is this intentional?
It will make it impossible for EPEL to build needed modules for EPEL 8.
I've also commented in the python 3.11 RFE here:
https://bugzilla.redhat.com/show_bug.cgi?id=2137139
Thanks for any information.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
Hi Everyone,
Our next board meeting will take place at 20:00 UTC next week:
`date -d "2023-04-12 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/HyfsgLsZh
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
=============================================
#centos-meeting: NFV SIG meeting - 2020-04-05
=============================================
Meeting started by amoralej at 15:01:45 UTC. The full logs are available
at
https://www.centos.org/minutes/2023/April/centos-meeting.2023-04-05-15.01.l…
.
Meeting summary
---------------
* gpg key in centos-release-nfv is not working (amoralej, 15:03:07)
* ACTION: amoralej to update the gpg key and create a new release of
centos-release-nfv (amoralej, 15:04:30)
* NFV SIG releases (amoralej, 15:05:43)
* ovn22.12 has been added for Centos Stream 9 and 8 (amoralej,
15:06:34)
* openvswitch3.1 has been added for Centos Stream 9 and 8 (amoralej,
15:06:46)
* building openvswitch and ovn against RHEL buildroots (amoralej,
15:09:49)
* OVS3.1 built against c9s has a newer version of rdma-core's
libibverbs which leads to an unresolvable dependency on non-Stream
systems looking for a soname for mlx rdma that doesn't exist (yet)
in rocky or rhel (amoralej, 15:12:02)
* building NFV SIG content would improve the compatibility with RHEL
derivatives (amoralej, 15:12:41)
* neil is willing to join NFV SIG and take care of rebuilds of
selected ovs and ovn versions for RHEL9 (amoralej, 15:17:10)
* LINK:
https://drop1.neilhanlon.me/irc/uploads/70bc9d4702cb964b/image.png
was just able to login (neil, 15:18:21)
* LINK: https://accounts.centos.org/group/sig-nfv/ is the actual list
(arrfab, 15:19:28)
Meeting ended at 15:35:35 UTC.
Action Items
------------
* amoralej to update the gpg key and create a new release of
centos-release-nfv
Action Items, by person
-----------------------
* amoralej
* amoralej to update the gpg key and create a new release of
centos-release-nfv
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* amoralej (62)
* neil (23)
* arrfab (10)
* centguard (4)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hello CentOS folks.
I've been told "I wanted to leave a comment ..., but I apparently don't have
sufficient permissions (it seems to be read only)" about this ticket:
https://issues.redhat.com/browse/CS-1502
Is that by design?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Let's chat about forums.centos.org !
IMHO, that service can be easily moved to a newer OS/PHP stack and so
continue to run. But on the other hand, I heard rumors that some forums
moderators would like to stop maintaining/moderating it after 2024.
I also heard that there is now a centos category on fedora discourse
(https://discussion.fedoraproject.org/c/centos/71)
So while we (centos infra) can easily migrate that server, should we ?
Let's spend some time investigating the options and take a decision
about it !
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi all,
Camilla announced this in december already
(https://lists.centos.org/pipermail/ci-users/2022-December/thread.html)
and we sent multiple reminders about that.
The plan was already knew since it was decided to move the whole CI
infra to AWS (announced in June 2022) but the last bit that had to move
was the openshift CI cluster (aka *.apps.ocp.ci.centos.org) to AWS
(https://console-openshift-console.apps.ocp.cloud.ci.centos.org/)
As the new cluster in AWS is deployed since end of November you still
have to migrate your workload from old to new cluster, and that *before*
end of March 2023 (see
https://sigs.centos.org/guide/ci/#migration-to-new-ci-instance)
We'll continue to send such reminders as long as we see tenants who
haven't migrated (yet)
We prefer announce it multiple times so that nobody will ask "where is
my app gone ?" when the whole cluster will be powered down end of March.
PS: if you have already migrated, please confirm to us so that we can
already delete your project/namespace/storage PV in the previous cluster.
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
https://planet.centos.org was deployed a long time ago to aggregate
feeds from various centos contributors and it was migrated from centos
release to centos newer release, as planet (python2 based app) was easy
to just rebuild.
Now that CentOS Linux 7 will go EOL next year, and that
https://blog.centos.org/ (linked to SSO) seems to be the only source for
blog posts, I'd like to consider just decommissioning that planet
instance, and the "Around CentOS" section of www.centos.org homepage
would fetch rss feed from blog.centos.org, instead of planet.centos.org
(just acting as a MITM these days)
Opinions, thoughts ?
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]