RDO Xena Released

RDO Xena Released

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Xena for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Xena is the 24th 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 at http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-xena/.

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.
PLEASE NOTE: RDO Xena provides packages for CentOS Stream 8 only. Please use the Victoria release for CentOS Linux 8 which will reach End Of Life (EOL) on December 31st, 2021 (https://www.centos.org/centos-linux-eol/).

Interesting things in the Xena release include:
  • The python-oslo-limit package has been added to RDO. This is the limit enforcement library which assists with quota calculation. Its aim is to provide support for quota enforcement across all OpenStack services.
  • The glance-tempest-plugin package has been added to RDO. This package provides a set of functional tests to validate Glance using the Tempest framework.
  • TripleO has been moved to an independent release model (see section TripleO in the RDO Xena release).

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

 

TripleO in the RDO Xena release:
In the Xena development cycle, TripleO has moved to an 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 Xena, TripleO will not support the Xena release. For TripleO users in RDO, this means that:
  • RDO Xena will include packages for TripleO tested at OpenStack Xena GA time.
  • Those packages will not be updated during the entire Xena maintenance cycle.
  • RDO will not be able to included patches required to fix bugs in TripleO on RDO Xena.
  • The lifecycle for the non-TripleO packages will follow the code merged and tested in upstream stable/Xena branches.
  • There will not be any TripleO Xena container images built/pushed, so interested users will have to do their own container builds when deploying Xena.
You can find details about this on the RDO webpage
Contributors

During the Xena cycle, we saw the following new RDO contributors:

  • Chris Sibbitt
  • Gregory Thiemonge
  • Julia Kreger
  • Leif Madsen
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 41 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories:
  • Alan Bishop
  • Alan Pevec
  • Alex Schultz
  • Alfredo Moralejo
  • Amy Marrich (spotz)
  • Bogdan Dobrelya
  • Chandan Kumar
  • Chris Sibbitt
  • Damien Ciabrini
  • Dmitry Tantsur
  • Eric Harney
  • Gaël Chamoulaud
  • Giulio Fidente
  • Goutham Pacha Ravi
  • Gregory Thiemonge
  • Grzegorz Grasza
  • Harald Jensas
  • James Slagle
  • Javier Peña
  • Jiri Podivin
  • Joel Capitao
  • Jon Schlueter
  • Julia Kreger
  • Lee Yarwood
  • Leif Madsen
  • Luigi Toscano
  • Marios Andreou
  • Mark McClain
  • Martin Kopec
  • Mathieu Bultel
  • Matthias Runge
  • Michele Baldessari
  • Pranali Deore
  • Rabi Mishra
  • Riccardo Pittau
  • Sagi Shnaidman
  • Sławek Kapłoński
  • Steve Baker
  • Takashi Kajinami
  • Wes Hayutin
  • Yatin Karel

 

The Next Release Cycle

At the end of one release, focus shifts immediately to the next release i.e Yoga.

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@lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev@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.

Article written by