The machinesets should use the nfv-worker flavor defined in OpenStack.
Use the “port” definition of the machinesets to attach the new workers to the low latency networks, and use the network section to attach them to the management network. For example:

apiVersion: ######
Kind: machineset

Metadata:
Name: nfv-worker
……
…. Probably something here about the labels to use.
Spec:
Provider_spec:
Flavor: nfv-worker
Networks:
Uuid : uuid of machineNetwork
Ports:
Uuid: uuid_of_ low_latency_network_1
Uuid: uuid_of_ low_latency_network_2
providerSpec:
value:
apiVersion: openstackproviderconfig.openshift.io/v1alpha1
cloudName: openstack
cloudsSecret:
name: openstack-cloud-credentials
namespace: openshift-machine-api
flavor: <nova_flavor>
image: <glance_image_name_or_location>
kind: OpenstackProviderSpec
ports:

• fixedIPs:
• subnetID: <dpdk_net1_subnet_UUID>
  nameSuffix: dpdk_net1
  networkID: <dpdk_net1_network_UUID>
  portSecurity: False
• fixedIPs:
• subnetID: <dpdk_net2_subnet_UUID>
  nameSuffix: dpdk_net2
  networkID: <dpdk_net2_network_UUID>
  portSecurity: False
• networkID: <SRIOV_network_UUID>
  nameSuffix: sriov
  fixedIPs:
• subnetID: <SRIOV_subnet_UUID>
  tags:
• sriov
  vnicType: direct
  portSecurity: False