7.14. Virtual machine networking

Procedure

1. Edit the interfaces spec of your virtual machine configuration file:

   kind: VirtualMachine
   spec:
     domain:
       devices:
         interfaces:
           - name: red
             masquerade: {} 1
             ports:
               - port: 80 2
     networks:
     - name: red
       pod: {}

   1

   Connect using masquerade mode

   2

   Allow incoming traffic on port 80

2. Create the virtual machine:

   $ oc create -f <vm-name>.yaml

Procedure

1. Edit the virtual machine YAML as follows:

   apiVersion: kubevirt.io/v1alpha3
   kind: VirtualMachine
   metadata:
     name: vm-ephemeral
     namespace: example-namespace
   spec:
     running: false
     template:
       metadata:
         labels:
           special: key 1
       spec:
         domain:
           devices:
             disks:
               - name: containerdisk
                 disk:
                   bus: virtio
               - name: cloudinitdisk
                 disk:
                   bus: virtio
             interfaces:
             - masquerade: {}
               name: default
           resources:
             requests:
               memory: 1024M
         networks:
           - name: default
             pod: {}
         volumes:
           - name: containerdisk
             containerDisk:
               image: kubevirt/fedora-cloud-container-disk-demo
           - name: cloudinitdisk
             cloudInitNoCloud:
               userData: |
                 #!/bin/bash
                 echo "fedora" | passwd fedora --stdin

   1

   Add the label special: key in the spec.template.metadata.labels section.

   注意

   Labels on a virtual machine are passed through to the pod. The labels on the VirtualMachine, for example special: key, must match the labels in the Service YAML selector attribute, which you create later in this procedure.

2. Save the virtual machine YAML to apply your changes.

3. Edit the Service YAML to configure the settings necessary to create and expose the Service object:

   apiVersion: v1
   kind: Service
   metadata:
     name: vmservice 1
     namespace: example-namespace 2
   spec:
     ports:
     - port: 27017
       protocol: TCP
       targetPort: 22 3
     selector:
       special: key 4
     type: ClusterIP 5

   1

   Specify the name of the service you are creating and exposing.

   2

   Specify namespace in the metadata section of the Service YAML that corresponds to the namespace you specify in the virtual machine YAML.

   3

   Add targetPort: 22, exposing the service on SSH port 22.

   4

   In the spec section of the Service YAML, add special: key to the selector attribute, which corresponds to the labels you added in the virtual machine YAML configuration file.

   5

   In the spec section of the Service YAML, add type: ClusterIP for a ClusterIP service. To create and expose other types of services externally, outside of the cluster, such as NodePort and LoadBalancer, replace type: ClusterIP with type: NodePort or type: LoadBalancer, as appropriate.

4. Save the Service YAML to store the service configuration.

5. Create the ClusterIP service:

   $ oc create -f <service_name>.yaml

6. Start the virtual machine. If the virtual machine is already running, restart it.

7. Query the Service object to verify it is available and is configured with type ClusterIP.

   Verification

   • Run the oc get service command, specifying the namespace that you reference in the virtual machine and Service YAML files.

     $ oc get service -n example-namespace

     Example output

     NAME        TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
     vmservice   ClusterIP   172.30.3.149   <none>        27017/TCP   2m

     • As shown from the output, vmservice is running.
     • The TYPE displays as ClusterIP, as you specified in the Service YAML.

8. Establish a connection to the virtual machine that you want to use to back your service. Connect from an object inside the cluster, such as another virtual machine.

   1. Edit the virtual machine YAML as follows:

      apiVersion: kubevirt.io/v1alpha3
      kind: VirtualMachine
      metadata:
        name: vm-connect
        namespace: example-namespace
      spec:
        running: false
        template:
          spec:
            domain:
              devices:
                disks:
                  - name: containerdisk
                    disk:
                      bus: virtio
                  - name: cloudinitdisk
                    disk:
                      bus: virtio
                interfaces:
                - masquerade: {}
                  name: default
              resources:
                requests:
                  memory: 1024M
            networks:
              - name: default
                pod: {}
            volumes:
              - name: containerdisk
                containerDisk:
                  image: kubevirt/fedora-cloud-container-disk-demo
              - name: cloudinitdisk
                cloudInitNoCloud:
                  userData: |
                    #!/bin/bash
                    echo "fedora" | passwd fedora --stdin

   2. Run the oc create command to create a second virtual machine, where file.yaml is the name of the virtual machine YAML:

      $ oc create -f <file.yaml>

   3. Start the virtual machine.

   4. Connect to the virtual machine by running the following virtctl command:

      $ virtctl -n example-namespace console <new-vm-name>

      注意

      For service type LoadBalancer, use the vinagre client to connect your virtual machine by using the public IP and port. External ports are dynamically allocated when using service type LoadBalancer.

   5. Run the ssh command to authenticate the connection, where 172.30.3.149 is the ClusterIP of the service and fedora is the user name of the virtual machine:

      $ ssh fedora@172.30.3.149 -p 27017

      Verification

      • You receive the command prompt of the virtual machine backing the service you want to expose. You now have a service backed by a running virtual machine.

