Chapter 18. Common administrative networking tasks Sometimes you might need to perform administration tasks on the Red Hat OpenStack Platform Networking service (neutron) such as configuring the Layer 2 Population driver or specifying the name assigned to ports by the internal DNS. 18.1. Configuring the L2 population driver The L2 Population driver enables broadcast, multicast, and unicast traffic to scale out on large overlay networks. By default, Open vSwitch GRE and VXLAN replicate broadcasts to every agent, including those that do not host the destination network. This design requires the acceptance of significant network and processing overhead. The alternative design introduced by the L2 Population driver implements a partial mesh for ARP resolution and MAC learning traffic; it also creates tunnels for a particular network only between the nodes that host the network. This traffic is sent only to the necessary agent by encapsulating it as a targeted unicast. To enable the L2 Population driver, complete the following steps: 1. Enable the L2 population driver by adding it to the list of mechanism drivers. You also must enable at least one tunneling driver: either GRE, VXLAN, or both. Add the appropriate configuration options to the ml2_conf.ini file: Note Neutron's Linux Bridge ML2 driver and agent were deprecated in Red Hat OpenStack Platform 11. The Open vSwitch (OVS) plugin OpenStack Platform director default, and is recommended by Red Hat for general usage. 2. Enable L2 population in the openvswitch_agent.ini file. Enable it on each node that contains the L2 agent: Note To install ARP reply flows, configure the arp_responder flag: 18.2. Tuning keepalived to avoid VRRP packet loss If the number of highly available (HA) routers on a single host is high, when an HA router fail over occurs, the Virtual Router Redundancy Protocol (VRRP) messages might overflow the IRQ queues. This overflow stops Open vSwitch (OVS) from responding and forwarding those VRRP messages. To avoid VRRP packet overload, you must increase the VRRP advertisement interval using the ha_vrrp_advert_int parameter in the ExtraConfig section for the Controller role. Procedure Log in to the undercloud as the stack user, and source the stackrc file to enable the director command line tools. Example Create a custom YAML environment file. Example Tip The Red Hat OpenStack Platform Orchestration service (heat) uses a set of plans called templates to install and configure your environment. You can customize aspects of the overcloud with a custom environment file , which is a special type of template that provides customization for your heat templates. In the YAML environment file, increase the VRRP advertisement interval using the ha_vrrp_advert_int argument with a value specific for your site. (The default is 2 seconds.) You can also set values for gratuitous ARP messages: ha_vrrp_garp_master_repeat The number of gratuitous ARP messages to send at one time after the transition to the master state. (The default is 5 messages.) ha_vrrp_garp_master_delay The delay for second set of gratuitous ARP messages after the lower priority advert is received in the master state. (The default is 5 seconds.) Example Run the openstack overcloud deploy command and include the core heat templates, environment files, and this new custom environment file. Important The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence. Example Additional resources 2.1.2 Data Forwarding Rules, Subsection 2 in RFC 4541 Environment files in the Director Installation and Usage guide Including environment files in overcloud creation in the Director Installation and Usage guide 18.3. Specifying the name that DNS assigns to ports You can specify the name assigned to ports by the internal DNS when you enable the Red Hat OpenStack Platform (RHOSP) Networking service (neutron) dns_domain for ports extension ( dns_domain_ports ). You enable the dns_domain for ports extension by declaring the RHOSP Orchestration (heat) NeutronPluginExtensions parameter in a YAML-formatted environment file. Using a corresponding parameter, NeutronDnsDomain , you specify your domain name, which overrides the default value, openstacklocal . After redeploying your overcloud, you can use the OpenStack Client port commands, port set or port create , with --dns-name to assign a port name. Also, when the dns_domain for ports extension is enabled, the Compute service automatically populates the dns_name attribute with the hostname attribute of the instance during the boot of VM instances. At the end of the boot process, dnsmasq recognizes the allocated ports by their instance hostname. Procedure Log in to the undercloud as the stack user, and source the stackrc file to enable the director command line tools. Example Create a custom YAML environment file ( my-neutron-environment.yaml ). Note Values inside parentheses are sample values that are used in the example commands in this procedure. Substitute these sample values with ones that are appropriate for your site. Example Tip The undercloud includes a set of Orchestration service templates that form the plan for your overcloud creation. You can customize aspects of the overcloud with environment files, which are YAML-formatted files that override parameters and resources in the core Orchestration service template collection. You can include as many environment files as necessary. In the environment file, add a parameter_defaults section. Under this section, add the dns_domain for ports extension, dns_domain_ports . Example Note If you set dns_domain_ports , ensure that the deployment does not also use dns_domain , the DNS Integration extension. These extensions are incompatible, and both extensions cannot be defined simultaneously. Also in the parameter_defaults section, add your domain name ( example.com ) using the NeutronDnsDomain parameter. Example Run the openstack overcloud deploy command and include the core Orchestration templates, environment files, and this new environment file. Important The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence. Example Verification Log in to the overcloud, and create a new port ( new_port ) on a network ( public ). Assign a DNS name ( my_port ) to the port. Example Display the details for your port ( new_port ). Example Output Under dns_assignment , the fully qualified domain name ( fqdn ) value for the port contains a concatenation of the DNS name ( my_port ) and the domain name ( example.com ) that you set earlier with NeutronDnsDomain . Create a new VM instance ( my_vm ) using the port ( new_port ) that you just created. Example Display the details for your port ( new_port ). Example Output Note that the Compute service changes the dns_name attribute from its original value ( my_port ) to the name of the instance with which the port is associated ( my_vm ). Additional resources Environment files in the Director Installation and Usage guide Including environment files in overcloud creation in the Director Installation and Usage guide port in the Command Line Interface Reference server create in the Command Line Interface Reference 18.4. Assigning DHCP attributes to ports You can use Red Hat Openstack Plaform (RHOSP) Networking service (neutron) extensions to add networking functions. You can use the extra DHCP option extension ( extra_dhcp_opt ) to configure ports of DHCP clients with DHCP attributes. For example, you can add a PXE boot option such as tftp-server , server-ip-address , or bootfile-name to a DHCP client port. The value of the extra_dhcp_opt attribute is an array of DHCP option objects, where each object contains an opt_name and an opt_value . IPv4 is the default version, but you can change this to IPv6 by including a third option, ip-version=6 . When a VM instance starts, the RHOSP Networking service supplies port information to the instance using DHCP protocol. If you add DHCP information to a port already connected to a running instance, the instance only uses the new DHCP port information when the instance is restarted. Some of the more common DHCP port attributes are: bootfile-name , dns-server , domain-name , mtu , server-ip-address , and tftp-server . For the complete set of acceptable values for opt_name , refer to the DHCP specification. Prerequisites You must have RHOSP administrator privileges. Procedure Log in to the undercloud host as the stack user. Source the undercloud credentials file: Create a custom YAML environment file. Example Your environment file must contain the keywords parameter_defaults . Under these keywords, add the extra DHCP option extension, extra_dhcp_opt . Example Run the deployment command and include the core heat templates, environment files, and this new custom environment file. Important The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence. Example Verification Source your credentials file. Example Create a new port ( new_port ) on a network ( public ). Assign a valid attribute from the DHCP specification to the new port. Example Display the details for your port ( new_port ). Example Sample output Additional resources OVN supported DHCP options Dynamic Host Configuration Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters Environment files in the Director Installation and Usage guide Including environment files in overcloud creation in the Director Installation and Usage guide port create in the Command Line Interface Reference port show in the Command Line Interface Reference 18.5. Enabling NUMA affinity on ports To enable users to create instances with NUMA affinity on the port, you must load the Red Hat Openstack Plaform (RHOSP) Networking service (neutron) extension, port_numa_affinity_policy . Prerequisites Access to the undercloud host and credentials for the stack user. Procedure Log in to the undercloud host as the stack user. Source the undercloud credentials file: To enable the port_numa_affinity_policy extension, open the environment file where the NeutronPluginExtensions parameter is defined, and add port_numa_affinity_policy to the list: Add the environment file that you modified to the stack with your other environment files, and redeploy the overcloud: Important The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence. Verification Source your credentials file. Example Create a new port. When you create a port, use one of the following options to specify the NUMA affinity policy to apply to the port: --numa-policy-required - NUMA affinity policy required to schedule this port. --numa-policy-preferred - NUMA affinity policy preferred to schedule this port. --numa-policy-legacy - NUMA affinity policy using legacy mode to schedule this port. Example Display the details for your port. Example Sample output When the extension is loaded, the Value column should read, legacy , preferred or required . If the extension has failed to load, Value reads None : Additional resources Environment files in the Director Installation and Usage guide Including environment files in overcloud creation in the Director Installation and Usage guide Creating an instance with NUMA affinity on the port in the Creating and Managing Instances guide 18.6. Loading kernel modules Some features in Red Hat OpenStack Platform (RHOSP) require certain kernel modules to be loaded. For example, the OVS firewall driver requires you to load the nf_conntrack_proto_gre kernel module to support GRE tunneling between two VM instances. By using a special Orchestration service (heat) parameter, ExtraKernelModules , you can ensure that heat stores configuration information about the required kernel modules needed for features like GRE tunneling. Later, during normal module management, these required kernel modules are loaded. Procedure On the undercloud host, logged in as the stack user, create a custom YAML environment file. Example Tip Heat uses a set of plans called templates to install and configure your environment. You can customize aspects of the overcloud with a custom environment file , which is a special type of template that provides customization for your heat templates. In the YAML environment file under parameter_defaults , set ExtraKernelModules to the name of the module that you want to load. Example Run the openstack overcloud deploy command and include the core heat templates, environment files, and this new custom environment file. Important The order of the environment files is important as the parameters and resources defined in subsequent environment files take precedence. Example Verification If heat has properly loaded the module, you should see output when you run the lsmod command on the Compute node: Example Additional resources Environment files in the Director Installation and Usage guide Including environment files in overcloud creation in the Director Installation and Usage guide 18.7. Configuring shared security groups When you want one or more Red Hat OpenStack Platform (RHOSP) projects to be able to share data, you can use the RHOSP Networking service (neutron) RBAC policy feature to share a security group. You create security groups and Networking service role-based access control (RBAC) policies using the OpenStack Client. You can apply a security group directly to an instance during instance creation, or to a port on the running instance. Note You cannot apply a role-based access control (RBAC)-shared security group directly to an instance during instance creation. To apply an RBAC-shared security group to an instance you must first create the port, apply the shared security group to that port, and then assign that port to the instance. See Adding a security group to a port . Prerequisites You have at least two RHOSP projects that you want to share. In one of the projects, the current project , you have created a security group that you want to share with another project, the target project . In this example, the ping_ssh security group is created: Example Procedure Log in to the overcloud for the current project that contains the security group. Obtain the name or ID of the target project. Obtain the name or ID of the security group that you want to share between RHOSP projects. Using the identifiers from the steps, create an RBAC policy using the openstack network rbac create command. In this example, the ID of the target project is 32016615de5d43bb88de99e7f2e26a1e . The ID of the security group is 5ba835b7-22b0-4be6-bdbe-e0722d1b5f24 : Example --target-project specifies the project that requires access to the security group. Tip You can share data between all projects by using the --target-all-projects argument instead of --target-project <target-project> . By default, only the admin user has this privilege. --action access_as_shared specifies what the project is allowed to do. --type indicates that the target object is a security group. 5ba835b7-22b0-4be6-bdbe-e0722d1b5f24 is the ID of the particular security group which is being granted access to. The target project is able to access the security group when running the OpenStack Client security group commands, in addition to being able to bind to its ports. No other users (other than administrators and the owner) are able to access the security group. Tip To remove access for the target project, delete the RBAC policy that allows it using the openstack network rbac delete command. Additional resources Creating a security group in the Creating and Managing Instances guide security group create in the Command Line Interface Reference network rbac create in the Command Line Interface Reference

