---
# Kayobe network configuration.

###############################################################################
# Network role to network mappings.

# Name of the network used for admin access to the overcloud
#admin_oc_net_name:

# Name of the network used by the seed to manage the bare metal overcloud
# hosts via their out-of-band management controllers.
#oob_oc_net_name:

# Name of the network used by the seed to provision the bare metal overcloud
# hosts.
#provision_oc_net_name:

# Name of the network used by the overcloud hosts to manage the bare metal
# compute hosts via their out-of-band management controllers.
#oob_wl_net_name:

# Name of the network used by the overcloud hosts to provision the bare metal
# workload hosts.
#provision_wl_net_name:

# Name of the network used to expose the internal OpenStack API endpoints.
#internal_net_name:

# List of names of networks used to provide external network access via
# Neutron.
# Deprecated name: external_net_name
# If external_net_name is defined, external_net_names will default to a list
# containing one item, external_net_name.
#external_net_names:

# Name of the network used to expose the public OpenStack API endpoints.
#public_net_name:

# Name of the network used by Neutron to carry tenant overlay network traffic.
#tunnel_net_name:

# Name of the network used to carry storage data traffic.
#storage_net_name:

# Name of the network used to carry storage management traffic.
#storage_mgmt_net_name:

# Name of the network used to carry swift storage data traffic.
#swift_storage_net_name:

# Name of the network used to carry swift storage replication traffic.
#swift_storage_replication_net_name:

# Name of the network used to perform hardware introspection on the bare metal
# workload hosts.
#inspection_net_name:

# Name of the network used to perform cleaning on the bare metal workload
# hosts
#cleaning_net_name:

###############################################################################
# Network definitions.

# NOTE: The content of this section is very deployment-specific, since it
# depends on the names and types of networks in the deployment. It should
# define the global attributes of networks. The following example shows a basic
# configuration for a network called "example":
#
# example_cidr: 10.0.0.0/24
# example_allocation_pool_start: 10.0.0.2
# example_allocation_pool_end: 10.0.0.254
# example_gateway: 10.0.0.1
# example_vlan: 42
#
# Host or group-specific network attributes such as interface names are
# typically configured via host or group variables.
#
# Further information on the available network attributes is provided in the
# network configuration reference in the Kayobe documentation.

###############################################################################
# Network virtual patch link configuration.

# Suffix for Open vSwitch bridge names.
#network_bridge_suffix_ovs:

# Prefix for virtual patch interface names.
#network_patch_prefix:

# Suffix for virtual patch link interface names when connected towards the
# physical interface.
#network_patch_suffix_phy:

# Suffix for virtual patch link interface names when connected towards the
# OVS bridge.
#network_patch_suffix_ovs:

###############################################################################
# Network routing table configuration.

# List of IP routing tables. Each item should be a dict containing 'id' and
# 'name' items. These tables will be added to /etc/iproute2/rt_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.
workaround_ansible_issue_8743: yes
