---
# 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 standard
# for the logical networks in Airship:
#
# https://wiki.opnfv.org/display/pharos/Intel+POD17
# +--------+------------+-----------------------------------+----------+----------+----------------+
# |        |            |                                   |          |          |                |
# +--------+------------+-----------------------------------+----------+----------+----------------+
# |IF0 1G  | dmz        | OoB & OAM (default route)         | VLAN 170 | untagged | 10.10.170.0/24 |
# |IF1 1G  | admin      | PXE boot network                  | VLAN 171 | untagged | 10.10.171.0/24 |
# |IF2 10G | private    | Underlay calico and ovs overlay   | VLAN 172 | untagged | 10.10.172.0/24 |
# |        | management | Management (unused for now)       | VLAN 174 | tagged   | 10.10.174.0/24 |
# |IF3 10G | storage    | Storage network                   | VLAN 173 | untagged | 10.10.173.0/24 |
# |        | public     | Public network for VMs            | VLAN 175 | tagged   | 10.10.175.0/24 |
# +--------+------------+-----------------------------------+----------+----------+----------------+
#
# For standard Airship 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.
#
# TODO: Given that we expect all network broadcast domains to span all racks in
# Airship, we should choose network names that do not include the rack number.
#
# TODO: FQDN naming standards for hosts
#
schema: 'drydock/NetworkLink/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: oob
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  # MaaS doesnt own this network like it does the others, so the noconfig label
  # is specified.
  labels:
    noconfig: enabled
  bonding:
    mode: disabled
  mtu: 1500
  linkspeed: auto
  trunking:
    mode: disabled
    default_network: oob
  allowed_networks:
    - oob
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: oob
  layeringDefinition:
    abstract: false
    layer: site
  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
  # NEWSITE-CHANGEME: Update with the site's out-of-band IP allocation range
  # FIXME: Is this IP range actually used/allocated for anything? The HW already
  # has its OOB IPs assigned. None of the Ubuntu OS's should need IPs on OOB
  # network either, as they should be routable via the default gw on OAM network
  ranges:
    - type: static
      start: 10.10.170.20
      end: 10.10.170.39
...
---
schema: 'drydock/NetworkLink/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: dmz
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  bonding:
    mode: disabled
  mtu: 1500
  linkspeed: auto
  trunking:
    mode: disabled
    default_network: dmz
  allowed_networks:
    - dmz
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: dmz
  layeringDefinition:
    abstract: false
    layer: site
  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.170.0/24
  routes:
    - subnet: 0.0.0.0/0
      # NEWSITE-CHANGEME: Set the OAM network gateway IP address
      gateway: 10.10.170.1
      metric: 100
  # NOTE: The first 10 IPs in the subnet are reserved for network infrastructure.
  # The remainder of the range is divided between two subnets of equal size:
  # one static, and one DHCP.
  # 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: Update to the first 10 IPs in the CIDR
    - type: reserved
      start: 10.10.170.1
      end: 10.10.170.19
    # NEWSITE-CHANGEME: Update to the first half of the remaining range after
    # excluding the 10 reserved IPs.
    - type: static
      start: 10.10.170.20
      end: 10.10.170.39
    # NEWSITE-CHANGEME: Update to the second half of the remaining range after
    # excluding the 10 reserved IPs.
    - type: dhcp
      start: 10.10.170.40
      end: 10.10.170.79
  dns:
    # NEWSITE-CHANGEME: FQDN for bare metal nodes.
    # Choose FQDN according to the node FQDN naming conventions at the top of
    # this document.
    domain: intel-pod17.opnfv.org
    # List of upstream DNS forwards. Verify you can reach them from your
    # environment. If so, you should not need to change them.
    # TODO: This should be populated via substitution from common-addresses
    servers: '8.8.8.8,8.8.4.4'
