diff options
Diffstat (limited to 'doc')
7 files changed, 15 insertions, 15 deletions
diff --git a/doc/source/reference/high-availability/haproxy-guide.rst b/doc/source/reference/high-availability/haproxy-guide.rst index 418ad534f..e5327e70b 100644 --- a/doc/source/reference/high-availability/haproxy-guide.rst +++ b/doc/source/reference/high-availability/haproxy-guide.rst @@ -6,7 +6,7 @@ HAProxy Guide Kolla Ansible supports a Highly Available (HA) deployment of Openstack and other services. High-availability in Kolla -is implented as via Keepalived and HAProxy. Keepalived manages virtual IP +is implemented as via Keepalived and HAProxy. Keepalived manages virtual IP addresses, while HAProxy load-balances traffic to service backends. These two components must be installed on the same hosts and they are deployed to hosts in the ``loadbalancer`` group. @@ -71,7 +71,7 @@ Backend weights When different baremetal are used in infrastructure as haproxy backends or they are overloaded for some reason, kolla-ansible is able to change -weight of backend per sevice. Weight can be any integer value from 1 to +weight of backend per service. Weight can be any integer value from 1 to 256. To set weight of backend per service, modify inventory file as below: diff --git a/doc/source/reference/logging-and-monitoring/central-logging-guide.rst b/doc/source/reference/logging-and-monitoring/central-logging-guide.rst index 4988f4ca5..edfdc845d 100644 --- a/doc/source/reference/logging-and-monitoring/central-logging-guide.rst +++ b/doc/source/reference/logging-and-monitoring/central-logging-guide.rst @@ -39,8 +39,8 @@ Applying log retention policies To stop your disks filling up, the Index State Management plugin for OpenSearch can be used to define log retention policies. A default -retention policy is applied to all indicies which match the -``opensearch_log_index_prefix``. This policy first closes old indicies, +retention policy is applied to all indices which match the +``opensearch_log_index_prefix``. This policy first closes old indices, and then eventually deletes them. It can be customised via the following variables: diff --git a/doc/source/reference/logging-and-monitoring/prometheus-guide.rst b/doc/source/reference/logging-and-monitoring/prometheus-guide.rst index a36e906f2..9a3c8333e 100644 --- a/doc/source/reference/logging-and-monitoring/prometheus-guide.rst +++ b/doc/source/reference/logging-and-monitoring/prometheus-guide.rst @@ -40,9 +40,9 @@ Basic Auth Prometheus is protected with basic HTTP authentication. Kolla-ansible will create the following users: ``admin``, ``grafana`` (if grafana is enabled) and ``skyline`` (if skyline is enabled). The grafana username can -be overidden using the variable +be overridden using the variable ``prometheus_grafana_user``, the skyline username can -be overidden using the variable ``prometheus_skyline_user``. +be overridden using the variable ``prometheus_skyline_user``. The passwords are defined by the ``prometheus_password``, ``prometheus_grafana_password`` and ``prometheus_skyline_password`` variables in @@ -56,7 +56,7 @@ The passwords are defined by the password: hello enabled: true -or completely overriden with the ``prometheus_basic_auth_users`` variable. +or completely overridden with the ``prometheus_basic_auth_users`` variable. Extending the default command line options ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -124,7 +124,7 @@ Extra files Sometimes it is necessary to reference additional files from within ``prometheus.yml``, for example, when defining file service discovery -configuration. To enable you to do this, kolla-ansible will resursively +configuration. To enable you to do this, kolla-ansible will recursively discover any files in ``{{ node_custom_config }}/prometheus/extras`` and template them. The templated output is then copied to ``/etc/prometheus/extras`` within the container on startup. For example to diff --git a/doc/source/reference/networking/designate-guide.rst b/doc/source/reference/networking/designate-guide.rst index b59b5fcfe..058af33b5 100644 --- a/doc/source/reference/networking/designate-guide.rst +++ b/doc/source/reference/networking/designate-guide.rst @@ -74,7 +74,7 @@ Infoblox Backend .. important:: When using Infoblox as the Designate backend the MDNS node - requires the container to listen on port 53. As this is a privilaged + requires the container to listen on port 53. As this is a privileged port you will need to build your designate-mdns container to run as the user root rather than designate. diff --git a/doc/source/reference/networking/neutron.rst b/doc/source/reference/networking/neutron.rst index 57b50efcb..c748c6d4e 100644 --- a/doc/source/reference/networking/neutron.rst +++ b/doc/source/reference/networking/neutron.rst @@ -225,7 +225,7 @@ Mellanox Infiniband (ml2/mlnx) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In order to add ``mlnx_infiniband`` to the list of mechanism driver -for ``neutron`` to support Infiniband virtual funtions, you need to +for ``neutron`` to support Infiniband virtual functions, you need to set the following (assuming neutron SR-IOV agent is also enabled using ``enable_neutron_sriov`` flag): diff --git a/doc/source/reference/shared-services/keystone-guide.rst b/doc/source/reference/shared-services/keystone-guide.rst index c0f157cb8..d0958a3f9 100644 --- a/doc/source/reference/shared-services/keystone-guide.rst +++ b/doc/source/reference/shared-services/keystone-guide.rst @@ -32,8 +32,8 @@ a buffer key - three in total. If the rotation interval is set lower than the sum of the token expiry and token allow expired window, more active keys will be configured in Keystone as necessary. -Further infomation on Fernet tokens is available in the :keystone-doc:`Keystone -documentation <admin/fernet-token-faq.html>`. +Further information on Fernet tokens is available in the +:keystone-doc:`Keystone documentation <admin/fernet-token-faq.html>`. Federated identity ------------------ diff --git a/doc/source/user/security.rst b/doc/source/user/security.rst index d0e185bce..b1cb4149a 100644 --- a/doc/source/user/security.rst +++ b/doc/source/user/security.rst @@ -41,7 +41,7 @@ This absolutely solves the problem of persistent data, but it introduces another security issue, permissions. With this host bind mount solution the data in ``var/lib/mysql`` will be owned by the mysql user in the container. Unfortunately, that mysql user in the container could have -any UID/GID and thats who will own the data outside the container +any UID/GID and that's who will own the data outside the container introducing a potential security risk. Additionally, this method dirties the host and requires host permissions to the directories to bind mount. @@ -98,8 +98,8 @@ The following variables should be configured in Kolla Ansible's * Bool - set to true or false -Prerequsites -============ +Prerequisites +============= Firewalld needs to be installed beforehand. Kayobe can be used to automate the installation and configuration of firewalld |