openstack/openstack-ansible-os_octavia
Code Issues Proposed changes

Fix spelling mistakes

Browse Source 
Just some various spelling mistakes I noticed while reading

Change-Id: Icc95027153b7fa86f856906630f1cfbde9149b25
This commit is contained in:
Jonathan Herlin 2021-08-27 16:15:42 +02:00
parent 799f003b85
commit 67c18d7034
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
defaults/main.yml
View File

@ -277,7 +277,7 @@ octavia_sync_provisioning_status: False
# For convenience, we make use of the neutron message vhost
# for the LBAAS event stream. We could make a completely
# seperate vhost, but the old LBAAS functionality is
# separate vhost, but the old LBAAS functionality is
# deprecated so it's a bit pointless unless there is demand
# for doing it. As such, we provide these defaults here for
# the template to use.
@ -334,14 +334,14 @@ octavia_management_net_subnet_allocation_pools: ""
octavia_management_net_dhcp: "True"
# Should Octavia set up the network and subnet?
octavia_service_net_setup: True
# This sets it to the container managment network based on how you setup
# This sets it to the container management network based on how you setup
# the provider net
octavia_provider_network: "{{ provider_networks|map(attribute='network')|selectattr('net_name','defined')|selectattr('net_name', 'equalto', octavia_provider_network_name)|list|first }}"
# The name of the network address pool
octavia_container_network_name: "{{ octavia_provider_network['ip_from_q'] }}_address"
octavia_hm_group: "octavia-health-manager"
# Note: We use some heuritsics here but if you do anyhting special make sure to use the
# ip addresses on the right network. This will use the container newtorking to figure out the ip
# Note: We use some heuristics here but if you do anything special make sure to use the
# ip addresses on the right network. This will use the container networking to figure out the ip
octavia_hm_hosts: "{% for host in groups[octavia_hm_group] %}{{ hostvars[host]['container_networks'][octavia_container_network_name]['address'] }}{% if not loop.last %},{% endif %}{% endfor %}"
# Set this to the right container port aka the eth you connect to the octavia
# management network

4
doc/source/configure-octavia.rst
View File

@ -215,7 +215,7 @@ For this process, use one of the physical hosts within the environment.
Alternatively you can specify the new image in the appropriate settings and rerun the
ansible with an appropriate tag.
You can find more information abpout the diskimage script and the process at
You can find more information about the diskimage script and the process at
https://opendev.org/openstack/octavia/tree/master/diskimage-create
Here is a script to perform all those tasks at once:
@ -259,7 +259,7 @@ Creating the cryptographic certificates
.. note::
For production installation make sure that you review this very
carefully with your own security requirements and potantially use
carefully with your own security requirements and potentially use
your own CA to sign the certificates.
The system will automatically generate and use self-signed

2
tests/test-octavia.yml
View File

@ -117,7 +117,7 @@
tags:
- skip_ansible_lint
- name: Register VIP IP # this is likley changing with a newer version of octaviaclient
- name: Register VIP IP # this is likely changing with a newer version of octaviaclient
shell: >
openstack loadbalancer show test-lb -c vip_address -f value
environment: "{{ env }}"