From b5b67db8d727c0003e2ec69bc40c7f938e69a8a5 Mon Sep 17 00:00:00 2001 From: Ariel Adam Date: Mon, 12 Oct 2020 15:36:16 +0300 Subject: [PATCH 1/2] docs: Fixing typo in virtualization.md file Changing "implementor" to "implementer" Fixes: #612 Signed-off-by: Ariel Adam Signed-off-by: Christophe de Dinechin --- docs/design/virtualization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/design/virtualization.md b/docs/design/virtualization.md index b019993be..67b480999 100644 --- a/docs/design/virtualization.md +++ b/docs/design/virtualization.md @@ -22,10 +22,10 @@ the multiple hypervisors and virtual machine monitors that Kata supports. ## Mapping container concepts to virtual machine technologies A typical deployment of Kata Containers will be in Kubernetes by way of a Container Runtime Interface (CRI) implementation. On every node, -Kubelet will interact with a CRI implementor (such as containerd or CRI-O), which will in turn interface with Kata Containers (an OCI based runtime). +Kubelet will interact with a CRI implementer (such as containerd or CRI-O), which will in turn interface with Kata Containers (an OCI based runtime). The CRI API, as defined at the [Kubernetes CRI-API repo](https://github.com/kubernetes/cri-api/), implies a few constructs being supported by the -CRI implementation, and ultimately in Kata Containers. In order to support the full [API](https://github.com/kubernetes/cri-api/blob/a6f63f369f6d50e9d0886f2eda63d585fbd1ab6a/pkg/apis/runtime/v1alpha2/api.proto#L34-L110) with the CRI-implementor, Kata must provide the following constructs: +CRI implementation, and ultimately in Kata Containers. In order to support the full [API](https://github.com/kubernetes/cri-api/blob/a6f63f369f6d50e9d0886f2eda63d585fbd1ab6a/pkg/apis/runtime/v1alpha2/api.proto#L34-L110) with the CRI-implementer, Kata must provide the following constructs: ![API to construct](./arch-images/api-to-construct.png) From 8ec3cf08f3928d3e7ef03a5d9c67e837730d37ba Mon Sep 17 00:00:00 2001 From: Ariel Adam Date: Wed, 26 Aug 2020 20:22:36 +0300 Subject: [PATCH 2/2] docs: Adding hyperlink to virtio-net in kata documentation 2.0 Referring virtio-net mentioning in the kata virtualization documentation to the virtio-networking blog series published and explaining how it works. Fixes #612 Signed-off-by: Ariel Adam --- docs/design/virtualization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/virtualization.md b/docs/design/virtualization.md index 67b480999..9467fa2a0 100644 --- a/docs/design/virtualization.md +++ b/docs/design/virtualization.md @@ -62,7 +62,7 @@ be changed by editing the runtime [`configuration`](./architecture.md/#configura Devices and features used: - virtio VSOCK or virtio serial - virtio block or virtio SCSI -- virtio net +- [virtio net](https://www.redhat.com/en/virtio-networking-series) - virtio fs or virtio 9p (recommend: virtio fs) - VFIO - hotplug