From f8322dffd306d5b8e1613891ba40275ff7a81d73 Mon Sep 17 00:00:00 2001 From: youri jeong Date: Tue, 11 Apr 2017 15:35:59 +0900 Subject: [PATCH] fix typo fix typo for specs/kubernetes-deployment.rst, tools/ovs-dpdkctl.sh, tools/setup_gate.sh 'managment' -> 'management' 'seperated' -> 'separated' 'occuring' -> 'occurring' 'discribed' -> 'described' 'recomended' -> 'recommended' 'thier' -> 'their' Change-Id: Ie59c600698c965cebd9a541b951d704eda9301cb --- specs/kubernetes-deployment.rst | 4 ++-- tools/ovs-dpdkctl.sh | 16 ++++++++-------- tools/setup_gate.sh | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/specs/kubernetes-deployment.rst b/specs/kubernetes-deployment.rst index c7eee00805..d5204f223c 100644 --- a/specs/kubernetes-deployment.rst +++ b/specs/kubernetes-deployment.rst @@ -10,7 +10,7 @@ pid=host, and --privileged features in docker. Since then, it has developed these features [1]. The objective is to manage the lifecycle of containerized OpenStack services by -using Kubernetes container managment tools in order to obtain the self-healing +using Kubernetes container management tools in order to obtain the self-healing and upgrade capabilities inherent in Kubernetes. Problem description @@ -86,7 +86,7 @@ the bootstrap tasks are reused to upgrade the database. This will allow deployment and upgrades to follow the same pipeline. The Kolla containers will communicate with the Kubernetes API server to in order -to be self aware of if any bootstrapping processes are occuring. +to be self aware of if any bootstrapping processes are occurring. Alternative bootstrap approaches: diff --git a/tools/ovs-dpdkctl.sh b/tools/ovs-dpdkctl.sh index 3b2d23586d..2b89ad4322 100755 --- a/tools/ovs-dpdkctl.sh +++ b/tools/ovs-dpdkctl.sh @@ -309,20 +309,20 @@ options: - debuging: - To enable debuging export OVS_DPDK_CTL_DEBUG=True - install: - - The varibles discribed below can be defined to customise + - The varibles described below can be defined to customise installation of ovs-dpdkctl. = ovs-dpdkctl.sh install - bridge_mappings: - - A comma seperated list of physnet to bridge mappings. + - A comma separated list of physnet to bridge mappings. - Example: bridge_mappings=physnet1:br-ex1,physnet2:br-ex2 - Default: "" - port_mappings: - - A comma seperated list of port to bridge mappings. + - A comma separated list of port to bridge mappings. - Example: port_mappings=eth1:br-ex1,eth2:br-ex2 - Default: generated form bridge_mappings assuming bridge names are constructed by appending br- to port name. - cidr_mappings: - - A comma seperated list of bridge to cidr mappings. + - A comma separated list of bridge to cidr mappings. - Example: cidr_mappings=br-ex1:192.168.1.1/24,br-ex2:192.168.2.1/24 - Default: "" - ovs_coremask: @@ -336,8 +336,8 @@ options: - A hex encoded string container a bitmask of what cpu cores to pin the dataplane pool mode driver treads of the ovs-vswitchd to. - Each bit set in the bitmask will result in the creating of a pmd. - - For best performance it is recomended to allocate at least 1 pmd per - numa node. On systems with HyperThreading enabled it is recomended to also + - For best performance it is recommended to allocate at least 1 pmd per + numa node. On systems with HyperThreading enabled it is recommended to also allocate the HT sibling core in the pmd_coremask.cores allocated to ovs with dpdk via the pmd_coremask should be removed from the nova vcpu_pin_set and isolated from the kernel scheduler. @@ -350,7 +350,7 @@ options: - Example: ovs_mem_channels=2 - Default: "4" - ovs_socket_mem: - - A comma seperated list of hugepage memory, specifed in MBs per numa node, + - A comma separated list of hugepage memory, specifed in MBs per numa node, allocated to the ovs-vswitchd to use for the dpdk dataplane. - For best performance memory should be allocated evenly across all numa node that will run a pmd. @@ -365,7 +365,7 @@ options: - Example: dpdk_interface_driver=vfio_pci - Default: "uio_pci_generic" - pci_whitelist: - - A repeated space seperated list of pci whitelist flags + - A repeated space separated list of pci whitelist flags for allowed ovs-dpdk ports. - The pci_whitelist allows multiple dpdk primary process to utilise different pci devices without resulting in a conflict diff --git a/tools/setup_gate.sh b/tools/setup_gate.sh index e2073560c2..d0e6921e4f 100755 --- a/tools/setup_gate.sh +++ b/tools/setup_gate.sh @@ -68,7 +68,7 @@ gate = cron,fluentd,glance,haproxy,keepalived,keystone,kolla-toolbox,mariadb,mem EOF if [[ "${DISTRO}" == "Debian" ]]; then - # Infra does not sign thier mirrors so we ignore gpg signing in the gate + # Infra does not sign their mirrors so we ignore gpg signing in the gate echo "RUN echo 'APT::Get::AllowUnauthenticated \"true\";' > /etc/apt/apt.conf" | sudo tee -a /etc/kolla/header # Optimize the repos to take advantage of the Infra provided mirrors for Ubuntu