Skip to content

[enterprise-4.15] #CNV-30305 - new NAD localnet content #71832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2024
Merged

[enterprise-4.15] #CNV-30305 - new NAD localnet content #71832

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions modules/virt-creating-nad-localnet-console.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
// Module included in the following assemblies:
//
// * virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc

:_mod-docs-content-type: PROCEDURE
[id="virt-creating-nad-localnet-console_{context}"]
= Creating a NAD for localnet topology using the web console

You can create a network attachment definition (NAD) to connect workloads to a physical network by using the {product-title} web console.

.Prerequisites
* Use `nmstate` to configure the localnet to OVS bridge mappings.

.Procedure

. Navigate to *Networking* -> *NetworkAttachmentDefinitions* in the web console.

. Click *Create Network Attachment Definition*. The network attachment definition must be in the same namespace as the pod or virtual machine using it.

. Enter a unique *Name* and optional *Description*.

. Select *OVN Kubernetes secondary localnet network* from the *Network Type* list.

. Enter the name of your pre-configured localnet identifier in the *Bridge mapping* field.

. Optional: You can explicitly set MTU to the specified value. The default value is chosen by the kernel.

. Optional: Encapsulate the traffic in a VLAN. The default value is none.

. Click *Create*.
5 changes: 4 additions & 1 deletion virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,12 @@ include::modules/virt-creating-localnet-nad-cli.adoc[leveloffset=+2]
You can attach a virtual machine (VM) to the OVN-Kubernetes secondary network interface by using the {product-title} web console or the CLI.

include::modules/virt-attaching-vm-to-ovn-secondary-nw-cli.adoc[leveloffset=+2]
include::modules/virt-creating-nad-localnet-console.adoc[leveloffset=+2]

[role="_additional-resources"]
[id="additional-resources_virt-connecting-vm-to-ovn-secondary-network"]
== Additional resources
* xref:../../networking/multiple_networks/configuring-additional-network.adoc#configuration-ovnk-additional-networks_configuring-additional-network[Configuration for an OVN-Kubernetes additional network]
* xref:../../networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.adoc#k8s-nmstate-about-the-k8s-nmstate-operator[About the Kubernetes NMState Operator]
* xref:../../networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.adoc#k8s-nmstate-about-the-k8s-nmstate-operator[About the Kubernetes NMState Operator]
* xref:../../networking/multiple_networks/configuring-additional-network.adoc#configuring-additional-network_configuration-additional-network-interface[Configuration for an OVN-Kubernetes additional network mapping]
* xref:../../networking/multiple_networks/configuring-additional-network.adoc#configuring-additional-network_configuration-additional-network-attachment[Configuration for an additional network attachment]