TripleO

I've finally gotten around to recording a demo of the current iteration of my tool to generate TripleO network isolation templates. You can watch the demo video (in which I say "umm". A lot. Sorry.) or check out the tool itself. There are also some templates generated with the tool if you want examples to start from.

This is sort of a PSA for something that has been available for quite a while. I run a Jenkins job locally that does RPM builds of proposed changes to a number of TripleO repos. This can be helpful if you want to test a change locally as it means you don't have to pull the code down and do a build yourself. Just sudo yum install -y https://repos.fedorapeople.org/repos/openstack-m/jenkins/rpm-build/333121/4/instack-undercloud-999.9.9-99999.noarch.rpm (for example) and you've got the change installed.

I had hoped to have this ready before the Austin summit, but...it didn't happen. Even so, this is the latest big advancement in OVB. It's now possible to do a baremetal-style deployment to OpenStack instances in a completely unmodified OpenStack cloud. Here's video proof: OVB on a stock OpenStack cloud.

This is going to be a bit of a different summit recap than my previous ones. Since Steve Hardy has already posted an excellent summary of the major TripleO topics from this summit, I'm not going to duplicate all of that here.

Instead, this will be a more personally focused post, wherein I reflect on my experience at this summit and how it compared to previous ones. If that kind of navel-gazing sounds incredibly uninteresting, then you might want to pull the rip cord now. :-)

One of the first things a new user of TripleO has to do is write a configuration file for their undercloud. While this is not as complex as, say, writing a nova.conf, there is still some level of difficulty due to the need for consistency between different options, and some less than ideal overlap/inconsistency between the options themselves. In the interest of easing new users' introduction to TripleO as much as possible, I've written a tool to help create undercloud.conf.

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.

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.

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.