>> But what sort of user experience and system architecture is intended? >> Is configuration of volumes planned to be done directly from the oVirt >> UI? > > Once a DRBD Manage storage cluster is set up, oVirt would handle the > management of DRBD volumes.
So does this mean there would be some kind of a "DRBD" cluster, like the "Gluseter cluster" oVirt has right now? >> As far as using DRBD for backing oVirt VMs, this seems to already be >> working. The oVirt CI system (which runs on top of oVirt) had been >> using a DRBD-backed NFS storage for years... >> > > The most recent release of DRBD contains new features that allow it to > integrate more directly with virtualization/cloud platforms. So VMs could > have DRBD-backed storage without additional overhead from NFS. Could you elaborate a little on how this works? Would this means the block devices would be configured on the hypervisors themselves? Is this intended to be some kind of a hyper-converged architecture? -- Barak Korren [email protected] RHEV-CI Team _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
