Chapter 8. ML2 networking-ansible

• Define a VLAN on the switch when creating a network in OpenStack
• Assign a VLAN to an access port on the switch when creating or updating a port in OpenStack
• Remove a VLAN from an access port on the switch when deleting a port in OpenStack

• A network switch with Ansible Network Automation support. Red Hat currently only supports the use of Juniper Networks (junos ) switches.

• The network switch also requires an SSH user so that Ansible Network Automation can interact with the device. This user requires certain permissions on the switch:

  • Access mode
  • Assign a VLAN to a port
  • Create VLANs

  For security purposes, do not provide the SSH user with administrator access to the switch.

• Prepare the VLANs you intend the switch to use. Preparation involves creating each VLAN on the switch then deleting each VLAN.
• The network switch ports reserved for bare metal guests initially require configuration to connect to the dedicated network for introspection. Beyond this, these ports require no additional configuration.

• The overcloud requires a provisioning network. Use one of the following options:

  • A bridged network for Ironic services.
  • A custom composable network for Ironic services.

  For more examples of configuring the provisioning network, see Chapter 3, Deploying an Overcloud with the Bare Metal Service.

• The overcloud requires a tenant network for the bare metal systems to use after the provisioning process. The examples in this guide use the default baremetal network mapped to a bridge named br-baremetal. This network also requires a range of VLAN IDs. The following Heat parameters set these values to suit examples in this guide:

  parameter_defaults:
    NeutronNetworkVLANRanges: baremetal:1200:1299
    NeutronFlatNetworks: datacentre,baremetal
    NeutronBridgeMappings: datacentre:br-ex,baremetal:br-baremetal

• The overcloud uses the introspection service to automatically identify certain hardware details and map them for other services to use. It is recommended that you enable the ironic introspection service to help map your interface-to-port details for networking-ansible to use. You can also accomplish this task manually.

• Automatic: Introspection of nodes. The automatic method requires setting the mac value for the respective switch as a part of the ML2HostConfigs parameter.
• Manual: Set the OpenStack Networking (neutron) port configuration. Use this method if your overcloud does not include bare metal introspection functionality.

Procedure

• Automatic:

  1. Run the introspection command:

     $ openstack baremetal introspection start [--wait] <NODENAME>

     The bare metal nodes obtain the switch’s MAC address during introspection. The networking-ansible ML2 driver uses this MAC address to map to the same MAC address defined with the mac parameter for the respective switch in the ML2HostConfigs parameter.

  2. Wait until the introspection completes.

• Manual:

  1. Create a port for the bare metal node. Use the following example command as a basis to create the port:

     $ openstack baremetal port create [NODE NIC MAC] --node [NODE UUID] \
         --local-link-connection port_id=[SWICH PORT ID] \
         --local-link-connection switch_info=[SWITCH NAME] \
         --local-link-connection switch_id=[SWITCH MAC]

     Replace the following values in brackets with your own environment details:

     [NODE NIC MAC]

     The MAC address of the NIC connected to the switch.

     --node [NODE UUID]

     The UUID of the node that uses the new port.

     --local-link-connection port_id=[SWITCH PORT ID]

     The port ID on the switch connecting to the bare metal node.

     --local-link-connection switch_info=[SWITCH NAME]

     The name of the switch connecting to the bare metal node. The switch name must match the respective switch name you defined in the ML2HostConfigs parameter.

     --local-link-connection switch_id=[SWITCH MAC]

     The MAC address of the switch. This must match the respective mac value from the switch configuration from the ML2HostConfigs parameter. This is an alternative option to using switch_info.

Prerequisites

• An overcloud with OpenStack Baremetal (ironic) services.
• An enabled networking-ansible ML2 driver.
• The ML2HostConfigs parameter contains switch access details.

• A registered bare metal node.

  1. Configuration of the respective bare metal port used for the node connection on the switch.
• A VLAN-based provisioning network defined in OpenStack Networking (neutron) for initial provisioning.
• A VLAN-based tenant network defined in OpenStack Networking (neutron) for internal communication.