--- # The purpose of this file is to define all of the NetworkLinks (i.e. layer 1 # devices) and Networks (i.e. layer 3 configurations). # # The following is reference configuration for Intel hosted POD17 # https://wiki.opnfv.org/display/pharos/Intel+POD17 # +--------+------------+-----------------------------------+-----------+----------+----------------+ # | | | | | | | # +--------+------------+-----------------------------------+-----------+----------+----------------+ # |IF0 1G | dmz | OOB and OAM (default route) | VLAN 170 | untagged | 10.10.170.0/25 | # |IF1 1G | pxe | PXE boot network | VLAN 171 | untagged | 10.10.171.0/24 | # |IF2 10G | calico | Underlay Calico | VLAN 172 | untagged | 10.10.172.0/24 | # | | overlay | overlay network for openstack SDN | VLAN 174 | tagged | 10.10.174.0/24 | # |IF3 10G | storage | Storage network | VLAN 173 | untagged | 10.10.173.0/24 | # | | routable | OVS-F (OVS Floating IP – Public) | VLAN 1173 | tagged | 10.10.175.0/24 | # +--------+------------+-----------------------------------+-----------+----------+----------------+ # # For standard Airship/OPNFV deployments, you should not need to modify the # number of NetworkLinks and Networks in this file. Only the IP addresses and # CIDRs should need editing. # # The general Drydock documentation contains additional details, exmaples # and how-tos on working with Drydock/YAMLs in more generic way and enabling # custom/additional features not represented here (such as bonded networks). # See https://airship-drydock.readthedocs.io/en/latest/topology.html#defining-networking schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: oob layeringDefinition: abstract: false layer: site parentSelector: network_role: oob topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Update with the site's out-of-band CIDR cidr: 10.10.170.0/24 routes: # NEWSITE-CHANGEME: Update with the site's out-of-band gateway IP - subnet: '0.0.0.0/0' gateway: 10.10.170.1 metric: 100 ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: pxe layeringDefinition: abstract: false layer: site parentSelector: network_role: pxe topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Update with the site's PXE network CIDR # NOTE: The CIDR minimum size = (number of nodes * 2) + 10 cidr: 10.10.171.0/24 # NOTE: The DHCP addresses are used when nodes perform a PXE boot # (DHCP address gets assigned), and when a node is commissioning in MaaS # (also uses DHCP to get its IP address). However, when MaaS installs the # operating system ("Deploying/Deployed" states), it will write a static IP # assignment to /etc/network/interfaces[.d] with IPs from the "static" # subnet defined here. ranges: # NEWSITE-CHANGEME: Exclude any reserved IPs for the lab. - type: reserved start: 10.10.171.1 end: 10.10.171.19 # NEWSITE-CHANGEME: Update to the first half of the remaining range after # excluding the reserved IPs. - type: static start: 10.10.171.20 end: 10.10.171.39 # NEWSITE-CHANGEME: Update to the second half of the remaining range after # excluding the reserved IPs. - type: dhcp start: 10.10.171.40 end: 10.10.171.128 # dns: # NEWSITE-CHANGEME: Use MAAS VIP as the DNS server. # MAAS has inbuilt DNS server and Debian mirror that allows nodes to be # deployed without requiring routed/internet access for the Admin/PXE interface. # See data.vip.maas_vip in networks/common-addresses.yaml. # TODO: This should be populated via substitution from common-addresses # servers: '10.10.171.20' ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: oam layeringDefinition: abstract: false layer: site parentSelector: network_role: oam topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Update with the site's DMZ network CIDR cidr: 10.10.170.0/24 routes: - subnet: 0.0.0.0/0 # NEWSITE-CHANGEME: Set the DMZ network gateway IP address # NOTE: This serves as the site's default route. gateway: 10.10.170.1 metric: 100 ranges: # NEWSITE-CHANGEME: Exclude any reserved IPs for the lab. - type: reserved start: 10.10.170.1 end: 10.10.170.19 # NEWSITE-CHANGEME: Update static range that will be used for the nodes. # See minimum range required for the nodes in baremetal/nodes.yaml. - type: static start: 10.10.170.20 end: 10.10.170.39 ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: calico layeringDefinition: abstract: false layer: site parentSelector: network_role: calico topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Set the CIDR for the Private network # NOTE: The CIDR minimum size = number of nodes + 10 cidr: 10.10.172.0/24 ranges: # NEWSITE-CHANGEME: Update to the remaining range excluding (if any) # reserved IPs. - type: static start: 10.10.172.1 end: 10.10.172.19 ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: overlay layeringDefinition: abstract: false layer: site parentSelector: network_role: os-overlay topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Set the VLAN ID which the Management network is on vlan: '174' # NEWSITE-CHANGEME: Set the CIDR for the Management network # NOTE: The CIDR minimum size = number of nodes + 10 cidr: 10.10.174.0/24 ranges: # NEWSITE-CHANGEME: Update to the first 10 IPs in the CIDR - type: reserved start: 10.10.174.1 end: 10.10.174.10 # NEWSITE-CHANGEME: Update to the remaining range excluding (if any) # reserved IPs. - type: static start: 10.10.174.11 end: 10.10.174.100 routes: - subnet: 0.0.0.0/0 # NEWSITE-CHANGEME: Update to the gateway address for this network gateway: 10.10.174.1 labels: # NEWSITE-CHANGEME: All cruisers should have this enabled, set to false if this # is a special case. If set to false, IP Addresses and CIDR will still need # to be specified above to satisfy the schema and substitution used by other documents. enabled: true ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: storage layeringDefinition: abstract: false layer: site parentSelector: network_role: storage topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Set the CIDR for the Storage network # NOTE: The CIDR minimum size = number of nodes + 10 cidr: 10.10.173.0/24 ranges: # NEWSITE-CHANGEME: Update to the remaining range excludin (if any) # reserved IPs. - type: static start: 10.10.173.1 end: 10.10.173.19 ... --- schema: 'drydock/Network/v1' metadata: schema: 'metadata/Document/v1' name: routable layeringDefinition: abstract: false layer: site parentSelector: network_role: os-routable topology: cruiserlite actions: - method: merge path: . storagePolicy: cleartext data: # NEWSITE-CHANGEME: Set the VLAN ID which the Public network is on vlan: '1173' # NEWSITE-CHANGEME: Set the CIDR for the OVS-F (OVS Floating IP – Public) network cidr: 10.10.175.0/24 ranges: - type: reserved # NEWSITE-CHANGEME: Update to the start and end addresses to be used for the Floating IP pool start: 10.10.175.31 end: 10.10.175.128 routes: - subnet: 0.0.0.0/0 # NEWSITE-CHANGEME: Update to the gateway address for this network gateway: 10.10.175.1 metric: 100 labels: # NEWSITE-CHANGEME: All cruisers should have this enabled, set to false if this # is a special case in corridor 1 that doesn't support a floating IP pool. # If set to false, IP Addresses and CIDR will still need to be specified # above to satisfy the schema and substitution used by other documents. enabled: true ...