1 # This configuration file defines Network Environment for a
2 # Baremetal Deployment of OPNFV. It contains default values
3 # for 4 following networks:
11 # *) optional networks
13 # Any values missing from this configuration file will be
14 # auto-detected by deployment script from the existing network
15 # configuration of the jumphost.
17 # Optional networks will be consolidated with the admin network
18 # if not explicitely configured.
20 # See short description of the networks in the comments below.
23 # DNS Servers for all nodes, comma delimited list
24 dns_servers: ["8.8.8.8", "8.8.4.4"]
26 # "admin" is the short name for Control Plane Network.
27 # During OPNFV deployment it is used for node provisioning so
28 # PXE boot should be enabled for the related interfaces on all
29 # the nodes in the OPNFV cluster. After the deployment this
30 # network is used as the OpenStack management network which
31 # carries e.g. communication between its internal components.
32 # This network must be IPv4 currently.
40 usable_ip_range: 192.0.2.11,192.0.2.99
42 provisioner_ip: 192.0.2.1
44 dhcp_range: 192.0.2.2,192.0.2.10
45 introspection_range: 192.0.2.100,192.0.2.120
47 # "private" is an optional network used as underlying physical
48 # network for virtual provider and tenant networks created by
49 # users. Traffic between virtual machines is carried by this
51 # This network must be IPv4 currently.
57 # "public" network is used for external connectivity.
58 # The external network provides Internet access for virtual
59 # machines. If floating IP range is defined for this network,
60 # floating IP addresses can be used for accessing virtual
61 # machines from outside of OPNFV cluster. Also external REST
62 # API calls use this network.
70 provisioner_ip: 2001:db8::1
72 # "storage" is an optional network used by storage backends.
73 # You can configure this network in order to reduce load on
74 # Control Plane Network.
78 cidr: fd00:fd00:fd00:2000::/64
80 # "api" is an optional network used by internal openstack api services.
83 cidr: fd00:fd00:fd00:4000::/64
86 # enabled: true #If disabled, public_network traffic will collapse to admin network
88 # bridged_interface: ''
89 # cidr: 192.168.37.0/24
90 # gateway: 192.168.37.1
91 # floating_ip_range: 192.168.37.200,192.168.37.220 #Range to allocate to floating IPs for the public network with Neutron
92 # usable_ip_range: 192.168.37.10,192.168.37.199 #Usable IP range on the public network, usually this is a shared subnet
93 # provisioner_ip: 192.168.37.1
96 # enabled: false #If disabled, underlay traffic will collapse to admin_network
97 # ipv6: true #This flag is only needed if cidr is not provided, and bridged_interface
98 # is used for address auto detection.
101 # enabled: false #If disabled, storage_network traffic will collapse to admin network
102 # ipv6: true #This flag is only needed if cidr is not provided, and bridged_interface
103 # is used for address auto detection.
106 # enabled: false #If disabled, api_network traffic will collapse to admin network
107 # ipv6: true #This flag is only needed if cidr is not provided, and bridged_interface
108 # is used for address auto detection.
110 #General behavior description (today's behavior, not necessarily optimal):
111 # - If a network has cidr field defined, no auto detection will be done. All missing fields will be generated according to CIDR.
112 # - If cidr is not specified, bridged_interface field must be specified. IP detection will be done on the system.
113 # In this case, an optional ipv6 field can be specified to indicate what kind of IP discovery takes place.
114 # - It is assumed the supplied cidr has enough address to generate all field today.
115 # - If a field is specified, no auto generation (from cidr) or auto detection (from bridged_interface) will be performed.
116 # It is assumed the value specified is correct.
117 # - Any networks can be specified to be IPv6, but only private, storage and public SHOULD. No check is performed to validate this.
120 # - All IP addresses can now be IPv4 or IPv6, we will detect the correct family and configure accordingly.
121 # Note that if any network is specified to be IPv6, we consider it a IPv6 deployment. IPv6 deployment does require additional
122 # configurations in resulting network environment yaml, such as enabling ipv6 support for NOVA, RABBITMQ, etc.