Skip to content

Commit eb519a9

Browse files
authored
Merge pull request #97234 from sbeskin-redhat/CNV_55995_Host_network_configuration_visualization
CNV-55995: Host network configuration visualization
2 parents e07741b + c6142d2 commit eb519a9

6 files changed

+59
-50
lines changed

modules/virt-create-node-network-config-console.adoc

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,33 +2,30 @@
22
[id="virt-create-node-network-config-console_{context}"]
33
= Creating a policy
44

5-
You can create a policy by using either a form or YAML in the web console.
5+
You can create a policy by using either a form or YAML in the web console. When creating a policy using a form, you can see how the new policy changes the topology of the nodes in your cluster in real time.
66

77
.Procedure
8-
. Navigate to *Networking**NodeNetworkConfigurationPolicy*.
8+
. Navigate to *Networking**Node Network Configuration*.
99

10-
. In the *NodeNetworkConfigurationPolicy* page, click *Create*, and select *From Form* option.
11-
+
12-
In case there are no existing policies, you can alternatively click *Create NodeNetworkConfigurationPolicy* to createa policy using form.
10+
. On the *Node Network Configuration* page, click *Create* and select the *From Form* option.
1311
+
1412
[NOTE]
1513
====
16-
To create policy using YAML, click *Create*, and select *With YAML* option. The following steps are applicable to create a policy only by using form.
14+
To create a policy using YAML, click *Create* -> *With YAML* option. However, the following steps apply only to the form method.
1715
====
18-
1916
. Optional: Check the *Apply this NodeNetworkConfigurationPolicy only to specific subsets of nodes using the node selector* checkbox to specify the nodes where the policy must be applied.
2017

2118
. Enter the policy name in the *Policy name* field.
22-
2319
. Optional: Enter the description of the policy in the *Description* field.
20+
. Click *Next* to move to the *Policy Interfaces* section.
2421

25-
. Optional: In the *Policy Interface(s)* section, a bridge interface is added by default with preset values in editable fields. Edit the values by executing the following steps:
22+
. In the *Bridging* part of the *Policy Interfaces* section, a bridge interface named `br0` is added by default with preset values in editable fields. If required, edit the values by performing the following steps:
2623

2724
.. Enter the name of the interface in *Interface name* field.
2825

29-
.. Select the network state from *Network state* dropdown. The default selected value is *Up*.
26+
.. Select the required network state. The default selected state is *Up*.
3027

31-
.. Select the type of interface from *Type* dropdown. The available values are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.
28+
.. Select the type of interface. The available types are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.
3229
+
3330
[NOTE]
3431
====
@@ -56,5 +53,5 @@ If you have selected *DHCP* option, uncheck the options that you want to disable
5653
====
5754
Alternatively, you can click *Edit YAML* on the top of the page to continue editing the form using YAML.
5855
====
59-
60-
. Click *Create* to complete policy creation.
56+
. Click *Next* to go to the *Review* section of the form.
57+
. Verify the settings and click *Create* to create the policy.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/k8s_nmstate/k8s-observing-node-network-state.adoc
4+
// * networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
5+
6+
:_mod-docs-content-type: PROCEDURE
7+
[id="virt-viewing-graphical-representation-of-network-state-of-node-console_{context}"]
8+
= Viewing a graphical representation of the network state of a node (NNS) topology from the web console
9+
10+
To make the configuration of the node network in the cluster easier to understand, you can view it in the form of a diagram. The NNS topology diagram displays all node components (network interface controllers, bridges, bonds, and VLANs), their properties and configurations, and connections between the nodes.
11+
12+
To open the topology view of the cluster, use the following steps:
13+
14+
* In the *Administrator* view of the {product-title} web console, navigate to *Networking* -> *Node Network Configuration*.
15+
+
16+
The NNS topology diagram opens. Each group of components represents a single node.
17+
+
18+
** To display the configuration and properties of a node, click inside the border of the node.
19+
** To display the features or the YAML file of a specific component (for example, an interface or a bridge), click the icon of the component.
20+
** The icons of active components have green borders; the icons of disconnected components have red borders.
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/k8s_nmstate/k8s-observing-node-network-state.adoc
4+
// * networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
5+
6+
:_mod-docs-content-type: PROCEDURE
7+
[id="virt-viewing-list-of-nodenetworkstate-resources-console_{context}"]
8+
= Viewing the list of NodeNetworkState resources
9+
10+
As an administrator, you can use the {product-title} web console to view the list of `NodeNetworkState` resources and network interfaces, and access network details.
11+
12+
.Procedure
13+
. Navigate to *Networking**Node Network Configuration*.
14+
. Click the *List* icon.
15+
+
16+
You can now view the list of `NodeNetworkState` resources and the corresponding interfaces that are created on the nodes.
17+
18+
* You can use *Filter* based on *Interface state*, *Interface type*, and *IP*, or the search bar based on criteria *Name* or *Label*, to narrow down the displayed `NodeNetworkState` resources.
19+
20+
* To access the detailed information about a `NodeNetworkState` resource, click the `NodeNetworkState` resource name listed in the *Name* column .
21+
22+
* To expand and view the *Network Details* section for the `NodeNetworkState` resource, click the greater than (*>*) symbol . Alternatively, you can click on each interface type under the *Network interface* column to view the network details.
23+

modules/virt-viewing-network-state-of-node-console.adoc

Lines changed: 0 additions & 35 deletions
This file was deleted.

networking/k8s_nmstate/k8s-nmstate-observing-node-network-state.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,6 @@ Node network state is the network configuration for all nodes in the cluster.
1111

1212
include::modules/virt-viewing-network-state-of-node.adoc[leveloffset=+1]
1313

14-
include::modules/virt-viewing-network-state-of-node-console.adoc[leveloffset=+1]
14+
include::modules/virt-viewing-graphical-representation-of-network-state-of-node-console.adoc[leveloffset=+1]
15+
16+
include::modules/virt-viewing-list-of-nodenetworkstate-resources-console.adoc[leveloffset=+1]

networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,9 @@ For more information, see "Creating a manifest object that includes a customized
2222
include::modules/virt-viewing-network-state-of-node.adoc[leveloffset=+1]
2323

2424
// Viewing the network state of a node from the web console
25-
include::modules/virt-viewing-network-state-of-node-console.adoc[leveloffset=+1]
25+
include::modules/virt-viewing-graphical-representation-of-network-state-of-node-console.adoc[leveloffset=+1]
26+
27+
include::modules/virt-viewing-list-of-nodenetworkstate-resources-console.adoc[leveloffset=+1]
2628

2729
// The `NodeNetworkConfigurationPolicy` manifest file
2830
include::modules/node-network-configuration-policy-file.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)