Hi, On 09/07/2012 05:59 PM, Neo Vlanik wrote: OpenStack is targeting an Elastic Cloud type network - people can buy server time, create instances themselves, install more or less what they want, and things like provisioning of time & server resources are important. oVirt is more for centrally-maintained networks of virtual machines, things like enterprise IT, university labs, test rigs where you have a nice big server or two and want to (say) test your web app on different distributions, with different browsers, that sort of thing. So there are different priorities, different technology choices, different target audiences. That said, it is possible to run through the OpenStack projects, and (aside from "Compute", their provisioning later) it's possible to draw parallels between pieces of the OpenStack architecture and pieces of the oVirt architecture. oVirt could, potentially, use OpenStack's image storage or identity service, and OpenStack could conceivably use pieces of oVirt to do the job for them. Of course, there are people around here who know this stuff much better than me, so it's entirely possible I've just made an ass of myself and the above is all wrong. Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

On 09/07/2012 08:46 PM, Jason Brooks wrote: I think both technologies are very complementary. OpenStack currently currently has no good management interface and I look at oVirt as mostly a cloud management interface. I can see a future in which oVirt is used to manage a bunch of openstack nodes. Quantum integration is already happening and User management is already external to oVirt so keystone can probably plugged in there at some point. Then either vdsm needs to learn to talk to nova or oVirt needs to learn to talk to nova as an alternative to vdsm. Regards, Dennis