openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

scrubbing CNV

Browse Source
This commit is contained in:
Kathryn Alexander
2020-03-25 09:50:11 -04:00
parent 38d52c6f03
commit 66edd81826
317 changed files with 2316 additions and 1843 deletions
Download Patch File Download Diff File Expand all files Collapse all files

199
_topic_map.yml
View File

@@ -1457,190 +1457,187 @@ Topics:
File: rhbjaeger-removing
---
Name: Container-native virtualization
Dir: cnv
Name: OpenShift virtualization
Dir: virt
Distros: openshift-enterprise,openshift-webscale
Topics:
- Name: About container-native virtualization
File: cnv-about-cnv
- Name: Container-native virtualization release notes
Dir: cnv_release_notes
- Name: About OpenShift virtualization
File: about-virt
- Name: OpenShift virtualization release notes
File: virt-2-4-release-notes
- Name: OpenShift virtualization installation
Dir: install
Topics:
- Name: Container-native virtualization release notes
File: cnv-2-4-release-notes
- Name: Container-native virtualization installation
Dir: cnv_install
Topics:
- Name: Preparing your OpenShift cluster for container-native virtualization
File: preparing-cluster-for-cnv
- Name: Installing container-native virtualization
File: installing-container-native-virtualization
- Name: Preparing your OpenShift cluster for OpenShift virtualization
File: preparing-cluster-for-virt
- Name: Installing OpenShift virtualization
File: installing-virt
- Name: Installing the virtctl client
File: cnv-installing-virtctl
- Name: Uninstalling container-native virtualization
File: uninstalling-container-native-virtualization
- Name: Upgrading container-native virtualization
File: upgrading-container-native-virtualization
File: virt-installing-virtctl
- Name: Uninstalling OpenShift virtualization
File: uninstalling-virt
- Name: Upgrading OpenShift virtualization
File: upgrading-virt
- Name: Using the CLI tools
File: cnv-using-the-cli-tools
File: virt-using-the-cli-tools
- Name: Virtual machines
Dir: cnv_virtual_machines
Dir: virtual_machines
Topics:
###VIRTUAL MACHINE CHESS SALAD (silly name to highlight that the commented out assemblies need to be checked against merged filenams)
- Name: Creating virtual machines
File: cnv-create-vms
File: virt-create-vms
- Name: Editing virtual machines
File: cnv-edit-vms
File: virt-edit-vms
- Name: Editing boot order
File: cnv-edit-boot-order
File: virt-edit-boot-order
- Name: Deleting virtual machines
File: cnv-delete-vms
File: virt-delete-vms
- Name: Deleting virtual machine instances
File: cnv-deleting-vmis
- Name: Controlling virtual machine states
File: cnv-controlling-vm-states
File: virt-deleting-vmis
- Name: Controlling virtual machines states
File: virt-controlling-vm-states
- Name: Accessing virtual machine consoles
File: cnv-accessing-vm-consoles
File: virt-accessing-vm-consoles
- Name: Installing VirtIO driver on an existing Windows virtual machine
File: cnv-installing-virtio-drivers-on-existing-windows-vm
File: virt-installing-virtio-drivers-on-existing-windows-vm
- Name: Installing VirtIO driver on a new Windows virtual machine
File: cnv-installing-virtio-drivers-on-new-windows-vm
File: virt-installing-virtio-drivers-on-new-windows-vm
- Name: Advanced virtual machine management
Dir: cnv_advanced_vm_management
Dir: advanced_vm_management
Topics:
#Advanced virtual machine configuration
- Name: Automating management tasks
File: cnv-automating-management-tasks
File: virt-automating-management-tasks
- Name: Configuring PXE booting for virtual machines
File: cnv-configuring-pxe-booting
File: virt-configuring-pxe-booting
- Name: Managing guest memory
File: cnv-managing-guest-memory
File: virt-managing-guest-memory
- Name: Enabling dedicated resources for a virtual machine
File: cnv-dedicated-resources-vm
#Importing virtual machines
File: virt-dedicated-resources-vm
# Importing virtual machines
- Name: Importing virtual machines
Dir: cnv_importing_vms
Dir: importing_vms
Topics:
- Name: TLS certificates for DataVolume imports
File: cnv-tls-certificates-for-dv-imports
File: virt-tls-certificates-for-dv-imports
- Name: Importing virtual machine images with DataVolumes
File: cnv-importing-virtual-machine-images-datavolumes
File: virt-importing-virtual-machine-images-datavolumes
- Name: Importing virtual machine images to block storage with DataVolumes
File: cnv-importing-virtual-machine-images-datavolumes-block
File: virt-importing-virtual-machine-images-datavolumes-block
- Name: Importing a VMware virtual machine or template
File: cnv-importing-vmware-vm
#Cloning virtual machines
File: virt-importing-vmware-vm
# Cloning virtual machines
- Name: Cloning virtual machines
Dir: cnv_cloning_vms
Dir: cloning_vms
Topics:
- Name: Enabling user permissions to clone DataVolumes across namespaces
File: cnv-enabling-user-permissions-to-clone-datavolumes
File: virt-enabling-user-permissions-to-clone-datavolumes
- Name: Cloning a virtual machine disk into a new DataVolume
File: cnv-cloning-vm-disk-into-new-datavolume
File: virt-cloning-vm-disk-into-new-datavolume
- Name: Cloning a virtual machine by using a DataVolumeTemplate
File: cnv-cloning-vm-using-datavolumetemplate
File: virt-cloning-vm-using-datavolumetemplate
- Name: Cloning a virtual machine disk into a new block storage DataVolume
File: cnv-cloning-vm-disk-into-new-datavolume-block
#Virtual machine networking
File: virt-cloning-vm-disk-into-new-datavolume-block
# Virtual machine networking
- Name: Virtual machine networking
Dir: cnv_vm_networking
Dir: vm_networking
Topics:
- Name: Using the default Pod network with container-native virtualization
File: cnv-using-the-default-pod-network-with-cnv
- Name: Using the default Pod network with OpenShift virtualization
File: virt-using-the-default-pod-network-with-virt
- Name: Attaching a virtual machine to multiple networks
File: cnv-attaching-vm-multiple-networks
File: virt-attaching-vm-multiple-networks
- Name: Installing the QEMU guest agent on virtual machines
File: cnv-installing-qemu-guest-agent
File: virt-installing-qemu-guest-agent
- Name: Viewing the IP address of NICs on a virtual machine
File: cnv-viewing-ip-of-vm-nic
#A BETTER NAME THAN 'STORAGE 4 U'
File: virt-viewing-ip-of-vm-nic
# A BETTER NAME THAN 'STORAGE 4 U'
- Name: Virtual machine disks
Dir: cnv_virtual_disks
Dir: virtual_disks
Topics:
- Name: Configuring local storage for virtual machines
File: cnv-configuring-local-storage-for-vms
File: virt-configuring-local-storage-for-vms
- Name: Uploading local disk images by using the virtctl tool
File: cnv-uploading-local-disk-images-virtctl
File: virt-uploading-local-disk-images-virtctl
- Name: Uploading a local disk image to a block storage DataVolume
File: cnv-uploading-local-disk-images-block
File: virt-uploading-local-disk-images-block
- Name: Moving a local virtual machine disk to a different node
File: cnv-moving-local-vm-disk-to-different-node
File: virt-moving-local-vm-disk-to-different-node
- Name: Expanding virtual storage by adding blank disk images
File: cnv-expanding-virtual-storage-with-blank-disk-images
File: virt-expanding-virtual-storage-with-blank-disk-images
- Name: Storage defaults for DataVolumes
File: cnv-storage-defaults-for-datavolumes
File: virt-storage-defaults-for-datavolumes
- Name: Preparing CDI scratch space
File: cnv-preparing-cdi-scratch-space
File: virt-preparing-cdi-scratch-space
- Name: Deleting DataVolumes
File: cnv-deleting-datavolumes
#Templates
File: virt-deleting-datavolumes
# Templates
- Name: Virtual machine templates
Dir: cnv_vm_templates
Dir: vm_templates
Topics:
- Name: Creating virtual machine templates
File: cnv-creating-vm-template
File: virt-creating-vm-template
- Name: Editing a virtual machine template
File: cnv-editing-vm-template
File: virt-editing-vm-template
- Name: Enabling dedicated resources for a virtual machine template
File: cnv-dedicated-resources-vm-template
File: virt-dedicated-resources-vm-template
- Name: Deleting a virtual machine template
File: cnv-deleting-vm-template
#Virtual machine live migration
File: virt-deleting-vm-template
# Virtual machine live migration
- Name: Live migration
Dir: cnv_live_migration
Dir: live_migration
Topics:
- Name: Virtual machine live migration
File: cnv-live-migration
File: virt-live-migration
- Name: Live migration limits and timeouts
File: cnv-live-migration-limits
File: virt-live-migration-limits
- Name: Migrating a virtual machine instance to another node
File: cnv-migrate-vmi
File: virt-migrate-vmi
- Name: Monitoring live migration of a virtual machine instance
File: cnv-monitor-vmi-migration
File: virt-monitor-vmi-migration
- Name: Cancelling the live migration of a virtual machine instance
File: cnv-cancel-vmi-migration
File: virt-cancel-vmi-migration
- Name: Configuring virtual machine eviction strategy
File: cnv-configuring-vmi-eviction-strategy
#Node maintenance mode
File: virt-configuring-vmi-eviction-strategy
# Node maintenance mode
- Name: Node maintenance
Dir: cnv_node_maintenance
Dir: node_maintenance
Topics:
- Name: Manually refreshing TLS certificates
File: cnv-refresh-certificates
File: virt-refresh-certificates
- Name: Node maintenance mode
File: cnv-node-maintenance
File: virt-node-maintenance
- Name: Setting a node to maintenance mode
File: cnv-setting-node-maintenance
File: virt-setting-node-maintenance
- Name: Resuming a node from maintenance mode
File: cnv-resuming-node
#Node Networking
File: virt-resuming-node
# Node Networking
- Name: Node networking
Dir: cnv_node_network
Dir: node_network
Topics:
- Name: Observing node network state
File: cnv-observing-node-network-state
File: virt-observing-node-network-state
- Name: Updating node network configuration
File: cnv-updating-node-network-config
File: virt-updating-node-network-config
- Name: Troubleshooting node network configuration
File: cnv-troubleshooting-node-network
#Logging, events, and monitoring
File: virt-troubleshooting-node-network
# Logging, events, and monitoring
- Name: Logging, events, and monitoring
Dir: cnv_logging_events_monitoring
Dir: logging_events_monitoring
Topics:
- Name: Viewing logs
File: cnv-logs
File: virt-logs
- Name: Viewing events
File: cnv-events
File: virt-events
- Name: Viewing information about virtual machine workloads
File: cnv-viewing-information-about-vm-workloads
File: virt-viewing-information-about-vm-workloads
- Name: Monitoring virtual machine health
File: cnv-monitoring-vm-health
File: virt-monitoring-vm-health
- Name: Viewing cluster information
File: cnv-using-dashboard-to-get-cluster-info
File: virt-using-dashboard-to-get-cluster-info
- Name: OpenShift cluster monitoring, logging, and Telemetry
File: cnv-openshift-cluster-monitoring
- Name: Collecting container-native virtualization data for Red Hat Support
File: cnv-collecting-cnv-data
File: virt-openshift-cluster-monitoring
- Name: Collecting OpenShift virtualization data for Red Hat Support
File: virt-collecting-virt-data
---
# OpenShift Serverless
Name: Serverless applications

14
cnv/cnv-about-cnv.adoc
View File

@@ -1,14 +0,0 @@
[id="cnv-about-cnv"]
= About container-native virtualization
include::modules/cnv-document-attributes.adoc[]
:context: cnv-about-cnv
toc::[]
Learn about {CNVProductName}'s capabilities and support scope.
include::modules/cnv-what-you-can-do-with-cnv.adoc[leveloffset=+1]
== {CNVProductNameStart} support
:FeatureName: {CNVProductNameStart}
include::modules/technology-preview.adoc[leveloffset=+2]

20
cnv/cnv-using-the-cli-tools.adoc
View File

