From f1f19d61244989d98b9720783bf9356b108cc902 Mon Sep 17 00:00:00 2001 From: liangcui Date: Wed, 23 Aug 2017 16:43:28 +0800 Subject: [PATCH] modify some misspellings in doc Change-Id: Ib03dac2b098180dc01910a7039eccaaeeea7060d --- doc/source/devref/kuryr_kubernetes_design.rst | 4 ++-- doc/source/installation/manual.rst | 4 ++-- doc/source/installation/ports-pool.rst | 2 +- doc/source/installation/services.rst | 2 +- doc/source/specs/pike/contrail_support.rst | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/devref/kuryr_kubernetes_design.rst b/doc/source/devref/kuryr_kubernetes_design.rst index 7ec70d9e5..e25454745 100644 --- a/doc/source/devref/kuryr_kubernetes_design.rst +++ b/doc/source/devref/kuryr_kubernetes_design.rst @@ -56,7 +56,7 @@ Design Principles should rely on existing communication channels, currently added to the pod metadata via annotations. 4. CNI Driver should not depend on Neutron. It gets all required details - from K8s API server (currenltly through K8s annotations), therefore + from K8s API server (currently through K8s annotations), therefore depending on Controller to perform its translation tasks. 5. Allow different neutron backends to bind K8s pods without code modification. This means that both Controller and CNI binding mechanism should allow @@ -120,7 +120,7 @@ case of the ResourceNotReady exception till it succeeds or the number of retries (time-based) is reached. Any unrecovered failure is logged without affecting other Handlers (of the current and other events). Events of the same group (same K8s object) are handled sequentially in the -order arrival. Events of different K8s objects are handled concurenlty. +order arrival. Events of different K8s objects are handled concurrently. .. image:: ../..//images/controller_pipeline.png :alt: controller pipeline diff --git a/doc/source/installation/manual.rst b/doc/source/installation/manual.rst index 3456fac0a..62cfacc25 100644 --- a/doc/source/installation/manual.rst +++ b/doc/source/installation/manual.rst @@ -63,7 +63,7 @@ Kubernetes load balancers and their members: will have gone through the router to reach the service. * Layer3: Octavia only creates the VIP port. The traffic from the service VIP to the members will go back to the router to reach the pod subnet. It is - important to note that will have some performance impact depending on the SDN. + important to note that it will have some performance impact depending on the SDN. At the moment Kuryr-Kubernetes supports only L3 mode (both for Octavia and for the deprecated Neutron-LBaaSv2. @@ -126,7 +126,7 @@ Link the CNI binary to CNI directory, where kubelet would find it:: $ ln -s $(which kuryr-cni) /opt/cni/bin/ Create the CNI config file for kuryr-cni: ``/etc/cni/net.d/10-kuryr.conf``. -Kubelet would only use the lexicographically first file in that direcotory, so +Kubelet would only use the lexicographically first file in that directory, so make sure that it is kuryr's config file:: { diff --git a/doc/source/installation/ports-pool.rst b/doc/source/installation/ports-pool.rst index 5fb67a921..478a12e21 100644 --- a/doc/source/installation/ports-pool.rst +++ b/doc/source/installation/ports-pool.rst @@ -14,7 +14,7 @@ And for the nested (VLAN+Trunk) case:: vif_pool_driver = nested On the other hand, there are a few extra (optional) configuration options -regarding the maximum and minimun desired sizes of the pools, where the +regarding the maximum and minimum desired sizes of the pools, where the maximum size can be disabled by setting it to 0:: [vif_pool] diff --git a/doc/source/installation/services.rst b/doc/source/installation/services.rst index 5fd8e43b5..2798a9a54 100644 --- a/doc/source/installation/services.rst +++ b/doc/source/installation/services.rst @@ -483,7 +483,7 @@ of doing the following: #. Configure Kubernetes API server to use only a subset of the addresses for services, **10.0.0.0/18**. The rest will be used for pods. To configure Kubernetes with this CIDR range you have to add the following parameter to - its command line invokation:: + its command line invocation:: --service-cluster-ip-range=10.0.0.0/18 diff --git a/doc/source/specs/pike/contrail_support.rst b/doc/source/specs/pike/contrail_support.rst index 0f5f65257..d6f5d1403 100644 --- a/doc/source/specs/pike/contrail_support.rst +++ b/doc/source/specs/pike/contrail_support.rst @@ -5,7 +5,7 @@ Kuryr Kubernetes OpenContrail Integration https://blueprints.launchpad.net/kuryr-kubernetes/+spec/kuryr-k8s-contrail-integration This spec proposes how to integrate OpenContrail with Kuryr-Kubernetes. -OpenContrail is an open source project that provides network virtuaization +OpenContrail is an open source project that provides network virtualization functionality to OpenStack. Integrating these will allow Kuryr to be used to bridge container-VM networking in a Contrail-based OpenStack deployment.