<div dir="ltr">Yeah, the hard part ahead is really to determine the workflow of each<div>of these calls. It would be great if we could have the steps needed to enable</div><div>an iscsi deployment, not necessarily based on GlusterFS.</div><div><br></div><div>For example, let's say a container called iscsi-server requests a shared PVC</div><div>from Kubernetes which is satisfied by GlusterFS. Once the container comes</div><div>up, what does the container do to provide an iscsi endpoint consumable by</div><div>another Kubernetes container?</div><div><br></div><div>- Luis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 17, 2016 at 6:02 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey All,<br>
<br>
Prasanna pointed me to a proposed block API page [1] that Luis created<br>
after a discussion Pranith and me had with him some time back.<br>
<br>
We discussed modeling block APIs in Heketi along the lines of<br>
OpenStack Cinder's APIs. The wiki page has a few basic APIs which seem<br>
good to get us going.<br>
<br>
We still need to evolve details on how the APIs are handled but if we<br>
can have some early reviews on the proposed APIs that would be great!<br>
<br>
Thanks,<br>
Vijay<br>
<br>
<br>
[1] <a href="https://github.com/heketi/heketi/wiki/Proposed-API:-Block-Storage" rel="noreferrer" target="_blank">https://github.com/heketi/<wbr>heketi/wiki/Proposed-API:-<wbr>Block-Storage</a><br>
______________________________<wbr>_________________<br>
heketi-devel mailing list<br>
<a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
</blockquote></div><br></div>