@@ -1,20 +0,0 @@
[id="cnv-using-the-cli-tools"]
= Using the CLI tools
include::modules/cnv-document-attributes.adoc[]
:context: using-the-cli-tools
toc::[]
The two primary CLI tools used for managing resources in the cluster are:
* The {CNVProductName} `virtctl` client
* The {product-title} `oc` client
.Prerequisites
* You must xref:../cnv/cnv_install/cnv-installing-virtctl.adoc#cnv-installing-virtctl[install the `virtctl` client].
include::modules/cnv-virtctl-commands.adoc[leveloffset=+1]
include::modules/cnv-openshift-client-commands.adoc[leveloffset=+1]
For more comprehensive information on `oc` client commands, see the
xref:../cli_reference/openshift_cli/developer-cli-commands.adoc#cli_reference[{product-title} CLI tools] documentation.

17
cnv/cnv_install/cnv-installing-virtctl.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-installing-virtctl"]
= Installing the `virtctl` client
include::modules/cnv-document-attributes.adoc[]
:context: cnv-installing-virtctl
toc::[]
The `virtctl` client is a command-line utility for managing {CNVProductName}
resources.
Install the client to your system by enabling the {CNVProductName} repository and
installing the `kubevirt-virtctl` package.
include::modules/cnv-enabling-cnv-repos.adoc[leveloffset=+1]
include::modules/cnv-installing-virtctl-client.adoc[leveloffset=+1]
See also:
xref:../../cnv/cnv-using-the-cli-tools.adoc#cnv-using-the-cli-tools[Using the CLI tools] for {CNVProductName}.

22
cnv/cnv_install/installing-container-native-virtualization.adoc
View File

@@ -1,22 +0,0 @@
[id="installing-container-native-virtualization"]
= Installing container-native virtualization
include::modules/cnv-document-attributes.adoc[]
:context: installing-container-native-virtualization
toc::[]
Install {CNVProductName} to add virtualization functionality to your {product-title}
cluster.
You can use the {product-title} {product-version}
xref:../../web_console/web-console.adoc#web-console-overview_web-console[web console]
to subscribe to and deploy the {CNVProductName} Operators.
.Prerequisites
* {product-title} {product-version}
:FeatureName: {CNVProductNameStart}
include::modules/technology-preview.adoc[leveloffset=+1]
include::modules/cnv-subscribing-to-the-catalog.adoc[leveloffset=+1]
include::modules/cnv-deploying-cnv.adoc[leveloffset=+1]

32
cnv/cnv_install/uninstalling-container-native-virtualization.adoc
View File

@@ -1,32 +0,0 @@
[id="uninstalling-container-native-virtualization"]
= Uninstalling container-native virtualization
include::modules/cnv-document-attributes.adoc[]
:context: uninstalling-container-native-virtualization
toc::[]
You can uninstall {CNVProductName} by using the {product-title}
xref:../../web_console/web-console.adoc#web-console-overview_web-console[web console].
.Prerequisites
* You must have {CNVProductName} {CNVVersion} installed.
* You must delete all xref:../../cnv/cnv_virtual_machines/cnv-delete-vms.adoc#cnv-delete-vm-web_cnv-delete-vms[virtual machines],
xref:../../cnv/cnv_virtual_machines/cnv-deleting-vmis.adoc#cnv-deleting-vmi_cnv-deleting-vmis[virtual machine instances],
and xref:../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-deleting-datavolumes.adoc#cnv-deleting-dvs_cnv-deleting-datavolumes[DataVolumes].
+
[IMPORTANT]
====
Attempting to uninstall {CNVProductName} without deleting these objects
results in failure.
====
include::modules/cnv-deleting-custom-resource.adoc[leveloffset=+1]
include::modules/cnv-deleting-catalog-subscription.adoc[leveloffset=+1]
[NOTE]
====
You can now delete the `openshift-cnv` namespace.
====
include::modules/deleting-a-namespace-using-the-web-console.adoc[leveloffset=+1]

14
cnv/cnv_live_migration/cnv-live-migration-limits.adoc
View File

@@ -1,14 +0,0 @@
[id="cnv-live-migration-limits"]
= Live migration limits and timeouts
include::modules/cnv-document-attributes.adoc[]
:context: cnv-live-migration-limits
toc::[]
Live migration limits and timeouts are applied so that migration processes do
not overwhelm the cluster. Configure these settings by editing the
`kubevirt-config` configuration file.
include::modules/cnv-configuring-live-migration-limits.adoc[leveloffset=+1]
include::modules/cnv-live-migration-limits-reftable.adoc[leveloffset=+1]

13
cnv/cnv_live_migration/cnv-live-migration.adoc
View File

@@ -1,13 +0,0 @@
[id="cnv-live-migration"]
= Virtual machine live migration
include::modules/cnv-document-attributes.adoc[]
:context: cnv-live-migration
toc::[]
include::modules/cnv-understanding-live-migration.adoc[leveloffset=+1]
.Additional resources:
* xref:../../cnv/cnv_live_migration/cnv-migrate-vmi.adoc#cnv-migrate-vmi[Migrating a virtual machine instance to another node]
* xref:../../cnv/cnv_node_maintenance/cnv-node-maintenance.adoc#cnv-node-maintenance[Node maintenance mode]
* xref:../../cnv/cnv_live_migration/cnv-live-migration-limits.adoc#cnv-live-migration-limits[Live migration limiting]

17
cnv/cnv_live_migration/cnv-migrate-vmi.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-migrate-vmi"]
= Migrating a virtual machine instance to another node
include::modules/cnv-document-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: cnv-migrate-vmi
toc::[]
Manually initiate a live migration of a virtual machine instance to another node using either the web console or the CLI.
include::modules/cnv-initiating-vm-migration-web.adoc[leveloffset=+1]
include::modules/cnv-initiating-vm-migration-cli.adoc[leveloffset=+1]
.Additional resources:
* xref:../../cnv/cnv_live_migration/cnv-monitor-vmi-migration.adoc#cnv-monitor-vmi-migration[Monitoring live migration of a virtual machine instance]
* xref:../../cnv/cnv_live_migration/cnv-cancel-vmi-migration.adoc#cnv-cancel-vmi-migration[Cancelling the live migration of a virtual machine instance]

11
cnv/cnv_live_migration/cnv-monitor-vmi-migration.adoc
View File

@@ -1,11 +0,0 @@
[id="cnv-monitor-vmi-migration"]
= Monitoring live migration of a virtual machine instance
include::modules/cnv-document-attributes.adoc[]
:context: cnv-monitor-vmi-migration
toc::[]
You can monitor the progress of a live migration of a virtual machine instance from either the web console or the CLI.
include::modules/cnv-monitoring-vm-migration-web.adoc[leveloffset=+1]
include::modules/cnv-monitoring-vm-migration-cli.adoc[leveloffset=+1]

17
cnv/cnv_logging_events_monitoring/cnv-events.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-events"]
= Viewing events
include::modules/cnv-document-attributes.adoc[]
:context: cnv-events
toc::[]
include::modules/cnv-understanding-events.adoc[leveloffset=+1]
See also:
xref:../../nodes/clusters/nodes-containers-events.adoc#nodes-containers-events[Viewing system event information in an {product-title} cluster].
include::modules/cnv-viewing-vm-events-web.adoc[leveloffset=+1]
include::modules/cnv-viewing-namespace-events-cli.adoc[leveloffset=+1]
include::modules/cnv-viewing-resource-events-cli.adoc[leveloffset=+1]

11
cnv/cnv_logging_events_monitoring/cnv-logs.adoc
View File

@@ -1,11 +0,0 @@
[id="cnv-logs"]
= Viewing virtual machine logs
include::modules/cnv-document-attributes.adoc[]
:context: cnv-logs
toc::[]
include::modules/cnv-understanding-logs.adoc[leveloffset=+1]
include::modules/cnv-viewing-virtual-machine-logs-cli.adoc[leveloffset=+1]
include::modules/cnv-viewing-virtual-machine-logs-web.adoc[leveloffset=+1]

13
cnv/cnv_logging_events_monitoring/cnv-monitoring-vm-health.adoc
View File

@@ -1,13 +0,0 @@
[id="cnv-monitoring-vm-health"]
= Monitoring virtual machine health
include::modules/cnv-document-attributes.adoc[]
:context: cnv-monitoring-vm-health
toc::[]
Use this procedure to create liveness and readiness probes
to monitor virtual machine health.
include::modules/cnv-about-liveness-readiness-probes.adoc[leveloffset=+1]
include::modules/cnv-define-http-liveness-probe.adoc[leveloffset=+1]
include::modules/cnv-define-tcp-liveness-probe.adoc[leveloffset=+1]
include::modules/cnv-define-readiness-probe.adoc[leveloffset=+1]

9
cnv/cnv_logging_events_monitoring/cnv-viewing-information-about-vm-workloads.adoc
View File

@@ -1,9 +0,0 @@
[id="cnv-viewing-information-about-vm-workloads"]
= Viewing information about virtual machine workloads
include::modules/cnv-document-attributes.adoc[]
:context: cnv-viewing-information-about-vm-workloads
toc::[]
You can view high-level information about your virtual machines by using the *Virtual Machines* dashboard in the {product-title} web console.
include::modules/cnv-about-the-vm-dashboard.adoc[leveloffset=+1]

12
cnv/cnv_node_maintenance/cnv-node-maintenance.adoc
View File

@@ -1,12 +0,0 @@
[id="cnv-node-maintenance"]
= Node maintenance mode
include::modules/cnv-document-attributes.adoc[]
:context: cnv-node-maintenance
toc::[]
include::modules/cnv-understanding-node-maintenance.adoc[leveloffset=+1]
.Additional resources:
* xref:../../cnv/cnv_live_migration/cnv-live-migration.adoc#cnv-live-migration[Virtual machine live migration]
* xref:../../cnv/cnv_live_migration/cnv-configuring-vmi-eviction-strategy.adoc#cnv-configuring-vmi-eviction-strategy[Configuring virtual machine eviction strategy]

13
cnv/cnv_node_maintenance/cnv-refresh-certificates.adoc
View File

@@ -1,13 +0,0 @@
[id="cnv-refresh-certificates"]
= Manually refreshing TLS certificates
include::modules/cnv-document-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: cnv-refresh-certificates
toc::[]
The TLS certificates for {CNVProductName} components are created at the time
of installation and are valid for one year. You must manually refresh
these certificates before they expire.
include::modules/cnv-refreshing-certificates.adoc[leveloffset=+1]

14
cnv/cnv_node_maintenance/cnv-resuming-node.adoc
View File

@@ -1,14 +0,0 @@
[id="cnv-resuming-node"]
= Resuming a node from maintenance mode
include::modules/cnv-document-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: cnv-resuming-node
toc::[]
Resuming a node brings it out of maintenance mode and schedulable again.
Resume a node from maintenance from either the web console or the CLI.
include::modules/cnv-resuming-node-maintenance-web.adoc[leveloffset=+1]
include::modules/cnv-resuming-node-maintenance-cli.adoc[leveloffset=+1]

18
cnv/cnv_node_maintenance/cnv-setting-node-maintenance.adoc
View File

@@ -1,18 +0,0 @@
[id="cnv-setting-node-maintenance"]
= Setting a node to maintenance mode
include::modules/cnv-document-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: cnv-setting-node-maintenance
toc::[]
include::modules/cnv-understanding-node-maintenance.adoc[leveloffset=+1]
Place a node into maintenance from either the web console or the CLI.
include::modules/cnv-setting-node-maintenance-web.adoc[leveloffset=+1]
include::modules/cnv-setting-node-maintenance-cli.adoc[leveloffset=+1]
.Additional resources:
* xref:../../cnv/cnv_node_maintenance/cnv-resuming-node.adoc#cnv-resuming-node[Resuming a node from maintenance mode]

14
cnv/cnv_node_network/cnv-observing-node-network-state.adoc
View File

@@ -1,14 +0,0 @@
[id="cnv-observing-node-network-state"]
= Observing node network state
include::modules/cnv-document-attributes.adoc[]
:context: cnv-observing-node-network-state
toc::[]
Node network state is the network configuration for all nodes in the cluster.
include::modules/cnv-about-nmstate.adoc[leveloffset=+1]
include::modules/cnv-viewing-network-state-of-node.adoc[leveloffset=+1]

