On 05/31/2016 12:15 PM, Yaniv Dary wrote:

Have you considered submitting a design document to the oVirt website.
We will be happy to help in making this happen.

I believe there is already one here: http://www.ovirt.org/develop/release-management/features/infra/drbd/

I would be happy to update it as that was written for DRBD 8.4 and I'm working with DRBD 9.

On Tue, May 31, 2016 at 8:54 PM, Hayley Swimelar <hayley@linbit.com> wrote:

On 05/31/2016 10:40 AM, Nir Soffer wrote:

On Tue, May 31, 2016 at 7:25 PM, Hayley Swimelar <hayley@linbit.com>
wrote:

On 05/31/2016 08:25 AM, Yaniv Dary wrote:

Can you explain the use case? What are you trying to use VDSM for?
The API you want to use is internal and can break without notice.

Hi Yaniv,

I'm working to to integrate DRBD storage into VDSM.

It will be a new type of storage domain, so I can't use the GUI since the
engine component won't be aware of it as far as I can tell.

The current plan is to have another developer on our end make changes to
the
Engine once the VDSM side is working.

Hi Hayley,

Sounds cool, can you describe in more details the use case, and how do
you think this
can work?

Hi Nir,

The use case is to make replicated block level storage available in oVirt.

VDSM should be able to communicate with DRBD via DRBD Manage, which is a
new administrative layer for the latest release.

Cheers,

Nir

--
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
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel