openstack/openstack-helm
Code Issues Proposed changes

Merge "Fix typos in docs"

Browse Source
This commit is contained in:
Zuul 2018-02-13 14:32:03 +00:00 committed by Gerrit Code Review
commit 47d7486172
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/fluent-logging.rst
View File

@ -25,7 +25,7 @@ each node and mounts the `/var/lib/docker/containers` directory. The Docker
container runtime engine directs events posted to stdout and stderr to this
directory on the host. Fluent-bit then forward the contents of that directory to
Fluentd. Fluentd runs as deployment at the designated nodes and expose service
for Fluent-bit to foward logs. Fluentd should then apply the Logstash format to
for Fluent-bit to forward logs. Fluentd should then apply the Logstash format to
the logs. Fluentd can also write kubernetes and OpenStack metadata to the logs.
Fluentd will then forward the results to Elasticsearch and to optionally kafka.
Elasticsearch indexes the logs in a logstash-* index by default. Kafka stores

2
doc/source/devref/oslo-config.rst
View File

@ -31,7 +31,7 @@ snippet for an imaginary Keystone configuration is described here:
- log
security_compliance:
password_expires_ignore_user_ids:
# Values in a list will be converted to a comma seperated key
# Values in a list will be converted to a comma separated key
- "123"
- "456"

2
doc/source/install/ext-dns-fqdn.rst
View File

@ -76,7 +76,7 @@ The default FQDN's for OpenStack-Helm are
We want to change the ***public*** configurations to match our DNS layouts above. In each Chart
``values.yaml`` is a ``endpoints`` configuration that has ``host_fqdn_override``'s for each API
that the Chart either produces or is dependant on. `Read more about how Endpoints are developed
that the Chart either produces or is dependent on. `Read more about how Endpoints are developed
<https://docs.openstack.org/openstack-helm/latest/devref/endpoints.html>`__.
Note while Glance Registry is listening on a Ingress http endpoint, you will not need to expose
the registry for external services.

2
doc/source/specs/fluentbit-fluentd-architecture.rst
View File

@ -83,7 +83,7 @@ each node and mounts the /var/lib/docker/containers directory. The Docker
container runtime engine directs events posted to stdout and stderr to this
directory on the host. Fluentbit then forward the contents of that directory to
Fluentd. Fluentd runs as deployment at the designated nodes and expose service
for Fluentbit to foward logs. Fluentd should then apply the Logstash format to
for Fluentbit to forward logs. Fluentd should then apply the Logstash format to
the logs. Fluentd can also write Kubernetes and OpenStack metadata to the logs.
Fluentd will then forward the results to Elasticsearch and to optionally Kafka.
Elasticsearch indexes the logs in a logstash-* index by default. Kafka stores