25
cnv/cnv_node_network/cnv-updating-node-network-config.adoc
View File

@@ -1,25 +0,0 @@
[id="cnv-updating-node-network"]
= Updating node network configuration
include::modules/cnv-document-attributes.adoc[]
:context: cnv-updating-node-network-config
toc::[]
You can update the node network configuration, such as adding or removing interfaces
from nodes, by applying `NodeNetworkConfigurationPolicy` manifests to the cluster.
include::modules/cnv-about-nmstate.adoc[leveloffset=+1]
include::modules/cnv-creating-interface-on-nodes.adoc[leveloffset=+1]
include::modules/cnv-confirming-policy-updates-on-nodes.adoc[leveloffset=+1]
include::modules/cnv-removing-interface-from-nodes.adoc[leveloffset=+1]
include::modules/cnv-restoring-node-network-configuration.adoc[leveloffset=+1]
include::modules/cnv-example-bridge-nncp.adoc[leveloffset=+1]
include::modules/cnv-example-vlan-nncp.adoc[leveloffset=+1]
include::modules/cnv-example-bond-nncp.adoc[leveloffset=+1]

21
cnv/cnv_virtual_machines/cnv-controlling-vm-states.adoc
View File

@@ -1,21 +0,0 @@
[id="cnv-controlling-vm-states"]
= Controlling virtual machine states
include::modules/cnv-document-attributes.adoc[]
:context: cnv-controlling-vm-states
toc::[]
You can stop, start, restart, and unpause virtual machines from the web console.
[NOTE]
====
To control virtual machines from the command-line interface (CLI), use the
xref:../../cnv/cnv-using-the-cli-tools.html#cnv-virtctl-commands_using-the-cli-tools[`virtctl` client].
====
include::modules/cnv-starting-vm-web.adoc[leveloffset=+1]
include::modules/cnv-restarting-vm-web.adoc[leveloffset=+1]
include::modules/cnv-stopping-vm-web.adoc[leveloffset=+1]
include::modules/cnv-unpausing-vm-web.adoc[leveloffset=+1]

42
cnv/cnv_virtual_machines/cnv-create-vms.adoc
View File

@@ -1,42 +0,0 @@
[id="cnv-create-vms"]
= Creating virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: cnv-create-vms
toc::[]
Use one of these procedures to create a virtual machine:
* Running the virtual machine wizard
* Pasting a pre-configured YAML file with the virtual machine wizard
* Using the CLI
* xref:../../cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-vmware-vm.adoc#cnv-importing-vmware-vm[Importing a VMware virtual machine or template with the virtual machine wizard]
[WARNING]
====
Do not create virtual machines in `openshift-*` namespaces.
Instead, create a new namespace or use an existing namespace without the
`openshift` prefix.
====
include::modules/cnv-creating-vm-wizard-web.adoc[leveloffset=+1]
Refer to the virtual machine wizard fields section when running the web console wizard.
:virtualmachine:
include::modules/cnv-vm-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-cloud-init-fields-web.adoc[leveloffset=+2]
include::modules/cnv-cdrom-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-networking-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-storage-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-creating-vm-yaml-web.adoc[leveloffset=+1]
include::modules/cnv-creating-vm.adoc[leveloffset=+1]
:virtualmachine!:
include::modules/cnv-vm-storage-volume-types.adoc[leveloffset=+1]
See the
https://kubevirt.io/api-reference/master/definitions.html#_v1_virtualmachinespec[kubevirt
API Reference] for a definitive list of virtual machine settings.

11
cnv/cnv_virtual_machines/cnv-delete-vms.adoc
View File

@@ -1,11 +0,0 @@
[id="cnv-delete-vms"]
= Deleting virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: cnv-delete-vms
toc::[]
You can delete a virtual machine from the web console or by using the `oc`
command-line interface.
include::modules/cnv-delete-vm-web.adoc[leveloffset=+1]
include::modules/cnv-deleting-vms.adoc[leveloffset=+1]

16
cnv/cnv_virtual_machines/cnv-edit-vms.adoc
View File

@@ -1,16 +0,0 @@
[id="cnv-edit-vms"]
= Editing virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: cnv-edit-vms
toc::[]
You can update a virtual machine configuration using either the YAML editor in the
web console or the OpenShift client on the command line. You can also update
a subset of the parameters in the *Virtual Machine Overview* of the web console.
include::modules/cnv-editing-vm-web.adoc[leveloffset=+1]
include::modules/cnv-editing-vm-yaml-web.adoc[leveloffset=+1]
include::modules/cnv-editing-vm-cli.adoc[leveloffset=+1]
include::modules/cnv-add-disk-to-vm.adoc[leveloffset=+1]
include::modules/cnv-add-nic-to-vm.adoc[leveloffset=+1]
include::modules/cnv-edit-cdrom-vm.adoc[leveloffset=+1]

17
cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-existing-windows-vm.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-installing-virtio-drivers-on-existing-windows-vm"]
= Installing VirtIO driver on an existing Windows virtual machine
include::modules/cnv-document-attributes.adoc[]
:context: cnv-installing-virtio-drivers-on-existing-windows-vm
toc::[]
include::modules/cnv-understanding-virtio-drivers.adoc[leveloffset=+1]
See also: xref:../../cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-new-windows-vm.adoc#cnv-installing-virtio-drivers-on-new-windows-vm[Installing Virtio drivers on a new Windows virtual machine].
include::modules/cnv-supported-virtio-drivers.adoc[leveloffset=+1]
include::modules/cnv-adding-virtio-drivers-vm-yaml.adoc[leveloffset=+1]
include::modules/cnv-installing-virtio-drivers-existing-windows.adoc[leveloffset=+1]
include::modules/cnv-removing-virtio-disk-from-vm.adoc[leveloffset=+1]

23
cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-new-windows-vm.adoc
View File

@@ -1,23 +0,0 @@
[id="cnv-installing-virtio-drivers-on-new-windows-vm"]
= Installing VirtIO driver on a new Windows virtual machine
include::modules/cnv-document-attributes.adoc[]
:context: cnv-installing-virtio-drivers-on-new-windows-vm"
toc::[]
.Prerequisites
* Windows installation media accessible by the virtual machine, such as
xref:../../cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes.adoc#cnv-importing-vm-datavolume_cnv-importing-virtual-machine-images-datavolumes[importing an ISO into a data volume]
and attaching it to the virtual machine.
include::modules/cnv-understanding-virtio-drivers.adoc[leveloffset=+1]
See also: xref:../../cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-existing-windows-vm.adoc#cnv-installing-virtio-drivers-on-existing-windows-vm[Installing VirtIO driver on an existing Windows virtual machine].
include::modules/cnv-supported-virtio-drivers.adoc[leveloffset=+1]
include::modules/cnv-adding-virtio-drivers-vm-yaml.adoc[leveloffset=+1]
include::modules/cnv-installing-virtio-drivers-installing-windows.adoc[leveloffset=+1]
include::modules/cnv-removing-virtio-disk-from-vm.adoc[leveloffset=+1]

19
cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-automating-management-tasks.adoc
View File

@@ -1,19 +0,0 @@
[id="cnv-automating-management-tasks"]
= Automating management tasks
include::modules/cnv-document-attributes.adoc[]
:context: cnv-automating-management-tasks
toc::[]
You can automate {CNVProductName} management tasks by using Red Hat Ansible
Automation Platform. Learn the basics by using an Ansible Playbook to create a new
virtual machine.
include::modules/cnv-about-red-hat-ansible-automation.adoc[leveloffset=+1]
include::modules/cnv-automating-virtual-machine-creation-with-ansible.adoc[leveloffset=+1]
To verify that the virtual machine was created, try to
xref:../../../cnv/cnv_virtual_machines/cnv-accessing-vm-consoles.adoc#cnv-accessing-vm-consoles[access the VM console].
include::modules/cnv-example-ansible-playbook-creating-vms.adoc[leveloffset=+1]

23
cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-configuring-pxe-booting.adoc
View File

@@ -1,23 +0,0 @@
[id="configuring-pxe-booting"]
= Configuring PXE booting for virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: pxe-booting
toc::[]
PXE booting, or network booting, is available in {CNVProductName}.
Network booting allows a computer to boot and load an
operating system or other program without requiring a locally attached
storage device. For example, you can use it to choose your desired OS
image from a PXE server when deploying a new host.
.Prerequisites
* A Linux bridge must be xref:../../../cnv/cnv_virtual_machines/cnv_vm_networking/cnv-attaching-vm-multiple-networks.adoc#attaching-to-multiple-networks[connected].
* The PXE server must be connected to the same VLAN as the bridge.
include::modules/cnv-networking-glossary.adoc[leveloffset=+1]
include::modules/cnv-pxe-booting-with-mac-address.adoc[leveloffset=+1]
include::modules/cnv-template-vmi-pxe-config.adoc[leveloffset=+1]

17
cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-managing-guest-memory.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-managing-guest-memory"]
= Managing guest memory
include::modules/cnv-document-attributes.adoc[]
:context: cnv-managing-guest-memory
toc::[]
If you want to adjust guest memory settings to suit a specific use case, you can
do so by editing the guest's YAML configuration file. {CNVProductNameStart} allows you
to configure guest memory overcommitment and disable guest memory overhead
accounting.
Both of these procedures carry some degree of risk. Proceed only if you are
an experienced administrator.
include::modules/cnv-configuring-guest-memory-overcommitment.adoc[leveloffset=+1]
include::modules/cnv-disabling-guest-memory-overhead-accounting.adoc[leveloffset=+1]

31
cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume-block.adoc
View File

@@ -1,31 +0,0 @@
[id="cnv-cloning-vm-disk-into-new-datavolume-block"]
= Cloning a virtual machine disk into a new block storage DataVolume
include::modules/cnv-document-attributes.adoc[]
:context: cnv-cloning-vm-disk-into-new-datavolume-block
toc::[]
You can clone the PersistentVolumeClaim (PVC) of a virtual machine disk into
a new block DataVolume by referencing the source PVC in your DataVolume configuration
file.
.Prerequisites
* If you require scratch space according to the
xref:#cnv-cdi-supported-operations-matrix_cnv-cloning-vm-disk-into-new-datavolume-block[CDI supported operations matrix], you must first
xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully.
* Users need xref:../../../cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-enabling-user-permissions-to-clone-datavolumes.adoc#cnv-enabling-user-permissions-to-clone-datavolumes[additional permissions] to clone the PVC of a virtual machine disk into another namespace.
:blockstorage:
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-about-block-pvs.adoc[leveloffset=+1]
include::modules/cnv-creating-local-block-pv.adoc[leveloffset=+1]
include::modules/cnv-cloning-pvc-of-vm-disk-into-new-datavolume.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]
:blockstorage!:

26
cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume.adoc
View File

@@ -1,26 +0,0 @@
[id="cnv-cloning-vm-disk-into-new-datavolume"]
= Cloning a virtual machine disk into a new DataVolume
include::modules/cnv-document-attributes.adoc[]
:context: cnv-cloning-vm-disk-into-new-datavolume
toc::[]
You can clone the PersistentVolumeClaim (PVC) of a virtual machine disk into
a new DataVolume by referencing the source PVC in your DataVolume configuration
file.
.Prerequisites
* You may need to xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully. The
xref:#cnv-cdi-supported-operations-matrix_cnv-cloning-vm-disk-into-new-datavolume[CDI supported operations matrix]
shows the conditions that require scratch space.
* Users need xref:../../../cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-enabling-user-permissions-to-clone-datavolumes.adoc#cnv-enabling-user-permissions-to-clone-datavolumes[additional permissions] to clone the PVC of a virtual machine disk into another namespace.
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-cloning-pvc-of-vm-disk-into-new-datavolume.adoc[leveloffset=+1]
include::modules/cnv-template-datavolume-clone.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]

27
cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-using-datavolumetemplate.adoc
View File

