You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some NFV use cases use the vnic_type= direct to connet the VFs of an SR-IOV capable NIC to the node VM as additional untrunked ports using openStackMachine.Spec.Ports whilst attaching the node VM to the primary network via a virtio port using openStackMachine.Spec.Networks
As an OpenShift user I would like to be able to deploy a node VM attached to the primary network through a Trunked port with additional ports attached to the vm which are NOT trunked.
The text was updated successfully, but these errors were encountered:
/kind feature
Describe the solution you'd like
Currently you can specify ports to be attached to the instance through
openStackMachine.Spec.Ports , and/or openStackMachine.Spec.Networks
And then ALL ports are either Trunked or Not Trunked depending on config.Trunk depending on instance.Trunk
Some NFV use cases use the vnic_type= direct to connet the VFs of an SR-IOV capable NIC to the node VM as additional untrunked ports using openStackMachine.Spec.Ports whilst attaching the node VM to the primary network via a virtio port using openStackMachine.Spec.Networks
As an OpenShift user I would like to be able to deploy a node VM attached to the primary network through a Trunked port with additional ports attached to the vm which are NOT trunked.
The text was updated successfully, but these errors were encountered: