Chapter 7. ML2 networking-ansible

Procedure

1. Create the /home/stack/templates/ml2-ansible-hosts.yaml and add the following initial content:

   parameter_defaults:
     ML2HostConfigs:

   Copy to Clipboard Toggle word wrap

2. Include a dict definition in the ML2HostConfigs parameter for each switch in your environment. Each dict key is the name of the switch and defines a specific ansible:[switchname] section in your OpenStack Networking (neutron) ML2 configuration. The dict value for each switch contains the switch details. For example, to configure three switches, add three switch keys to the ML2HostConfigs parameter:

   parameter_defaults:
     ML2HostConfigs:
       switch1:
         [SWITCH DETAILS]
       switch2:
         [SWITCH DETAILS]
       switch3:
         [SWITCH DETAILS]

   Copy to Clipboard Toggle word wrap

3. Include the following key value pairs for each switch dict:

   ansible_network_os

   (Required) The operating system of the switch. Red Hat currently only supports junos.

   ansible_host

   (Required) The IP or hostname of the switch.

   ansible_user

   (Required) The user that Ansible uses to access the switch.

   ansible_ssh_pass

   (Required) The SSH password that Ansible uses to access the switch.

   mac

   Chassis MAC ID of the network device. Used to map the link layer discovery protocol (LLDP) MAC address value to the switch name defined in the ML2HostConfigs configuration.

   manage_vlans

   A Boolean variable to define whether OpenStack Networking (neutron) controls the creation and deletion of VLANs on the physical device. This functionality causes the switch to create and delete VLANs with IDs respective to their Neutron networks. If you have predefined these VLANs on the switch and do not require Neutron to create or delete VLANs on the switch, set this parameter to false. The default value is true.

4. The following example shows how to map these values to their respective keys in a full ML2HostConfigs parameter:

   parameter_defaults:
     ML2HostConfigs:
       switch1:
         ansible_network_os: junos
         ansible_host: 10.0.0.1
         ansible_user: ansible
         ansible_ssh_pass: "p@55w0rd!"
         mac: 01:23:45:67:89:AB
         manage_vlans: false

   Copy to Clipboard Toggle word wrap
5. Save the /home/stack/templates/ml2-ansible-hosts.yaml file.

6. When running the overcloud deployment command, include the /usr/share/openstack-tripleo-heat-templates/environments/neutron-ml2-ansible.yaml and /home/stack/templates/ml2-ansible-hosts.yaml files with the -e option:

   $ openstack overcloud deploy --templates \
     ...
     -e /usr/share/openstack-tripleo-heat-templates/environments/neutron-ml2-ansible.yaml \
     -e /home/stack/templates/ml2-ansible-hosts.yaml \
     ...

   Copy to Clipboard Toggle word wrap

Procedure

1. Create the provisioning network and subnet. This depends on the type of provisioning network you are using. See Chapter 4, Configuring for the Bare Metal Service After Deployment for information on configuring the provisioning network.

2. Create a tenant network and subnet:

   $ openstack network create --provider-network-type vlan --provider-physical-network baremetal tenant-net
   $ openstack subnet create --network tenant-net --subnet-range 192.168.3.0/24 --allocation-pool start=192.168.3.10,end=192.168.3.20 tenant-subnet

   Copy to Clipboard Toggle word wrap

   Ensure that you set the --provider-network-type option to vlan to ensure networking-ansible functionality.

Procedure

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]

   Copy to Clipboard Toggle word wrap

   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.

Procedure

1. Create the bare metal system:

   openstack server create --flavor baremetal --image overcloud-full --key default --network tenant-net test1

   Copy to Clipboard Toggle word wrap

   The overcloud initially creates the bare metal system on the provisioning network. When the creation completes, the networking-ansible driver changes the port configuration on the switch so that the bare metal system uses the tenant network.