...
---
schema: 'drydock/NetworkLink/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: admin
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  bonding:
    mode: disabled
  mtu: 1500
  linkspeed: auto
  trunking:
    mode: disabled
    default_network: admin
  allowed_networks:
    - admin
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: admin
  layeringDefinition:
    abstract: false
    layer: site
  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
  # routes:
  #   - subnet: 0.0.0.0/0
  #     # NEWSITE-CHANGEME: Set the OAM network gateway IP address
  #     gateway: 10.10.171.1
  #     metric: 100
  # NOTE: The first 10 IPs in the subnet are reserved for network infrastructure.
  # The remainder of the range is divided between two subnets of equal size:
  # one static, and one DHCP.
  # 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: Update to the first 10 IPs in the CIDR
    - 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 10 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 10 reserved IPs.
    - type: dhcp
      start: 10.10.171.40
      end: 10.10.171.79
  dns:
    # NEWSITE-CHANGEME: FQDN for bare metal nodes.
    # Choose FQDN according to the node FQDN naming conventions at the top of
    # this document.
    domain: intel-pod17.opnfv.org
    # List of upstream DNS forwards. Verify you can reach them from your
    # environment. If so, you should not need to change them.
    # TODO: This should be populated via substitution from common-addresses
    servers: '10.10.171.100'
...
---
schema: 'drydock/NetworkLink/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: data1
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  bonding:
    mode: disabled
  # NEWSITE-CHANGEME: Ensure the network switches in the environment are
  # configured for this MTU or greater. Even if switches are configured for or
  # can support a slightly higher MTU, there is no need (and negliable benefit)
  # to squeeze every last byte into the MTU (e.g., 9216 vs 9100). Leave MTU at
  # 9100 for maximum compatibility.
  mtu: 1500
  linkspeed: auto
  trunking:
    mode: 802.1q
  allowed_networks:
    - private
    - management
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: private
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  # NEWSITE-CHANGEME: Set the VLAN ID which the storage network is on
  vlan: '0'
  mtu: 1500
  # NEWSITE-CHANGEME: Set the CIDR for the storage network
  # NOTE: The CIDR minimum size = number of nodes + 10
  cidr: 10.10.172.0/24
  ranges:
    # NEWSITE-CHANGEME: Update to the remaining range after excluding the 10
    # 10 reserved IPs.
    - type: static
      start: 10.10.172.1
      end: 10.10.172.19
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: management
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  # NEWSITE-CHANGEME: Set the VLAN ID which the OAM network is on
  vlan: '174'
  mtu: 1500
  # NEWSITE-CHANGEME: Set the CIDR for the OAM network
  # NOTE: The CIDR minimum size = number of nodes + 10
  cidr: 10.10.174.0/24
  routes:
    - subnet: 0.0.0.0/0
      # NEWSITE-CHANGEME: Set the OAM network gateway IP address
      gateway: 10.10.174.1
      metric: 100
  ranges:
    # NEWSITE-CHANGEME: Update to the remaining range after excluding the 10
    # 10 reserved IPs.
    - type: static
      start: 10.10.174.1
      end: 10.23.21.19
  dns:
    # NEWSITE-CHANGEME: FQDN for bare metal nodes.
    # Choose FQDN according to the node FQDN naming conventions at the top of
    # this document.
    domain: intel-pod17.opnfv.org
    # List of upstream DNS forwards. Verify you can reach them from your
    # environment. If so, you should not need to change them.
    # TODO: This should be populated via substitution from common-addresses
    servers: '8.8.8.8,8.8.4.4'
...
---
schema: 'drydock/NetworkLink/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: data2
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  bonding:
    mode: disabled
  # NEWSITE-CHANGEME: Ensure the network switches in the environment are
  # configured for this MTU or greater. Even if switches are configured for or
  # can support a slightly higher MTU, there is no need (and negliable benefit)
  # to squeeze every last byte into the MTU (e.g., 9216 vs 9100). Leave MTU at
  # 9100 for maximum compatibility.
  mtu: 1500
  linkspeed: auto
  trunking:
    mode: 802.1q
    default_network: storage
  allowed_networks:
    - storage
    - public
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: storage
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  # NEWSITE-CHANGEME: Set the VLAN ID which the storage network is on
  vlan: '0'
  mtu: 1500
  # 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 after excluding the 10
    # 10 reserved IPs.
    - type: static
      start: 10.10.173.1
      end: 10.10.173.19
...
---
schema: 'drydock/Network/v1'
metadata:
  schema: 'metadata/Document/v1'
  name: public
  layeringDefinition:
    abstract: false
    layer: site
  storagePolicy: cleartext
data:
  vlan: '1173'
  mtu: 1500
  cidr: 10.10.175.0/24
...