QuintupleO Status Update

At the Atlanta OpenStack Summit we had a session on something called QuintupleO, otherwise known as "TripleO wasn't confusing enough, let's add another layer" :-) Barring a few specific concerns from other teams, which I believe have now been addressed to their satisfaction, everyone seemed to be on board with the idea. But what exactly is QuintupleO, and where does it stand today? Read on to find out.

Host Filesystem Impact on Tempest Performance in OpenStack

As I mentioned in a previous post, about a year ago I picked up a 1U server from EBay to use as a local single-node OpenStack environment. In general I was quite happy with it, but at some point I got tired of paying for electricity to run a fairly power-hungry server that sits idle, or close to it, about 95% of the time. The fans also picked up an annoying whine somewhere along the line, so once I discovered how much more efficient a modern desktop processor would be, while actually performing better than the old dual server ones, I decided it was time for a new box. This post will be the story of my journey to get Tempest running in an acceptable fashion on it, and what I learned along the way.

Debugging Syntax and Import Errors in OpenStack Unit Tests

Most OpenStack projects use a combination of tox, testr, and subunit to run their unit tests. This works fine as long as you don't have any simple errors in your code, such as a typo in an import or a missing closing paren. In those cases testr or subunit may swallow the error and you won't know exactly where it is (I hear this may be fixed in some version of the tools, but the one I'm currently using still has this limitation). To fix this, we need another way to run unit tests that will expose the actual error to us.

Using a Branch Under Review in TripleO

One of the unintended consequences of Feature Freeze in OpenStack is that a lot of new features get merged in a hurry at the end of the cycle. That's obviously not ideal, but it's a reality we all have to live with for now. TripleO has been bitten by this a few times recently, and the long gate queue that also goes along with Feature Freeze means sometimes fixes for problems take a long time (days) to merge in the other projects. In the gate we have tempreverts and cherry-picks to mitigate that problem, but for local devtest those features are not available. Fortunately there's another solution.

Debugging Early Dracut Problems

I've recently been trying to enable the Dracut deploy ramdisks I posted about earlier for RHEL7. I've been running into some issues that weren't present on the other platforms I've tested so far, and because of that I want to ask for some help from some Dracut experts. Unfortunately, the problem I'm having occurs so early in the Dracut boot process that it hasn't started any device management yet, so attaching a disk to collect logs doesn't work immediately.

Tags:

Dell CS24-SC Remote KVM on Linux

My working BMC Hotkey settings

A little less than a year ago I picked up an old Dell CS24-SC 1U server from EBay. It's got a ton of power - dual quad core, 24 GB of RAM, 4 146 GB 15k SAS drives, and an integrated BMC. That last is something I've struggled with though. Because this is a server, I really don't want to leave a keyboard and mouse plugged in to it all the time. Unfortunately, I haven't been able to get the remote KVM functionality working. Until now, that is.

Using Dracut to Build Deployment Ramdisks

For TripleO I was tasked with enabling our deployment ramdisks to be built with Dracut. There are a couple of reasons we want to do this.

Juno Summit Thoughts

I attended my first OpenStack Summit in Atlanta last week, and now that I'm (mostly) recovered I wanted to write down some of my thoughts about the experience.

Updating Drupal on OpenShift

The first security update for Drupal since I started this blog was released a while back, and I negligently dragged my feet in actually applying it here because I was unsure how to do so in OpenShift. It turns out to be quite simple, but it did take me a while to figure out all the steps so I figured I would write them down here to help anyone else doing the same thing.

My Devtest Workflow

I said in a previous post that I would write something up about my devtest workflow once I had it nailed down a bit more, and although it's an always-evolving thing, I think I've got a pretty good setup at this point so I figured I'd go ahead and write it up. Instead of including scripts and such here, I'm just going to link to my Github repo where all of this stuff is stored and reference those scripts in this post.

Pages

Subscribe to BLOG.info(self) RSS