openstack/openstack-helm
Code Issues Proposed changes

Remove the duplicated words

Browse Source 
Change-Id: I36da4bda4fb4772e92118501c4d68f3623cfeb18
This commit is contained in:
zhulingjie 2018-06-10 19:03:10 -04:00
parent 4f7af527ba
commit cf98731b69
3 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

@ -5,7 +5,7 @@ Logging Requirements
-------------------- --------------------
OpenStack-Helm defines a centralized logging mechanism to provide insight into OpenStack-Helm defines a centralized logging mechanism to provide insight into
the the state of the OpenStack services and infrastructure components as the state of the OpenStack services and infrastructure components as
well as underlying Kubernetes platform. Among the requirements for a logging well as underlying Kubernetes platform. Among the requirements for a logging
platform, where log data can come from and where log data need to be delivered platform, where log data can come from and where log data need to be delivered
are very variable. To support various logging scenarios, OpenStack-Helm should are very variable. To support various logging scenarios, OpenStack-Helm should

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

@ -22,7 +22,7 @@ Problem Description
=================== ===================
OpenStack-Helm defines a centralized logging mechanism to provide insight into OpenStack-Helm defines a centralized logging mechanism to provide insight into
the the state of the OpenStack services and infrastructure components as the state of the OpenStack services and infrastructure components as
well as underlying Kubernetes platform. Among the requirements for a logging well as underlying Kubernetes platform. Among the requirements for a logging
platform, where log data can come from and where log data need to be delivered platform, where log data can come from and where log data need to be delivered
are very variable. To support various logging scenarios, OpenStack-Helm should are very variable. To support various logging scenarios, OpenStack-Helm should

4
tools/deployment/developer/common/900-use-it.sh
View File

@ -108,7 +108,7 @@ if helm ls --short | grep -q "^cinder$"; then
instance_uuid \ instance_uuid \
-f value -c output_value) -f value -c output_value)
# Get the the devices that are present on the instance # Get the devices that are present on the instance
DEVS_PRE_ATTACH=$(mktemp) DEVS_PRE_ATTACH=$(mktemp)
ssh -i ${HOME}/.ssh/osh_key cirros@${FLOATING_IP} lsblk > ${DEVS_PRE_ATTACH} ssh -i ${HOME}/.ssh/osh_key cirros@${FLOATING_IP} lsblk > ${DEVS_PRE_ATTACH}
@ -118,7 +118,7 @@ if helm ls --short | grep -q "^cinder$"; then
-t ./tools/gate/files/heat-vm-volume-attach.yaml \ -t ./tools/gate/files/heat-vm-volume-attach.yaml \
heat-vm-volume-attach heat-vm-volume-attach
# Get the the devices that are present on the instance # Get the devices that are present on the instance
DEVS_POST_ATTACH=$(mktemp) DEVS_POST_ATTACH=$(mktemp)
ssh -i ${HOME}/.ssh/osh_key cirros@${FLOATING_IP} lsblk > ${DEVS_POST_ATTACH} ssh -i ${HOME}/.ssh/osh_key cirros@${FLOATING_IP} lsblk > ${DEVS_POST_ATTACH}