OpenQRM headaches

I spent another 4 hours testing (or better: trying to get running!) OpenQRM. I already worked on getting it built, installed, and getting a Xen host and guest domains running and controlled with it for some more 24 hours over two days a while ago, without real success yet.

While OpenQRM seems like an interesting solution for people who want to build an control a complete datacenter in exactly the way the OpenQRM guys define it, it is definetely not a flexible solution, or something that can be "simply and easily" used for managing Xen systems - and that's what I tried to do with it.

Even changing the IP address of the storage server to be used wasn't easily possible - the way to go if you need that, is: adding a new storage server, and adding all the images that are available on this server again, manually, then changing all systems using this storage server to use the new one.

Matt, the project manager, is very helpful and responsive when I ask things on the meiling list, and he's a really nice guy. Still, I cannot give the tool good credits for the things I am testing it for: having a management console for a Xen server and infrastructure.

There are some other downsides of openqrm: it's packages come with a lot of stuff that is put into /opt - a lot of libraries which can be found on any system are doubled here, just in different versions.
I've been explained that is because "the other versions of these libraries don't fit our needs".
So I have busybox, rsync, php5(I don't even unsderstand what this is for, as the web interface is running as a servlet in tomcat), and others lying around in /opt in some random versions.

What about security updates to these? Will OpenQRM developers make a new release when any of these has security problem? Will I (easily) be able to install a new version of these libs myself, and OpenQRM will run fine with the security fixed version?
Will there be simple installable packages from the main software repositories of any distribution?
Probably none of these can be answered with a "yes".

These things are all good for the people offering support for the software - if any problem in any of these areas arises in your production datacenter after you decided to use OpenQRM, they will make quite some cash - if you have it. If not, you're lost.
I think this is vendor lock-in at it's best - exactly the contrary what you want to get if you decide to use Open Source software.

It's definitely a project that has it's niche where it will find it's users, but I don't see me becoming a big fan of it...
Still, I will look at it again in a while, to see if it made some progress. :)