-
At the end of last week, I spied an exciting tweet about oVirt: Not long after I started using oVirt and Gluster together, the projects started talking about a way to improve Gluster performance by enabling virtualization hosts to access Gluster volumes directly, using Gluster’s libgfapi, rather than through a FUSE-mounted location on the virtualization host. There was a little bit of fit and finish work to be done, and then we’d all be basking in the glow of ~30%…
·
¶¶¶¶¶
¶¶¶¶¶
¶¶¶¶¶
-
One of the cooler new features in oVirt 3.1 is the platform’s support for creating and managing Gluster volumes. oVirt’s web admin console now includes a graphical tool for configuring these volumes, and vdsm, the service for responsible for controlling oVirt’s virtualization nodes, has a new sibling, vdsm-gluster, for handling the back end work. Gluster and oVirt make a good team — the scale out, open source storage project provides a nice way of weaving the local storage on individual compute nodes…
·
¶¶¶¶¶
¶¶¶¶¶
¶¶¶¶¶
-
Update: I’ve written an updated version of this guide for oVirt 3.2. Last February or so, I wrote a post about getting up and running with oVirt, the open source virtualization management project, on a single test machine. Various things have changed since then, such as a shiny new oVirt 3.1 release, so I’m going to update the process in this post. What you need: A test machine, ideally an x86_64 system with multiple cores, hardware virtualization extensions and plenty…
·
¶¶¶¶¶
¶¶¶¶¶
¶¶¶¶¶
-
NOTE: The most recent version of this howto, for oVirt 4.1, lives HERE. As a fan both of x86 virtualization and of open source software, I long wondered when the “Linux of virtualization” would emerge. Maybe I should say instead, the GNU/Linux of virtualization, because I’m talking about more than just a kernel for virtualization — we’ve had those for a while now, in the forms of Xen and of KVM. Rather, I’ve been looking for the virtualization project that’ll…
·
¶¶¶¶¶
¶¶¶¶¶
¶¶¶¶¶
jebpages 