Merge pull request #62957 from apinnick/post-install-configuration

post-install configuration

Author: apinnick

_topic_maps/_topic_map.yml

@@ -3629,18 +3629,23 @@ Topics:
   - Name: Installing OKD Virtualization
     File: installing-virt
     Distros: openshift-origin
-  - Name: Specifying nodes for OpenShift Virtualization components
-    File: virt-specifying-nodes-for-virtualization-components
-    Distros: openshift-enterprise
-  - Name: Specifying nodes for OKD Virtualization components
-    File: virt-specifying-nodes-for-virtualization-components
-    Distros: openshift-origin
   - Name: Uninstalling OpenShift Virtualization
     File: uninstalling-virt
     Distros: openshift-enterprise
   - Name: Uninstalling OKD Virtualization
     File: uninstalling-virt
     Distros: openshift-origin
+- Name: Post-installation configuration
+  Dir: post_installation_configuration
+  Topics:
+  - Name: Post-installation configuration
+    File: virt-post-install-config
+  - Name: Node placement rules
+    File: virt-node-placement-virt-components
+  - Name: Network configuration
+    File: virt-post-install-network-config
+  - Name: Storage configuration
+    File: virt-post-install-storage-config
 - Name: Updating
   Dir: updating
   Topics:

modules/k8s-nmstate-installing-the-kubernetes-nmstate-operator.adoc

@@ -1,10 +1,11 @@
 // This is included in the following assemblies:
 //
 // networking/k8s_nmstate/k8s-nmstate-about-the-kubernetes-nmstate-operator.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 
 :_content-type: PROCEDURE
 [id="installing-the-kubernetes-nmstate-operator-web-console_{context}"]
-= Installing the Kubernetes NMState Operator using the web console
+= Installing the Kubernetes NMState Operator by using the web console
 
 You can install the Kubernetes NMState Operator by using the web console. After it is installed, the Operator can deploy the NMState State Controller as a daemon set across all of the cluster nodes.
 

modules/nw-sriov-configuring-device.adoc

@@ -2,6 +2,7 @@
 //
 // * networking/hardware_networks/configuring-sriov-device.adoc
 // * virt/vm_networking/virt-connecting-vm-to-sriov.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 
 ifeval::["{context}" == "configuring-sriov-device"]
 :ocp-sriov:
@@ -10,6 +11,9 @@ endif::[]
 ifeval::["{context}" == "virt-connecting-vm-to-sriov"]
 :virt-sriov:
 endif::[]
+ifeval::["{context}" == "virt-post-install-network-config"]
+:virt-sriov:
+endif::[]
 
 :_content-type: PROCEDURE
 [id="nw-sriov-configuring-device_{context}"]

modules/nw-sriov-installing-operator.adoc

@@ -1,12 +1,13 @@
 // Module included in the following assemblies:
 //
 // * networking/hardware_networks/installing-sriov-operator.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 
 :_content-type: PROCEDURE
 [id="installing-sr-iov-operator_{context}"]
-= Installing SR-IOV Network Operator
+= Installing the SR-IOV Network Operator
 
-As a cluster administrator, you can install the SR-IOV Network Operator by using the {product-title} CLI or the web console.
+As a cluster administrator, you can install the Single Root I/O Virtualization (SR-IOV) Network Operator by using the {product-title} CLI or the web console.
 
 [id="install-operator-cli_{context}"]
 == CLI: Installing the SR-IOV Network Operator

modules/nw-sriov-network-attachment.adoc

@@ -2,6 +2,7 @@
 //
 // * networking/hardware_networks/configuring-sriov-net-attach.adoc
 // * virt/vm_networking/virt-connecting-vm-to-sriov.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 
 // Note: IB does not support ipam with `type=dhcp`.
 

modules/virt-about-node-placement-virt-components.adoc

@@ -0,0 +1,18 @@
+// Module included in the following assemblies:
+//
+// * vvirt/post_installation_configuration/virt-node-placement-virt-components.adoc
+
+:_content-type: CONCEPT
+[id="virt-about-node-placement-virt-components_{context}"]
+= About node placement rules for {VirtProductName} components
+
+You can use node placement rules for the following tasks:
+
+* Deploy virtual machines only on nodes intended for virtualization workloads.
+* Deploy Operators only on infrastructure nodes.
+* Maintain separation between workloads.
+
+Depending on the object, you can use one or more of the following rule types:
+
+`nodeSelector`:: Allows pods to be scheduled on nodes that are labeled with the key-value pair or pairs that you specify in this field. The node must have labels that exactly match all listed pairs.
+`affinity`:: Enables you to use more expressive syntax to set rules that match nodes with pods. Affinity also allows for more nuance in how the rules are applied. For example, you can specify that a rule is a preference, not a requirement. If a rule is a preference, pods are still scheduled when the rule is not satisfied.

modules/virt-applying-node-placement-rules.adoc

@@ -0,0 +1,25 @@
+// Module included in the following assemblies:
+//
+// * virt/post_installation_configuration/virt-node-placement-virt-components.adoc
+
+:_content-type: PROCEDURE
+[id="virt-applying-node-place-rules_{context}"]
+= Applying node placement rules
+
+You can apply node placement rules by editing a `Subscription`, `HyperConverged`, or `HostPathProvisioner` object using the command line.
+
+.Prerequisites
+
+* The `oc` CLI tool is installed.
+* You are logged in with cluster administrator permissions.
+
+.Procedure
+
+. Edit the object in your default editor by running the following command:
++
+[source,terminal]
+----
+$ oc edit <resource_type> <resource_name> -n {CNVNamespace}
+----
+
+. Save the file to apply the changes.

modules/virt-configuring-secondary-network-vm-live-migration.adoc

@@ -1,10 +1,11 @@
 // Module included in the following assemblies:
 //
 // * virt/vm_networking/virt-dedicated-network-live-migration.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 
 :_content-type: PROCEDURE
 [id="virt-configuring-secondary-network-vm-live-migration_{context}"]
-= Configuring a dedicated secondary network for virtual machine live migration
+= Configuring a dedicated secondary network for live migration
 
 To configure a dedicated secondary network for live migration, you must first create a bridge network attachment definition (NAD) by using the CLI. Then, you add the name of the `NetworkAttachmentDefinition` object to the `HyperConverged` custom resource (CR).
 
@@ -52,7 +53,7 @@ spec:
 oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
-. Add the name of the `NetworkAttachmentDefinition` object to the `spec.liveMigrationConfig` stanza of the `HyperConverged` CR. For example:
+. Add the name of the `NetworkAttachmentDefinition` object to the `spec.liveMigrationConfig` stanza of the `HyperConverged` CR:
 +
 .Example `HyperConverged` manifest
 [source,yaml]

modules/virt-creating-hpp-basic-storage-pool.adoc

@@ -1,6 +1,7 @@
 // Module included in the following assemblies:
 //
 // * virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.adoc
+// * virt/post_installation_configuration/virt-post-install-storage-config.adoc
 
 :_content-type: PROCEDURE
 [id="virt-creating-hpp-basic-storage-pool_{context}"]

modules/virt-creating-linux-bridge-nad-web.adoc

@@ -1,6 +1,7 @@
 // Module included in the following assemblies:
 //
 // * virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc
+// * virt/post_installation_configuration/virt-post-install-network-config.adoc
 //This file contains UI elements and/or package names that need to be updated.
 
 :_content-type: PROCEDURE