Chapter 9. neutron test The neutron test applies to OpenStack products or components that implement features for the OpenStack Networking service. The test uses Tempest Framework integrated with the Red Hat OpenStack Services on OpenShift (RHOSO) to test both operational and functional features. The neutron test verifies the functionality of the neutron driver or backend that you are certifying by running selected feature tests. The following feature groups are currently tested: Section 9.1, "neutron-base-ipv4" (required) Section 9.2, "neutron-base-ipv6" (required) Section 9.3, "neutron-address-scope" (optional) Section 9.4, "neutron-agents" (optional) Section 9.5, "neutron-allowed-address-pair" (optional) Section 9.6, "neutron-auto-allocated-topology" (optional) Section 9.7, "neutron-availability-zones" (optional) Section 9.8, "neutron-extra-dhcp-options" (optional) Section 9.9, "neutron-ip-availability" (optional) Section 9.10, "neutron-l3" (required) Section 9.11, "neutron-l3-ipv6" (required) Section 9.12, "neutron-l3-flavors" (optional) Section 9.13, "neutron-mtu" (optional) Section 9.14, "neutron-multicast" (optional) Section 9.15, "neutron-network-segment-range" (optional) Section 9.16, "neutron-port-security" (optional) Section 9.17, "neutron-security-groups" (optional) Section 9.18, "neutron-tags" (optional) Section 9.19, "neutron-port-forwarding" (optional) Section 9.20, "neutron-revision" (optional) Section 9.21, "neutron-rbac" (optional) Section 9.22, "neutron-shared-network" (optional) Section 9.23, "neutron-trunk-ports" (optional) Section 9.24, "neutron-quality-of-service" (optional) Section 9.25, "neutron-server-operations" (required) Section 9.26, "neutron-quota" (optional) Section 9.27, "neutron-dns-integration" (optional) Prerequisites When you deploy OpenStack, ensure that you provide at least two EDPM compute nodes. For more information on configuring a neutron see, Configuring networking services . Configure a public subnet before running the tempest tests. Note Ensure that the external network has a sufficient number of IP addresses available in the allocation_pools . The required number of IP addresses may vary depending on the number of test workers running concurrently. Configure a public image with an advanced operating system. By default, Tempest tests use the Cirros image to generate instances, which is sufficient for most tests. However, some network-related tests require an image such as RHEL with additional tools (e.g., tcpdump, Python). Note This configuration is managed by the rhos-cert-init script , but you need to provide certain values, such as the image URL. The Tempest and neutron-tempest-plugin offer numerous configuration options for testing the neutron component. Certification test environments do not configure most of these options automatically, except those related to the advanced image and flavor. If certifying the driver requires specific additional configuration settings, use a tempest-conf-overrides file. Initialize the certification test environment with the rhos-cert-init command. Create the tempest-conf-overrides file and add the required configuration settings. Note In the tempest-conf-overrides file, enter the necessary configuration settings on a separate line without comments. Add required configuration options to the file, for example: 9.1. neutron-base-ipv4 The neutron-base-ipv4 test validates the driver and base functionalities of neutron. It verifies that API operations for resources such as ports, networks, subnets, and subnet pools are functioning correctly. Additionally, it checks if basic connectivity for instances are working fine. This test is mandatory. 9.2. neutron-base-ipv6 The neutron-base-ipv6 test verifies that the driver and base functionalities of neutron work correctly with IPv6. This test is mandatory. 9.3. neutron-address-scope The neutron-address-scope test verifies that all operations for managing address scopes can be performed with the help of a vendor driver. This test is optional. 9.4. neutron-agents The neutron-agents test verifies that all operations for managing neutron agents can be performed with the help of a vendor driver. This test is optional. 9.5. neutron-allowed-address-pair The neutron-allowed-address-pair test verifies that the allowed-address-pairs operates correctly with the help of a vendor driver. This test is optional. 9.6. neutron-auto-allocated-topology The neutron-auto-allocated-topology (get-me-a-network extension) test verifies whether a tenant user can delete or retrieve allocated topologies. This test is optional. 9.7. neutron-availability-zones The neutron-availability-zones test verifies that all standard API operations can be applied to availability zones. This test is mandatory if the driver supports availability zones in Neutron. 9.8. neutron-extra-dhcp-options The neutron-extra-dhcp-options test verifies that setting extra DHCP options works correctly with a vendor driver. This test is optional. 9.9. neutron-ip-availability The neutron-ip-availability test verifies that the APIs for checking the number of available and used IP addresses in networks works correctly with a vendor driver. This test is optional. 9.10. neutron-l3 The neutron-l3 test verifies that the driver functionalities related to L3 services, including routers and Floating IPs, works correctly with the vendor driver. This test is mandatory if the vendor's driver supports L3 services. 9.11. neutron-l3-ipv6 The neutron-l3-ipv6 test verifies that the driver functionalities related to L3 services and IPv6, including routers, works correctly with the vendor driver. This test is mandatory if the vendor's driver supports L3 services for IPv6. 9.12. neutron-l3-flavors The neutron-l3-flavors test verifies that all standard flavor operations can be performed using a third-party plugin or driver. This test is optional. 9.13. neutron-mtu The neutron-mtu test verifies whether the vendor driver allows setting and changing the MTU for networks. This test is optional. 9.14. neutron-multicast The neutron-multicast test verifies whether the vendor driver supports multicast traffic between virtual machines (VMs). This test is optional. 9.15. neutron-network-segment-range The neutron-network-segment-range test verifies whether the vendor driver allows management of available network segment ranges for tenants. This test is optional. 9.16. neutron-port-security The neutron-port-security test verifies whether the vendor driver allows enabling or disabling port security for ports and networks. This test is optional. 9.17. neutron-security-groups The neutron-security-groups test verifies that neutron's security group APIs and functionalities operate correctly with the vendor driver. This test is optional. 9.18. neutron-tags The neutron-tags test verifies that neutron's API for managing tags on various resources, such as networks and ports, operate correctly with the vendor driver. This test is optional. 9.19. neutron-port-forwarding The neutron-port-forwarding test verifies that neutron's Floating IP Port Forwarding APIs and functionalities operate correctly with the vendor driver. This test is optional. 9.20. neutron-revision The neutron-revision test verifies that the vendor driver allows setting and checking revisions for API resources such as ports and networks. This test is optional. 9.21. neutron-rbac The neutron-rbac test verifies that all Role-Based Access Control (RBAC) operations can be performed on various Neutron resources. This test is optional. 9.22. neutron-shared-network The neutron-shared-network test verifies whether the vendor driver allows to share networks with all other tenants in the cloud. This test is optional. 9.23. neutron-trunk-ports The neutron-trunk-ports test verifies whether neutron's Trunk APIs and functionalities operate correctly with the vendor driver. This test is optional. 9.24. neutron-quality-of-service The neutron-quality-of-service test verifies that neutron's QoS APIs and functionalities work correctly with the vendor driver. This test is optional. 9.25. neutron-server-operations The neutron-server-operations test verifies the connectivity to instances before and after key operations, including: Cold or live migration Resize and revert resize Pause and unpause Reboot Stop or start This test is mandatory. 9.26. neutron-quota The neutron-quota test verifies whether the vendor driver allows management of resource quotas for each project. This test is optional. 9.27. neutron-dns-integration The neutron-dns-integration test verifies whether the integration between neutron and Designate (DNS as a Service) functions correctly. This test is optional.

Commands:
neutron_plugin_options.max_mtu 9000