Open Stack

The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Yoga for RPM-based distributions, CentOS Stream and
Red Hat Enterprise Linux. RDO is suitable for building private, public, and
hybrid clouds. Yoga is the 25th release from the OpenStack project, which
is the work of more than 1,000 contributors from around the world.

The release is already available on the CentOS mirror network:

   - For CentOS Stream 8
   http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-yoga
   - For CentOS Stream 9
   http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-yoga/

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.

Interesting things in the Yoga release include:

   - RDO Yoga is the first RDO version built and tested for CentOS Stream 9.
   - In order to ease transition from CentOS Stream 8, RDO Yoga is also
   built and tested for CentOS Stream 8. Note that next release of RDO will be
   available only for CentOS Stream 9.

The highlights of the broader upstream OpenStack project may be read via
https://releases.openstack.org/yoga/highlights.html

TripleO in the RDO Yoga release:

Since the Xena development cycle, TripleO follows the Independent release
model
<https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-independent-release.html>
and will only maintain branches for selected OpenStack releases. In the
case of Yoga, TripleO will not support the Yoga release. For TripleO users
in RDO, this means that:

   - RDO Yoga will include packages for TripleO tested at OpenStack Yoga GA
   time.
   - Those packages will not be updated during the entire Yoga maintenance
   cycle.
   - RDO will not be able to included patches required to fix bugs in
   TripleO on RDO Yoga.
   - The lifecycle for the non-TripleO packages will follow the code merged
   and tested in upstream stable/yoga branches.
   - There will not be any TripleO Yoga container images built/pushed, so
   interested users will have to do their own container builds when deploying
   Yoga.

You can find details about this on the RDO Webpage
<https://www.rdoproject.org/documentation/tripleo-in-xena/>

*Contributors*
During the Yoga cycle, we saw the following new RDO contributors:

   - Adriano Vieira Petrich
   - Andrea Bolognani
   - Dariusz Smigiel
   - David Vallee Delisle
   - Douglas Viroel
   - Jakob Meng
   - Lucas Alvares Gomes
   - Luis Tomas Bolivar
   - T. Nichole Williams
   - Karolina Kula

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
40 contributors who participated in producing this release. This list
includes commits to rdo-packages, rdo-infra, and redhat-website
repositories:

   - Adriano Vieira Petrich
   - Alan Bishop
   - Alan Pevec
   - Alex Schultz
   - Alfredo Moralejo
   - Amy Marrich (spotz)
   - Andrea Bolognani
   - Chandan Kumar
   - Daniel Alvarez Sanchez
   - Dariusz Smigiel
   - David Vallee Delisle
   - Douglas Viroel
   - Emma Foley
   - Gaël Chamoulaud
   - Gregory Thiemonge
   - Harald
   - Jakob Meng
   - James Slagle
   - Jiri Podivin
   - Joel Capitao
   - Jon Schlueter
   - Julia Kreger
   - Kashyap Chamarthy
   - Lee Yarwood
   - Lon Hohberger
   - Lucas Alvares Gomes
   - Luigi Toscano
   - Luis Tomas Bolivar
   - Martin Kopec
   - mathieu bultel
   - Matthias Runge
   - Riccardo Pittau
   - Sergey
   - Stephen Finucane
   - Steve Baker
   - Takashi Kajinami
   - T. Nichole Williams
   - Tobias Urdin
   - Karolina Kula
   - User otherwiseguy
   - Yatin Karel

*The Next Release Cycle*
At the end of one release, focus shifts immediately to the next release i.e
Zed.

*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 the users at lists.rdoproject.org for RDO-specific users
and operators. For more developer-oriented content we recommend joining the
dev at 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 and TripleO IRC channels (#centos, #centos-devel in Libera Chat
network, and #tripleo on OFTC), 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 #tripleo on the OFTC IRC network and follow us on
Twitter @RDOCommunity. You can also find us on Facebook and YouTube.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220427/65ed8b58/attachment.htm>