Then definitely don't go the Cinder route. We make WAY too many Ceph-centric assumptions there. I wonder how much effort it would be to implement a DRBD domain in a similar fashion to the existing block domains. On Mon, Jun 13, 2016 at 7:54 PM, Hayley Swimelar <hayley@linbit.com> wrote:
On 06/13/2016 09:51 AM, Allon Mureinik wrote:
Maybe I'm being daft, but I'm missing something basic here. What's the end goal? A DRBD Storage Domain in oVirt?
Hi Allon,
A DRBD Storage Domain in oVirt is the goal, yes.
On Fri, Jun 3, 2016 at 9:13 PM, Hayley Swimelar <hayley@linbit.com> wrote:
Hello all,
A DRBD integration into oVirt is currently being planned.
DRBD provides replicated, highly available block storage. For those unfamiliar with DRBD more information can be found here: https://www.drbd.org/en/comp/drbd-linux-driver
DRBD 9 is the latest version of DRBD and interacts with DRBD Manage which is a daemon exposed via a D-Bus api. More information can be found here: https://www.drbd.org/en/comp/drbdmanage
DRBD Manage handles the creation, assignment, etc. of DRBD volumes and is the interface through which Cinder manages DRBD.
We are looking for advice on how best to have oVirt communicate with DRBD Manage and we have come to two options:
1) Use Cinder. Although we are integrated into Cinder, there are concerns about the need to set up a complete Cinder instance to provide access to DRBD.
2) The alternative to Cinder would be to have the oVirt Engine communicate directly to DRBD Manage via D-Bus.
Any advice on the best way to achieve this would be much appreciated.
-- Hayley Swimelar LINBIT | Keeping the Digital World Running DRBD — Corosync — Pacemaker +1-503-573-1262 x212 _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Hayley Swimelar LINBIT | Keeping the Digital World Running DRBD — Corosync — Pacemaker +1-503-573-1262 x212