@@ -1,27 +0,0 @@
[id="cnv-cloning-vm-using-datavolumetemplate"]
= Cloning a virtual machine by using a DataVolumeTemplate
include::modules/cnv-document-attributes.adoc[]
:context: cnv-cloning-vm-using-datavolumetemplate
toc::[]
You can create a new virtual machine by cloning the PersistentVolumeClaim (PVC) of
an existing VM. By including a `dataVolumeTemplate` in your virtual machine
configuration file, you create a new DataVolume from the original PVC.
.Prerequisites
* You may need to xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully. The
xref:#cnv-cdi-supported-operations-matrix_cnv-cloning-vm-using-datavolumetemplate[CDI supported operations matrix]
shows the conditions that require scratch space.
* Users need xref:../../../cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-enabling-user-permissions-to-clone-datavolumes.adoc#cnv-enabling-user-permissions-to-clone-datavolumes[additional permissions] to clone the PVC of a virtual machine disk into another namespace.
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-creating-new-vm-from-cloned-pvc-using-datavolumetemplate.adoc[leveloffset=+1]
include::modules/cnv-template-datavolume-vm.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]

39
cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes-block.adoc
View File

@@ -1,39 +0,0 @@
[id="cnv-importing-virtual-machine-images-datavolumes-block"]
= Importing virtual machine images to block storage with DataVolumes
include::modules/cnv-document-attributes.adoc[]
:context: cnv-importing-virtual-machine-images-datavolumes-block
toc::[]
You can import an existing virtual machine image into your {product-title}
cluster. {CNVProductNameStart} uses DataVolumes to automate the import of data and the
creation of an underlying PersistentVolumeClaim (PVC).
[CAUTION]
====
When you import a disk image into a PVC, the disk image is
expanded to use the full storage capacity that is requested in the PVC. To use
this space, the disk partitions and file system(s) in the virtual machine
might need to be expanded.
The resizing procedure varies based on the operating system that is installed on the virtual machine.
Refer to the operating system documentation for details.
====
.Prerequisites
* If you require scratch space according to the
xref:#cnv-cdi-supported-operations-matrix_cnv-importing-virtual-machine-images-datavolumes-block[CDI supported operations matrix], you must first
xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully.
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-about-block-pvs.adoc[leveloffset=+1]
include::modules/cnv-creating-local-block-pv.adoc[leveloffset=+1]
include::modules/cnv-importing-vm-to-block-pv.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]

39
cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes.adoc
View File

@@ -1,39 +0,0 @@
[id="cnv-importing-virtual-machine-images-datavolumes"]
= Importing virtual machine images with DataVolumes
include::modules/cnv-document-attributes.adoc[]
:context: cnv-importing-virtual-machine-images-datavolumes
toc::[]
You can import an existing virtual machine image into your {product-title}
cluster. {CNVProductNameStart} uses DataVolumes to automate the import of data and the
creation of an underlying PersistentVolumeClaim (PVC).
[CAUTION]
====
When you import a disk image into a PVC, the disk image is
expanded to use the full storage capacity that is requested in the PVC. To use
this space, the disk partitions and file system(s) in the virtual machine
might need to be expanded.
The resizing procedure varies based on the operating system installed on the VM.
Refer to the operating system documentation for details.
====
.Prerequisites
* If the endpoint requires a TLS certificate, the certificate must be
xref:../../../cnv/cnv_virtual_machines/cnv_importing_vms/cnv-tls-certificates-for-dv-imports.adoc#cnv-adding-tls-certificates-for-authenticating-dv-imports_cnv-tls-certificates-for-dv-imports[included in a ConfigMap]
in the same namespace as the DataVolume and referenced in the DataVolume configuration.
* You may need to xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully.
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-importing-vm-datavolume.adoc[leveloffset=+1]
include::modules/cnv-template-datavolume-vm.adoc[leveloffset=+1]
include::modules/cnv-template-datavolume-import.adoc[leveloffset=+1]

34
cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-vmware-vm.adoc
View File

@@ -1,34 +0,0 @@
[id="cnv-importing-vmware-vm"]
= Importing a VMware virtual machine or template
include::modules/cnv-document-attributes.adoc[]
:context: cnv-importing-vmware-vm
toc::[]
You can import a single VMware virtual machine or template into your {product-title} cluster.
If you import a VMware template, the wizard creates a virtual machine based on the template.
:FeatureName: Importing a VMware virtual machine or template
include::modules/technology-preview.adoc[leveloffset=+1]
:!FeatureName:
.Prerequisites
* If you use NFS-backed storage for the 2 GB disk that is attached to the Conversion Pod, you must link:https://access.redhat.com/solutions/4982751[configure a hostPath volume].
include::modules/cnv-creating-vddk-image.adoc[leveloffset=+1]
include::modules/cnv-importing-vmware-vm.adoc[leveloffset=+1]
Refer to the xref:cnv-importing-vmware-vm-wizard-fields_cnv-importing-vmware-vm[virtual machine wizard fields] section for more information on the wizard fields.
include::modules/cnv-updating-imported-vm-network-name.adoc[leveloffset=+1]
include::modules/cnv-troubleshooting-vmware-vm-import.adoc[leveloffset=+1]
[id="cnv-importing-vmware-vm-wizard-fields_{context}"]
== Virtual machine wizard fields
:virtualmachine:
include::modules/cnv-vm-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-cloud-init-fields-web.adoc[leveloffset=+2]
include::modules/cnv-networking-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-storage-wizard-fields-web.adoc[leveloffset=+2]
:virtualmachine!:

11
cnv/cnv_virtual_machines/cnv_importing_vms/cnv-tls-certificates-for-dv-imports.adoc
View File

@@ -1,11 +0,0 @@
[id="cnv-tls-certificates-for-dv-imports"]
= TLS certificates for DataVolume imports
include::modules/cnv-document-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: cnv-tls-certificates-for-dv-imports
toc::[]
include::modules/cnv-adding-tls-certificates-for-authenticating-dv-imports.adoc[leveloffset=+1]
include::modules/cnv-example-configmap-tls-certificate.adoc[leveloffset=+1]

17
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-configuring-local-storage-for-vms.adoc
View File

@@ -1,17 +0,0 @@
[id="cnv-configuring-local-storage-for-vms"]
= Configuring local storage for virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: cnv-configuring-local-storage-for-vms
toc::[]
You can configure local storage for your virtual machines by using the hostpath
provisioner feature.
include::modules/cnv-about-hostpath-provisioner.adoc[leveloffset=+1]
include::modules/cnv-configuring-selinux-hpp-on-rhcos8.adoc[leveloffset=+1]
include::modules/cnv-using-hostpath-provisioner.adoc[leveloffset=+1]
include::modules/cnv-creating-storage-class.adoc[leveloffset=+1]

15
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-deleting-datavolumes.adoc
View File

@@ -1,15 +0,0 @@
[id="cnv-deleting-datavolumes"]
= Deleting DataVolumes
include::modules/cnv-document-attributes.adoc[]
:context: cnv-deleting-datavolumes
toc::[]
You can manually delete a DataVolume by using the `oc` command-line interface. +
[NOTE]
====
When you delete a virtual machine, the DataVolume it uses is automatically deleted.
====
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-listing-dvs.adoc[leveloffset=+1]
include::modules/cnv-deleting-dvs.adoc[leveloffset=+1]

14
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-expanding-virtual-storage-with-blank-disk-images.adoc
View File

@@ -1,14 +0,0 @@
[id="cnv-expanding-virtual-storage-with-blank-disk-images"]
= Expanding virtual storage by adding blank disk images
include::modules/cnv-document-attributes.adoc[]
:context: cnv-expanding-virtual-storage-with-blank-disk-images
toc::[]
You can increase your storage capacity or create new data partitions by adding
blank disk images to {CNVProductName}.
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-creating-blank-disk-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-template-blank-disk-datavolume.adoc[leveloffset=+1]

22
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-moving-local-vm-disk-to-different-node.adoc
View File

@@ -1,22 +0,0 @@
[id="cnv-moving-local-vm-disk-to-different-node"]
= Moving a local virtual machine disk to a different node
include::modules/cnv-document-attributes.adoc[]
:context: cnv-moving-local-vm-disk-to-different-node
toc::[]
Virtual machines that use local volume storage can be moved so that they run on a specific node.
You might want to move the virtual machine to a specific node for the following reasons:
* The current node has limitations to the local storage configuration.
* The new node is better optimized for the workload of that virtual machine.
To move a virtual machine that uses local storage, you must clone the underlying volume by using a DataVolume. After the cloning operation is complete, you can xref:../../../cnv/cnv_virtual_machines/cnv-edit-vms.adoc#cnv-edit-vms[edit the virtual machine configuration] so that it uses the new DataVolume, or xref:../../../cnv/cnv_virtual_machines/cnv-edit-vms.adoc#cnv-vm-add-disk_cnv-edit-vms[add the new DataVolume to another virtual machine].
[NOTE]
====
Users without the `cluster-admin` role require xref:../../../cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-enabling-user-permissions-to-clone-datavolumes.adoc#cnv-enabling-user-permissions-to-clone-datavolumes[additional user permissions] in order to clone volumes across namespaces.
====
include::modules/cnv-cloning-local-volume-to-another-node.adoc[leveloffset=+1]

19
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc
View File

@@ -1,19 +0,0 @@
[id="cnv-preparing-cdi-scratch-space"]
= Preparing CDI scratch space
include::modules/cnv-document-attributes.adoc[]
:context: cnv-preparing-cdi-scratch-space
toc::[]
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-understanding-scratch-space.adoc[leveloffset=+1]
include::modules/cnv-operations-requiring-scratch-space.adoc[leveloffset=+1]
include::modules/cnv-defining-storageclass-in-cdi-configuration.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]
.Additional resources
* See the xref:../../../storage/dynamic-provisioning.adoc#about_dynamic-provisioning[Dynamic provisioning] section for more information on StorageClasses and how these are defined in the cluster.

16
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-storage-defaults-for-datavolumes.adoc
View File

@@ -1,16 +0,0 @@
[id="cnv-storage-defaults-for-datavolumes"]
= Storage defaults for DataVolumes
include::modules/cnv-document-attributes.adoc[]
:context: cnv-storage-defaults-for-datavolumes
toc::[]
The `kubevirt-storage-class-defaults` ConfigMap provides _access mode_ and _volume mode_ defaults for DataVolumes. You can edit or add storage class defaults to the ConfigMap in order to create DataVolumes in the web console that better match the underlying storage.
include::modules/cnv-about-storage-setting-for-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-editing-kubevirtstorageclassdefaults-web.adoc[leveloffset=+1]
include::modules/cnv-editing-kubevirtstorageclassdefaults-cli.adoc[leveloffset=+1]
include::modules/cnv-example-kubevirtstorageclassdefaults.adoc[leveloffset=+1]

37
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-block.adoc
View File

@@ -1,37 +0,0 @@
[id="cnv-uploading-local-disk-images-block"]
= Uploading a local disk image to a block storage DataVolume
include::modules/cnv-document-attributes.adoc[]
:context: cnv-uploading-local-disk-images-block
toc::[]
You can upload a local disk image into a block DataVolume by using the
`virtctl` command-line utility.
In this workflow, you create a local block device to use as a PersistentVolume,
associate this block volume with an `upload` DataVolume, and use `virtctl`
to upload the local disk image into the DataVolume.
.Prerequisites
* xref:../../../cnv/cnv_install/cnv-installing-virtctl.adoc#cnv-installing-virtctl[Install]
the `kubevirt-virtctl` package.
* If you require scratch space according to the
xref:#cnv-cdi-supported-operations-matrix_cnv-uploading-local-disk-images-block[CDI supported operations matrix], you must first
xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully.
:blockstorage:
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-about-block-pvs.adoc[leveloffset=+1]
include::modules/cnv-creating-local-block-pv.adoc[leveloffset=+1]
include::modules/cnv-creating-an-upload-dv.adoc[leveloffset=+1]
include::modules/cnv-uploading-local-disk-image-dv.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]
:blockstorage!:

26
cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-virtctl.adoc
View File

