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:

2. The ML2HostConfigs parameter requires a dict value with details about your switches. Each initial key in the dict is a name for the switch. This value defines a specific ansible:[switchname] section in your OpenStack Networking (neutron) ML2 configuration. Each switch name key requires its own dict that contains the actual switch details. For example, to configure three switches, add three switch keys:

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

3. Each switch requires certain key value pairs in the dict:

   ansible_network_os

   (Required) The operating system of the switch. Options include junos and eos.

   Important

   Arista Extensible Operating System (eos) support is available in this release as a Technology Preview, and therefore is not fully supported by Red Hat. It should only be used for testing, and should not be deployed in a production environment. For more information about Technology Preview features, see Scope of Coverage Details.

   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. This is a required value when using introspection to perform automatic port 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: juno
         ansible_host: 10.0.0.1
         ansible_user: ansible
         ansible_ssh_pass: "p@55w0rd!"
         mac: "01:23:45:67:89:AB"
         manage_vlans: false

5. Save the /home/stack/templates/ml2-ansible-hosts.yaml file.

6. When you run 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. The following example demonstrates how to include these files:

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

Procedure

1. Create the bare metal system:

   • To create a bare metal system that uses an access port, run the following command:

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

   • To create a bare metal system that uses a trunk port, run the following command:

     openstack server create --flavor baremetal --image overcloud-full --port {primary-port-uuid} --key default test1