Everything is a Freaking DNS problem

Alan Robertson is discussing how Managed Virtualization (including HA) conflicts with System Management

He has some interesting points regarding managing infrastructure , in his vision there are just too much layers that don't talk to eachother .
He also points out some of the issues with CIM and SNMP .

Alan thinks the ideal way to go is to have your HA solution manage your Virtualization also.

I`m wondering if this doesn't add too much complexity.

If you are already making sure the services in your virtual machines are highly available, then why would you want to add another layer of complexity ? Surely the idea of being able to migrate virtual machines around sounds tempting but do we really need that extra layer of complexity ?

I've explained that migrating a virtual machine to another server won't help you when your apps crash or when your physical server fails.

But keeping an overview of which services are running where from 1 place seems like an interesting idea.

I've been tinkering about using the resource concept of Linux-HA however to serve another purpose than pure high availability. You might want to use its constraints to define how many virtual machines should run on and how much resources they can use on a certain physical machine. Hence create a loadbalancing infrastructure with it.

(I`m really really hoping someone now replies to this with a url which gives me a HAResource that does Live Migration :))

Most people who know me remember me having a passion for oldskool hardware, So the Computer History museum having a set of videos up on YouTube. looks interresting

I hope one day , we can have a similar museum at this side of the ocean.. I still have most of my hardware collection to donate there !

So you like this project and start pushing feedback, and small patches
on a frequent base to the project lead . At a certain point in time the
project lead gets so overloaded or fed up with your patches that he
decided there has to be a way for you to stop annoying him.

So he'll give you CVS commit access.

That's the day you'll break the project with your patch :)

Everybody who once spent 5 minutes debugging drupal forms will spot the difference..

$form['currency'] = array(
 '#type' => 'textfield',
 '#title' => t('currency'),
 '#size' => 60,
 '#maxlength' => 255,
 '#default_value' => $dateset->currency,
 '#description' =>t('currency')
);

Looks an awfull lot like

$form['currency'] = array(
 '#type' => 'textfield',
 '#title' => t('currency'),
 '#size' => 60,
 '#maxlength' => 255,
 '#value' => $dateset->currency,
 '#description' =>t('currency')
);

Only the second one isn't much use in a form :)

New Zealand sounds like a much better place to emigrate to than The Netherlands

The Netherlands is heading to more Open Source adoption with a with a policy !

Under the policy, approved Wednesday, government organizations will still be able to use proprietary software and formats, but will have to justify that decision under the principle of "adopt or explain" why not,

It's a really good example of what other governements should do ..

But then again .. we first need a governement :(

Russel has a good insight on blogrolls

Probably the best way of acknowledging your friends via blogging (if you choose to do so) would be to make an occasional links post which contains short positive recommendations to the best posts your friends wrote. If every month or two someone writes a links post (post which has little content, merely recommendations for other posts) which references your posts then you know that they like you (and you get a Technorati.com boost), so a blogroll entry hardly seems necessary. An additional benefit for giving such direct credit is that the person receiving the links will know what you consider to be their best work which will help them in their future writing.

Karan wonders over an EEE or a Nokia ..

Given the fact that I never used my 700 really much I'd opt for the EEE.
It seems to have a decent keyboard that I can use to write mails and stuff.
If anyone around has one .. I`d love to test if it is actually usable as a Laptop replacement to travel with.

Hmm.. I should probably tag it with dowant on delicious :)

For those of you reading my blog the old fashioned way with a browser you might have seen the ProfOss Virtualisation conference Badge popping up on the right.

For the others:

So come and hear me speak at ProfOSS next January !

Not even that long ago I discussed Innovation in Open Source projects ..

Let me refresh your memory...
Call me oldfashioned but I still think of most of the closed source shops as 9to5 developers that write code because their boss tells them. Their boss is being instructed by clueless marketing people that promise impossible features to customers with impossible deadlines. An Open Source developer writes code because he wants to fix something , because he needs a feature , not because someone tells him to do so. To there is much more passion to be found in the heart of an open source developer than in your average closed shop developer.

Now add Michael Dolan 's comments on Open Source projects lead and managed by a sole corporate with no actual community to my notes.

Then try to understand why Sun announces this , now I wonder .. what are they going to pay people for .. features that the corporate product management wants, or features the community wants ? There is money involved .. so who will be calling the shots ?
I hope they make the right choices .. I really do !

But I'm afraid Sun still doesn't understand how to play with the opensource crowd. They try .. but run into too much walls As Michael notes , you can hardly call Open Solaris a succesfull open source project as it still doesn't have a real community. I hope one day they will realise that , drop their commercially driven doomed to fail open projects and start contributing to some projects with a real community. It took them a while to figure out the right thing to do with Java .. I`m sure they'll learn and figure out this time also :)

Sun isn't the only one not to understand how the community works.. but it's one of the most public ones that needs our help.

So what have we learned so far ..
* Open Sourcing an end of life proprietary proprietary does not work
* Managing an Open Source in oldschool inhouse proprietary style doesn't work

And lots more ...