Everything is a Freaking DNS problem - vendorlock http://127.0.0.1:8080/blog/taxonomy/term/610/0 en Vendor Lock vs Vendor Lock http://127.0.0.1:8080/blog/node/496 <p>Henning Sprang seems to have a different view on the concept of a <cite>Vendor LockIn</cite> than I do</p> <p>On his blog <a href="http://lazyb0y.blogspot.com/2007/11/openqrm-vs-vendor-lock-in.html#links" rel="nofollow">The daily laziness: OpenQRM vs. vendor lock in???</a> , he describes how openQRM <cite>Locks</cite> into using .. openQRM.</p> <p>Well, not really .. at least not in my opinion, although openQRM still has a long way to go and the proposals for a meaner and leaner Henning gives are certainly valid, </p> <p>openQRM however does not force you to do anything you don't like. The source is available and free, you can modify its behaviour , you yourselve can spend time on in, learn and modify the platform no one .<br /> (given the complexity I agree you won't dive into it in just 5 minutes but you nothing (b)locks you) </p> <p>Certainly in the virtualization field openQRM gives you the freedom to migrate your machines from one virtualization technology to another, Today VMWare, tomorrow KVM, the week after Xen<br /> or all 3 or them from one management console (can come handy after a merger) all with the same interface. None of the commercial products out there will even think about giving you a GUI to manage their competition.</p> <p>On top of that when you go out and buy VMWare , you can only manage VMWare instances and you get a framework that will also force you to work in a way you can't change. You have only one company to talk to, VMWare, (maybe via its integrators but they can't fix issues , they don't have the source) with openQRM you can hire other people besides Qlusters , you can change to another organisation to support you. </p> <p>Try that with VMWare , I fear you are Locked In</p> http://127.0.0.1:8080/blog/node/496#comments kvm lockin openqrm qemu vendorlock vmware xen Mon, 05 Nov 2007 22:56:54 +0000 Kris Buytaert 496 at http://127.0.0.1:8080/blog