Minor typo fixes and grammar adjustments
Change-Id: I2d7376045ff0c764c60b2dc2bf90ad1ff37c07b4 Closes-Bug: 1602315
This commit is contained in:
parent
8ab8803f5a
commit
85239b1307
|
@ -90,8 +90,8 @@ section in the :doc:`User References <../user/index>` documentation.
|
|||
Scaling a Cluster
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
Now you can try change the size of your cluster. To increase the size of the
|
||||
cluster, use the following command:
|
||||
Now you can try to change the size of your cluster. To increase the size,
|
||||
use the following command:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
@ -129,7 +129,7 @@ a cluster is resized. For more details, please check the
|
|||
Creating a Node
|
||||
---------------
|
||||
|
||||
Another way to manage cluster node membership is to create a standalone code
|
||||
Another way to manage cluster node membership is to create a standalone node
|
||||
then add it to a cluster. To create a node using a given profile:
|
||||
|
||||
.. code-block:: console
|
||||
|
@ -171,7 +171,7 @@ command:
|
|||
$ senlin cluster-show mycluster
|
||||
$ senlin node-show oldnode
|
||||
|
||||
For other commands and options cluster membership management, please check the
|
||||
For other cluster membership management commands and options, please check the
|
||||
:doc:`Cluster Membership <../user/membership>` section in the
|
||||
:doc:`User References <../user/index>` documentation.
|
||||
|
||||
|
|
|
@ -49,13 +49,13 @@ To verify the policy creation, you can do:
|
|||
Attaching a Policy
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The enforce a policy on a cluster, you will attach a policy to a cluster:
|
||||
The enforce a policy on a cluster, attach a policy to it:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ senlin cluster-policy-attach -p dp01 mycluster
|
||||
|
||||
To verify the policy attach operation, you can do:
|
||||
To verify the policy attach operation, do the following:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
@ -66,7 +66,7 @@ Verifying a Policy
|
|||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To verify the deletion policy attached to the cluster ``mycluster``, you
|
||||
can try expanding the cluster followed by shrinking it:
|
||||
can try expanding the cluster, followed by shrinking it:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@
|
|||
Working with Receivers
|
||||
======================
|
||||
|
||||
Receivers are the event sinks associated to senlin clusters so that when
|
||||
Receivers are the event sinks associated to senlin clusters. When
|
||||
certain events (or alarms) are seen by a monitoring software, the software can
|
||||
notify the senlin clusters of those events (or alarms). When senlin receives
|
||||
those notifications, it can automatically trigger some predefined operations
|
||||
|
@ -35,7 +35,7 @@ cluster:
|
|||
|
||||
$ senlin receiver-create -c mycluster -a CLUSTER_SCALE_IN w_scale_in
|
||||
|
||||
The output from the command will be something like shown below:
|
||||
The output from the command will be something like this:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
|
|
@ -14,6 +14,6 @@ properties:
|
|||
# This param buys an instance some time before deletion
|
||||
grace_period: 60
|
||||
|
||||
# Whether the deletion will reduce the desired capability of
|
||||
# the cluster as well.
|
||||
# Whether the deletion will reduce the desired capacity of
|
||||
# the cluster as well
|
||||
reduce_desired_capacity: False
|
||||
|
|
Loading…
Reference in New Issue