Fixed typos across the TripleO documentation
This patch fixes some typos in the current documentation. Change-Id: I35155244d581ddfc316064e35e851f55b6d853f1
This commit is contained in:
parent
a4a0b1588a
commit
3050f3c5c7
@ -248,7 +248,7 @@ environment which enables the configuration.
|
|||||||
|
|
||||||
The "actions" property of the `OS::Heat::SoftwareDeployments` resource may be
|
The "actions" property of the `OS::Heat::SoftwareDeployments` resource may be
|
||||||
used to specify when the configuration should be applied, e.g only on CREATE,
|
used to specify when the configuration should be applied, e.g only on CREATE,
|
||||||
only on DELETE etc. If this is ommitted, the heat default is to apply the
|
only on DELETE etc. If this is omitted, the heat default is to apply the
|
||||||
config on CREATE and UPDATE, e.g on initial deployment and every subsequent
|
config on CREATE and UPDATE, e.g on initial deployment and every subsequent
|
||||||
update.
|
update.
|
||||||
|
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
Modifying default node configuration
|
Modifying default node configuration
|
||||||
====================================
|
====================================
|
||||||
|
|
||||||
Many service configurarion options are already exposed via parameters in the
|
Many service configuration options are already exposed via parameters in the
|
||||||
top-level `overcloud.yaml` template, and these options should
|
top-level `overcloud.yaml` template, and these options should
|
||||||
be used wherever available to influence overcloud configuration.
|
be used wherever available to influence overcloud configuration.
|
||||||
|
|
||||||
|
@ -80,8 +80,8 @@ are made in order to check the stack creation:
|
|||||||
|
|
||||||
- Create a subnet in the nova network.
|
- Create a subnet in the nova network.
|
||||||
|
|
||||||
- Create a test stack called tenant-stack, using heat, which spawns a guest in
|
- Create a test stack called tenant-stack, using heat, which spawns a guest
|
||||||
the overcloud and attach it to the nova network.
|
in the overcloud and attach it to the nova network.
|
||||||
|
|
||||||
- Ping the floating IP address assigned to the new guest.
|
- Ping the floating IP address assigned to the new guest.
|
||||||
|
|
||||||
|
@ -31,7 +31,7 @@ Learn `how to contribute into TripleO Docs
|
|||||||
Reporting Bugs
|
Reporting Bugs
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
**OpenStack Upstream**: If you find bugs or volnurabilities which affect
|
**OpenStack Upstream**: If you find bugs or vulnerabilities which affect
|
||||||
upstream projects, please follow OpenStack's process of filing bugs.
|
upstream projects, please follow OpenStack's process of filing bugs.
|
||||||
|
|
||||||
* Learn `how to create Bugs in OpenStack
|
* Learn `how to create Bugs in OpenStack
|
||||||
|
@ -13,7 +13,7 @@ the following command can be used::
|
|||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
When scaling down random servers of specified role will be deleted, how to
|
When scaling down random servers of specified role will be deleted, how to
|
||||||
delete specific nodes is decribed in :ref:`delete_nodes`.
|
delete specific nodes is described in :ref:`delete_nodes`.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
The different scale parameters can be seen in the output of::
|
The different scale parameters can be seen in the output of::
|
||||||
|
@ -19,7 +19,7 @@ has failed::
|
|||||||
| 7e88af95-535c-4a55-b78d-2c3d9850d854 | overcloud | CREATE_FAILED | 2015-04-06T17:57:16Z |
|
| 7e88af95-535c-4a55-b78d-2c3d9850d854 | overcloud | CREATE_FAILED | 2015-04-06T17:57:16Z |
|
||||||
+--------------------------------------+------------+--------------------+----------------------+
|
+--------------------------------------+------------+--------------------+----------------------+
|
||||||
|
|
||||||
Occassionally, Heat is not even able to create the the stack, so the ``heat
|
Occasionally, Heat is not even able to create the the stack, so the ``heat
|
||||||
stack-list`` output will be empty. If this is the case, observe the message
|
stack-list`` output will be empty. If this is the case, observe the message
|
||||||
that was printed to the terminal when ``instack-deploy-overcloud`` or ``heat
|
that was printed to the terminal when ``instack-deploy-overcloud`` or ``heat
|
||||||
stack-create`` was run.
|
stack-create`` was run.
|
||||||
@ -52,7 +52,7 @@ in the resulting table.
|
|||||||
For example, **Maintenance** goes to ``True`` automatically, if wrong power
|
For example, **Maintenance** goes to ``True`` automatically, if wrong power
|
||||||
credentials are provided.
|
credentials are provided.
|
||||||
|
|
||||||
* If **Provision State** is ``available`` then the problem occured before
|
* If **Provision State** is ``available`` then the problem occurred before
|
||||||
bare metal deployment has even started. Proceed with `Debugging Using Heat`_.
|
bare metal deployment has even started. Proceed with `Debugging Using Heat`_.
|
||||||
|
|
||||||
* If **Provision State** is ``active`` and **Power State** is ``power on``,
|
* If **Provision State** is ``active`` and **Power State** is ``power on``,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user