Skip to content
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

Jump to bottom

Additional Cosmetic Fixes #6

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Additional Cosmetic Fixes #6

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f91d0ef
Fix URL text in 09_network_management.adoc
christophermay07 May 22, 2024
2dd755f
Fix whitespace and capitalization
christophermay07 May 22, 2024
a3a42a6
Update for grammar / punctuation
christophermay07 May 22, 2024
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
12 changes: 6 additions & 6 deletions workshop/content/09_network_management.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ By default, all virtual machines are attached to the OpenShift software-defined

However, virtual machines may also connect directly to one or more external networks, such as VLANs, when needed. This is in addition to the SDN, which means that, for example, the administrator can connect to the VM from an external IP address, but the application communicates across the SDN with other VMs hosted by OpenShift Virtualization.

At a high level, this is done by configuring the host networking, such as creating a mode 4 (LACP) bond and a Linux bridge on top. This workshop segment will walk through the next step in that process, creating a network attachment definition to allow VMs to connect to that bridge and, therefore, directly to the external network.
At a high level, this is done by configuring the host networking, such as creating a mode 4 (LACP) bond and a Linux bridge on top. This workshop segment will walk through the next step in that process, creating a network attachment definition to allow VMs to connect to that bridge and, therefore, directly to the external network.

// WKTBD: Maybe add some NetworkPolicy (there is a web console wizard available now in 4.13).

Expand All @@ -30,11 +30,11 @@ The OpenShift environment has already been configured with a Linux Bridge on eac
In order to use the Linux Bridge with your VM you need to create a *Network Attachment Definition*. This is what tells OpenShift about the network and allows the virtual machines to connect to it. Network Attachment Definitions are specific to the project/namespace they're created in, unless they're created in the `default` project. This gives you, the administrator, the ability to control which networks are and aren't available to users who have access to manage their own Vms. Once the Network Attachment Definition has been created, it can then be used by virtual machines when configuring their network adapters.

[NOTE]
A network attachment definition instructs openshift to utilise an existing network device. In our case that device was previously created and is named br-flat. You must use that name or OpenShift won’t be able to place your VM on any compute nodes as it can only utilise nodes with that specifically named network device on it.
A network attachment definition instructs OpenShift to utilise an existing network device. In our case that device was previously created and is named br-flat. You must use that name or OpenShift won’t be able to place your VM on any compute nodes as it can only utilise nodes with that specifically named network device on it.

How is this done?

To manage an OpenShift node's network configuration you use a tool, available as an operator, called nmstate. With nmstate you can create network interfaces on OpenShift compute nodes using Kubernetes constructs. You can do this following naming that suits your needs and network requirements. For more info about nmstate, and to learn more about the host networking and how to view and manage the configuration, see the ([nmstate documentation](https://docs.openshift.com/container-platform/4.15/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html) or speak with your lab proctors."
To manage an OpenShift node's network configuration you use a tool, available as an operator, called nmstate. With nmstate you can create network interfaces on OpenShift compute nodes using Kubernetes constructs. You can do this following naming that suits your needs and network requirements. For more info about nmstate, and to learn more about the host networking and how to view and manage the configuration, see the https://docs.openshift.com/container-platform/4.15/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html[nmstate documentation] or speak with your lab proctors.

. Navigate to *Networking* -> *Network Attachment Definitions* and click *Create network attachment definition*:
+
Expand Down Expand Up @@ -77,7 +77,7 @@ image::images/Networking/05_VM_Network_Attach.png[]
+
image::images/Networking/06_VM_Network_Console.png[]
+
The `eth1` interface obtains an IP address from the flat network (`192.168.3.x/24`). That network has a DHCP server providing IPs to that network.
The `eth1` interface obtains an IP address from the flat network (`192.168.3.x/24`). That network has a DHCP server providing IPs to that network.
+

. (Optional) Verify external connectivity of the VM using the OpenShift web terminal.
Expand All @@ -90,15 +90,15 @@ image::images/OCP_Terminal_Icon.png[]
+
image::images/OCP_Terminal.png[]

.. Type the following command replacing the IP
.. Type the following command, replacing the IP
+
[%nowrap]
----
curl 192.168.3.118:22
----
+
[NOTE]
Replace the IP which the IP assigned to the node.
Replace the IP with the IP assigned to the node.
+
.Sample Output
+
Expand Down