<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 6, 2021 at 1:04 AM Amnon Ilan <<a href="mailto:ailan@redhat.com">ailan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 30, 2021 at 2:50 AM Eric Ernst <<a href="mailto:eric.g.ernst@gmail.com" target="_blank">eric.g.ernst@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Ya'll,<div><br></div><div>I'd like to see if we can create a pattern in upstream Kata Containers to help facilitate directly assigning volumes to the VM via virtio-blk, skipping any mounts on the host, and avoiding needing to use a shared file-system for the particular volume. Some of the benefits in doing this:</div><div> - we can better isolate the host (no mounted filesystem),</div><div> - more efficient and much faster data path that non-dax virtiofs.</div><div> - avoid inode caching/memory overheads of virtiofs on the host.</div><div><br></div><div>In Kubernetes today, there is not a direct communication channel between CSI and the runtime. To make this work on a shorter timeline, therefore, we need to come up with a less traditional way to communicate between the user, CSI and the runtime. I have a proposal in place that "works" today, and I'd like to get feedback on how to improve it, and see if it could be a good fit for upstream. Please see: the proposal at [1], and the PR associated with that proposal at [2].</div></div></div></div></div></blockquote><div><br></div><div>I'm not an expert here, but why not use raw block rather than adding the annotation <span style="color:rgb(36,41,46);font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,monospace;font-size:13.6px;box-sizing:border-box">skip-hostmount</span> </div><div><a href="https://kubernetes.io/blog/2019/03/07/raw-block-volume-support-to-beta/" target="_blank">https://kubernetes.io/blog/2019/03/07/raw-block-volume-support-to-beta/</a></div><div><br></div><div><a class="gmail_plusreply" id="gmail-m_3945276000479580646plusReplyChip-2" href="mailto:owasserm@redhat.com" target="_blank">+Orit Wasserman</a> <br></div></div></div></blockquote><div><br></div><div>Hey Amnon,</div><div><br></div><div>Raw block is supported well in Kata today (it just works); the problem is that the workload/user would then need to utilize a raw block, when in most cases, they want a mounted filesystem to interact with.</div><div><br></div><div>The direct-assignment work's goal is to provide a mounted filesystem to the container workload.</div><div><br></div><div>Eric </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div><br></div><div>Thanks,</div><div>Amnon</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Please let me know if you:</div><div> - have any suggestions on the pattern</div><div> - you are a user that would find this pattern helpful for their use-cases</div><div><br></div><div>Thanks,</div><div>Eric</div><div><br></div><div>[1] - <a href="https://github.com/egernst/kata-containers/blob/da-proposal/docs/design/direct-assign-volume.md" target="_blank">https://github.com/egernst/kata-containers/blob/da-proposal/docs/design/direct-assign-volume.md</a></div><div>[2] - <a href="https://github.com/kata-containers/kata-containers/pull/1568" target="_blank">https://github.com/kata-containers/kata-containers/pull/1568</a></div><div><br></div></div></div></div></div>
_______________________________________________<br>
kata-dev mailing list<br>
<a href="mailto:kata-dev@lists.katacontainers.io" target="_blank">kata-dev@lists.katacontainers.io</a><br>
<a href="http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev" rel="noreferrer" target="_blank">http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev</a><br>
</blockquote></div></div>
</blockquote></div></div>