@@ -1,26 +0,0 @@
[id="cnv-uploading-local-disk-images-virtctl"]
= Uploading local disk images by using the virtctl tool
include::modules/cnv-document-attributes.adoc[]
:context: cnv-uploading-local-disk-images-virtctl
toc::[]
You can upload a locally stored disk image to a new or existing DataVolume by using the
`virtctl` command-line utility.
.Prerequisites
* xref:../../../cnv/cnv_install/cnv-installing-virtctl.adoc#cnv-installing-virtctl[Install]
the `kubevirt-virtctl` package.
* If you require scratch space according to the
xref:#cnv-cdi-supported-operations-matrix_cnv-uploading-local-disk-images-virtctl[CDI supported operations matrix], you must first
xref:../../../cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc#cnv-defining-storageclass-in-cdi-configuration_cnv-preparing-cdi-scratch-space[define a StorageClass or prepare CDI scratch space]
for this operation to complete successfully.
include::modules/cnv-about-datavolumes.adoc[leveloffset=+1]
include::modules/cnv-creating-an-upload-dv.adoc[leveloffset=+1]
include::modules/cnv-uploading-local-disk-image-dv.adoc[leveloffset=+1]
include::modules/cnv-cdi-supported-operations-matrix.adoc[leveloffset=+1]

32
cnv/cnv_virtual_machines/cnv_vm_networking/cnv-using-the-default-pod-network-with-cnv.adoc
View File

@@ -1,32 +0,0 @@
[id="cnv-using-the-default-pod-network-with-cnv"]
= Using the default Pod network for virtual machines
include::modules/cnv-document-attributes.adoc[]
:context: cnv-using-the-default-pod-network-with-cnv
toc::[]
You can use the default Pod network with {CNVProductName}. To do so,
you must use the `masquerade` binding method. It is the only recommended
binding method for use with the default Pod network. Do not use
`masquerade` mode with non-default networks.
[NOTE]
====
For secondary networks, use the `bridge` binding method.
====
include::modules/cnv-configuring-masquerade-mode-cli.adoc[leveloffset=+1]
[id="cnv-selecting-binding-method"]
== Selecting binding method
If you create a virtual machine from the {CNVProductName}
xref:../../../cnv/cnv_virtual_machines/cnv-create-vms.adoc#cnv-create-vms[web console wizard],
select the required binding method from the *Networking* screen.
include::modules/cnv-networking-wizard-fields-web.adoc[leveloffset=+2]
== Virtual machine configuration examples for the default network
include::modules/cnv-template-vm-config.adoc[leveloffset=+2]
include::modules/cnv-template-windows-vmi.adoc[leveloffset=+2]

24
cnv/cnv_vm_templates/cnv-creating-vm-template.adoc
View File

@@ -1,24 +0,0 @@
[id="cnv-creating-vm-template"]
= Creating virtual machine templates
include::modules/cnv-document-attributes.adoc[]
:context: cnv-creating-vm-template
toc::[]
Using Virtual machines templates is an easy way to create multiple virtual machines
with similar configuration. After a template is created, reference the template
when creating virtual machines.
include::modules/cnv-creating-template-wizard-web.adoc[leveloffset=+1]
[id="cnv-template-wizard-fields"]
== Virtual machine template interactive wizard fields
The following tables describe the fields for the *Basic Settings*, *Networking*,
and *Storage* panes in the *Create Virtual Machine Template* interactive wizard.
:vmtemplate:
include::modules/cnv-vm-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-cloud-init-fields-web.adoc[leveloffset=+2]
include::modules/cnv-networking-wizard-fields-web.adoc[leveloffset=+2]
include::modules/cnv-storage-wizard-fields-web.adoc[leveloffset=+2]
:vmtemplate!:

11
cnv/cnv_vm_templates/cnv-deleting-vm-template.adoc
View File

@@ -1,11 +0,0 @@
[id="cnv-deleting-vm-template"]
= Deleting a virtual machine template
include::modules/cnv-document-attributes.adoc[]
:context: cnv-deleting-vm-template
toc::[]
You can delete a virtual machine template in the web console.
include::modules/cnv-deleting-template-web.adoc[leveloffset=+1]

15
cnv/cnv_vm_templates/cnv-editing-vm-template.adoc
View File

@@ -1,15 +0,0 @@
[id="cnv-editing-vm-template"]
= Editing virtual machine templates
include::modules/cnv-document-attributes.adoc[]
:context: cnv-editing-vm-template
toc::[]
You can update a virtual machine template in the web console, either by editing
the full configuration in the YAML editor or by editing a subset of the
parameters in the *Virtual Machine Template Overview* screen.
include::modules/cnv-editing-vm-web.adoc[leveloffset=+1]
include::modules/cnv-editing-template-yaml-web.adoc[leveloffset=+1]
include::modules/cnv-add-disk-to-vm.adoc[leveloffset=+1]
include::modules/cnv-add-nic-to-vm.adoc[leveloffset=+1]
include::modules/cnv-edit-cdrom-vm.adoc[leveloffset=+1]

1
cnv/cnv_vm_templates/images
View File

@@ -1 +0,0 @@
../../images

1
cnv/cnv_vm_templates/modules
View File

@@ -1 +0,0 @@
../../modules/

21
cnv/upgrading-container-native-virtualization.adoc
View File

@@ -1,21 +0,0 @@
[id="upgrading-container-native-virtualization"]
= Upgrading container-native virtualization
include::modules/cnv-document-attributes.adoc[]
:context: upgrading-container-native-virtualization
toc::[]
You can manually upgrade to the next minor version of {CNVProductName} and
monitor the status of an update by using the web console.
:FeatureName: {CNVProductNameStart}
include::modules/technology-preview.adoc[leveloffset=+1]
include::modules/cnv-about-upgrading-cnv.adoc[leveloffset=+1]
include::modules/cnv-upgrading-cnv.adoc[leveloffset=+1]
include::modules/cnv-monitoring-upgrade-status.adoc[leveloffset=+1]
.Additional information
* xref:../operators/understanding_olm/olm-understanding-olm.adoc#olm-csv_olm-understanding-olm[ClusterServiceVersions (CSVs)]

9
contributing_to_docs/doc_guidelines.adoc
View File

@@ -79,6 +79,15 @@ important terms that may cause confusion. For example, the
`managing_authorization_policies.adoc` file name would be appropriate for an
assembly titled "Managing Authorization Policies".
== Directory names
If you create a directory with a multiple-word name, separate each word with an
underscore, for example `backup_and_restore`. Do not create a top-level directory
in the repository without checking with the docs team. In the main OpenShift
docs, you can create one level of subdirectories. In the docs for features that
are designed to be used with OpenShift, such as Service Mesh and OpenShift virtualization,
you can create two levels of subdirectories.
== Assembly/Module titles and section headings
Use sentence case in all titles and section headings. See http://www.titlecase.com/ or

2
modules/about-must-gather.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-collecting-cnv-data.adoc
// * virt/logging_events_monitoring/virt-collecting-virt-data.adoc
// * support/gathering-cluster-data.adoc
// * serverless/serverless-support.adoc
// * service_mesh/service_mesh_support/ossm-collecting-ossm-data.adoc

12
modules/cluster-logging-about-components.adoc
View File

@@ -2,8 +2,8 @@
//
// * logging/cluster-logging.adoc
ifeval::["{context}" == "cnv-openshift-cluster-monitoring"]
:cnv-logging:
ifeval::["{context}" == "virt-openshift-cluster-monitoring"]
:virt-logging:
endif::[]
[id="cluster-logging-about-components_{context}"]
@@ -26,10 +26,10 @@ There are currently 5 different types of cluster logging components:
* curation - This is the component that trims logs by age. The current implementation is Curator.
* event routing - This is the component forwards {product-title} events to cluster logging. The current implementation is Event Router.
ifndef::cnv-logging[]
ifndef::virt-logging[]
In this document, we may refer to logStore or Elasticsearch, visualization or Kibana, curation or Curator, collection or Fluentd, interchangeably, except where noted.
endif::cnv-logging[]
endif::virt-logging[]
ifeval::["{context}" == "cnv-openshift-cluster-monitoring"]
:!cnv-logging:
ifeval::["{context}" == "virt-openshift-cluster-monitoring"]
:!virt-logging:
endif::[]

2
modules/cluster-logging-about.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-openshift-cluster-monitoring.adoc
// * virt/logging_events_monitoring/virt-openshift-cluster-monitoring.adoc
// * logging/cluster-logging.adoc
// * serverless/knative_serving/cluster-logging-serverless.adoc

20
modules/cnv-about-collecting-cnv-data.adoc
View File

@@ -1,20 +0,0 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-collecting-cnv-data.adoc
[id="cnv-about-collecting-cnv-data_{context}"]
= About collecting container-native virtualization data
You can use the `oc adm must-gather` CLI command to collect information about your
cluster, including features and objects associated with {CNVProductName}:
* The Hyperconverged Cluster Operator namespaces (and child objects)
* All namespaces (and their child objects) that belong to any {CNVProductName}
resources
* All {CNVProductName} Custom Resource Definitions (CRDs)
* All namespaces that contain virtual machines
* All virtual machine definitions
To collect {CNVProductName} data with `must-gather`, you must specify the
{CNVProductName} image:
`--image=registry.redhat.io/container-native-virtualization/cnv-must-gather-rhel8`.

21
modules/cnv-about-datavolumes.adoc
View File

@@ -1,21 +0,0 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-expanding-virtual-storage-with-blank-disk-images.adoc
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-block.adoc
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-using-datavolumetemplate.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-enabling-user-permissions-to-clone-datavolumes.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume-block.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes-block.adoc
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-deleting-datavolumes.adoc
[id="cnv-about-datavolumes_{context}"]
= About DataVolumes
`DataVolume` objects are custom resources that are provided by the Containerized
Data Importer (CDI) project. DataVolumes orchestrate import, clone, and upload
operations that are associated with an underlying PersistentVolumeClaim (PVC).
DataVolumes are integrated with KubeVirt, and they prevent a virtual machine
from being started before the PVC has been prepared.

2
modules/cnv-accessing-vmi-web.adoc
View File

@@ -1,7 +1,7 @@
// Module included in the following assemblies:
//
[id="cnv-accessing-vmi-web_{context}"]
[id="virt-accessing-vmi-web_{context}"]
= Connecting to a virtual machine with the web console
You can connect to a virtual machine by using the web console.

21
modules/cnv-deleting-catalog-subscription.adoc
View File

@@ -1,21 +0,0 @@
// Module included in the following assemblies:
//
// * cnv/cnv_install/uninstalling-container-native-virtualization.adoc
[id="cnv-deleting-catalog-subscription_{context}"]
= Deleting the {CNVProductNameStart} catalog subscription
To finish uninstalling {CNVProductName}, delete the
*{CNVProductNameStart}* catalog subscription.
.Prerequisites
* An active subscription to the *{CNVProductNameStart}* catalog
.Procedure
. Navigate to the *Operators* -> *OperatorHub* page.
. Search for *{CNVProductNameStart}* and then select it.
. Click *Uninstall*.

26
modules/cnv-enabling-cnv-repos.adoc
View File

@@ -1,26 +0,0 @@
// Module included in the following assemblies:
//
// cnv_install/cnv-installing-virtctl.adoc
[id="cnv-enabling-cnv-repos_{context}"]
= Enabling container-native virtualization repositories
Red Hat offers {CNVProductName} repositories for both Red Hat Enterprise Linux 8
and Red Hat Enterprise Linux 7:
* Red Hat Enterprise Linux 8 repository: `cnv-2.3-for-rhel-8-x86_64-rpms`
* Red Hat Enterprise Linux 7 repository: `rhel-7-server-cnv-2.3-rpms`
The process for enabling the repository in `subscription-manager` is the same
in both platforms.
.Procedure
* Use `subscription manager` to enable the appropriate {CNVProductName} repository for
your system:
+
----
# subscription-manager repos --enable <repository>
----

2
modules/deleting-a-namespace-using-the-web-console.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * cnv/cnv_install/uninstalling-container-native-virtualization.adoc
// * virt/install/uninstalling-virt.adoc
[id="deleting-a-namespace-using-the-web-console_{context}"]
= Deleting a namespace using the web console

10
modules/gathering-data-specific-features.adoc
View File

