Aggregated news from external sources
If you run an infrastructure, there’s a good chance you have some debt tucked
in your system somewhere. There’s also a good chance that you’re not getting
enough time to fix those debts. There will most likely be a good reason why
something is done in the way it is. This is just how things are in general.
After I joined Gluster, I’ve worked with my fellow sysadmin to tackle our large
infrastructure technical debt over the course of time. It goes like this:
That is in no way and exhaustive list. But we’ve managed to tackle 2.5 items
from the list. Here’s what we did in order:
If I look at it, it almost looks like I’ve failed. But again, like dealing with
most infrastructure debt, you touch one thing and you realize it’s broken in
someway and someone depended on that breakage. What I’ve done is I’ve had to
pick and prioritize what things I would spend my time on. At the end of the
day, I have to justify my time in terms of moving the project forward. Fixing
the infrastructure debt for Gerrit was a great example. I could actually focus
on it with everyone’s support. Fixing Jenkins was a priority since we wanted to
use some of the newer features, again I had backing to do that. Moving things
to our hardware is where things get tricky. There’s some financial goals we can
hit if we make the move, but outside of that, we have no reason to move. But
long-term, we want to me mostly in our hardware, since we spent money on it.
This is, understandably going slow. There’s a subtle capacity difference and
the noisy neighbor problem affects us quite strongly when we try to do anything
in this regard.
Source: nigelb (Catching up with Infrastructure Debt)
In order to plan the content for upcoming releases, it is good to take a moment of pause, step back and attempt to look at the consumption of GlusterFS within large enterprises. With the enterprise architecture taking large strides towards cloud and more specifically, the hybrid cloud, continued efforts towards...
The Gluster community is pleased to announce the release of 7.0, our latest release. This is a major release that includes a range of code improvements and stability fixes along with a few features as noted below. A selection of the key features and bugs addressed are documented in this...
Progress cannot be made without change. As technologists, we recognize this every day. Most of the time, these changes are iterative: progresssive additions of features to projects like Gluster. Sometimes those changes are small, and sometimes not. And that’s, of course, just talking about our project. But one of the...