Merge pull request #66687 from apinnick/CNV-26969-update-getting-started

CNV- 26969: Getting started

Author: apinnick

virt/getting_started/virt-getting-started.adoc

@@ -38,41 +38,48 @@ Plan and install {VirtProductName} on an {product-title} cluster:
 [id="creating-and-managing-vms_{context}"]
 == Creating and managing virtual machines
 
-Create virtual machines (VMs):
+Create a virtual machine (VM):
 
-* xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-rh-images.adoc#virt-creating-vm-from-template_virt-creating-vms-from-rh-images[Create a VM from a template].
-* xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-rh-images.adoc#virt-creating-vm-instancetype_virt-creating-vms-from-rh-images[Create a VM from an instance type].
-* xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-rh-images.adoc#virt-creating-vm-cli_virt-creating-vms-from-rh-images[Create a VM from the command line].
-
-:FeatureName: Creating a virtual machine from an instance type
+* xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-rh-images.adoc#virt-creating-vms-from-rh-images[Create a VM from a Red Hat image].
++
+You can create a VM by using a Red Hat template or an instance type.
++
+:FeatureName: Creating a VM from an instance type
 include::snippets/technology-preview.adoc[]
 
-Connect to VMs:
+* xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-custom-images.adoc#virt-creating-vms-from-custom-images[Create a VM from a custom image].
++
+You can create a VM by importing a custom image from a container registry or a web page, by uploading an image from your local machine, or by cloning a persistent volume claim (PVC).
+
+Connect a VM to a secondary network:
+
+* xref:../../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#virt-connecting-vm-to-linux-bridge[Linux bridge network].
+* xref:../../virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc#virt-connecting-vm-to-ovn-secondary-network[Open Virtual Network (OVN)-Kubernetes secondary network].
+* xref:../../virt/vm_networking/virt-connecting-vm-to-sriov.adoc#virt-connecting-vm-to-sriov[Single Root I/O Virtualization (SR-IOV) network].
++
+[NOTE]
+====
+VMs are connected to the pod network by default.
+====
+
+Connect to a VM:
 
 * Connect to the xref:../../virt/virtual_machines/virt-accessing-vm-consoles.adoc#serial-console_virt-accessing-vm-consoles[serial console] or xref:../../virt/virtual_machines/virt-accessing-vm-consoles.adoc#vnc-console_virt-accessing-vm-consoles[VNC console] of a VM.
 * xref:../../virt/virtual_machines/virt-accessing-vm-ssh.adoc#virt-accessing-vm-ssh[Connect to a VM by using SSH].
 * xref:../../virt/virtual_machines/virt-accessing-vm-consoles.adoc#desktop-viewer_virt-accessing-vm-consoles[Connect to the desktop viewer for Windows VMs].
 
-Manage VMs:
-
-* xref:../../virt/virtual_machines/virt-controlling-vm-states.adoc#virt-controlling-vm-states[Stop, start, pause, and restart a VM by using the web console].
-* xref:../../virt/getting_started/virt-using-the-cli-tools.adoc#virt-virtctl-commands_virt-using-the-cli-tools[Manage a VM, expose a port, or connect to the serial console by using the `virtctl` CLI tool].
-* xref:../../virt/virtual_machines/virt-exporting-vms.adoc#virt-accessing-exported-vm-manifests_virt-exporting-vms[Export VMs].
+Manage a VM:
 
+* xref:../../virt/virtual_machines/virt-controlling-vm-states.adoc#virt-controlling-vm-states[Manage a VM by using the web console].
+* xref:../../virt/getting_started/virt-using-the-cli-tools.adoc#virt-virtctl-commands_virt-using-the-cli-tools[Manage a VM by using the `virtctl` CLI tool].
+* xref:../../virt/virtual_machines/virt-exporting-vms.adoc#virt-accessing-exported-vm-manifests_virt-exporting-vms[Export a VM].
 
 [id="next-steps_{context}"]
 == Next steps
 
