summaryrefslogtreecommitdiff
path: root/specs
diff options
context:
space:
mode:
authorjeckxie <xiexiaozhe@inspur.com>2016-12-08 14:54:06 +0800
committerjeckxie <xiexiaozhe@inspur.com>2016-12-08 14:54:06 +0800
commit6bde2f6839d370f3c0cdf07d6a65cc013a8303e7 (patch)
tree20979d225046bb330b4e6b393621e1cc09dae81f /specs
parent37168c55a1ca3192ab26ad97b03f0e781e02c86b (diff)
downloadkolla-6bde2f6839d370f3c0cdf07d6a65cc013a8303e7.tar.gz
kolla-6bde2f6839d370f3c0cdf07d6a65cc013a8303e7.zip
Fix dir specs typo error
Change-Id: I9426b176a0d7af452c569590b771e4661b4652a2
Diffstat (limited to 'specs')
-rw-r--r--specs/kubernetes-deployment.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/specs/kubernetes-deployment.rst b/specs/kubernetes-deployment.rst
index 37cfc759f..d5204f223 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:
@@ -246,7 +246,7 @@ kibana as the default logging mechanism.
The community will implement centralized logging by using a 'side car' container
in the Kubernetes pod [17]. The logging service will trace the logs from the
shared volume of the running serivce and send the data to elastic search. This
-solution is ideal because volumes are shared amoung the containers in a pod.
+solution is ideal because volumes are shared among the containers in a pod.
Implementation
==============