Rephrase "networking basis" in watcher devref

This patch replaces "networking basis" with "basic Neutron constructs"
in doc/source/devref/k8s_api_watcher_design.rst.

Change-Id: I1043adc70b8f9c77f85870cdb0824044db17719c
Signed-off-by: Taku Fukushima <f.tac.mac@gmail.com>
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
This commit is contained in:
Antoni Segura Puimedon 2016-08-30 17:48:41 +02:00
parent e2a537937a
commit 8888c860df
No known key found for this signature in database
GPG Key ID: 2329618D2967720A
1 changed files with 3 additions and 3 deletions

View File

@ -62,9 +62,9 @@ The main focus of Raven is the following resources.
* Service (Optional) * Service (Optional)
* Endpoints (Optional) * Endpoints (Optional)
Namespaces are translated into the networking basis, Neutron networks and Namespaces are translated into the basic Neutron constructs, Neutron networks
subnets for the cluster and the service using the explicitly predefined values and subnets for the cluster and the service using the explicitly predefined
in the configuration file, or implicitly specified by the environment values in the configuration file, or implicitly specified by the environment
variables, e.g., ``FLANNEL_NET=172.16.0.0/16`` as specified variables, e.g., ``FLANNEL_NET=172.16.0.0/16`` as specified
`in the deployment phase <https://github.com/kubernetes/kubernetes/search?utf8=%E2%9C%93&q=FLANNEL_NET>`_. `in the deployment phase <https://github.com/kubernetes/kubernetes/search?utf8=%E2%9C%93&q=FLANNEL_NET>`_.
Raven also creates Neutron routers for connecting the cluster subnets and the service subnets. Raven also creates Neutron routers for connecting the cluster subnets and the service subnets.