summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaoyangLiu <liumaoyang@inspur.com>2018-12-16 15:39:14 +0800
committerMaoyangLiu <liumaoyang@inspur.com>2018-12-16 15:40:06 +0800
commit6088e871c19e8fbb7b08d8a1c607155a4f930e92 (patch)
treea56056af3dd4306b3cd59290d295cd8562ea29f5
parent074454b636b600482c5d830c64a0f313cf3b3719 (diff)
fix typo mistakes
Notes
Notes (review): Code-Review+2: Chris MacNaughton (icey) <chris.macnaughton@canonical.com> Workflow+1: Chris MacNaughton (icey) <chris.macnaughton@canonical.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Wed, 19 Dec 2018 08:37:10 +0000 Reviewed-on: https://review.openstack.org/625416 Project: openstack/charm-specs Branch: refs/heads/master
-rw-r--r--specs/stein/backlog/swift-extended-cluster-operations.rst4
-rw-r--r--specs/stein/implemented/octavia.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/specs/stein/backlog/swift-extended-cluster-operations.rst b/specs/stein/backlog/swift-extended-cluster-operations.rst
index cf3295a..4d79a38 100644
--- a/specs/stein/backlog/swift-extended-cluster-operations.rst
+++ b/specs/stein/backlog/swift-extended-cluster-operations.rst
@@ -42,7 +42,7 @@ effectively maintain a Swift cluster over time:
42 have already been initialised. 42 have already been initialised.
43 43
44This forces operators to manually apply changes like adjusting the 44This forces operators to manually apply changes like adjusting the
45partition-power to accomodate for additional storage added to the cluster. This 45partition-power to accommodate for additional storage added to the cluster. This
46poses great risk since manually editing the rings/builders and syncing them 46poses great risk since manually editing the rings/builders and syncing them
47across the cluster could easily conflict with the swift-proxy charm's native 47across the cluster could easily conflict with the swift-proxy charm's native
48support for doing this resulting in a broken cluster. 48support for doing this resulting in a broken cluster.
@@ -64,7 +64,7 @@ refuse to make changes until the operator has paused the swift-proxy units i.e.
64placed them into "maintenance mode" which will shutdown the api services and 64placed them into "maintenance mode" which will shutdown the api services and
65block any restarts until the units are resumed. The user will also have the 65block any restarts until the units are resumed. The user will also have the
66option to set disable-ring-balance=true if they want check that their changes 66option to set disable-ring-balance=true if they want check that their changes
67have been applied successully (to the builder files) prior to having the rings 67have been applied successfully (to the builder files) prior to having the rings
68rebuilt and sycned across the cluster. 68rebuilt and sycned across the cluster.
69 69
70For the swift-storage charms, where currently one can only add devices but not 70For the swift-storage charms, where currently one can only add devices but not
diff --git a/specs/stein/implemented/octavia.rst b/specs/stein/implemented/octavia.rst
index 47aa227..916b043 100644
--- a/specs/stein/implemented/octavia.rst
+++ b/specs/stein/implemented/octavia.rst
@@ -49,7 +49,7 @@ software itself and dynamic scaling of the service.
49 49
50On the scaling side, most if not all, of the ``octavia`` services benefit from 50On the scaling side, most if not all, of the ``octavia`` services benefit from
51being scaled out proportional to the number of running load balancers and load 51being scaled out proportional to the number of running load balancers and load
52balancer life cycle events. Thus it makse sense to co-locate the API, Worker, 52balancer life cycle events. Thus it makes sense to co-locate the API, Worker,
53Health Manager and Housekeeping Manager daemons in the same charm unit, and 53Health Manager and Housekeeping Manager daemons in the same charm unit, and
54scale by increasing the number of charm units deployed. 54scale by increasing the number of charm units deployed.
55 55