Procedure

1. In the correct project in the OpenShift Virtualization console, click Workloads Virtualization from the side menu.
2. Click the Virtual Machines tab.
3. Select a virtual machine to open the Virtual Machine Overview screen.
4. Click Network Interfaces to display the NICs already attached to the virtual machine.
5. Click Add Network Interface to create a new slot in the list.
6. Fill in the Name, Model, Network, Type, and MAC Address for the new NIC.
7. Click the Add button to save and attach the NIC to the virtual machine.

Procedure

1. Create an SriovNetworkNodePolicy object, and then save the YAML in the <name>-sriov-node-network.yaml file. Replace <name> with the name for this configuration.

2. Create the SriovNetworkNodePolicy object:

   $ oc create -f <name>-sriov-node-network.yaml

   where <name> specifies the name for this configuration.

   After applying the configuration update, all the pods in sriov-network-operator namespace transition to the Running status.

3. To verify that the SR-IOV network device is configured, enter the following command. Replace <node_name> with the name of a node with the SR-IOV network device that you just configured.

   $ oc get sriovnetworknodestates -n openshift-sriov-network-operator <node_name> -o jsonpath='{.status.syncStatus}'

Procedure

1. Create the following SriovNetwork object, and then save the YAML in the <name>-sriov-network.yaml file. Replace <name> with a name for this additional network.

2. To create the object, enter the following command. Replace <name> with a name for this additional network.

   $ oc create -f <name>-sriov-network.yaml

3. Optional: To confirm that the NetworkAttachmentDefinition object associated with the SriovNetwork object that you created in the previous step exists, enter the following command. Replace <namespace> with the namespace you specified in the SriovNetwork object.

   $ oc get net-attach-def -n <namespace>

Procedure

1. Include the SR-IOV network details in the spec.domain.devices.interfaces and spec.networks of the virtual machine configuration:

   kind: VirtualMachine
   ...
   spec:
     domain:
       devices:
         interfaces:
         - name: <default> 1
           masquerade: {} 2
         - name: <nic1> 3
           sriov: {}
     networks:
     - name: <default> 4
       pod: {}
     - name: <nic1> 5
       multus:
           networkName: <sriov-network> 6
   ...

   1

   A unique name for the interface that is connected to the Pod network.

   2

   The masquerade binding to the default Pod network.

   3

   A unique name for the SR-IOV interface.

   4

   The name of the Pod network interface. This must be the same as the interfaces.name that you defined earlier.

   5

   The name of the SR-IOV interface. This must be the same as the interfaces.name that you defined earlier.

   6

   The name of the SR-IOV network attachment definition.

2. Apply the virtual machine configuration:

   $ oc apply -f <vm-sriov.yaml> 1

   1

   The name of the virtual machine YAML file.

Procedure

1. Access the virtual machine command line through one of the consoles or by SSH.

2. Install the QEMU guest agent on the virtual machine:

   $ yum install -y qemu-guest-agent

3. Start the QEMU guest agent service:

   $ systemctl start qemu-guest-agent

4. Ensure the service is persistent:

   $ systemctl enable qemu-guest-agent

1. Verify that the guest agent is installed and running by entering the following command:

   $ systemctl status qemu-guest-agent

2. If the guest agent is not installed and running, install and run the guest agent on the virtual machine.

Procedure

1. In the OpenShift Virtualization console, click Workloads Virtualization from the side menu.
2. Click the Virtual Machines tab.
3. Select a virtual machine name to open the Virtual Machine Overview screen.