Everything is a Freaking DNS problem

You must have noticed the fuzz around CentOS, the open Letter , and luckily Lance showing up again ..

I've been a long time CentOS user , so this kind of events are pretty close to my heart, I never really worried about the future of the project , the CentOS community is was standing behind their message as one group. If Lance wouldn't have shown up again quoting Arrfab:
"The worst would be to switch to another domain name .. but you already know that everything is a fscking DNS problem"

In this case it would actually be more of a mareketing problem :)

Fact is that sometimes an active community standing up against a lesser active project lead has it's results, however this time there probably won't be any other DNS entries to be added , but I hope one day the logo will become better :)

Jan Wildeboer pointed us to the Mayflower post about their letter from the European Commission.

It seems like the the European Commision , more specifically the Directorate General for Competition , really is interested in our input regarding the matter, I mailed them and also got a questionnaire to fill in.

So if you have something interesting to tell them don't hesitate to contact them too.

My yesterday post about RiverMuse only being available on Fedora Core 9 wasn't even cold yet and today Rivermuse already announced the availability of their RHEL5 binaries.

Awesome Open Source !

Probably every day there's a new Open Source project popping up left or right, sometimes they dissapear quickly , others are here to stay.

Enter Djagios, a Nagios configuration tool written in Django. At this time it's in development phase but development is going pretty good now, Djagios has been incepted by fellow Inuit Jochen Maes

It aims at filling the gap between the vi and emacs Nagios guru's and the manegerial type who just wants to and make Nagios usable for them.

We're already rolling out proof of concept setups of Djagios at different key customers so it's definitely here to stay :)

First of all, I don't come from a Tivoli, OpenView background , I have never touched the commercial network monitoring tools and I`m not a network guy . I'm an infrastructure guy whith a focus on Open Source platforms so I have been using Nagios and more recently Zabbix, Zenoss etc for the better part of the last 2 decades in large to very large environments.
My syslogs go to a central (r)syslog)-ng) server where I frequently abuse grep. So If my experience with RiverMuse is not what it should be , there's work to be done on both sides ;)

So When looking at my Rivermuse setup (in a VirtualBox FC9 setup) my first tought is "Those Rivermuse folks will really need to explain me what their tool is all about .. as to me it's just a fancy colortail integrated with snmp traps."

Hopefully it's not just that and it all becomes clear in a couple of days .. Apart from the FC9 annoyancy there is the frequent Unresponsive script errors.

And those I fear will be the real killer problems for RiverMuse

On the other hand, RiverMuse does good job in displaying the actual events in your network and following up the actions that one ... after a while you'll get a good overview of the actual issues as opposed to all the relevant events

I've dropped RiverMuse into my blade test setup (more on that subject later) and I`ll be keeping a look on what I can learn from it but the dreaded Unresponsive scripts that I know so well from Bamboo really need to be fixed :)

Well time will tell :)

So you need that old FC9 instance on your fresh F11 install.

Obviously I started a KVM instance on my desktop and installed FC9 in a Virtual Machine,
It took long to install, too long, so I looked if KVM was working correctly
Kvm was loaded but not in use ..
And then you remember why you had VirtualBox on that machine before it's upgrade . indeed, this machine was to old it was not a VT Capable machine . VirtualBox performs much better there ..

But you already have a working installed Qemu image.
What do you do ? Google tells you about vidtool but all you find are broken links ..

So you look further and you find that you can use VBoxManage for the same functionality

VBoxManage convertdd FC9.bin FC0.vdi

Rivermuse is the new Fault Management platform tool on the market, their initial relase was lurking around the corner for a while now but since earlier this week it finally arrived

Eager to see what all the fuzz was about I jumped to their dowload page to find an yum repository for Fedora Core 9, that's right .. it's july 2009 and RiverMuse released their platform for a Linux distribution that got it's End Of Life notice last month.

On a fresh Fedora 11 box off course you get a zillion dependency mismatches.
So over to the source code. After installing some build dependencies I managed to build desktop-trunk-8.fc11.noarch.rpm rivermusece-trunk-8.fc11.noarch.rpm
rpms

However these depend on extremely fresh versions of rsyslog >= 4.1.6 where as Fedora 11 is only on 3.21 and RHEL is even only on 2.0.6.

The initial checkout I had had no README file yet .. so creating a build wasn't really easy ..

In the meanwhile they have promised builds for other versions.

So the battle is between me getting time to setup an FC9 box somehwere and they releasing fresher RPM's .. I hope they win :)

Over at Virtualization.com I asked the crowd what they planned to do when RedHat plans on finally migrating from Xen to KVM .. you can have your say too . :

My FC10 to FC11 yum upgrade got stuck on a zillion dependencies .. well actually libssl and mysql from Remi .. but from there it's a whole chain of other things. So I had the great idea to go for the F11 Live CD, the LiveCD works like a charm,, only upon trying to install the live CD to my OS partition it started failing on me with a bunch of squashfs errors ,

It really looks like this F11Beta blocking issue which apparently didn't get solved completely after all.. the annoying part is that I can't reproduce the issue anymore .. as my system is now fully working .. maybe on my office desktop next week :)

Oh well.. the full DVD ISO got downloaded and burned and now I can once again enjoy the annoyancies of a freshly installed distro, missing packages, configs that have lightly chaged etc :) Wonder if sound is working out of the box now :)

Update: It works .. partly ... (no sound in firefox it seems atm..)

Dear Hardware / Appliance and any other kind of being that creates web interfaces to manage devices remotely. Pleaze keep in mind that plenty of these kind of machines are being managed from behind a ssh tunnel so people often connect to them using http://localhost:8080/ where 8080 locally is mapped e.g. via ssh to the port 80 on the remote port.

If your application does anything closely to rewriting the localhost:8080 part to localhost it will fail and I as a potential purchaser of your device wil vote against buying your stuff.
(This is specifically annoying if I want to tunnel 16 KVM/IP boxen to my localhost 8001:8016)

You offcourse score good points for supporting an ssh connection to that same device that allows me to do the everything I actually want to do :)