openstack/kayobe
Code Issues Proposed changes

Document variables to configure connectivity check

Browse Source 
If ICMP is filtered, it can be useful to change the IP and hostname used
by the network connectivity check feature.

Change-Id: I7432287dcb43992688600415fbb360709a532565
This commit is contained in:
Pierre Riteau 2021-07-29 12:57:29 +02:00
parent 0b1a052b0e
commit 3d4792ee32
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/administration/general.rst
View File

@ -71,3 +71,8 @@ Note that this will run on the seed, seed hypervisor, and overcloud hosts. If
any of these hosts are not expected to be active (e.g. prior to overcloud any of these hosts are not expected to be active (e.g. prior to overcloud
deployment), the set of target hosts may be limited using the ``--limit`` deployment), the set of target hosts may be limited using the ``--limit``
argument. argument.
These checks will attempt to ping the external IP address ``8.8.8.8`` and
external hostname ``google.com``. They can be configured with the
``nc_external_ip`` and ``nc_external_hostname`` variables in
``$KAYOBE_CONFIG_PATH/networks.yml``.

9
etc/kayobe/networks.yml
View File

@ -196,6 +196,15 @@
# 'name' items. These tables will be added to /etc/iproute2/rt_tables. # 'name' items. These tables will be added to /etc/iproute2/rt_tables.
#network_route_tables: #network_route_tables:
###############################################################################
# Network connectivity check configuration.
# External IP address to check. Default is 8.8.8.8.
#nc_external_ip:
# External hostname to check. Default is google.com.
#nc_external_hostname:
############################################################################### ###############################################################################
# Dummy variable to allow Ansible to accept this file. # Dummy variable to allow Ansible to accept this file.
workaround_ansible_issue_8743: yes workaround_ansible_issue_8743: yes