rhpds / roadshow_ocpvirt_instructions

Lab Instructions for OCP Virtualization Roadshow
Apache License 2.0
28 stars 61 forks source link

NMstate warning update #34

Closed augustrh closed 8 months ago

augustrh commented 11 months ago

I'll raise as a PR shortly, but adding here for visibility.

Some attendees didn’t understand/notice the note about the host network (bridge) being pre-created (br-flat) so used a custom name when creating their network attachment definition (or simply had a typo). This leads to a state where the machine can’t start as it can’t find the bridge named on any node (as it does not exist). The current warning is not all that clear to those with intro knowledge to OCP and networking so I'd propose to make it clearer.

OLD: "Due to time constraints, the host network has already been configured in this lab. If you want to learn more about the host networking, along with how to view and manage the configuration, please use the NMState documentation found here."

PROPOSED: "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 one of the compute nodes as it must find compute nodes with that specificaly named network device on it.

You use an operator called NMState to create network configurations on OpenShift nodes. You can create interfaces with any naming to suit your needs and network requirements. For more info about NMstate see the documentation or speak with your lab proctors."

augustrh commented 11 months ago

PROPOSED: "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 one of the compute nodes as it must utilise nodes with that specifically named network device on it.

To manage an OpenShift node's network configuration you use a tool, available as an operator, called nmstate to create. With nmstate can create interfaces using Kubernetes constructs on your OpenShift compute nodes. You can do this following any naming that suit your needs and network requirements. For more info about nmstate see the documentation (nmstate) or speak with your lab proctors."

augustrh commented 11 months ago

PR sent: https://github.com/rhpds/roadshow_ocpvirt_instructions/pull/35

augustrh commented 8 months ago

PR has been merged so this issue being closed.