Skip to content

Commit f5522f8

Browse files
committed
web console checkups
1 parent f99dbec commit f5522f8

File tree

4 files changed

+65
-1
lines changed

4 files changed

+65
-1
lines changed
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * virt/monitoring/virt-running-cluster-checkups.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="virt-latency-checkup-web-console_{context}"]
7+
= Running a latency checkup in the web console
8+
9+
Run a latency checkup to verify network connectivity and measure the latency between two virtual machines attached to a secondary network interface.
10+
11+
.Prerequisites
12+
13+
* You must add a `NetworkAttachmentDefinition` to the namespace.
14+
15+
.Procedure
16+
17+
. Navigate to *Virtualization* -> *Checkups* in the web console.
18+
. Click the *Network latency* tab.
19+
. Click *Install permissions*.
20+
. Click *Run checkup*.
21+
. Enter a name for the checkup in the *Name* field.
22+
. Select a *NetworkAttachmentDefinition* from the drop-down menu.
23+
. Optional: Set a duration for the latency sample in the *Sample duration (seconds)* field.
24+
. Optional: Define a maximum latency time interval by enabling *Set maximum desired latency (milliseconds)* and defining the time interval.
25+
. Optional: Target specific nodes by enabling *Select nodes* and specifying the *Source node* and *Target node*.
26+
. Click *Run*.
27+
28+
You can view the status of the latency checkup in the *Checkups* list on the *Latency checkup* tab. Click on the name of the checkup for more details.

modules/virt-measuring-latency-vm-secondary-network.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
:_mod-docs-content-type: PROCEDURE
66
[id="virt-measuring-latency-vm-secondary-network_{context}"]
7-
= Running a latency checkup
7+
= Running a latency checkup on the CLI
88

99
You use a predefined checkup to verify network connectivity and measure latency between two virtual machines (VMs) that are attached to a secondary network interface. The latency checkup uses the ping utility.
1010

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * virt/monitoring/virt-running-cluster-checkups.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="virt-storage-checkup-web-console_{context}"]
7+
= Running a storage checkup in the web console
8+
9+
Run a storage checkup to validate that storage is working correctly for virtual machines.
10+
11+
.Procedure
12+
13+
. Navigate to *Virtualization* -> *Checkups* in the web console.
14+
. Click the *Storage* tab.
15+
. Click *Install permissions*.
16+
. Click *Run checkup*.
17+
. Enter a name for the checkup in the *Name* field.
18+
. Enter a timeout value for the checkup in the *Timeout (minutes)* fields.
19+
. Click *Run*.
20+
21+
You can view the status of the storage checkup in the *Checkups* list on the *Storage* tab. Click on the name of the checkup for more details.

virt/monitoring/virt-running-cluster-checkups.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,21 @@ include::snippets/technology-preview.adoc[]
2222

2323
include::modules/virt-about-cluster-checkup-framework.adoc[leveloffset=+1]
2424

25+
== Running cluster checkups in the web console
26+
27+
Use the web console to run a latency or storage checkup on a cluster.
28+
29+
Use the following procedures the first time you run a latency checkup and storage checkup in the web console. For additional checkups, click *Run checkup* on either checkup tab, and select the appropriate checkup from the drop down menu.
30+
31+
[IMPORTANT]
32+
====
33+
Before you run a latency checkup, you must first xref:../../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#virt-connecting-vm-to-linux-bridge[create a bridge interface] on the cluster nodes to connect the VM's secondary interface to any interface on the node. If you do not create a bridge interface, the VMs will not start and the job will fail.
34+
====
35+
36+
include::modules/virt-latency-checkup-web-console.adoc[leveloffset=+2]
37+
38+
include::modules/virt-storage-checkup-web-console.adoc[leveloffset=+2]
39+
2540
include::modules/virt-measuring-latency-vm-secondary-network.adoc[leveloffset=+1]
2641

2742
include::modules/virt-checking-cluster-dpdk-readiness.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)