I have upgraded the database and the wordpress install that power this site to the current versions. Now it’s time to fix my table backup scripts. Please let me know if there are problems or unexpected behavior.
Part of the problem with moving to a smaller space is putting all the things you have accumulated into order once the move is finished. I’ve come to the realization that I need more shelf space for my computer and camera gear, and there’s none to be had without knocking out a few walls and building an addition on to the house. Even buying new bookcases is out, as there’s no available wall space to put them. It looks like I’m going to have to build up, not out.
I’d already been thinking about building myself a proper computer desk for a number of months. At the moment, I’m using a folding card table as a work surface. It’s sturdy, it works, but it’s a pain. It’s the wrong height for me to work at and it’s not wide or deep enough for my needs. What I’m looking at building will be nearly 7 feet long and 4 feet deep, with under-mounted wire management. If I keep it really simple, I’m looking at at least $70 in wood costs. If I build it out a little more, to handle the stereo and the printer, and possibly the speakers, the cost doesn’t go up too much, but the need for a solid plan does.
The desk is Phase 1. Phase 2 is to build a lofted bookcase above the desk. Two or three shelves high, running from wall to wall (leaving a space for the door, of course). That will have to come later, but I need to do enough design work on the desk to make the bookshelf a possibility later. It wouldn’t be a good thing to have to take the desk apart and rebuild it a few months after I assemble it, just to make the bookcase fit. So, it’s off to the bookstore to look at how to design and build desks and shelves, and time to learn how to properly operate woodworking tools.
The break I’ve been taking from blogging is willful and self-imposed. We have been moving from Raleigh to Chapel Hill, and only yesterday did we finally get the last box unpacked. We still have a lot of sorting and arranging to do – this house is smaller than the last – but we are out of the woods in terms of the dregs of moving. I don’t think I ever want to move the washer and dryer again, and the entertainment cabinet… don’t get me started.
Sadly, there’s more arranging to do, and soon. My wife’s grandfather passed away from a stroke a few days ago, and we had been keeping our extra furniture at his house. This will have to be moved in the near future – and I’m not sure where a gigantic dining room table fits into our life at this point. It would be a Greek tragedy to dispose of it now, so we will figure it out. Just another piece of the puzzle.
A number of months ago, I found myself working on a very large Nagios installation – 2000 hosts, 3300+ service checks, and that was just the beginning. Looking at what had been improved from Nagios 1.4 (which was the older version that was running and needed to be upgraded) and Nagios 3.2, the new shiny version, I saw a lot of under-the-hood kind of changes that are well appreciated, in terms of performance and scalability, but very little that would make an end user even slightly interested in the upgrade. The web interface is straight out of 1998 – using frames and compiled C code to drive CGIs. The database backend had been pulled out and made into a standalone product called NDOUtils, which was still listed as beta, and hadn’t received an update in over 2 years.
In short the primary Nagios developer had slowed down on the end user stuff – probably busy with other things. Today, I found out what those other things are, and I’m not sure I’m pleased. He has announced a commercial, closed-source front end called Nagios XI, that purports to fix a lot of the problems the community wants fixed. It looks like he’s been working with other projects (like pnp4nagios) to make Nagios XI similar to Zenoss or Groundworks – an better integrated monitoring, reporting and analytical platform.
What amuses me is that earlier this year, a number of independent developers became tired with the slow progress on Nagios, and forked the whole project. The name of the fork is Icinga, which is by design unpronounceable. They have already added Oracle databases as a supported backend, and fixed a number of long standing ndo2db problems. They are also close to releasing an AJAX-y web front end. All open source, and they are encouraging community involvement.
To be entirely honest, at this point, the next time I’m planning a major system upgrade, I’m going to look long and hard at Icing’s project. My predecessor had already abstracted away all the crummy web-UI for the Nagios, and I’m extending that as best I can. It looks like the Icing project has my priorities closer to heart than the ‘core’ Nagios developers. We’ll have to see how it shakes out.
I have installed OpenSolaris on a VM in my home network, and updated it to the latest bits (129 at the time of this writing), which supports ZFS’s new block-level deduplication. I’m delighted with the update – it’s reasonably fast (a small office server probably won’t notice the load increase at all) and it does exactly what it’s supposed to – only storing one copy of the blocks in a file, even when the blocks are present in different files. It’s a great way to save space on disk, especially if you are running backups of multiple computers, as there will be significant overlap between them.
This opens the way for me to get serious about rebuilding my two Solaris file servers, as there is no upgrade path from the Nevada builds to the OpenSolaris platform. I’ve already reinstalled the smaller of the two boxes, as it’s only remaining tasks had been running a backup DNS server and processing my network logs. I’m going to have to be much more careful when it comes to moving the larger server, as it hosts all my digital media, including my Aperture photo library. So, it’s time to test extensively on the new box and make sure any initial gotchas are ironed out.
The first interesting test was opening up all of my tar’ed and gz’ed home directory backups and dumping them into a dedup-enabled filesystem on the new system. It looks very promising – it’s a much more efficient way to store files as %90 of the data between backups hasn’t changed. Once I move all the old files off the zfs pool, I’ll be able to report the difference in space, and the reported dedup ratio.
The Guru College is Digg proof thanks to caching by WP Super Cache
