F OpenNebula/one#7678: Dummy interface

content/product/operation_references/configuration_references/template.md

@@ -361,7 +361,7 @@ The hypervisor column states that the attribute is **O**ptional, **M**andatory,
 | `OUTBOUND_AVG_BW`    | Average bitrate for the interface in kilobytes/second for outbound traffic.                                                               | O                   | O                   |
 | `OUTBOUND_PEAK_BW`   | Maximum bitrate for the interface in kilobytes/second for outbound traffic.                                                               | O                   | O                   |
 | `OUTBOUND_PEAK_KB`   | Data that can be transmitted at peak speed in kilobytes.                                                                                  | O                   | -                   |
-| `NETWORK_MODE`       | To let the Scheduler pick the VNET if set to auto), any other value will be ignored By default, the network mode is not set.              | O                   | O                   |
+| `NETWORK_MODE`       | Network selection mode. Set to `auto` to let the Scheduler pick the VNET, or to `dummy` to create a KVM guest interface without attaching it to a Virtual Network. By default, the network mode is not set. | O | O (`auto` only) |
 | `SCHED_REQUIREMENTS` | Define the requirement when `NETWORK_MODE` is auto.                                                                                       | O                   | O                   |
 | `SCHED_RANK`         | Define the rank when `NETWORK_MODE` is auto.                                                                                              | O                   | O                   |
 | `NAME`               | Name of the NIC.                                                                                                                          | O                   | O                   |

content/product/virtual_machines_operation/virtual_machines/vm_instances.md

@@ -1376,7 +1376,7 @@ The `onevm` command manages OpenNebula Virtual Machines. The general structure o
 | `--name name`                 | Name for the new VM                             |
 | `--net_context`               | Adds network contextualization parameters       |
 | `-n`, `--network id\|name`    | Selects the virtual network                     |
-| `--nic network0,network1`     | Networks to attach. To use a network owned by another user run `user[network]`. Additional attributes are supported like with the `--disk` option. Also you can use `auto` if you want  OpenNebula to automatically select the network |
+| `--nic network0,network1`     | Networks to attach. To use a network owned by another user run `user[network]`. Additional attributes are supported like with the `--disk` option. You can also use `auto` to let OpenNebula select the network or `dummy` to add a KVM interface without a Virtual Network |
 | `--nic-id nic_id`             | NIC to use when SSH                            |
 | `--nic_name name`             | Name of the NIC                                |
 | `--no-expand`                 | Disables expand                                 |

content/product/virtual_machines_operation/virtual_machines/vm_templates.md

@@ -57,6 +57,15 @@ Network interfaces can be defined in two different ways:
 - **Manual selection**: interfaces are attached to a pre-selected Virtual Network. Note that this may require building multiple templates that consider the available networks in each cluster.
 - **Automatic selection**: Virtual Networks will be scheduled like other resources needed by the VM (like Hosts or datastores). This way, you can specify the type of network the VM will need and it will be automatically selected among those available in the cluster. [See more details here]({{% relref "../../cluster_configuration/networking_system/manage_vnets#vgg-vm-vnets" %}}).
 
+KVM Templates can also define dummy interfaces, which create a guest NIC without attaching it to any OpenNebula Virtual Network. Dummy interfaces are not Virtual Networks. They do not inherit Virtual Network attributes such as gateway, DNS, security groups, or contextualization values. If no `MAC` is provided, OpenNebula generates one automatically. A dummy interface is defined with `NETWORK_MODE = "dummy"` in a `NIC` section:
+
+```default
+NIC = [
+  NETWORK_MODE = "dummy",
+  MAC          = "02:00:5e:00:00:01"
+]
+```
+
 Network **interface alias** allows you to have more than one IP on each network interface. This does not create a new virtual interface on the VM. The alias address is added to the network interface. An alias can be attached and detached. Note also that when an NIC with an alias is detached, all the associated aliases are also detached.
 
 The alias takes a lease from the network which it belongs to. So, for the OpenNebula it is the same as an NIC and exposes the same management interface, it is just different in terms of the associated Virtual Network interface within the VM.

content/software/release_information/release_notes/whats_new.md

@@ -30,6 +30,7 @@ The OpenNebula team is excited to announce the availability of the **OpenNebula
 ## KVM
 
 * Enable filtering by OS ID/type/version/architecture in [QEMU Guest Agent Monitoring](/product/operation_references/hypervisor_configuration/kvm_driver/#qemu-guest-agent-monitoring).
+* Added support for [dummy interfaces]({{% relref "vm_templates#network-interfaces--alias" %}}), allowing KVM VMs to use guest NICs that are not attached to any OpenNebula Virtual Network.
 
 ## LXC