[heketi-devel] Block APIs with Heketi

[Luis Pabon]

Yeah, the hard part ahead is really to determine the workflow of each
of these calls.  It would be great if we could have the steps needed to
enable
an iscsi deployment, not necessarily based on GlusterFS.

For example, let's say a container called iscsi-server requests a shared PVC
from Kubernetes which is satisfied by GlusterFS.  Once the container comes
up, what does the container do to provide an iscsi endpoint consumable by
another Kubernetes container?

- Luis

On Thu, Nov 17, 2016 at 6:02 PM, Vijay Bellur <vbellur at redhat.com> wrote:

> Hey All,
>
> Prasanna pointed me to a proposed block API page [1] that Luis created
> after a discussion Pranith and me had with him some time back.
>
> We discussed modeling block APIs in Heketi along the lines of
> OpenStack Cinder's APIs. The wiki page has a few basic APIs which seem
> good to get us going.
>
> We still need to evolve details on how the APIs are handled but if we
> can have some early reviews on the proposed APIs that would be great!
>
> Thanks,
> Vijay
>
>
> [1] https://github.com/heketi/heketi/wiki/Proposed-API:-Block-Storage
> _______________________________________________
> heketi-devel mailing list
> heketi-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/heketi-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/heketi-devel/attachments/20161207/33355e6a/attachment.html>