Corrected some misspellings in the tropleo doc
Change-Id: Iff76cd7ba6d776f786b2acde8eb945a4b3986652
This commit is contained in:
parent
2c573e93ef
commit
880e51f5e8
@ -22,7 +22,7 @@ where the Undercloud installation has been performed.
|
||||
manner, and will often be used to refer to the method detailed in this
|
||||
documentation.
|
||||
|
||||
At a high level, an additonal cli arg (``--config-download``) is passed to
|
||||
At a high level, an additional cli arg (``--config-download``) is passed to
|
||||
``openstack overcloud deploy``, which enables the various pieces to use
|
||||
Ansible in the manner detailed here.
|
||||
|
||||
@ -35,7 +35,7 @@ ports.
|
||||
The difference is that although Heat creates all the deployment data necessary
|
||||
via SoftwareDeployment resources to perform the Overcloud installation and
|
||||
configuration, it does not apply any of the deployments. The data is only made
|
||||
available via the Heat API, and an additonal config-download workflow is
|
||||
available via the Heat API, and an additional config-download workflow is
|
||||
triggered after the Heat stack is completed that downloads all of the
|
||||
deployment data from Heat.
|
||||
|
||||
|
@ -37,7 +37,7 @@ Default Security Values in Horizon
|
||||
|
||||
The following config directives are set to ``True`` as a secure default, however
|
||||
if a reason exists for an operator to disable one of the following values, they
|
||||
can do so using an enviroment file.
|
||||
can do so using an environment file.
|
||||
|
||||
.. note:: The following directives should only be set to ``False`` once the
|
||||
potential security impacts are fully understood.
|
||||
@ -66,7 +66,7 @@ vulnerability, so this option allows extra security hardening where iframes are
|
||||
not used in deployment.
|
||||
|
||||
If however a reason exists to allow Iframe embedding, then the following
|
||||
parameter can be set within an enviroment file::
|
||||
parameter can be set within an environment file::
|
||||
|
||||
parameter_defaults:
|
||||
ControllerExtraConfig:
|
||||
@ -86,7 +86,7 @@ SSH Banner Text
|
||||
---------------
|
||||
|
||||
SSH ``/etc/issue`` Banner text can be set using the following parameters in an
|
||||
enviroment file::
|
||||
environment file::
|
||||
|
||||
resource_registry:
|
||||
OS::TripleO::Services::Sshd: ../puppet/services/sshd.yaml
|
||||
@ -118,7 +118,7 @@ is capable of logging many events such as someone changing the system time,
|
||||
changes to Mandatory / Discretionary Access Control, creating / destroying users
|
||||
or groups.
|
||||
|
||||
Rules can be declared using an enviroment file and injected into
|
||||
Rules can be declared using an environment file and injected into
|
||||
``/etc/audit/audit.rules``::
|
||||
|
||||
parameter_defaults:
|
||||
|
@ -90,13 +90,13 @@ the default, which is ``False``.
|
||||
How do I repair broken nodes
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Usually, the nodes should only be deleted when the hardware is decomissioned.
|
||||
Usually, the nodes should only be deleted when the hardware is decommissioned.
|
||||
Before that, you're expected to remove instances from them using scale-down.
|
||||
However, in some cases, it may be impossible to repair a node with e.g. broken
|
||||
power management, and it gets stuck in an abnormal state.
|
||||
|
||||
.. warning::
|
||||
Before proceeding with this section, always try to decomission a node
|
||||
Before proceeding with this section, always try to decommission a node
|
||||
normally, by scaling down your cloud. Forcing node deletion may cause
|
||||
unpredicable results.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user