-* Connect the VMs to secondary networks:
-
-** xref:../../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#virt-connecting-vm-to-linux-bridge[Connect a VM to a Linux bridge network].
-** xref:../../virt/vm_networking/virt-connecting-vm-to-sriov.adoc#virt-connecting-vm-to-sriov[Connect a VM to an SR-IOV network].
-+
-[NOTE]
-====
-VMs are connected to the pod network by default. You must configure a secondary network, such as Linux bridge or SR-IOV, and then add the network to the VM configuration.
-====
-
-* xref:../../virt/live_migration/virt-about-live-migration.adoc#virt-about-live-migration[Live migrate VMs].
+* xref:../../virt/post_installation_configuration/virt-post-install-config.adoc#virt-post-install-config[Review post-installation configuration options].
+* xref:../../virt/storage/virt-storage-config-overview.adoc#virt-storage-config-overview[Configure storage options and automatic boot source updates].
+* xref:../../virt/monitoring/virt-monitoring-overview.adoc#virt-monitoring-overview[Learn about monitoring and health checks].
+* xref:../../virt/live_migration/virt-about-live-migration.adoc#virt-about-live-migration[Learn about live migration].
 * xref:../../virt/backup_restore/virt-backup-restore-overview.adoc#virt-backup-restore-overview[Back up and restore VMs].
 * link:https://access.redhat.com/articles/6994974[Tune and scale your cluster].

virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc

@@ -1,12 +1,12 @@
-:_content-type: ASSEMBLY                                        
-[id="virt-connecting-vm-to-ovn-secondary-network"]                            
-= Connecting a virtual machine to an OVN-Kubernetes secondary network                                                
-include::_attributes/common-attributes.adoc[]                   
-:context: virt-connecting-vm-to-ovn-secondary-network                        
-                                                                
-toc::[]   
+:_content-type: ASSEMBLY
+[id="virt-connecting-vm-to-ovn-secondary-network"]
+= Connecting a virtual machine to an OVN-Kubernetes secondary network
+include::_attributes/common-attributes.adoc[]
+:context: virt-connecting-vm-to-ovn-secondary-network
 
-You can connect a virtual machine (VM) to an OVN-Kubernetes secondary network. The OVN-Kubernetes Container Network Interface (CNI) plug-in uses the Geneve (Generic Network Virtualization Encapsulation) protocol to create an overlay network between nodes. 
+toc::[]
+
+You can connect a virtual machine (VM) to an Open Virtual Network (OVN)-Kubernetes secondary network. The OVN-Kubernetes Container Network Interface (CNI) plug-in uses the Geneve (Generic Network Virtualization Encapsulation) protocol to create an overlay network between nodes.
 
 {VirtProductName} currently supports the flat layer 2 topology. This topology connects workloads by a cluster-wide logical switch. You can use this overlay network to connect VMs on different nodes, without having to configure any additional physical networking infrastructure.
 
@@ -16,24 +16,20 @@ To configure an OVN-Kubernetes secondary network and attach a VM to that network
 
 . Add information about the secondary network interface to the VM specification by using the web console or the xref:../../virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc#virt-attaching-vm-to-ovn-secondary-nw-cli_virt-connecting-vm-to-ovn-secondary-network[CLI].
 
-
 [id="creating-ovn-layer2-nad"]
 == Creating an OVN-Kubernetes NAD
 
 You can create an OVN-Kubernetes flat layer 2 network attachment definition (NAD) by using the {product-title} web console or the CLI.
 
-
 include::modules/virt-creating-layer2-nad-cli.adoc[leveloffset=+2]
 
-
 [id="attaching-vm-to-ovn-secondary-nw"]
 == Attaching a virtual machine to the OVN-Kubernetes secondary network
 
 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]
 
-
 [role="_additional-resources"]
 [id="additional-resources_virt-connecting-vm-to-ovn-secondary-network"]
 == Additional resources