openstack/tripleo-heat-templates
Code Issues Proposed changes

Merge "Correct spelling"

Browse Source
This commit is contained in:
Zuul 2018-08-06 17:40:42 +00:00 committed by Gerrit Code Review
commit 06e1751be1
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
network_data.yaml
View File

@ -34,8 +34,8 @@
# allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}] # allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}]
# gateway_ip: '10.0.2.254' # gateway_ip: '10.0.2.254'
# #
# To support backward compatility, two versions of the network definitions will # To support backward compatibility, two versions of the network definitions
# be created, network/<network>.yaml and network/<network>_v6.yaml. Only # will be created, network/<network>.yaml and network/<network>_v6.yaml. Only
# one of these files may be used in the deployment at a time, since the # one of these files may be used in the deployment at a time, since the
# parameters used for configuration are the same in both files. In the # parameters used for configuration are the same in both files. In the
# future, this behavior may be changed to create only one file for custom # future, this behavior may be changed to create only one file for custom

4
network_data_ganesha.yaml
View File

@ -31,8 +31,8 @@
# allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}] # allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}]
# gateway_ip: '10.0.2.254' # gateway_ip: '10.0.2.254'
# #
# To support backward compatility, two versions of the network definitions will # To support backward compatibility, two versions of the network definitions
# be created, network/<network>.yaml and network/<network>_v6.yaml. Only # will be created, network/<network>.yaml and network/<network>_v6.yaml. Only
# one of these files may be used in the deployment at a time, since the # one of these files may be used in the deployment at a time, since the
# parameters used for configuration are the same in both files. In the # parameters used for configuration are the same in both files. In the
# future, this behavior may be changed to create only one file for custom # future, this behavior may be changed to create only one file for custom