If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2019/10/rdo-train-released/ ---
The RDO community is pleased to announce the general availability of the RDO build for OpenStack Train for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Train is the 20th release from the OpenStack project, which is the work of more than 1115 contributors https://www.stackalytics.com/?metric=commits from around the world.
The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-train/. While we normally also have the release available via http://mirror.centos.org/altarch/7/cloud/ppc64le/ and http://mirror.centos.org/altarch/7/cloud/aarch64/ – there have been issues with the mirror network which is currently being addressed via https://bugs.centos.org/view.php?id=16590. http://mirror.centos.org/altarch/7/cloud/aarch64/
The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux 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: At this time, RDO Train provides packages for CentOS7 only. We plan to move RDO to use CentOS8 as soon as possible during Ussuri development cycle so Train will be the last release working on CentOS7.
*Interesting things in the Train release include:*
- Openstack Ansible https://docs.openstack.org/openstack-ansible/latest/, which provides ansible playbooks and roles for deployment, added murano https://docs.openstack.org/murano/latest/ support and fully migrated to systemd-journald from rsyslog. This project makes deploying OpenStack from source in a way that makes it scalable while also being simple to operate, upgrade, and grow. - Ironic https://wiki.openstack.org/wiki/Ironic, the Bare Metal service, aims to produce an OpenStack service and associated libraries capable of managing and provisioning physical machines in a security-aware and fault-tolerant manner. Beyond providing basic support for building software RAID and a myriad of other highlights, this project now offers a new tool for building ramdisk images, ironic-python-agent-builder https://docs.openstack.org/ironic-python-agent-builder/latest/.
*Other improvements include:*
- Tobiko https://tobiko.readthedocs.io/en/latest/ is now available within RDO! This project is an OpenStack testing framework focusing on areas mostly complementary to Tempest https://docs.openstack.org/tempest/latest/. While the tempest main focus has been testing OpenStack rest APIs, the main Tobiko focus would be to test OpenStack system operations while “simulating” the use of the cloud as the final user would. Tobiko’s test cases populate the cloud with workloads such as instances, allows the CI workflow to perform an operation such as an update or upgrade, and then runs test cases to validate that the cloud workloads are still functional. - Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/train/highlights.html. https://releases.openstack.org/train/highlights.html
*Contributors* During the Train cycle, we saw the following new RDO contributors:
- Joel Capitao - Zoltan Caplovic - Sorin Sbarnea - Sławek Kapłoński - Damien Ciabrini - Beagles - Soniya Vyas - Kevin Carter (cloudnull) - fpantano - Michał Dulko - Stephen Finucane - Sofer Athlan-Guyot - Gauvain Pocentek - John Fulton - Pete Zaitcev
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 65 contributors who participated in producing this release. This list includes commits to rdo-packages and rdo-infra repositories:
- Adam Kimball - Alan Bishop - Alex Schultz - Alfredo Moralejo - Arx Cruz - Beagles - Bernard Cafarelli - Bogdan Dobrelya - Brian Rosmaita - Carlos Goncalves - Cédric Jeanneret - Chandan Kumar - Damien Ciabrini - Daniel Alvarez - David Moreau Simard - Dmitry Tantsur - Emilien Macchi - Eric Harney - fpantano - Gael Chamoulaud - Gauvain Pocentek - Jakub Libosvar - James Slagle - Javier Peña - Joel Capitao - John Fulton - Jon Schlueter - Kashyap Chamarthy - Kevin Carter (cloudnull) - Lee Yarwood - Lon Hohberger - Luigi Toscano - Luka Peschke - marios - Martin Kopec - Martin Mágr - Matthias Runge - Michael Turek - Michał Dulko - Michele Baldessari - Natal Ngétal - Nicolas Hicher - Nir Magnezi - Otherwiseguy - Gabriele Cerami - Pete Zaitcev - Quique Llorente - Radomiropieralski - Rafael Folco - Rlandy - Sagi Shnaidman - shrjoshi - Sławek Kapłoński - Sofer Athlan-Guyot - Soniya Vyas - Sorin Sbarnea - Stephen Finucane - Steve Baker - Steve Linabery - Tobias Urdin - Tony Breeds - Tristan de Cacqueray - Victoria Martinez de la Cruz - Wes Hayutin - Yatin Karel - Zoltan Caplovic
*The Next Release Cycle* At the end of one release, focus shifts immediately to the next, Ussuri, which has an estimated GA the week of 11-15 May 2020. The full schedule is available at https://releases.openstack.org/ussuri/schedule.html.
Twice during each release cycle, RDO hosts official Test Days http://rdoproject.org/testday/ shortly after the first and third milestones; therefore, the upcoming test days are 19-20 December 2019 for Milestone One and 16-17 April 2020 for Milestone Three.
*Get Started* There are three ways to get started with RDO.
To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack http://rdoproject.org/install/packstack/ installation. You can run RDO on a single node to get a feel for how it works.
For a production deployment of RDO, use the TripleO Quickstart http://rdoproject.org/tripleo/ and you’ll be running a production cloud in short order.
Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program https://www.openstack.org/passport/. 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 participates in a Q&A service at https://ask.openstack.org. We also have our users@lists.rdoproject.org for RDO-specific users and operrators. 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 http://rdoproject.org/.
The #rdo channel on Freenode IRC is also an excellent place to find and give help.
We also welcome comments and requests on the CentOS devel mailing list https://lists.centos.org/mailman/listinfo/centos-devel and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net), 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 http://rdoproject.org/contribute/, peruse the CentOS Cloud SIG page https://wiki.centos.org/SpecialInterestGroup/Cloud, and inhale the RDO packaging documentation https://www.rdoproject.org/documentation/rdo-packaging/.
Join us in #rdo and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity https://twitter.com/rdocommunity. You can also find us on Facebook https://www.facebook.com/rdocommunity/ and YouTube https://www.youtube.com/RDOcommunity.