A Friend asked me a question about the following piece of music:

I am moving all of my tooling over from Docker to podman and buildah. One thing I want to reproduce it the mariadb setup I used.

When building a strategy for computing, we need to think large scale. I’ve been trying to frame the discussion in terms of a million nodes in a dozen data centers. How is OpenStack going to be able to handle this?

In my last post, I went from the Azure Web Portal to the command line. Time to go one step further and use Ansible.

While Azure figured prominently in my work about a year ago, I have not had as much to do with it again until recently. I had to relearn everything I had set up last year. As a Keystone and FreeIPA developer, I was focused on identity. Thus, it is somewhat ironic that I had problems getting my head around the identity setup when using Ansible to manage Azure. Here are the steps I went through to go from using the Web Portal to getting Ansible to work. Part one gets through the identity stuff.

One of the main reasons for a strategy of “go virtual first” is the ease of checkpointing and restoring key pieces of infrastructure. When running a PXE provisioning system, the PXE server itself is a piece of key infrastructure, and thus is a viable candidate for running in a Virtual Machine. How did I set up the network to make that possible? macvtap.

OpenStack is Network intensive. The setup I had previously, based around a Juniper Router, did not have enough Ports to reflect a real OpenStack deployment. I decided to forgo GigE speeds and get an older Cicso Catalyst 2960-WS Switch. Here is the new setup.
Continue reading →

The tools that we’ve used to develop Keystone have changed a bit over the years.  As I work on some long standing bugs, I’ve had to learn what the latest tools are, and how to use them.  Recently I had to track down the cause of a failed Tempest run.  Here are the steps I went through to find the trace.

Continue reading →