Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1874102

Summary: [ovirt] support network interfaces in machine spec
Product: OpenShift Container Platform Reporter: Luis Martinho <lmartinh>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED NOTABUG QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: medium    
Version: 4.8CC: aos-bugs, gzaidman, jokerman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-05 14:43:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luis Martinho 2020-08-31 15:03:49 UTC 
Document URL: 
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html-single/networking/index

or

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html-single/post-installation_configuration/index


Section Number and Name: 
Add a new section with the description of how can this configuration be done.

Describe the issue: 
This request is regarding the bug https://bugzilla.redhat.com/show_bug.cgi?id=1830852 that as no documentation describing of how to configure the worker hosts network interfaces using the machineSets in RedHat Virtualization.

Suggestions for improvement: 
-Add a chapter informing that the multiple network interfaces can be configured in the worker hosts using machineSets (when RHV is the infrastructure). 

-Add a configuration example to make this configuration of comment https://bugzilla.redhat.com/show_bug.cgi?id=1830852#c5

similar to:

2.See and edit machineset of worker to add netwrk interface
oc get machinesets <mc_worker-worker> -n openshift-machine-api -o yaml

spec:
  replicas: 3
  selector:
    matchLabels:
      machine.openshift.io/cluster-api-cluster: secondary-s5zgz
      machine.openshift.io/cluster-api-machineset: secondary-s5zgz-worker-0
  template:
    metadata:
      labels:
        machine.openshift.io/cluster-api-cluster: secondary-s5zgz
        machine.openshift.io/cluster-api-machine-role: worker
        machine.openshift.io/cluster-api-machine-type: worker
        machine.openshift.io/cluster-api-machineset: secondary-s5zgz-worker-0
    spec:
      metadata: {}
      providerSpec:
        value:
          apiVersion: ovirtproviderconfig.machine.openshift.io/v1beta1
          cluster_id: 9073e91d-e9b2-4322-af86-e38c574ee14c
          cpu:
            cores: 2
            sockets: 2
            threads: 1
          credentialsSecret:
            name: ovirt-credentials
          id: ""
          kind: OvirtMachineProviderSpec
          memory_mb: 24576
          metadata:
            creationTimestamp: null
          name: ""
--------> network_interfaces:
-------->   - vnic_profile_id: ad13ab27-3aae-4c65-a7e8-70b732121570
...
...
"

"

"
Comment 1 Gal Zaidman 2021-10-05 14:43:22 UTC 
At least now in the description of a machineset we have:
"""
Optional: List of the network interfaces of the VM. If you include this parameter, OpenShift Container Platform discards all network interfaces from the template and creates new ones
"""

https://docs.openshift.com/container-platform/4.8/machine_management/creating_machinesets/creating-machineset-rhv.html