@@ -1,8 +1,10 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-collecting-cnv-data.adoc
// * virt/logging_events_monitoring/virt-collecting-virt-data.adoc
// Dependency: modules/cnv-document-attributes.adoc
//This file contains UI elements and/or package names that need to be updated.
// Dependency: modules/virt-document-attributes.adoc
[id="gathering-data-specific-features_{context}"]
= Gathering data about specific features
@@ -23,7 +25,7 @@ more than one feature by running a single command.
. Run the `oc adm must-gather` command with one or more `--image` or `--image-stream`
arguments. For example, the following command gathers both the default cluster
data and information specific to {CNVProductName}:
data and information specific to {VirtProductName}:
+
----
$ oc adm must-gather \
@@ -31,7 +33,7 @@ $ oc adm must-gather \
--image=registry.redhat.io/container-native-virtualization/cnv-must-gather-rhel8 <2>
----
<1> Default {product-title} must-gather image
<2> {CNVProductNameStart} must-gather image
<2> {VirtProductName} must-gather image
. Create a compressed file from the `must-gather` directory that was just created
in your working directory. For example, on a computer that uses a Linux

2
modules/monitoring-about-cluster-monitoring.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-openshift-cluster-monitoring.adoc
// * virt/logging_events_monitoring/virt-openshift-cluster-monitoring.adoc
// * monitoring/cluster_monitoring/about-cluster-monitoring.adoc
// This module uses a conditionalized title so that the module

2
modules/support.adoc
View File

@@ -27,7 +27,7 @@ When submitting a support case, it is recommended to provide the following infor
endif::[]
* Access other product documentation.
// TODO: verify that these settings apply for Service Mesh and CNV, etc.
// TODO: verify that these settings apply for Service Mesh and OpenShift virtualization, etc.
If you have a suggestion for improving this documentation or have found an
error, please submit a link:http://bugzilla.redhat.com[Bugzilla report] against the
*OpenShift Container Platform* product for the *Documentation* component. Please

2
modules/telemetry-about-telemetry.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-openshift-cluster-monitoring.adoc
// * virt/logging_events_monitoring/virt-openshift-cluster-monitoring.adoc
// * support/remote_health_monitoring/about-remote-health-monitoring.adoc
[id="telemetry-about-telemetry_{context}"]

14
modules/telemetry-what-information-is-collected.adoc
View File

@@ -1,10 +1,10 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-openshift-cluster-monitoring.adoc
// * virt/logging_events_monitoring/virt-openshift-cluster-monitoring.adoc
// * support/remote_health_monitoring/about-remote-health-monitoring.adoc
ifeval::["{context}" == "cnv-openshift-cluster-monitoring"]
:cnv-cluster:
ifeval::["{context}" == "virt-openshift-cluster-monitoring"]
:virt-cluster:
endif::[]
[id="what-information-is-collected_{context}"]
@@ -21,9 +21,9 @@ Primary information collected by Telemetry includes:
* The number of members in the etcd cluster and number of objects currently stored in the etcd cluster
* The number of CPU cores and RAM used per machine type - infra or master
* The number of CPU cores and RAM used per cluster
ifdef::cnv-cluster[]
ifdef::virt-cluster[]
* The number of running virtual machine instances in the cluster
endif::cnv-cluster[]
endif::virt-cluster[]
* Use of {product-title} framework components per cluster
* The version of the {product-title} cluster
* Health, condition, and status for any {product-title} framework component that is installed on the cluster, for example Cluster Version Operator, Cluster Monitoring, Image Registry, and Elasticsearch for Logging
@@ -32,7 +32,7 @@ endif::cnv-cluster[]
Telemetry does not collect identifying information such as user names, passwords, or the names or addresses of user resources.
ifeval::["{context}" == "cnv-openshift-cluster-monitoring"]
:!cnv-cluster:
ifeval::["{context}" == "virt-openshift-cluster-monitoring"]
:!virt-cluster:
endif::[]

8
modules/cnv-about-block-pvs.adoc → modules/virt-about-block-pvs.adoc
View File

@@ -1,10 +1,10 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-block.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume-block.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes-block.adoc
// * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume-block.adoc
// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes-block.adoc
[id="cnv-about-block-pvs_{context}"]
[id="virt-about-block-pvs_{context}"]
= About block PersistentVolumes
A block PersistentVolume (PV) is a PV that is backed by a raw block device. These volumes

22
modules/virt-about-collecting-virt-data.adoc Normal file
View File

@@ -0,0 +1,22 @@
// Module included in the following assemblies:
//
// * virt/logging_events_monitoring/virt-collecting-virt-data.adoc
//This file contains UI elements and/or package names that need to be updated.
[id="virt-about-collecting-virt-data_{context}"]
= About collecting {VirtProductName} data
You can use the `oc adm must-gather` CLI command to collect information about your
cluster, including features and objects associated with {VirtProductName}:
* The Hyperconverged Cluster Operator namespaces (and child objects)
* All namespaces (and their child objects) that belong to any {VirtProductName}
resources
* All {VirtProductName} Custom Resource Definitions (CRDs)
* All namespaces that contain virtual machines
* All virtual machine definitions
To collect {VirtProductName} data with `must-gather`, you must specify the
{VirtProductName} image:
`--image=registry.redhat.io/container-native-virtualization/cnv-must-gather-rhel8`.

20
modules/virt-about-datavolumes.adoc Normal file
View File

@@ -0,0 +1,20 @@
// Module included in the following assemblies:
//
// * virt/virtual_machines/virtual_disks/virt-expanding-virtual-storage-with-blank-disk-images.adoc
// * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
// * virt/virtual_machines/virtual_disks/virt-preparing-cdi-scratch-space.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-using-datavolumetemplate.adoc
// * virt/virtual_machines/cloning_vms/virt-enabling-user-permissions-to-clone-datavolumes.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume-block.adoc
// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes-block.adoc
[id="virt-about-datavolumes_{context}"]
= About DataVolumes
`DataVolume` objects are custom resources that are provided by the Containerized
Data Importer (CDI) project. DataVolumes orchestrate import, clone, and upload
operations that are associated with an underlying PersistentVolumeClaim (PVC).
DataVolumes are integrated with KubeVirt, and they prevent a virtual machine
from being started before the PVC has been prepared.

6
modules/cnv-about-dedicated-resources.adoc → modules/virt-about-dedicated-resources.adoc
View File

@@ -1,9 +1,9 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-dedicated-resources-vm.adoc
// * cnv/cnv_vm_templates/cnv-dedicated-resources-vm-template.adoc
// * virt/virtual_machines/advanced_vm_management/virt-dedicated-resources-vm.adoc
// * virt/vm_templates/virt-dedicated-resources-vm-template.adoc
[id="cnv-about-dedicated-resources_{context}"]
[id="virt-about-dedicated-resources_{context}"]
= About dedicated resources

8
modules/cnv-about-hostpath-provisioner.adoc → modules/virt-about-hostpath-provisioner.adoc
View File

@@ -1,15 +1,15 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-configuring-local-storage-for-vms.adoc
// * virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.adoc
[id="cnv-about-hostpath-provisioner_{context}"]
[id="virt-about-hostpath-provisioner_{context}"]
= About the hostpath provisioner
The hostpath provisioner is a local storage provisioner designed for
{CNVProductName}. If you want to configure local storage for
{VirtProductName}. If you want to configure local storage for
virtual machines, you must enable the hostpath provisioner first.
When you install the {CNVProductName} Operator, the hostpath provisioner Operator
When you install the {VirtProductName} Operator, the hostpath provisioner Operator
is automatically installed. To use it, you must:
* Configure SELinux:

4
modules/cnv-about-liveness-readiness-probes.adoc → modules/virt-about-liveness-readiness-probes.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-monitoring-vm-health.adoc
// * virt/logging_events_monitoring/virt-monitoring-vm-health.adoc
[id="cnv-about-liveness-readiness-probes_{context}"]
[id="virt-about-liveness-readiness-probes_{context}"]
= About liveness and readiness probes

6
modules/cnv-about-nmstate.adoc → modules/virt-about-nmstate.adoc
View File

@@ -1,11 +1,11 @@
// Module included in the following assemblies:
//
// * cnv/cnv_node_network/cnv-observing-node-network-state.adoc
// * virt/node_network/virt-observing-node-network-state.adoc
[id="cnv-about-nmstate_{context}"]
[id="virt-about-nmstate_{context}"]
= About nmstate
{CNVProductNameStart} uses link:https://nmstate.github.io/[`nmstate`] to report on and configure the state of the node network. This makes it possible to modify network policy configuration, such as by creating a Linux bridge on all nodes, by applying a single configuration manifest to the cluster.
{VirtProductName} uses link:https://nmstate.github.io/[`nmstate`] to report on and configure the state of the node network. This makes it possible to modify network policy configuration, such as by creating a Linux bridge on all nodes, by applying a single configuration manifest to the cluster.
Node networking is monitored and updated by the following objects:

8
modules/cnv-about-red-hat-ansible-automation.adoc → modules/virt-about-red-hat-ansible-automation.adoc
View File

@@ -1,17 +1,17 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-automating-management-tasks.adoc
// * virt/virtual_machines/advanced_vm_management/virt-automating-management-tasks.adoc
[id="cnv-about-red-hat-ansible-automation_{context}"]
[id="virt-about-red-hat-ansible-automation_{context}"]
= About Red Hat Ansible Automation
link:https://docs.ansible.com/ansible/latest/index.html[Ansible] is an automation
tool used to configure systems, deploy software, and perform rolling updates.
Ansible includes support for {CNVProductName}, and Ansible modules enable you to
Ansible includes support for {VirtProductName}, and Ansible modules enable you to
automate cluster management tasks such as template, persistent volume claim, and
virtual machine operations.
Ansible provides a way to automate {CNVProductName} management, which you can also
Ansible provides a way to automate {VirtProductName} management, which you can also
accomplish by using the `oc` CLI tool or APIs. Ansible is unique because it
allows you to integrate
link:https://docs.ansible.com/ansible/latest/modules/list_of_cloud_modules.html#kubevirt[KubeVirt modules] with other Ansible modules.

13
modules/cnv-about-storage-setting-for-datavolumes.adoc → modules/virt-about-storage-setting-for-datavolumes.adoc
View File

@@ -1,15 +1,15 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-storage-defaults-for-datavolumes.adoc
// * virt/virtual_machines/virtual_disks/virt-storage-defaults-for-datavolumes.adoc
[id="cnv-about-kubevirtstorageclassdefaults_{context}"]
[id="virt-about-kubevirtstorageclassdefaults_{context}"]
= About storage settings for DataVolumes
DataVolumes require a defined _access mode_ and _volume mode_ to be created in the web console.
DataVolumes require a defined _access mode_ and _volume mode_ to be created in the web console.
These storage settings are configured by default with a `ReadWriteOnce` access mode and `Filesystem` volume mode.
You can modify these settings by editing the `kubevirt-storage-class-defaults` ConfigMap in the `openshift-cnv` namespace.
You can also add settings for other storage classes in order to create DataVolumes in the web console for different storage types.
You can also add settings for other storage classes in order to create DataVolumes in the web console for different storage types.
[NOTE]
====
@@ -18,7 +18,7 @@ You must configure storage settings that are supported by the underlying storage
All DataVolumes that you create in the web console use the default storage settings unless you specifya storage class that is also defined in the ConfigMap.
[id="cnv-datavolumes-access-modes_{context}"]
[id="virt-datavolumes-access-modes_{context}"]
== Access modes
DataVolumes support the following access modes:
@@ -28,11 +28,10 @@ DataVolumes support the following access modes:
`ReadWriteMany` is recommended if the underlying storage supports it.
[id="cnv-datavolumes-volume-modes_{context}"]
[id="virt-datavolumes-volume-modes_{context}"]
== Volume modes
The volume mode defines if a volume is intended to be used with a formatted filesystem or to remain in raw block state. DataVolumes support the following volume modes:
* `Filesystem`: Creates a filesystem on the DataVolume. This is the default setting.
* `Block`: Creates a block DataVolume. Only use `Block` if the underlying storage supports it.

24
modules/cnv-about-the-overview-dashboard.adoc → modules/virt-about-the-overview-dashboard.adoc
View File

