BLOG.info(self)

One of the things that came out of the PTL tips and tricks discussion in Denver was that some people are not in favor of courtesy ping lists for meeting reminders. The recommended method was to add a custom highlight to your client for "#startmeeting [name]". I did that, but I also decided to take the opportunity to add a custom highlight for "oslo" so I get notified when people are talking about Oslo-related things in other channels.

Just back from the Denver Summit and PTG, so here are my thoughts about the Summit. I expect to post my PTG wrapup to the openstack-discuss mailing list since it's more developer-specific.

Edit: It turns out this doesn't help as much as I thought. Jenkins ignores duplicate webhook calls, so this is only helpful if your Jenkins missed a call. I'm still searching for a decent way to re-run jobs on a Github repo. :-( I'm leaving the rest of the post in place because it still has some useful information in it.

As foretold in a previous post, OVB has been imported to OpenStack Infra. The repo can now be found at https://git.openstack.org/cgit/openstack/openstack-virtual-baremetal. All future development will happen there so you should update any existing references you may have. In addition, changes will now be proposed via Gerrit instead of Github pull requests. \o/

I recently helped track down a bug exposed by a recent oslo.privsep release that added threading to allow parallel privileged calls. It was a segfault happening in the privsep daemon that was caused by a C call in a privileged Neutron module. This, as you might expect, was a little tricky to debug so I thought I'd document the process for posterity.

As promised in my previous update on OVB, the 2.0-dev branch has been merged to master. If this breaks you, switch to the stable/1.0 branch, which is the same as master was prior to the 2.0-dev merge. Note that this does not mean OVB is officially 2.0 yet. I've found a couple more deprecated things that need to be removed before we declare 2.0. That will likely happen soon though.

There is some work underway to import the OVB repo from Github into the OpenStack Gerrit instance. This will allow us to more easily set up gate jobs so proposed changes can be tested automatically instead of the current "system" which involves me pulling down changes and running the test script against them. It will have some implications for users of OVB in the near future, so this is a summary of the plans and actions that need to be taken.

As I was going through cleaning up all of the spam accounts created on this blog over the holidays, it occurred to me that there have been precisely zero legitimate comments made in the approximately five years that it has existed. This makes me think that the time I've spent cleaning up after spammers has been wasted, and I'm no longer going to do it. As a result, user registration is now limited to administrators (me) so if you really want to comment on a post you'll need to ask me for an account through one of the contact methods listed in the About page

As mentioned in a previous update, OVB 2.0 is coming. This update to is to notify everyone that a development branch is available in the repo and discuss some of the changes made so far.

These topics may seem like strange bedfellows, but trust me: there's a method to my madness. Originally this was going to be part of my Berlin summit post, but as I was writing it got rather long and I started to feel it was important enough to deserve a standalone post. Since there are two separate but related topics here, I've split the post. If you're interested in my technical thoughts on upstream performance testing, read on. If you're only interested in the click-baity release-shaming part, feel free to skip to that section. It mostly stands on its own.