From bdcd788119ce338f431c7ee1c6fc9a0db5642065 Mon Sep 17 00:00:00 2001 From: Taku Fukushima Date: Fri, 10 Jun 2016 12:58:44 +0900 Subject: [PATCH] Move the description of the pool member creation This patch moves the description of the pool member creation to the section for the kube-proxy emulation using the LBaaS. Change-Id: I7e93f31d02cbb518f3910008c1e8513f37dda302 Signed-off-by: Taku Fukushima --- doc/source/devref/k8s_api_watcher_design.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/source/devref/k8s_api_watcher_design.rst b/doc/source/devref/k8s_api_watcher_design.rst index 9719a376..a9fc5ddc 100644 --- a/doc/source/devref/k8s_api_watcher_design.rst +++ b/doc/source/devref/k8s_api_watcher_design.rst @@ -75,16 +75,15 @@ API. The apiserver ensures namespaces are created before pods are creted. Pods contain the information required by creating Neutron ports. If pods are associated with the specific namespace, the ports are created and associated -with the subnets for the namespace. In this case Raven also creates a LBaaS -member for each port translated from the pod coordinating with the service -translation. +with the subnets for the namespace. Although it's optional, Raven can emulate kube-proxy_. This is for the network controller that leverages isolated datapath from ``docker0`` bridge such as Open vSwitch datapath. Services contain the information for the emulation. Raven -maps kube-proxy to Neutron load balancers with VIPs. For "externalIPs" type K8s -service, Raven associates a floating IP with a load balancer for enabling the -pubilc accesses. +maps kube-proxy to Neutron load balancers with VIPs. In this case Raven also +creates a LBaaS pool member for each port translated from the pod coordinating +with the service translation. For "externalIPs" type K8s service, Raven +associates a floating IP with a load balancer for enabling the pubilc accesses. ================= ============= Kubernetes Neutron