@@ -1,13 +1,13 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-using-dashboard-to-get-cluster-info.adoc
// * virt/logging_events_monitoring/virt-using-dashboard-to-get-cluster-info.adoc
// * web_console/using-dashboard-to-get-cluster-information.adoc
ifeval::["{context}" == "cnv-using-dashboard-to-get-cluster-info"]
:cnv-cluster:
ifeval::["{context}" == "virt-using-dashboard-to-get-cluster-info"]
:virt-cluster:
endif::[]
[id="cnv-about-the-overview-dashboard_{context}"]
[id="virt-about-the-overview-dashboard_{context}"]
= About the {product-title} dashboards page
The {product-title} dashboard consists of the following cards:
@@ -23,13 +23,13 @@ Status include *ok*, *error*, *warning*, *in progress*, and *unknown*. Resources
** Number of nodes
** Number of Pods
** Persistent storage volume claims
ifdef::cnv-cluster[]
** Virtual machines (available if {CNVProductName} is installed)
endif::cnv-cluster[]
ifdef::virt-cluster[]
** Virtual machines (available if {VirtProductName} is installed)
endif::virt-cluster[]
** Bare metal hosts in the cluster, listed according to their state (only available in *metal3* environment).
ifdef::cnv-cluster[]
* *Cluster Health* summarizes the current health of the cluster as a whole, including relevant alerts and descriptions. If {CNVProductName} is installed, the overall health of {CNVProductName} is diagnosed as well. If more than one subsystem is present, click *See All* to view the status of each subsystem.
endif::cnv-cluster[]
ifdef::virt-cluster[]
* *Cluster Health* summarizes the current health of the cluster as a whole, including relevant alerts and descriptions. If {VirtProductName} is installed, the overall health of {VirtProductName} is diagnosed as well. If more than one subsystem is present, click *See All* to view the status of each subsystem.
endif::virt-cluster[]
* *Cluster Capacity* charts help administrators understand when additional resources are required in the cluster. The charts contain an inner ring that displays current consumption, while an outer ring displays thresholds configured for the resource, including information about:
** CPU time
** Memory allocation
@@ -39,6 +39,6 @@ endif::cnv-cluster[]
* *Events* lists messages related to recent activity in the cluster, such as Pod creation or virtual machine migration to another host.
* *Top Consumers* helps administrators understand how cluster resources are consumed. Click on a resource to jump to a detailed page listing Pods and nodes that consume the largest amount of the specified cluster resource (CPU, memory, or storage).
ifeval::["{context}" == "cnv-using-dashboard-to-get-cluster-info"]
:!cnv-cluster:
ifeval::["{context}" == "virt-using-dashboard-to-get-cluster-info"]
:!virt-cluster:
endif::[]

4
modules/cnv-about-the-vm-dashboard.adoc → modules/virt-about-the-vm-dashboard.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_logging_events_monitoring/cnv-viewing-information-about-vm-workloads.adoc
// * virt/logging_events_monitoring/virt-viewing-information-about-vm-workloads.adoc
[id="cnv-about-the-vm-dashboard_{context}"]
[id="virt-about-the-vm-dashboard_{context}"]
= About the Virtual Machines dashboard
Access the *Virtual Machines* dashboard from the {product-title} web console by navigating to the *Workloads* -> *Virtual Machines* page and

14
modules/cnv-about-upgrading-cnv.adoc → modules/virt-about-upgrading-virt.adoc
View File

@@ -1,16 +1,16 @@
// Module included in the following assemblies:
//
// * cnv/upgrading-container-native-virtualization.adoc
// * virt/upgrading-virt.adoc
[id="cnv-about-upgrading-cnv_{context}"]
= About upgrading container-native virtualization
[id="virt-about-upgrading-virt_{context}"]
= About upgrading {VirtProductName}
== How {CNVProductName} upgrades work
== How {VirtProductName} upgrades work
* You can upgrade to the next minor version of {CNVProductName} by using the
* You can upgrade to the next minor version of {VirtProductName} by using the
{product-title} web console to change the channel of your Operator subscription.
* You can enable automatic _z-stream_ updates during {CNVProductName} installation.
* You can enable automatic _z-stream_ updates during {VirtProductName} installation.
* Updates are delivered via the _Marketplace Operator_, which is deployed
during {product-title} installation. The Marketplace Operator makes
@@ -19,7 +19,7 @@ external Operators available to your cluster.
* The amount of time an update takes to complete depends on your network
connection. Most automatic updates complete within fifteen minutes.
== How {CNVProductName} upgrades affect your cluster
== How {VirtProductName} upgrades affect your cluster
* Upgrading does not interrupt virtual machine workloads.
** Virtual machine Pods are not restarted or migrated during an upgrade. If you

6
modules/cnv-accessing-rdp-console.adoc → modules/virt-accessing-rdp-console.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-accessing-vm-consoles.adoc
// * virt/virtual_machines/virt-accessing-vm-consoles.adoc
[id="cnv-accessing-rdp-console_{context}"]
[id="virt-accessing-rdp-console_{context}"]
= Connecting to a Windows virtual machine with an RDP console
The Remote Desktop Protocol (RDP) provides a better console experience for
@@ -21,7 +21,7 @@ Windows virtual machine.
.Procedure
. Log in to the {CNVProductName} cluster through the `oc` CLI tool as a user with
. Log in to the {VirtProductName} cluster through the `oc` CLI tool as a user with
an access token.
+
----

4
modules/cnv-accessing-serial-console.adoc → modules/virt-accessing-serial-console.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-accessing-vm-consoles.adoc
// * virt/virtual_machines/virt-accessing-vm-consoles.adoc
[id="cnv-accessing-serial-console_{context}"]
[id="virt-accessing-serial-console_{context}"]
= Accessing the serial console of a virtual machine instance
The `virtctl console` command opens a serial console to the specified virtual

4
modules/cnv-accessing-vmi-ssh.adoc → modules/virt-accessing-vmi-ssh.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-accessing-vm-consoles.adoc
// * virt/virtual_machines/virt-accessing-vm-consoles.adoc
[id="cnv-accessing-vmi-ssh_{context}"]
[id="virt-accessing-vmi-ssh_{context}"]
= Accessing a virtual machine instance via SSH
You can use SSH to access a virtual machine after you expose port

4
modules/cnv-accessing-vnc-console.adoc → modules/virt-accessing-vnc-console.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-accessing-vm-consoles.adoc
// * virt/virtual_machines/virt-accessing-vm-consoles.adoc
[id="cnv-accessing-vnc-console_{context}"]
[id="virt-accessing-vnc-console_{context}"]
= Accessing the graphical console of a virtual machine instances with VNC
The `virtctl` client utility can use the `remote-viewer` function to open a

4
modules/cnv-add-boot-order-web.adoc → modules/virt-add-boot-order-web.adoc
View File

@@ -1,9 +1,9 @@
// Module included in the following assembly:
//
// * cnv/cnv_users_guide/cnv-edit-boot-order.adoc
// * virt/virt_users_guide/virt-edit-boot-order.adoc
//
[id="cnv-add-boot-order-web_{context}"]
[id="virt-add-boot-order-web_{context}"]
= Adding items to a boot order list in the web console
Add items to a boot order list by using the web console.

14
modules/cnv-add-disk-to-vm.adoc → modules/virt-add-disk-to-vm.adoc
View File

@@ -1,22 +1,22 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-edit-vms.adoc
// * cnv/cnv_vm_templates/cnv-editing-vm-template.adoc
// * virt/virtual_machines/virt-edit-vms.adoc
// * virt/vm_templates/virt-editing-vm-template.adoc
// Establishing conditionals so content can be re-used for editing VMs
// and VM templates.
ifeval::["{context}" == "cnv-edit-vms"]
ifeval::["{context}" == "virt-edit-vms"]
:object: virtual machine
:object-gui: Virtual Machines
endif::[]
ifeval::["{context}" == "cnv-editing-vm-template"]
ifeval::["{context}" == "virt-editing-vm-template"]
:object: virtual machine template
:object-gui: Virtual Machine Templates
endif::[]
[id="cnv-vm-add-disk_{context}"]
[id="virt-vm-add-disk_{context}"]
= Adding a virtual disk to a {object}
@@ -33,12 +33,12 @@ Use this procedure to add a virtual disk to a {object}.
// Unsetting all conditionals used in module
ifeval::["{context}" == "cnv-edit-vms"]
ifeval::["{context}" == "virt-edit-vms"]
:object!:
:object-gui!:
endif::[]
ifeval::["{context}" == "cnv-editing-vm-template"]
ifeval::["{context}" == "virt-editing-vm-template"]
:object!:
:object-gui!:
endif::[]

14
modules/cnv-add-nic-to-vm.adoc → modules/virt-add-nic-to-vm.adoc
View File

@@ -1,19 +1,19 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-edit-vms.adoc
// * cnv/cnv_vm_templates/cnv-editing-vm-template.adoc
// * virt/virtual_machines/virt-edit-vms.adoc
// * virt/vm_templates/virt-editing-vm-template.adoc
ifeval::["{context}" == "cnv-edit-vms"]
ifeval::["{context}" == "virt-edit-vms"]
:object: virtual machine
:object-gui: Virtual Machines
endif::[]
ifeval::["{context}" == "cnv-editing-vm-template"]
ifeval::["{context}" == "virt-editing-vm-template"]
:object: virtual machine template
:object-gui: Virtual Machine Templates
endif::[]
[id="cnv-vm-add-nic_{context}"]
[id="virt-vm-add-nic_{context}"]
= Adding a network interface to a {object}
@@ -45,12 +45,12 @@ is defined on the virtual machine and connected to the network.
// Scrubbing all conditionals used in module
ifeval::["{context}" == "cnv-edit-vms"]
ifeval::["{context}" == "virt-edit-vms"]
:object!:
:object-gui!:
endif::[]
ifeval::["{context}" == "cnv-editing-vm-template"]
ifeval::["{context}" == "virt-editing-vm-template"]
:object!:
:object-gui!:
endif::[]

4
modules/cnv-adding-tls-certificates-for-authenticating-dv-imports.adoc → modules/virt-adding-tls-certificates-for-authenticating-dv-imports.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-tls-certificates-for-dv-imports.adoc
// * virt/virtual_machines/importing_vms/virt-tls-certificates-for-dv-imports.adoc
[id="cnv-adding-tls-certificates-for-authenticating-dv-imports_{context}"]
[id="virt-adding-tls-certificates-for-authenticating-dv-imports_{context}"]
= Adding TLS certificates for authenticating DataVolume imports
TLS certificates for registry or HTTPS endpoints must be added to a ConfigMap

45
modules/cnv-adding-virtio-drivers-vm-yaml.adoc → modules/virt-adding-virtio-drivers-vm-yaml.adoc
View File

@@ -1,30 +1,32 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-new-windows-vm.adoc
// * cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-existing-windows-vm.adoc
// * virt/virtual_machines/virt-installing-virtio-drivers-on-new-windows-vm.adoc
// * virt/virtual_machines/virt-installing-virtio-drivers-on-existing-windows-vm.adoc
[id="cnv-adding-virtio-drivers-vm-yaml_{context}"]
//This file contains UI elements and/or package names that need to be updated.
[id="virt-adding-virtio-drivers-vm-yaml_{context}"]
= Adding VirtIO drivers container disk to a virtual machine
{CNVProductNameStart} distributes VirtIO drivers for Microsoft Windows as a
container disk, which is available from the
link:https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/virtio-win[Red Hat Container Catalog].
To install these drivers to a Windows virtual machine, attach the
`container-native-virtualization/virtio-win` container disk to the virtual machine as a SATA CD drive
in the virtual machine configuration file.
{VirtProductName} distributes VirtIO drivers for Microsoft Windows as a
container disk, which is available from the
link:https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/virtio-win[Red Hat Container Catalog].
To install these drivers to a Windows virtual machine, attach the
`container-native-virtualization/virtio-win` container disk to the virtual machine as a SATA CD drive
in the virtual machine configuration file.
.Prerequisites
* Download the `container-native-virtualization/virtio-win` container disk from the
* Download the `container-native-virtualization/virtio-win` container disk from the
link:https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/virtio-win[Red Hat Container Catalog].
This is not mandatory, because the container disk will be downloaded from the Red Hat registry
This is not mandatory, because the container disk will be downloaded from the Red Hat registry
if it not already present in the cluster, but it can reduce installation time.
.Procedure
. Add the `container-native-virtualization/virtio-win` container disk as a `cdrom` disk in the
Windows virtual machine configuration file. The container disk will be
downloaded from the registry if it is not already present in the cluster.
. Add the `container-native-virtualization/virtio-win` container disk as a `cdrom` disk in the
Windows virtual machine configuration file. The container disk will be
downloaded from the registry if it is not already present in the cluster.
+
[source,yaml]
----
@@ -41,19 +43,18 @@ volumes:
image: container-native-virtualization/virtio-win
name: virtiocontainerdisk
----
<1> {CNVProductNameStart} boots virtual machine disks in the order defined in the
`VirtualMachine` configuration file. You can either define other disks for the
virtual machine before the `container-native-virtualization/virtio-win` container disk or use the optional
<1> {VirtProductName} boots virtual machine disks in the order defined in the
`VirtualMachine` configuration file. You can either define other disks for the
virtual machine before the `container-native-virtualization/virtio-win` container disk or use the optional
`bootOrder` parameter to ensure the virtual machine boots from the correct disk.
If you specify the `bootOrder` for a disk, it must be specified for all disks
If you specify the `bootOrder` for a disk, it must be specified for all disks
in the configuration.
. The disk is available once the virtual machine has started:
** If you add the container disk to a running virtual machine, use
`oc apply -f <vm.yaml>` in the CLI or reboot the virtual machine for the changes
** If you add the container disk to a running virtual machine, use
`oc apply -f <vm.yaml>` in the CLI or reboot the virtual machine for the changes
to take effect.
** If the virtual machine is not running, use `virtctl start <vm>`.
After the virtual machine has started, the VirtIO drivers can be installed from
After the virtual machine has started, the VirtIO drivers can be installed from
the attached SATA CD drive.

