BLOG.info(self)

I was running fstrim on a couple of old drives in anticipation of installing them in an even older RAID controller that doesn't support the trim command.[0] To do this, I formatted the entire drive as ext4, mounted it, then ran fstrim -v /mnt/temp to discard all of the unused blocks. I did this using a USB-SATA adapter, and what I noticed was that after running fstrim the adapter activity light was still blinking like crazy. I was curious if fstrim was still running, even though the command had completed already.

The Oslo team held its second virtual PTG this week. We had a number of good discussions and even ran slightly over the 2 hours we scheduled, so I think it was a successful event. The first hour was mostly topics relating to Oslo itself, while the second hour was set aside for some cross-project discussions with the Nova team. Read on for details of both hours.

This has been driving me nuts for years. The problem is that when I move the mouse to the far left edge of the screen, my mouse clicks are ignored. I can't right click to bring up the context menu, I can't use the scroll wheel to switch virtual desktops. The latter is my particular pet peeve because I always leave a gap at the left edge of the screen, and when I want to change desktop I just move the mouse over there and scroll.

Updated 2020-08-10, see edit below

I recently had to upgrade a CentOS 7 server to CentOS 8. I foolishly expected this to be easy since it wasn't a heavily customized install in the first place and most of the stuff I cared about was in my home directory. I was, as you may have guessed, wrong.

The problem was that CentOS 8 removed the driver for the Dell H700 RAID controller in my server. Setting aside the wisdom of that decision, here's how to get around it:

I've recently had occasion to do a fair amount of work with Go modules and vendoring, and I've had trouble finding simple how-tos for doing some (to me) basic things. It turns out they aren't that complicated, but they do involve multiple systems working together which may not be obvious to Go newbies (like me!). I'm writing this down both for my own reference and in the hopes that maybe it will help someone else get started with this stuff. I make no promises as to the accuracy of these steps, but they did what I needed.

Fair warning: This post is a bunch of self-indulgent complaining. I've debated whether to even write it, but I'm hoping maybe it will be cathartic to put in words all of the godawful stuff that happened to me and - more importantly - my loved ones this year. I'm not in a glass-half-full kind of mood though, so I'm not holding my breath.

Despite my trepidation about the trip (some of it well-founded!), I made it to Shanghai and back for the Open Infrastructure Summit and Project Teams Gathering. I even managed to get some work done while I was there. :-)

First, I recommend reading the opening of Colleen Murphy's blog post about the event (and the rest of it too, if you have any interest in what Keystone is up to). It does an excellent job of describing the week at a high level. To summarize in my own words, the energy of this event was a little off. Many regular contributors were not present because of the travel situation and there was less engagement from local contributors than I would have hoped for. However, that doesn't mean nothing good came out of it!

In fact, it was a surprisingly active week for Oslo, especially given that only myself and two other cores were there and we had limited discussion within the team. It turns out Oslo was a popular topic of conversation in various Forum sessions, particularly oslo.messaging. This led to some good conversation at the PTG and a proposal for a new Oslo library. Not only were both Oslo summit sessions well attended, but good questions were asked in both so people weren't just there waiting for the next talk. ;-) In fact, I went 10 minutes over time on the project update (oops!), in part because I hadn't really planned time for questions since I've never gotten any in the past. Not complaining though.

Read on for more detail about all of this.

This is a problem I ran into recently and found only one other discussion of, which turned out to be unrelated to my situation. In short, running podman image prune on my system was failing with the following error message:

Error: failed to prune image: Image used by bbe74e76b2e3850ea27f2498ca4e504d271ac230a00c496a37291f3ee8d8b49c: image is in use by a container

Thing is, I had no containers on the system when this error happened. It seems that the actual problem was that I had built an image using buildah, and podman couldn't handle that.

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.