Commands:
[ml2] type_drivers = local,flat,vlan,gre,vxlan,geneve mechanism_drivers = l2population
[agent] l2_population = True
[agent] l2_population = True arp_responder = True
source ~/stackrc
vi /home/stack/templates/my-neutron-environment.yaml
parameter_defaults: ControllerExtraConfig: neutron::agents::l3::ha_vrrp_advert_int: 7 neutron::config::l3_agent_config: DEFAULT/ha_vrrp_garp_master_repeat: value: 5 DEFAULT/ha_vrrp_garp_master_delay: value: 5
openstack overcloud deploy --templates -e [your-environment-files] -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-neutron-environment.yaml
source ~/stackrc
vi /home/stack/templates/my-neutron-environment.yaml
parameter_defaults: NeutronPluginExtensions: "qos,port_security,dns_domain_ports"
parameter_defaults: NeutronPluginExtensions: "qos,port_security,dns_domain_ports" NeutronDnsDomain: "example.com"
openstack overcloud deploy --templates -e [your-environment-files] -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-neutron-environment.yaml
source ~/overcloudrc openstack port create --network public --dns-name my_port new_port
openstack port show -c dns_assignment -c dns_domain -c dns_name -c name new_port
+-------------------------+----------------------------------------------+ | Field | Value | +-------------------------+----------------------------------------------+ | dns_assignment | fqdn='my_port.example.com', | | | hostname='my_port', | | | ip_address='10.65.176.113' | | dns_domain | example.com | | dns_name | my_port | | name | new_port | +-------------------------+----------------------------------------------+
openstack server create --image rhel --flavor m1.small --port new_port my_vm
openstack port show -c dns_assignment -c dns_domain -c dns_name -c name new_port
+-------------------------+----------------------------------------------+ | Field | Value | +-------------------------+----------------------------------------------+ | dns_assignment | fqdn='my_vm.example.com', | | | hostname='my_vm', | | | ip_address='10.65.176.113' | | dns_domain | example.com | | dns_name | my_vm | | name | new_port | +-------------------------+----------------------------------------------+
source ~/stackrc
vi /home/stack/templates/my-octavia-environment.yaml
parameter_defaults: NeutronPluginExtensions: "qos,port_security,extra_dhcp_opt"
openstack overcloud deploy --templates -e <your_environment_files> -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml -e /home/stack/templates/my-octavia-environment.yaml
source ~/overcloudrc
openstack port create --extra-dhcp-option name=domain-name,value=test.domain --extra-dhcp-option name=ntp-server,value=192.0.2.123 --network public new_port
openstack port show new_port -c extra_dhcp_opts
+-----------------+-----------------------------------------------------------------+ | Field | Value | +-----------------+-----------------------------------------------------------------+ | extra_dhcp_opts | ip_version='4', opt_name='domain-name', opt_value='test.domain' | | | ip_version='4', opt_name='ntp-server', opt_value='192.0.2.123' | +-----------------+-----------------------------------------------------------------+
source ~/stackrc
parameter_defaults: NeutronPluginExtensions: "qos,port_numa_affinity_policy"
openstack overcloud deploy --templates -e <your_environment_files> -e /home/stack/templates/<custom_environment_file>.yaml
source ~/overcloudrc
openstack port create --network public --numa-policy-legacy myNUMAAffinityPort
openstack port show myNUMAAffinityPort -c numa_affinity_policy
+----------------------+--------+ | Field | Value | +----------------------+--------+ | numa_affinity_policy | legacy | +----------------------+--------+
vi /home/stack/templates/my-modules-environment.yaml
ComputeParameters: ExtraKernelModules: nf_conntrack_proto_gre: {} ControllerParameters: ExtraKernelModules: nf_conntrack_proto_gre: {}
openstack overcloud deploy --templates -e [your-environment-files] -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-modules-environment.yaml
sudo lsmod | grep nf_conntrack_proto_gre
openstack security group create ping_ssh
openstack project list
openstack security group list
openstack network rbac create --target-project 32016615de5d43bb88de99e7f2e26a1e --action access_as_shared --type security_group 5ba835b7-22b0-4be6-bdbe-e0722d1b5f24