4
modules/cnv-automating-virtual-machine-creation-with-ansible.adoc → modules/virt-automating-virtual-machine-creation-with-ansible.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-automating-management-tasks.adoc
// * virt/virtual_machines/advanced_vm_management/virt-automating-management-tasks.adoc
[id="cnv-automating-virtual-machine-creation-with-ansible_{context}"]
[id="virt-automating-virtual-machine-creation-with-ansible_{context}"]
= Automating virtual machine creation
You can use the `kubevirt_vm` Ansible Playbook to create virtual machines in

4
modules/cnv-cancelling-vm-migration-cli.adoc → modules/virt-cancelling-vm-migration-cli.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_live_migration/cnv-cancel-vmi-migration.adoc
// * virt/live_migration/virt-cancel-vmi-migration.adoc
[id="cnv-cancelling-vm-migration-cli_{context}"]
[id="virt-cancelling-vm-migration-cli_{context}"]
= Cancelling live migration of a virtual machine instance in the CLI
Cancel the live migration of a virtual machine instance by deleting the

6
modules/cnv-cancelling-vm-migration-web.adoc → modules/virt-cancelling-vm-migration-web.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_live_migration/cnv-cancel-vmi-migration.adoc
// * virt/live_migration/virt-cancel-vmi-migration.adoc
[id="cnv-cancelling-vm-migration-web_{context}"]
[id="virt-cancelling-vm-migration-web_{context}"]
= Cancelling live migration of a virtual machine instance in the web console
A live migration of the virtual machine instance can be cancelled using the
@@ -12,7 +12,7 @@ on the *Virtual Machine Details* screen.
.Procedure
. In the {CNVProductName} console, click *Workloads* -> *Virtual Machines*.
. In the {VirtProductName} console, click *Workloads* -> *Virtual Machines*.
. You can cancel the migration from this screen, which makes it easier to perform actions on multiple virtual machines in the one screen, or from the *Virtual Machine Details* screen where you can view comprehensive details of the selected virtual machine:
** Click the Options menu {kebab} at the end of virtual machine and select
*Cancel Virtual Machine Migration*.

18
modules/cnv-cdi-supported-operations-matrix.adoc → modules/virt-cdi-supported-operations-matrix.adoc
View File

@@ -1,16 +1,16 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-virtctl.adoc
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-uploading-local-disk-images-block.adoc
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-preparing-cdi-scratch-space.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-using-datavolumetemplate.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume-block.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-virtual-machine-images-datavolumes-block.adoc
// * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-virtctl.adoc
// * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
// * virt/virtual_machines/virtual_disks/virt-preparing-cdi-scratch-space.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-using-datavolumetemplate.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume-block.adoc
// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes-block.adoc
[id="cnv-cdi-supported-operations-matrix_{context}"]
[id="virt-cdi-supported-operations-matrix_{context}"]
= CDI supported operations matrix
This matrix shows the supported CDI operations for content types against endpoints, and which of these operations requires scratch space.

6
modules/cnv-cdrom-wizard-fields-web.adoc → modules/virt-cdrom-wizard-fields-web.adoc
View File

@@ -1,9 +1,9 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-create-vms.adoc
// * cnv/cnv_vm_templates/cnv-creating-vm-template.adoc
// * virt/virtual_machines/virt-create-vms.adoc
// * virt/vm_templates/virt-creating-vm-template.adoc
[id="cnv-cdrom-wizard-fields-web_{context}"]
[id="virt-cdrom-wizard-fields-web_{context}"]
= CD-ROM fields
|===

84
modules/virt-cli-reference-controlling-vms.adoc Normal file
View File

@@ -0,0 +1,84 @@
// Module included in the following assemblies:
//
// * virt/virtual_machines/virt-controlling-vm-states.adoc
[id="virt-cli-reference-controlling-vms_{context}"]
= CLI reference for controlling virtual machines
Use the following `virtctl` client utility and `oc` commands to change the state of the virtual
machines and display lists of the virtual machines and the virtual machine instances
that represent them.
[NOTE]
====
When you run `virtctl` commands, you modify the virtual machines themselves,
not the virtual machine instances that represent them in the web console.
====
== start
Start a virtual machine.
.Example: Start a virtual machine in the current project
----
$ virtctl start <example-vm>
----
.Example: Start a virtual machine in a specific project
----
$ virtctl start <example-vm> -n <project_name>
----
== restart
Restart a running virtual machine.
.Example: Restart a virtual machine in the current project
----
$ virtctl restart <example-vm>
----
.Example: Restart a virtual machine in a specific project
----
$ virtctl restart <example-vm> -n <project_name>
----
== stop
Stop a running virtual machine.
.Example: Stop a virtual machine in the current project
----
$ virtctl stop <example-vm>
----
.Example: Stop a virtual machine in a specific project
----
$ virtctl stop <example-vm> -n <project_name>
----
== list
List the virtual machines or virtual machine instances in a project. The
virtual machine instances are abstractions that represent the virtual machines
themselves.
.Example: List the virtual machines in the current project
----
$ oc get vm
----
.Example: List the virtual machines in a specific project
----
$ oc get vm -n <project_name>
----
.Example: List the running virtual machine instances in the current project
----
$ oc get vmi
----
.Example: List the running virtual machine instances in a specific project
----
$ oc get vmi -n <project_name>
----

10
modules/cnv-cloning-local-volume-to-another-node.adoc → modules/virt-cloning-local-volume-to-another-node.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-moving-local-vm-disk-to-different-node.adoc
// * virt/virtual_machines/virtual_disks/virt-moving-local-vm-disk-to-different-node.adoc
[id="cnv-cloning-local-volume-to-another-node_{context}"]
[id="virt-cloning-local-volume-to-another-node_{context}"]
= Cloning a local volume to another node
You can move a virtual machine disk so that it runs on a specific node by cloning the underlying PersistentVolumeClaim (PVC).
@@ -18,13 +18,13 @@ If the destination PV is smaller than the source PVC, the cloning operation fail
.Prerequisites
* The virtual machine must not be running. Power down the virtual machine before cloning the virtual machine disk.
* The virtual machine must not be running. Power down the virtual machine before cloning the virtual machine disk.
.Procedure
. Either create a new local PV on the node, or identify a local PV already on the node:
* Create a local PV that includes the `nodeAffinity.nodeSelectorTerms` parameters. The following manifest creates a `10Gi` local PV on `node01`.
* Create a local PV that includes the `nodeAffinity.nodeSelectorTerms` parameters. The following manifest creates a `10Gi` local PV on `node01`.
+
[source,yaml]
----
@@ -80,7 +80,7 @@ spec:
...
----
<1> The `kubernetes.io/hostname` key uses the node host name to select a node.
<2> The host name of the node.
<2> The host name of the node.
. Add a unique label to the PV:
+

6
modules/cnv-cloning-pvc-of-vm-disk-into-new-datavolume.adoc → modules/virt-cloning-pvc-of-vm-disk-into-new-datavolume.adoc
View File

@@ -1,11 +1,11 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume.adoc
// * cnv/cnv_virtual_machines/cnv_cloning_vms/cnv-cloning-vm-disk-into-new-datavolume-block.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume-block.adoc
// `blockstorage` conditionals are used (declared in the "*-block" assembly) to separate content
[id="cnv-cloning-pvc-of-vm-disk-into-new-datavolume_{context}"]
[id="virt-cloning-pvc-of-vm-disk-into-new-datavolume_{context}"]
= Cloning the PersistentVolumeClaim of a virtual machine disk into a new DataVolume
You can clone a PersistentVolumeClaim (PVC) of an existing virtual machine disk

8
modules/cnv-cloud-init-fields-web.adoc → modules/virt-cloud-init-fields-web.adoc
View File

@@ -1,10 +1,10 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv-create-vms.adoc
// * cnv/cnv_virtual_machines/cnv_importing_vms/cnv-importing-vmware-vm.adoc
// * cnv/cnv_vm_templates/cnv-creating-vm-template.adoc
// * virt/virtual_machines/virt-create-vms.adoc
// * virt/virtual_machines/importing_vms/virt-importing-vmware-vm.adoc
// * virt/vm_templates/virt-creating-vm-template.adoc
[id="cnv-cloud-init-fields-web_{context}"]
[id="virt-cloud-init-fields-web_{context}"]
= Cloud-init fields
|===

4
modules/cnv-configuring-guest-memory-overcommitment.adoc → modules/virt-configuring-guest-memory-overcommitment.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_advanced_vm_management/cnv-managing-guest-memory.adoc
// * virt/virtual_machines/advanced_vm_management/virt-managing-guest-memory.adoc
[id="cnv-configuring-guest-memory-overcommitment_{context}"]
[id="virt-configuring-guest-memory-overcommitment_{context}"]
= Configuring guest memory overcommitment
If your virtual workload requires more memory than available, you can

4
modules/cnv-configuring-live-migration-limits.adoc → modules/virt-configuring-live-migration-limits.adoc
View File

@@ -1,9 +1,9 @@
// Module included in the following assemblies:
//
// * cnv/cnv_live_migration/cnv-live-migration-limits.adoc
// * virt/live_migration/virt-live-migration-limits.adoc
[id="cnv-configuring-live-migration-limits_{context}"]
[id="virt-configuring-live-migration-limits_{context}"]
= Configuring live migration limits and timeouts
Configure live migration limits and timeouts for the cluster by adding updated

4
modules/cnv-configuring-masquerade-mode-cli.adoc → modules/virt-configuring-masquerade-mode-cli.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_vm_networking/cnv-using-the-default-pod-network-with-cnv.adoc
// * virt/virtual_machines/vm_networking/virt-using-the-default-pod-network-with-virt.adoc
[id="cnv-configuring-masquerade-mode-cli_{context}"]
[id="virt-configuring-masquerade-mode-cli_{context}"]
= Configuring masquerade mode from the command line
You can use masquerade mode to hide a virtual machine's outgoing traffic behind

4
modules/cnv-configuring-selinux-hpp-on-rhcos8.adoc → modules/virt-configuring-selinux-hpp-on-rhcos8.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * cnv/cnv_virtual_machines/cnv_virtual_disks/cnv-configuring-local-storage-for-vms.adoc
// * virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.adoc
[id="cnv-configuring-selinux-hpp-on-rhcos8_{context}"]
[id="virt-configuring-selinux-hpp-on-rhcos8_{context}"]
= Configuring SELinux for the hostpath provisioner on Red Hat Enterprise Linux CoreOS 8
You must configure SELinux before you create the HostPathProvisioner custom

Some files were not shown because too many files have changed in this diff Show More