Here’s the latest edition of the community blog round-up. Thanks for your contributions!
Deleting an image on RDO by Adam Young
So I uploaded a qcow image… but did it wrong. It was tagged as raw instead of qcow, and now I want it gone. Only problem… it is stuck.
Keystonerc for RDO cloud by Adam Young
If you are using RDO Cloud and want to do command line Ops, here is the outline of a keystone.rc file you can use to get started.
Debugging TripleO revisited – Heat, Ansible & Puppet by Steve Hardy
Some time ago I wrote a post about debugging TripleO heat templates, which contained some details of possible debug workflows when TripleO deployments fail. In recent releases we’ve made some major changes to the TripleO architecture. In this post I’d like to provide a refreshed tutorial on typical debug workflow, primarily focusing on the configuration phase of a typical TripleO deployment, and with particular focus on interfaces which have changed or are new since my original debugging post.
Listing iptables rules with line numbers by Lars Kellogg-Stedman
You can list
iptablesrules with rule numbers using the
--line-numbersoption, but this only works in list (-L) mode. I find it much more convenient to view rules using the output from
FOSDEM ’18, and the CentOS Brussels Dojo by Rich Bowen
The first weekend in February always finds me in Brussels for FOSDEM and the various associated events, and this year is no exception.
Matching Create and Teardown in an Ansible Role by Adam Young
Nothing lasts forever. Except some developer setups that no-one seems to know who owns, and no one is willing to tear down. I’ve tried to build the code to clean up after myself into my provisioning systems. One pattern I’ve noticed is that the same data is required for building and for cleaning up a cluster. When I built Ossipee, each task had both a create and a teardown stage. I want the same from Ansible. Here is how I’ve made it work thus far.
Deploying an image on OpenStack that is bigger than the available flavors. by Adam Young
Today I tried to use our local OpenStack instance to deploy CloudForms Management Engine (CFME). Our OpenStack deployment has a set of flavors that all are defined with 20 GB Disks. The CFME image is larger than this, and will not deploy on the set of flavors. Here is how I worked around it.
Freeing up a Volume from a Nova server that errored by Adam Young
Trial and error. Its a key part of getting work done in my field, and I make my share of errors. Today, I tried to create a virtual machine in Nova using a bad glance image that I had converted to a bootable volume: