From 9e56987d811535d278be354fadae61c72b695354 Mon Sep 17 00:00:00 2001 From: subhamkrai Date: Tue, 12 Apr 2022 15:06:02 +0530 Subject: [PATCH] docs: update design doc path in multus design update design doc path in multus design. Signed-off-by: subhamkrai --- design/ceph/multus-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/ceph/multus-network.md b/design/ceph/multus-network.md index 678751b0c351..53742a03c620 100644 --- a/design/ceph/multus-network.md +++ b/design/ceph/multus-network.md @@ -1,7 +1,7 @@ # Multus networking integration with Ceph (not finalized yet and subject to update) We have already explored and explained the benefit of multi-homed networking, so this document will not rehearse that but simply focus on the implementation for the Ceph backend. -If you are interested in learning more about multi-homed networking you can read the [design documentation on that matter](../core/multi-homed-cluster.md). +If you are interested in learning more about multi-homed networking you can read the [design documentation on that matter](../common/multi-homed-cluster.md). To make the story short, [Multus](https://github.com/intel/multus-cni) should allow us to get the same performance benefit as `HostNetworking` as well as increasing the security. Using `HostNetworking` results in exposing **all** the network interfaces (the entire stack) of the host inside the container where Multus allows you to pick the one you want.