CNV-17539: Document default storage provider for CNV+SNO

Moving module content to assembly

Author: Bob Gaydos

modules/virt-about-vm-templates.adoc

@@ -20,8 +20,3 @@ You can use the filters in the template *Catalog* to sort the templates by attri
 You cannot edit or delete a *Red Hat Supported* or *Red Hat Provided* template. You can clone the template, save it as a custom virtual machine template, and then edit it.
 
 You can also create a custom virtual machine template by editing a YAML file example.
-
-[IMPORTANT]
-====
-Due to differences in storage behavior, some virtual machine templates are incompatible with {sno}. To ensure compatibility, do not set the `evictionStrategy` field for any templates or virtual machines that use data volumes or storage profiles.
-====

modules/virt-sno-differences.adoc

@@ -0,0 +1,23 @@
+// Module included in the following assemblies:
+//
+// * virt/about-virt.adoc
+
+:_content-type: CONCEPT
+[id="virt-sno-differences_{context}"]
+= {sno-caps} differences
+
+You can install {VirtProductName} on a single-node cluster.
+
+When provisioning a {sno} cluster with the assisted installer, preconfigured persistent storage is deployed automatically.
+
+* In {VirtProductName} 4.10 and 4.11, the HostPath Provisioner (HPP) is automatically installed.
+* In {VirtProductName} 4.12, the OpenShift Data Foundation Logical Volume Manager Operator is the provided out-of-the-box storage solution. You can also manually deploy using the HPP.
+
+[NOTE]
+====
+{sno-caps} does not support high availability. Be aware of the following differences in functionality from a multiple-node cluster:
+
+* Pod disruption budgets are not supported.
+* Live migration is not supported.
+* Due to differences in storage behavior, some virtual machine templates are incompatible with {sno}. To ensure compatibility,  templates or virtual machines that use data volumes or storage profiles must not have the eviction strategy set.
+====

virt/about-virt.adoc

@@ -20,4 +20,24 @@ You can check your {VirtProductName} cluster for compliance issues by installing
 :FeatureName: {VirtProductName} integration with the Compliance Operator
 include::snippets/technology-preview.adoc[]
 
-include::modules/virt-supported-cluster-version.adoc[leveloffset=+2]
+include::modules/virt-supported-cluster-version.adoc[leveloffset=+2]
+
+include::modules/virt-sno-differences.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources_about-virt"]
+== Additional resources
+
+* xref:../installing/installing_sno/install-sno-preparing-to-install-sno.adoc#install-sno-about-installing-on-a-single-node_install-sno-preparing[About {sno}]
+
+* link:https://cloud.redhat.com/blog/using-the-openshift-assisted-installer-service-to-deploy-an-openshift-cluster-on-metal-and-vsphere[Assisted installer]
+
+* xref:../virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.adoc#virt-configuring-local-storage-for-vms[Hostpath Provisioner (HPP)]
+
+* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.10/html-single/deploying_openshift_data_foundation_on_single_node_openshift_clusters/index#doc-wrapper[{product-title} Data Foundation Logical Volume Manager Operator]
+
+* xref:../nodes/pods/nodes-pods-priority.adoc#priority-preemption-other_nodes-pods-priority[Pod disruption budgets]
+
+* xref:../virt/live_migration/virt-live-migration.adoc#virt-live-migration[Live migration]
+
+* xref:../virt/live_migration/virt-configuring-vmi-eviction-strategy.adoc#virt-configuring-vmi-eviction-strategy[Eviction strategy]

virt/install/preparing-cluster-for-virt.adoc

@@ -13,14 +13,6 @@ Review this section before you install {VirtProductName} to ensure that your clu
 You can use any installation method, including user-provisioned, installer-provisioned, or assisted installer, to deploy {product-title}. However, the installation method and the cluster topology might affect {VirtProductName} functionality, such as snapshots or live migration.
 ====
 
-.{sno-caps} differences
-
-You can install {VirtProductName} on a single-node cluster. See xref:../../installing/installing_sno/install-sno-preparing-to-install-sno.adoc#install-sno-about-installing-on-a-single-node_install-sno-preparing[About {sno}] for more information. {sno-caps} does not support high availability, which results in the following differences:
-
-* xref:../../nodes/pods/nodes-pods-priority.adoc#priority-preemption-other_nodes-pods-priority[Pod disruption budgets] are not supported.
-* xref:../../virt/live_migration/virt-live-migration.adoc#virt-live-migration[Live migration] is not supported.
-* Templates or virtual machines that use data volumes or storage profiles must not have the xref:../../virt/live_migration/virt-configuring-vmi-eviction-strategy.adoc#virt-configuring-vmi-eviction-strategy[`evictionStrategy`] set.
-
 .FIPS mode
 
 If you install your cluster in xref:../../installing/installing-fips.adoc#installing-fips-mode_installing-fips[FIPS mode], no additional setup is required for {VirtProductName}.