Community Blog Round Up: 30 August

Published by on

There have only been four articles in the past month? YES! But brace yourself. Release is HERE! Today is the official release day of OpenStack’s latest version, Rocky. And, sure, while we only have four articles for today’s blogroll, we’re about to get a million more posts as everyone installs, administers, uses, reads, inhales, and embraces the latest version of OpenStack. Please enjoy John’s personal system for running TripleO Quickstart at home as well as how to update ceph-ansible in a containerized undercloud, inhale Gonéri’s introduction to distributed CI and InfraRed, a tool to deploy and test OpenStack, and experience Jiří’s instructions to upgrade ceph and OpenShift Origin with TripleO.

Photo by Anderson Aguirre on Unsplash

PC for tripleo quickstart by John

I built a machine for running TripleO Quickstart at home.

Read more at http://blog.johnlikesopenstack.com/2018/08/pc-for-tripleo-quickstart.html

Distributed-CI and InfraRed by Gonéri Le Bouder

Red Hat OpenStack QE team maintains a tool to deploy and test OpenStack. This tool can deploy different types of topologies and is very modular. You can extend it to cover some new use-case. This tool is called InfraRed and is a free software and is available on GitHub.

Read more at https://blogs.rdoproject.org/2018/08/distributed-ci-and-infrared/

Updating ceph-ansible in a containerized undercloud by John

In Rocky the TripleO undercloud will run containers. If you’re using TripleO to deploy Ceph in Rocky, this means that ceph-ansible shouldn’t be installed on your undercloud server directly because your undercloud server is a container host. Instead ceph-ansible should be installed on the mistral-executor container because, as per config-download, That is the container which runs ansible to configure the overcloud.–

Read more at http://blog.johnlikesopenstack.com/2018/08/updating-ceph-ansible-in-containerized.html

Upgrading Ceph and OKD (OpenShift Origin) with TripleO by Jiří Stránský

In OpenStack’s Rocky release, TripleO is transitioning towards a method of deployment we call config-download. Basically, instead of using Heat to deploy the overcloud end-to-end, we’ll be using Heat only to manage the hardware resources and Ansible tasks for individual composable services. Execution of software configuration management (which is Ansible on the top level) will no longer go through Heat, it will be done directly. If you want to know details, i recommend watching James Slagle’s TripleO Deep Dive about config-download.

Read more at https://www.jistr.com/blog/2018-08-15-upgrading-ceph-and-okd-with-tripleo/

Article written by

Rain is a systematic, slightly psychic, interdisciplinary community liaison with a Bachelor’s in dance and a Master’s in IT. An epic public speaker, she has disappeared within a box stuffed with swords, created life, and flown through the air with the greatest of ease. Seriously. Rain is an active technical contributor with RDO, Fedora Project, OpenStack, TripleO, and DjangoGirls. Come say hello. Bring cake.