BLOG.info(self)

Update 2018-10-17: The plugin I discuss below no longer works with current versions of Thunderbird. Fortunately, there is another that provides the same functionality and is still compatible. See my followup post for details.

Quite a while ago my corporate calendar got switched from an internally hosted system to THE CLOUD!!!!

Ahem. Sorry, my buzzword detector went off and I flinched and hit caps lock. Don't ask me how that resulted in all of the !'s. ;-)

I did a post in the past about using caching and local mirrors to speed up TripleO development, but at this point TripleO has changed so much that pretty much everything in that post is completely outdated, so I thought it was time for another one about my current caching setup.

Status

It's been a while since my last OVB update, and I've been meaning to post a network diagram for quite a while now so I figured I would combine the two.

In general, the news is good. Not only have I continued to use OVB for my primary TripleO development environment, but I also know of at least a couple other people who have done successful deployments with OVB. There is also some serious planning going on around how to switch the TripleO CI cloud over to OVB to make it more flexible and maintainable.

Another summit has come and gone, and I survived two trans-Pacific flights! A mere 16 hours of sleep when I got home is all it took to (mostly) get over the jet lag. :-)

But this isn't a travel blog, so you probably don't care about that. You want to know what's going on with OpenStack, at least from my perspective. If you don't care about that either, the back button is ^thataway^. Or maybe \/thataway\/ if you're on a mobile device.

Because every decent project related to OpenStack has to go through at least one rename. ;-)

Actually there are practical reasons behind this rename. First, it turns out a lot of people think you're joking if you start talking about QuintupleO (and to be fair, the name started out as a very tongue-in-cheek thing). More importantly, OpenStack Virtual Baremetal has applications outside of just TripleO, which is a fact that tends to get lost in the Stack-ception of the old name.

Edit ( 2015-10-07): Some changes have happened recently in TripleO that have obsoleted the templates below. I've created a Git repo for the templates so it is easier to keep them up to date: https://github.com/cybertron/tripleo-network-templates The discussion below is still relevant, but the actual template snippets won't work in a current TripleO setup so they need to be replaced with the ones from Github.

It turns out I've had spammers registering accounts on this site for quite a while now. Fortunately, I require admin verification of any new accounts, so none of the spammers got anywhere. Unfortunately, I had failed to configure my email address, so I wasn't getting notified of any user registrations.

Configs updated 2017/2/28 to reflect what I'm using now.

As part of my continuing investigation into QuintupleO, I've been playing around with multi-node devstack to see how QuintupleO works across multiple compute hosts. The good news is that the answer is "quite well" (another blog post on that topic is probably needed as well), and since some of the devstack multi-host documentation I found through Google was a bit out of date, I thought I'd go ahead and post what I've been using for my devstack setup.

Yes, it's still a thing.

Evidently there is a belief out there that TripleO died this cycle (which is understandable, in some ways), but I assure you we are still hard at work on it. In fact, there are some big changes in progress as I write this.

Third time's a charm, right?

Well, yes and no. Overall I would call the summit a success, and a lot of good things came out of it. It wasn't all sunshine and puppies though, and there are definitely some things I personally, and we as a community, could improve. Which means I should have lots of interesting things to talk about in this post. Let's get right to it.