Red Hat OpenStack 10 (Newton)

OVS 2.5

DPDK 2.2

Create director going through steps described in a documentation

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/director_installation_and_usage/chap-installing_the_undercloud

Follow the procedure till point 5.6 then use templates use provided in the repo

Download templates

• su - stack
• source stackrc
• cd ~/templates
• git clone https://github.com/PrzemekGrygiel/RHOS10_OVS_with_DVR.git
• cd RHOS10_OVS_with_DVR/

NIC1 - 1G for deploying and management only

NIC2 - br-ex interface with Internal API (tag) and External network (untag)

NIC3 and NIC4 - 10G in LACP bond without tagged tenant network interface

On compute nodes DPDK is enabled, on controllers it is optional. If you use storage networks they should be attached to NIC2 as tagged

• cd ovs-dvr-dpdk/

• Edit "network-environment.yaml" providing appropriate VLANs, NICs, network addresses and NUMA configuration

• Start deployment ./overcloud-deploy.sh

• After deployment move Tenant network from br-ex (tagged) to br-link (untagged)on all compute nodes

  • log on compute using user heat-admin from director stack user account ([stack@manager ~]$ ssh heat-admin@[compute IP])
  • ovs-vsctl del-port br-ex [tenant net vlan int. name]
  • move interface configuration from /etc/sysconfig/network-scripts/ifcfg-vlanXX to /etc/sysconfig/network-scripts/ifcfg-br-link as untagged
  • ifdown br-link, ifup br-link

• if creation of VMs fail please add root roghts for libvirt qemu editing /etc/libvirt/qemu.conf uncomentings lines:

  user = "root"
  
  group = "root
  

  and restart libvirt by
  systemctl restart libvirtd

• to have SG change firewall driver from IPtables to OVS as described there:

https://bugzilla.redhat.com/show_bug.cgi?id=1367678 in openvswitch_agent.ini change to firewall_driver = x to firewall_driver = openvswitch

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/#sect-ovd-dpdk-flavor-deploy-instance

NIC1 - 1G for deploying and management only

NIC2 - not used

NIC3 and NIC4 - 10G in LACP bond with tagged interfaces

If you use storage networks they should be attached to NIC3 and NIC4 as tagged

TBD

TBD

• cd ovs-dvr-km/
• Edit "network-environment.yaml" providing appropriate VLANs, NICs, network addresses and NUMA configuration
• please notice that network configuration for Controllers and computes is the same
• Start deployment ./overcloud-deploy-dvr.sh