From 64876e4fa56054283e6528e7c24d8ddf50288546 Mon Sep 17 00:00:00 2001 From: Sandro Bonazzola Date: Mon, 24 May 2021 18:15:49 +0200 Subject: [PATCH 1/3] Use symlink to common RHV documentation uses a system that requires common directory to be within each docuemtation guide. Using symlinks here to help moving the documentation to upstream first. It has a downside: live reload raises errors like: Directory: ovirt-site/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common is already being watched through: ovirt-site/source/documentation/common MORE INFO: https://github.com/guard/listen/blob/master/README.md ** ERROR: directory is already being watched! ** Signed-off-by: Sandro Bonazzola --- _config.yml | 14 ++++++- .../administration_guide/appe-Proxies.adoc | 2 +- .../chap-Backups_and_Migration.adoc | 14 +++---- .../administration_guide/chap-Clusters.adoc | 8 ++-- .../chap-Data_Centers.adoc | 2 +- .../chap-Global_Configuration.adoc | 2 +- .../administration_guide/chap-Hosts.adoc | 8 ++-- .../chap-Logical_Networks.adoc | 4 +- .../administration_guide/chap-Storage.adoc | 26 ++++++------ .../documentation/administration_guide/common | 1 + .../administration_guide/index.adoc | 2 +- .../part-Administering_the_Environment.adoc | 2 +- ...ork_Labels_to_Host_Network_Interfaces.adoc | 2 +- ...vice_Neutron_for_Network_Provisioning.adoc | 2 +- .../topics/Adding_and_removing_tags.adoc | 2 +- ...uster_Optimization_Settings_Explained.adoc | 2 +- .../topics/Creating_a_New_Cluster.adoc | 2 +- .../topics/Creating_a_New_Data_Center.adoc | 2 +- ..._device_with_the_lldp_labeler_service.adoc | 2 +- .../topics/Customizing_hosts_with_tags.adoc | 2 +- .../topics/Destroying_a_storage_domain.adoc | 2 +- .../topics/Editing_Vfs_on_NIC.adoc | 2 +- ...nabling_Passthrough_on_a_vNIC_Profile.adoc | 2 +- ...al_Disk_to_an_OpenStack_Image_Service.adoc | 2 +- .../topics/Force_Removing_a_Data_Center.adoc | 2 +- .../Importing_an_Unregistered_Disk_Image.adoc | 2 +- ...ing_or_isolating_a_nonresponsive_host.adoc | 2 +- .../topics/Re-initializing_a_Data_Center.adoc | 2 +- .../topics/Reclaiming_Virtual_Disk_Space.adoc | 2 +- .../topics/Updating_OVFs.adoc | 2 +- ...pdating_a_host_between_minor_releases.adoc | 6 +-- .../con-Self-hosted_Engine_Architecture.adoc | 2 +- .../con-Standalone_Manager_Architecture.adoc | 2 +- ...-Adding_standard_hosts_to_the_Manager.adoc | 2 +- ...oc-Maintaining_the_Self-Hosted_Engine.adoc | 4 +- ...onal_Considerations_Device_Assignment.adoc | 2 +- .../sriov/conc-Hardware_Considerations.adoc | 2 +- ...Virtual_Machine_Cluster_Compatibility.adoc | 2 +- ...ing_the_Cluster_Compatibility_Version.adoc | 2 +- .../proc-Updating_Individual_Hosts.adoc | 2 +- .../proc-Updating_all_hosts_in_a_cluster.adoc | 2 +- ...alling_and_Configuring_Data_Warehouse.adoc | 4 +- .../documentation/data_warehouse_guide/common | 1 + .../data_warehouse_guide/index.adoc | 4 +- .../disaster_recovery_guide/common | 1 + .../disaster_recovery_guide/index.adoc | 2 +- .../common | 1 + .../index.adoc | 40 +++++++++---------- .../common | 1 + .../index.adoc | 40 +++++++++---------- .../common | 1 + .../index.adoc | 28 ++++++------- .../common | 1 + .../index.adoc | 32 +++++++-------- .../chap-Accessing_the_VM_Portal.adoc | 4 +- .../introduction_to_the_vm_portal/common | 1 + .../introduction_to_the_vm_portal/index.adoc | 2 +- .../common | 1 + .../index.adoc | 20 +++++----- .../assembly-Remote_Upgrading_from_4-0.adoc | 30 +++++++------- .../assembly-Remote_Upgrading_from_4-1.adoc | 24 +++++------ .../assembly-Remote_Upgrading_from_4-2.adoc | 20 +++++----- .../assembly-SHE_Upgrading_from_4-0.adoc | 34 ++++++++-------- .../assembly-SHE_Upgrading_from_4-1.adoc | 24 +++++------ .../assembly-SHE_Upgrading_from_4-2.adoc | 22 +++++----- .../assembly-SHE_Upgrading_from_4-3.adoc | 26 ++++++------ .../assembly-Upgrading_from_4-0.adoc | 26 ++++++------ .../assembly-Upgrading_from_4-0_ff.adoc | 18 ++++----- .../assembly-Upgrading_from_4-1.adoc | 20 +++++----- .../assembly-Upgrading_from_4-1_ff.adoc | 14 +++---- .../assembly-Upgrading_from_4-2.adoc | 18 ++++----- .../assembly-Upgrading_from_4-2_ff.adoc | 14 +++---- .../assembly-Upgrading_from_4-3.adoc | 22 +++++----- ...d_Hat_Virtualization_Upgrade_Overview.adoc | 2 +- .../chap-Updates_between_Minor_Releases.adoc | 14 +++---- source/documentation/upgrade_guide/common | 1 + source/documentation/upgrade_guide/index.adoc | 2 +- ...Hat_Enterprise_Linux_Virtual_Machines.adoc | 4 +- ...p-Installing_Windows_Virtual_Machines.adoc | 4 +- .../virtual_machine_management_guide/common | 1 + .../index.adoc | 2 +- ...ng_ongoing_virtual_machine_migrations.adoc | 2 +- ...Changing_the_CD_for_a_Virtual_Machine.adoc | 2 +- .../topics/Cloning_a_Virtual_Machine.adoc | 2 +- ...late_from_an_existing_virtual_machine.adoc | 2 +- .../Editing_Virtual_Machine_Properties.adoc | 2 +- ...xporting_a_virtual_machines_to_a_host.adoc | 2 +- ...virtual_machines_to_the_export_domain.adoc | 2 +- .../topics/Hot_Plugging_Virtual_Memory.adoc | 2 +- .../topics/Hot_Plugging_a_Virtual_Disk.adoc | 2 +- .../Importing_a_Virtual_Machine_from_KVM.adoc | 2 +- .../Importing_a_Virtual_Machine_from_Xen.adoc | 2 +- ...irtual_Machine_from_a_VMware_Provider.adoc | 2 +- .../Importing_an_OVA_file_from_a_host.adoc | 2 +- .../Importing_an_Unregistered_Disk_Image.adoc | 2 +- .../topics/Live_migration_prerequisites.adoc | 2 +- ...g_Virtual_Disks_From_Virtual_Machines.adoc | 2 +- ...ual_Machine_System_Settings_Explained.adoc | 2 +- ...ual_virtual_machines_to_a_data_domain.adoc | 2 +- 99 files changed, 366 insertions(+), 345 deletions(-) create mode 120000 source/documentation/administration_guide/common create mode 120000 source/documentation/data_warehouse_guide/common create mode 120000 source/documentation/disaster_recovery_guide/common create mode 120000 source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common create mode 120000 source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common create mode 120000 source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common create mode 120000 source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common create mode 120000 source/documentation/introduction_to_the_vm_portal/common create mode 120000 source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common create mode 120000 source/documentation/upgrade_guide/common create mode 120000 source/documentation/virtual_machine_management_guide/common diff --git a/_config.yml b/_config.yml index aff1a6a4010..4d4ba9ae78f 100644 --- a/_config.yml +++ b/_config.yml @@ -138,27 +138,37 @@ exclude: - CONTRIBUTING.md - CODEOWNERS # avoid generating paginated asciidoc content - - documentation/common/**/*.adoc + - documentation/common/**/* - documentation/administration_guide/appe* - documentation/administration_guide/chap* + - documentation/administration_guide/common/**/*.adoc - documentation/administration_guide/part* - documentation/administration_guide/topics - documentation/data_warehouse_guide/chap* - documentation/data_warehouse_guide/topics + - documentation/data_warehouse_guide/common/**/*.adoc - documentation/disaster_recovery_guide/assembly - documentation/disaster_recovery_guide/concept - documentation/disaster_recovery_guide/reference - documentation/disaster_recovery_guide/task + - documentation/disaster_recovery_guide/common/**/*.adoc + - documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common/**/*.adoc + - documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common/**/*.adoc + - documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common/**/*.adoc + - documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common/**/*.adoc - documentation/introduction_to_the_vm_portal/topics - documentation/introduction_to_the_vm_portal/chap* + - documentation/introduction_to_the_vm_portal/common/**/*.adoc + - documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common/**/*.adoc - documentation/upgrade_guide/assembly* - documentation/upgrade_guide/chap-* - documentation/upgrade_guide/topics + - documentation/upgrade_guide/common/**/*.adoc - documentation/virtual_machine_management_guide/appe* - documentation/virtual_machine_management_guide/chap* - documentation/virtual_machine_management_guide/topics - documentation/virtual_machine_management_guide/assembly* - + - documentation/virtual_machine_management_guide/common/**/*.adoc sass: add_charset: true style: :compressed diff --git a/source/documentation/administration_guide/appe-Proxies.adoc b/source/documentation/administration_guide/appe-Proxies.adoc index 9bbd138d4b7..2028646b16d 100644 --- a/source/documentation/administration_guide/appe-Proxies.adoc +++ b/source/documentation/administration_guide/appe-Proxies.adoc @@ -27,6 +27,6 @@ include::topics/Installing_and_Configuring_a_Squid_Proxy.adoc[] include::topics/Websocket_Proxy_Overview.adoc[] -// include::../common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+3] +// include::common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+3] :context!: proxy_admin diff --git a/source/documentation/administration_guide/chap-Backups_and_Migration.adoc b/source/documentation/administration_guide/chap-Backups_and_Migration.adoc index 03f411be9a0..da35aacd78e 100644 --- a/source/documentation/administration_guide/chap-Backups_and_Migration.adoc +++ b/source/documentation/administration_guide/chap-Backups_and_Migration.adoc @@ -17,30 +17,30 @@ include::topics/Restoring_a_Backup_with_the_engine-backup_Command.adoc[] include::topics/Restoring_a_Backup_to_a_Fresh_Installation.adoc[] -include::../common/backup-restore/proc-Restoring_a_Backup_to_Overwrite_an_Existing_Installation.adoc[leveloffset=+3] +include::common/backup-restore/proc-Restoring_a_Backup_to_Overwrite_an_Existing_Installation.adoc[leveloffset=+3] include::topics/Restoring_a_Backup_with_Different_Credentials.adoc[] -include::../common/backup-restore/assembly-Backing_up_and_Restoring_a_Self-Hosted_Engine.adoc[leveloffset=+3] +include::common/backup-restore/assembly-Backing_up_and_Restoring_a_Self-Hosted_Engine.adoc[leveloffset=+3] -include::../common/backup-restore/assembly-Recovering_a_Self-Hosted_Engine.adoc[leveloffset=+3] +include::common/backup-restore/assembly-Recovering_a_Self-Hosted_Engine.adoc[leveloffset=+3] -include::../common/backup-restore/assembly-Overwriting_a_Self-Hosted_Engine.adoc[leveloffset=+3] +include::common/backup-restore/assembly-Overwriting_a_Self-Hosted_Engine.adoc[leveloffset=+3] [[migrating-rhv-databases]] === Migrating {virt-product-fullname} Databases to Remote Servers :context: migrate_database -include::../common/database/proc-Migrating_the_Manager_database_to_a_remote_server.adoc[leveloffset=+3] +include::common/database/proc-Migrating_the_Manager_database_to_a_remote_server.adoc[leveloffset=+3] //Adding back context :context: migrate_database -include::../common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+3] +include::common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+3] //Adding back context :context: migrate_database -include::../common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+3] +include::common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+3] :context!: migrate_database diff --git a/source/documentation/administration_guide/chap-Clusters.adoc b/source/documentation/administration_guide/chap-Clusters.adoc index 255f55c6fbe..76637d1ac32 100644 --- a/source/documentation/administration_guide/chap-Clusters.adoc +++ b/source/documentation/administration_guide/chap-Clusters.adoc @@ -41,13 +41,13 @@ include::topics/Removing_a_cluster.adoc[leveloffset=-1] include::topics/Memory_Optimization.adoc[leveloffset=-1] -include::../common/admin/con_UEFI_Q35_explanation.adoc[leveloffset=+2] +include::common/admin/con_UEFI_Q35_explanation.adoc[leveloffset=+2] -include::../common/admin/proc_Configuring_cluster_to_use_Q35_or_UEFI.adoc[leveloffset=+3] +include::common/admin/proc_Configuring_cluster_to_use_Q35_or_UEFI.adoc[leveloffset=+3] -include::../common/admin/proc_Configuring_vm_to_use_Q35_or_UEFI.adoc[leveloffset=+3] +include::common/admin/proc_Configuring_vm_to_use_Q35_or_UEFI.adoc[leveloffset=+3] :context: admin :admin: -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+2] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+2] diff --git a/source/documentation/administration_guide/chap-Data_Centers.adoc b/source/documentation/administration_guide/chap-Data_Centers.adoc index c9d16bb5be1..9cd4cca7e60 100644 --- a/source/documentation/administration_guide/chap-Data_Centers.adoc +++ b/source/documentation/administration_guide/chap-Data_Centers.adoc @@ -24,7 +24,7 @@ include::topics/Changing_the_Data_Center_Storage_Type.adoc[leveloffset=-1] :context: admin :admin: -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+2] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+2] [[sect-Data_Centers_and_Storage_Domains]] == Data Centers and Storage Domains diff --git a/source/documentation/administration_guide/chap-Global_Configuration.adoc b/source/documentation/administration_guide/chap-Global_Configuration.adoc index d13acda5b9b..46748f596c4 100644 --- a/source/documentation/administration_guide/chap-Global_Configuration.adoc +++ b/source/documentation/administration_guide/chap-Global_Configuration.adoc @@ -70,7 +70,7 @@ include::topics/Managing_System_Permissions_for_a_Virtual_Disk.adoc[] include::topics/Virtual_Disk_User_Roles_Explained.adoc[] :context: system_permissions -include::../common/admin/proc-Setting_Legacy_SPICE_Cipher.adoc[leveloffset=+3] +include::common/admin/proc-Setting_Legacy_SPICE_Cipher.adoc[leveloffset=+3] [[sect-Scheduling_Policies]] diff --git a/source/documentation/administration_guide/chap-Hosts.adoc b/source/documentation/administration_guide/chap-Hosts.adoc index 19a89715d7d..5978bb7cd0c 100644 --- a/source/documentation/administration_guide/chap-Hosts.adoc +++ b/source/documentation/administration_guide/chap-Hosts.adoc @@ -13,7 +13,7 @@ include::topics/Satellite_Host_Provider_Hosts.adoc[] === Host Tasks :context: host_tasks -include::../common/install/proc-Adding_standard_hosts_to_the_Manager.adoc[leveloffset=+3] +include::common/install/proc-Adding_standard_hosts_to_the_Manager.adoc[leveloffset=+3] include::topics/Adding_a_Satellite_Host_Provider_Host.adoc[] @@ -40,7 +40,7 @@ include::topics/Configuring_Host_Power_Management_Settings.adoc[] include::topics/Configuring_Host_SPM_Settings.adoc[] -include::../common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+3] +include::common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+3] include::topics/Moving_a_host_to_maintenance_mode.adoc[] @@ -53,7 +53,7 @@ include::topics/Removing_a_host.adoc[] include::topics/Updating_a_host_between_minor_releases.adoc[leveloffset=+3] :admin: -include::../common/install/proc-Reinstalling_Hosts.adoc[leveloffset=+3] +include::common/install/proc-Reinstalling_Hosts.adoc[leveloffset=+3] :admin!: :context: host_tasks @@ -66,7 +66,7 @@ include::topics/Viewing_Host_Devices.adoc[] include::topics/Accessing_Cockpit_from_the_Admin_Portal.adoc[] -include::../common/admin/proc-Setting_Legacy_SPICE_Cipher.adoc[leveloffset=+3] +include::common/admin/proc-Setting_Legacy_SPICE_Cipher.adoc[leveloffset=+3] :context!: host_tasks diff --git a/source/documentation/administration_guide/chap-Logical_Networks.adoc b/source/documentation/administration_guide/chap-Logical_Networks.adoc index 2b88bf7ceb2..86efca304dd 100644 --- a/source/documentation/administration_guide/chap-Logical_Networks.adoc +++ b/source/documentation/administration_guide/chap-Logical_Networks.adoc @@ -90,9 +90,9 @@ include::topics/Adding_Network_Labels_to_Host_Network_Interfaces.adoc[] include::topics/Changing_the_FQDN_of_a_Host.adoc[] -include::../common/network/con-IPv6_Networking_Support.adoc[leveloffset=+3] +include::common/network/con-IPv6_Networking_Support.adoc[leveloffset=+3] -include::../common/sriov/assembly-Set_Up_and_Configure_SR-IOV.adoc[leveloffset=+3] +include::common/sriov/assembly-Set_Up_and_Configure_SR-IOV.adoc[leveloffset=+3] :Network!: [[sect-Network_Bonding]] diff --git a/source/documentation/administration_guide/chap-Storage.adoc b/source/documentation/administration_guide/chap-Storage.adoc index f3b8af6afc6..4312cbdc4cd 100644 --- a/source/documentation/administration_guide/chap-Storage.adoc +++ b/source/documentation/administration_guide/chap-Storage.adoc @@ -55,40 +55,40 @@ include::topics/Understanding_Storage.adoc[] [[sect-Preparing_and_Adding_NFS_Storage]] === Preparing and Adding NFS Storage -include::../common/storage/proc-Preparing_NFS_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Preparing_NFS_Storage.adoc[leveloffset=+3] -include::../common/storage/proc-Adding_NFS_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Adding_NFS_Storage.adoc[leveloffset=+3] include::topics/Increasing_NFS_Storage.adoc[] [[sect-Preparing_and_Adding_Local_Storage]] === Preparing and Adding Local Storage -include::../common/storage/proc-Preparing_Local_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Preparing_Local_Storage.adoc[leveloffset=+3] -include::../common/storage/proc-Adding_Local_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Adding_Local_Storage.adoc[leveloffset=+3] [[sect-Preparing_and_Adding_POSIX_Compliant_File_System_Storage]] === Preparing and Adding POSIX-compliant File System Storage -include::../common/storage/ref-Preparing_POSIX_Storage.adoc[leveloffset=+3] +include::common/storage/ref-Preparing_POSIX_Storage.adoc[leveloffset=+3] -include::../common/storage/proc-Adding_POSIX_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Adding_POSIX_Storage.adoc[leveloffset=+3] [[sect-Preparing_and_Adding_Block_Storage]] === Preparing and Adding Block Storage -include::../common/storage/ref-Preparing_iSCSI_Storage.adoc[leveloffset=+3] +include::common/storage/ref-Preparing_iSCSI_Storage.adoc[leveloffset=+3] -include::../common/storage/proc-Adding_iSCSI_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Adding_iSCSI_Storage.adoc[leveloffset=+3] include::topics/Configuring_iSCSI_Multipathing.adoc[] include::topics/proc-Migrating_a_logical_network_to_an_iscsi_bond.adoc[leveloffset=+3] -include::../common/storage/ref-Preparing_FCP_Storage.adoc[leveloffset=+3] +include::common/storage/ref-Preparing_FCP_Storage.adoc[leveloffset=+3] -include::../common/storage/proc-Adding_FCP_Storage.adoc[leveloffset=+3] +include::common/storage/proc-Adding_FCP_Storage.adoc[leveloffset=+3] include::topics/Increasing_iSCSI_or_FCP_Storage.adoc[] @@ -97,9 +97,9 @@ include::topics/Reusing_LUNs.adoc[] [[Adding_Red_Hat_Gluster_Storage]] === Preparing and Adding {gluster-storage-fullname} -include::../common/storage/ref-Preparing_Red_Hat_Gluster_Storage.adoc[leveloffset=+3] +include::common/storage/ref-Preparing_Red_Hat_Gluster_Storage.adoc[leveloffset=+3] -include::../common/storage/ref-Adding_Red_Hat_Gluster_Storage.adoc[leveloffset=+3] +include::common/storage/ref-Adding_Red_Hat_Gluster_Storage.adoc[leveloffset=+3] [[sect-Importing_Existing_Storage_Domains]] @@ -138,7 +138,7 @@ include::topics/Detaching_a_storage_domain.adoc[] include::topics/Attaching_a_storage_domain.adoc[] -include::../common/storage/proc-Removing_a_Storage_Domain.adoc[leveloffset=+3] +include::common/storage/proc-Removing_a_Storage_Domain.adoc[leveloffset=+3] include::topics/Destroying_a_storage_domain.adoc[] diff --git a/source/documentation/administration_guide/common b/source/documentation/administration_guide/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/administration_guide/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/administration_guide/index.adoc b/source/documentation/administration_guide/index.adoc index ed332154537..0ed9e9dd7ed 100644 --- a/source/documentation/administration_guide/index.adoc +++ b/source/documentation/administration_guide/index.adoc @@ -1,5 +1,5 @@ = Administration Guide -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] // Make sure Jekyll displays a guide title [discrete] diff --git a/source/documentation/administration_guide/part-Administering_the_Environment.adoc b/source/documentation/administration_guide/part-Administering_the_Environment.adoc index f7423b844ee..6e54dce4e43 100644 --- a/source/documentation/administration_guide/part-Administering_the_Environment.adoc +++ b/source/documentation/administration_guide/part-Administering_the_Environment.adoc @@ -1,7 +1,7 @@ [[part-Administering_the_Environment]] = Administering the Environment -include::../common/she/chap-Administering_the_Self-Hosted_Engine.adoc[leveloffset=+1] +include::common/she/chap-Administering_the_Self-Hosted_Engine.adoc[leveloffset=+1] include::chap-Backups_and_Migration.adoc[] diff --git a/source/documentation/administration_guide/topics/Adding_Network_Labels_to_Host_Network_Interfaces.adoc b/source/documentation/administration_guide/topics/Adding_Network_Labels_to_Host_Network_Interfaces.adoc index 7083536b522..907cab8d788 100644 --- a/source/documentation/administration_guide/topics/Adding_Network_Labels_to_Host_Network_Interfaces.adoc +++ b/source/documentation/administration_guide/topics/Adding_Network_Labels_to_Host_Network_Interfaces.adoc @@ -22,7 +22,7 @@ There are two methods of adding labels to a host network interface: You can automate the process of assigning labels to host network interfaces in the configured list of clusters with the LLDP Labeler service. -include::../../common/network/proc-Configuring_LLDP_Labeler.adoc[] +include::../common/network/proc-Configuring_LLDP_Labeler.adoc[] You have added a network label to a host network interface. Newly created logical networks with the same label are automatically assigned to all host network interfaces with that label. Removing a label from a logical network automatically removes that logical network from all host network interfaces with that label. diff --git a/source/documentation/administration_guide/topics/Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning.adoc b/source/documentation/administration_guide/topics/Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning.adoc index 73ae4971233..47afdf6f708 100644 --- a/source/documentation/administration_guide/topics/Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning.adoc +++ b/source/documentation/administration_guide/topics/Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning.adoc @@ -26,7 +26,7 @@ Although network nodes and regular hosts can be used in the same cluster, virtua . Use the Red Hat OpenStack Platform director to deploy the Networker role on the network node. See link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/index#sect-Creating_a_New_Role[Creating a New Role] and https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/index#Standalone-Networker[Networker] in the _Red Hat OpenStack Platform Advanced Overcloud Customization Guide_. ifdef::rhv-doc[] -include::../../common/install/snip-RHEL_repo_steps.adoc[] +include::../common/install/snip-RHEL_repo_steps.adoc[] endif::[] . Install the Openstack Networking hook: + diff --git a/source/documentation/administration_guide/topics/Adding_and_removing_tags.adoc b/source/documentation/administration_guide/topics/Adding_and_removing_tags.adoc index 8136b7e5206..0ddf93900fd 100644 --- a/source/documentation/administration_guide/topics/Adding_and_removing_tags.adoc +++ b/source/documentation/administration_guide/topics/Adding_and_removing_tags.adoc @@ -6,7 +6,7 @@ You can assign tags to and remove tags from hosts, virtual machines, and users. *Adding and Removing Tags to and from Objects* . Select the object(s) you want to tag or untag. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Assign Tags*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Assign Tags*. . Select the check box to assign a tag to the object, or clear the check box to detach the tag from the object. . Click btn:[OK]. diff --git a/source/documentation/administration_guide/topics/Cluster_Optimization_Settings_Explained.adoc b/source/documentation/administration_guide/topics/Cluster_Optimization_Settings_Explained.adoc index 1e0adfbd486..ddff04bc860 100644 --- a/source/documentation/administration_guide/topics/Cluster_Optimization_Settings_Explained.adoc +++ b/source/documentation/administration_guide/topics/Cluster_Optimization_Settings_Explained.adoc @@ -5,7 +5,7 @@ Memory page sharing allows virtual machines to use up to 200% of their allocated memory by utilizing unused memory in other virtual machines. This process is based on the assumption that the virtual machines in your {virt-product-fullname} environment will not all be running at full capacity at the same time, allowing unused memory to be temporarily allocated to a particular virtual machine. :context: cluster_opt_settings -include::../../common/admin/snip-CPU-Considerations.adoc[] +include::../common/admin/snip-CPU-Considerations.adoc[] The table below describes the settings for the *Optimization* tab in the *New Cluster* and *Edit Cluster* windows. diff --git a/source/documentation/administration_guide/topics/Creating_a_New_Cluster.adoc b/source/documentation/administration_guide/topics/Creating_a_New_Cluster.adoc index 6a86fa7ca64..c9e07e751f8 100644 --- a/source/documentation/administration_guide/topics/Creating_a_New_Cluster.adoc +++ b/source/documentation/administration_guide/topics/Creating_a_New_Cluster.adoc @@ -37,4 +37,4 @@ For details, see link:https://access.redhat.com/solutions/634853[]. . Click the *Fencing policy* tab to enable or disable fencing in the cluster, and select fencing options. . Click the *MAC Address Pool* tab to specify a MAC address pool other than the default pool for the cluster. For more options on creating, editing, or removing MAC address pools, see xref:sect-MAC_Address_Pools[]. . Click btn:[OK] to create the cluster and open the *Cluster - Guide Me* window. -. The *Guide Me* window lists the entities that need to be configured for the cluster. Configure these entities or postpone configuration by clicking the *Configure Later* button. Configuration can be resumed by selecting the cluster and clicking *More Actions* (image:../common/images/moreactions.png[]), then clicking *Guide Me*. +. The *Guide Me* window lists the entities that need to be configured for the cluster. Configure these entities or postpone configuration by clicking the *Configure Later* button. Configuration can be resumed by selecting the cluster and clicking *More Actions* (image:common/images/moreactions.png[]), then clicking *Guide Me*. diff --git a/source/documentation/administration_guide/topics/Creating_a_New_Data_Center.adoc b/source/documentation/administration_guide/topics/Creating_a_New_Data_Center.adoc index 6ea19941e5c..03bc43ceadd 100644 --- a/source/documentation/administration_guide/topics/Creating_a_New_Data_Center.adoc +++ b/source/documentation/administration_guide/topics/Creating_a_New_Data_Center.adoc @@ -18,7 +18,7 @@ You can specify a MAC pool range for a cluster. Setting a MAC pool range is no l . Enter the *Name* and *Description* of the data center. . Select the *Storage Type*, *Compatibility Version*, and *Quota Mode* of the data center from the drop-down menus. . Click btn:[OK] to create the data center and open the *Data Center - Guide Me* window. -. The *Guide Me* window lists the entities that need to be configured for the data center. Configure these entities or postpone configuration by clicking the *Configure Later* button. Configuration can be resumed by selecting the data center and clicking *More Actions* (image:../common/images/moreactions.png[]), then clicking *Guide Me*. +. The *Guide Me* window lists the entities that need to be configured for the data center. Configure these entities or postpone configuration by clicking the *Configure Later* button. Configuration can be resumed by selecting the data center and clicking *More Actions* (image:common/images/moreactions.png[]), then clicking *Guide Me*. The new data center will remain *Uninitialized* until a cluster, host, and storage domain are configured for it; use *Guide Me* to configure these entities. diff --git a/source/documentation/administration_guide/topics/Creating_a_bond_device_with_the_lldp_labeler_service.adoc b/source/documentation/administration_guide/topics/Creating_a_bond_device_with_the_lldp_labeler_service.adoc index 9f73037b229..3b0d9863d55 100644 --- a/source/documentation/administration_guide/topics/Creating_a_bond_device_with_the_lldp_labeler_service.adoc +++ b/source/documentation/administration_guide/topics/Creating_a_bond_device_with_the_lldp_labeler_service.adoc @@ -5,7 +5,7 @@ The LLDP Labeler service enables you to create a bond device automatically with NICs with xref:Bond_logical_networks_compatibility[incompatible logical networks] cannot be bonded. -include::../../common/network/proc-Configuring_LLDP_Labeler.adoc[] +include::../common/network/proc-Configuring_LLDP_Labeler.adoc[] . Attach a logical network to the new bond and configure it. See xref:Editing_host_network_interfaces[] for instructions. + diff --git a/source/documentation/administration_guide/topics/Customizing_hosts_with_tags.adoc b/source/documentation/administration_guide/topics/Customizing_hosts_with_tags.adoc index f0b371f0534..73081cebf86 100644 --- a/source/documentation/administration_guide/topics/Customizing_hosts_with_tags.adoc +++ b/source/documentation/administration_guide/topics/Customizing_hosts_with_tags.adoc @@ -6,7 +6,7 @@ You can use tags to store information about your hosts. You can then search for *Customizing hosts with tags* . Click menu:Compute[Hosts] and select a host. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Assign Tags*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Assign Tags*. . Select the check boxes of applicable tags. . Click btn:[OK]. diff --git a/source/documentation/administration_guide/topics/Destroying_a_storage_domain.adoc b/source/documentation/administration_guide/topics/Destroying_a_storage_domain.adoc index 51d7c4977e1..a3e523ac42d 100644 --- a/source/documentation/administration_guide/topics/Destroying_a_storage_domain.adoc +++ b/source/documentation/administration_guide/topics/Destroying_a_storage_domain.adoc @@ -7,6 +7,6 @@ A storage domain encountering errors may not be able to be removed through the n *Destroying a Storage Domain* . Click menu:Storage[Domains]. -. Select the storage domain and click *More Actions* (image:../common/images/moreactions.png[]), then click *Destroy*. +. Select the storage domain and click *More Actions* (image:common/images/moreactions.png[]), then click *Destroy*. . Select the *Approve operation* check box. . Click btn:[OK]. diff --git a/source/documentation/administration_guide/topics/Editing_Vfs_on_NIC.adoc b/source/documentation/administration_guide/topics/Editing_Vfs_on_NIC.adoc index ae71f655f03..97cdc650a36 100644 --- a/source/documentation/administration_guide/topics/Editing_Vfs_on_NIC.adoc +++ b/source/documentation/administration_guide/topics/Editing_Vfs_on_NIC.adoc @@ -1,7 +1,7 @@ [[Editing_VFs_on_NIC]] ==== Configuring virtual functions on a NIC -include::../../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] +include::../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] Single Root I/O Virtualization (SR-IOV) enables you to use each PCIe endpoint as multiple separate devices by using physical functions (PFs) and virtual functions (VFs). A PCIe card can have between one and eight PFs. Each PF can have many VFs. The number of VFs it can have depends on the specific type of PCIe device. diff --git a/source/documentation/administration_guide/topics/Enabling_Passthrough_on_a_vNIC_Profile.adoc b/source/documentation/administration_guide/topics/Enabling_Passthrough_on_a_vNIC_Profile.adoc index 4e35d22dfa1..0259381f211 100644 --- a/source/documentation/administration_guide/topics/Enabling_Passthrough_on_a_vNIC_Profile.adoc +++ b/source/documentation/administration_guide/topics/Enabling_Passthrough_on_a_vNIC_Profile.adoc @@ -1,7 +1,7 @@ [[Enabling_Passthrough_on_a_vNIC_Profile]] ==== Enabling Passthrough on a vNIC Profile -include::../../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] +include::../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] The passthrough property of a vNIC profile enables a vNIC to be directly connected to a virtual function (VF) of an SR-IOV-enabled NIC. The vNIC will then bypass the software network virtualization and connect directly to the VF for direct device assignment. diff --git a/source/documentation/administration_guide/topics/Exporting_a_Virtual_Disk_to_an_OpenStack_Image_Service.adoc b/source/documentation/administration_guide/topics/Exporting_a_Virtual_Disk_to_an_OpenStack_Image_Service.adoc index 5ab4b6df6c6..595d36c6f93 100644 --- a/source/documentation/administration_guide/topics/Exporting_a_Virtual_Disk_to_an_OpenStack_Image_Service.adoc +++ b/source/documentation/administration_guide/topics/Exporting_a_Virtual_Disk_to_an_OpenStack_Image_Service.adoc @@ -9,7 +9,7 @@ Virtual disks can only be exported if they do not have multiple volumes, are not ==== . Click menu:Storage[Disks] and select the disks to export. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Export*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Export*. . From the *Domain Name* drop-down list, select the OpenStack Image Service to which the disks will be exported. . From the *Quota* drop-down list, select a quota for the disks if a quota is to be applied. . Click btn:[OK]. diff --git a/source/documentation/administration_guide/topics/Force_Removing_a_Data_Center.adoc b/source/documentation/administration_guide/topics/Force_Removing_a_Data_Center.adoc index 6df8cc7b5f1..cfddd3dac15 100644 --- a/source/documentation/administration_guide/topics/Force_Removing_a_Data_Center.adoc +++ b/source/documentation/administration_guide/topics/Force_Removing_a_Data_Center.adoc @@ -11,7 +11,7 @@ It may be necessary to *Destroy* a corrupted storage domain before you can *Forc *Force Removing a Data Center* . Click menu:Compute[Data Centers] and select the data center to remove. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Force Remove*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Force Remove*. . Select the *Approve operation* check box. . Click btn:[OK] diff --git a/source/documentation/administration_guide/topics/Importing_an_Unregistered_Disk_Image.adoc b/source/documentation/administration_guide/topics/Importing_an_Unregistered_Disk_Image.adoc index 2a04c62c8bf..c8f9e85e143 100644 --- a/source/documentation/administration_guide/topics/Importing_an_Unregistered_Disk_Image.adoc +++ b/source/documentation/administration_guide/topics/Importing_an_Unregistered_Disk_Image.adoc @@ -13,7 +13,7 @@ Only QEMU-compatible disks can be imported into the {engine-name}. . Click menu:Storage[Domains]. . Click the storage domain's name. This opens the details view. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Scan Disks* so that the {engine-name} can identify unregistered disks. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Scan Disks* so that the {engine-name} can identify unregistered disks. . Click the *Disk Import* tab. . Select one or more disk images and click *Import*. . Select the appropriate *Disk Profile* for each disk. diff --git a/source/documentation/administration_guide/topics/Manually_fencing_or_isolating_a_nonresponsive_host.adoc b/source/documentation/administration_guide/topics/Manually_fencing_or_isolating_a_nonresponsive_host.adoc index 107de6e4c45..da9cd29b8a9 100644 --- a/source/documentation/administration_guide/topics/Manually_fencing_or_isolating_a_nonresponsive_host.adoc +++ b/source/documentation/administration_guide/topics/Manually_fencing_or_isolating_a_nonresponsive_host.adoc @@ -13,7 +13,7 @@ Do not use the *Confirm host has been rebooted* option unless you have manually . In the Administration Portal, click menu:Compute[Hosts] and confirm the host's status is `Non Responsive`. . Manually reboot the host. This could mean physically entering the lab and rebooting the host. -. In the Administration Portal, select the host and click *More Actions* (image:../common/images/moreactions.png[]), then click *Confirm 'Host has been Rebooted'*. +. In the Administration Portal, select the host and click *More Actions* (image:common/images/moreactions.png[]), then click *Confirm 'Host has been Rebooted'*. . Select the *Approve Operation* check box and click btn:[OK]. . If your hosts take an unusually long time to boot, you can set `ServerRebootTimeout` to specify how many seconds to wait before determining that the host is `Non Responsive`: + diff --git a/source/documentation/administration_guide/topics/Re-initializing_a_Data_Center.adoc b/source/documentation/administration_guide/topics/Re-initializing_a_Data_Center.adoc index 86e2497fd2c..383536be5b9 100644 --- a/source/documentation/administration_guide/topics/Re-initializing_a_Data_Center.adoc +++ b/source/documentation/administration_guide/topics/Re-initializing_a_Data_Center.adoc @@ -10,7 +10,7 @@ You can import any backup or exported virtual machines or templates into your ne . Click menu:Compute[Data Centers] and select the data center. . Ensure that any storage domains attached to the data center are in maintenance mode. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Re-Initialize Data Center*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Re-Initialize Data Center*. . The *Data Center Re-Initialize* window lists all available (detached; in maintenance mode) storage domains. Click the radio button for the storage domain you are adding to the data center. . Select the *Approve operation* check box. . Click btn:[OK]. diff --git a/source/documentation/administration_guide/topics/Reclaiming_Virtual_Disk_Space.adoc b/source/documentation/administration_guide/topics/Reclaiming_Virtual_Disk_Space.adoc index 3d301478af0..04b284139d5 100644 --- a/source/documentation/administration_guide/topics/Reclaiming_Virtual_Disk_Space.adoc +++ b/source/documentation/administration_guide/topics/Reclaiming_Virtual_Disk_Space.adoc @@ -20,7 +20,7 @@ Perform this operation before cloning a virtual machine, creating a template bas . Click menu:Compute[Virtual Machines] and shut down the required virtual machine. . Click the virtual machine's name. This opens the details view. . Click the *Disks* tab. Ensure that the disk's status is `OK`. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Sparsify*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Sparsify*. . Click btn:[OK]. A `Started to sparsify` event appears in the *Events* tab during the sparsify operation and the disk's status displays as `Locked`. When the operation is complete, a `Sparsified successfully` event appears in the *Events* tab and the disk's status displays as `OK`. The unused disk space has been returned to the host and is available for use by other virtual machines. diff --git a/source/documentation/administration_guide/topics/Updating_OVFs.adoc b/source/documentation/administration_guide/topics/Updating_OVFs.adoc index 492217c92fe..12713528669 100644 --- a/source/documentation/administration_guide/topics/Updating_OVFs.adoc +++ b/source/documentation/administration_guide/topics/Updating_OVFs.adoc @@ -5,6 +5,6 @@ By default, OVFs are updated every 60 minutes. However, if you have imported an *Updating OVFs* . Click menu:Storage[Domains]. -. Select the storage domain and click *More Actions* (image:../common/images/moreactions.png[]), then click *Update OVFs*. +. Select the storage domain and click *More Actions* (image:common/images/moreactions.png[]), then click *Update OVFs*. + The OVFs are updated and a message appears in *Events*. diff --git a/source/documentation/administration_guide/topics/Updating_a_host_between_minor_releases.adoc b/source/documentation/administration_guide/topics/Updating_a_host_between_minor_releases.adoc index d8a7a50c263..51d94802714 100644 --- a/source/documentation/administration_guide/topics/Updating_a_host_between_minor_releases.adoc +++ b/source/documentation/administration_guide/topics/Updating_a_host_between_minor_releases.adoc @@ -6,12 +6,12 @@ You can update xref:Updating_all_hosts_in_a_cluster_admin[all hosts in a cluster], or update xref:Updating_Individual_Hosts_admin[individual hosts]. -include::../../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] You should update the hosts from the Administration Portal. However, you can update the hosts using `dnf upgrade` instead: -include::../../common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+1] :admin_minor_updates!: diff --git a/source/documentation/common/arch/con-Self-hosted_Engine_Architecture.adoc b/source/documentation/common/arch/con-Self-hosted_Engine_Architecture.adoc index bd3d812d3d6..9ca6cd81267 100644 --- a/source/documentation/common/arch/con-Self-hosted_Engine_Architecture.adoc +++ b/source/documentation/common/arch/con-Self-hosted_Engine_Architecture.adoc @@ -12,4 +12,4 @@ The minimum setup of a self-hosted engine environment includes: * One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. .Self-Hosted Engine {virt-product-fullname} Architecture -image::../common/images/RHV_SHE_ARCHITECTURE1.png[Self-Hosted Engine {virt-product-fullname} Architecture] +image::common/images/RHV_SHE_ARCHITECTURE1.png[Self-Hosted Engine {virt-product-fullname} Architecture] diff --git a/source/documentation/common/arch/con-Standalone_Manager_Architecture.adoc b/source/documentation/common/arch/con-Standalone_Manager_Architecture.adoc index 97fb00ba1c0..488f37bae48 100644 --- a/source/documentation/common/arch/con-Standalone_Manager_Architecture.adoc +++ b/source/documentation/common/arch/con-Standalone_Manager_Architecture.adoc @@ -12,4 +12,4 @@ The minimum setup for a standalone {engine-name} environment includes: * One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. .Standalone {engine-name} {virt-product-fullname} Architecture -image::../common/images/RHV_STANDARD_ARCHITECTURE1.png[Standalone {engine-name} {virt-product-fullname} Architecture] +image::common/images/RHV_STANDARD_ARCHITECTURE1.png[Standalone {engine-name} {virt-product-fullname} Architecture] diff --git a/source/documentation/common/install/proc-Adding_standard_hosts_to_the_Manager.adoc b/source/documentation/common/install/proc-Adding_standard_hosts_to_the_Manager.adoc index 9e03d178532..9350be03151 100644 --- a/source/documentation/common/install/proc-Adding_standard_hosts_to_the_Manager.adoc +++ b/source/documentation/common/install/proc-Adding_standard_hosts_to_the_Manager.adoc @@ -19,4 +19,4 @@ Adding a host to your {virt-product-fullname} environment can take some time, as . Click btn:[OK]. -The new host displays in the list of hosts with a status of `Installing`, and you can view the progress of the installation in the *Events* section of the *Notification Drawer* (image:../common/images/EventsIcon.png[]). After a brief delay the host status changes to `Up`. +The new host displays in the list of hosts with a status of `Installing`, and you can view the progress of the installation in the *Events* section of the *Notification Drawer* (image:common/images/EventsIcon.png[]). After a brief delay the host status changes to `Up`. diff --git a/source/documentation/common/she/proc-Maintaining_the_Self-Hosted_Engine.adoc b/source/documentation/common/she/proc-Maintaining_the_Self-Hosted_Engine.adoc index 99fd6f78df5..053c5d6e635 100644 --- a/source/documentation/common/she/proc-Maintaining_the_Self-Hosted_Engine.adoc +++ b/source/documentation/common/she/proc-Maintaining_the_Self-Hosted_Engine.adoc @@ -52,10 +52,10 @@ Stop the high-availability agents on all self-hosted engine nodes in the cluster . Put all of the self-hosted engine nodes into global maintenance mode: .. In the Administration Portal, click menu:Compute[Hosts] and select any self-hosted engine node. -.. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Enable Global HA Maintenance*. +.. Click *More Actions* (image:common/images/moreactions.png[]), then click *Enable Global HA Maintenance*. . After you have completed any maintenance tasks, disable the maintenance mode: .. In the Administration Portal, click menu:Compute[Hosts] and select any self-hosted engine node. -.. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Disable Global HA Maintenance*. +.. Click *More Actions* (image:common/images/moreactions.png[]), then click *Disable Global HA Maintenance*. .Setting the global maintenance mode from the command line diff --git a/source/documentation/common/sriov/conc-Additional_Considerations_Device_Assignment.adoc b/source/documentation/common/sriov/conc-Additional_Considerations_Device_Assignment.adoc index 8d8fb7257f5..fe29a22492a 100644 --- a/source/documentation/common/sriov/conc-Additional_Considerations_Device_Assignment.adoc +++ b/source/documentation/common/sriov/conc-Additional_Considerations_Device_Assignment.adoc @@ -19,7 +19,7 @@ Refer to vendor specification for determining processor-based and controller hub In addition, any PCIe switch or bridge within the I/O topology also requires ACS support, otherwise it may extend the IOMMU group. [id='Summary_of_Hardware_Considerations_for_Device_Assignment'] -=== Summary of Hardware Considerations for Device Assignment +== Summary of Hardware Considerations for Device Assignment * CPU must support IOMMU (for example, VT-d or AMD-Vi). IBM POWER8 supports IOMMU by default. * Firmware must support IOMMU. diff --git a/source/documentation/common/sriov/conc-Hardware_Considerations.adoc b/source/documentation/common/sriov/conc-Hardware_Considerations.adoc index 59c9fad2f8c..2eb951a9575 100644 --- a/source/documentation/common/sriov/conc-Hardware_Considerations.adoc +++ b/source/documentation/common/sriov/conc-Hardware_Considerations.adoc @@ -8,7 +8,7 @@ The PCIe specification supports greater numbers of VFs through the implementatio The system firmware (BIOS or UEFI) allocates resources, including memory, I/O port apertures, and PCIe bus number ranges, for the PCIe topology. As such, SR-IOV must be supported and enabled by the firmware in order to allocate sufficient resources. -=== Summary of Hardware Considerations for SR-IOV +== Summary of Hardware Considerations for SR-IOV * Firmware (BIOS or UEFI) must support SR-IOV. Check if the extension is enabled by default. If not, enable it manually. This is similar to enabling the virtualization extension (VT-d or AMD-Vi). Refer to vendor manuals for specific details. * Root ports, or ports immediately upstream of the PCIe device (such as a PCIe switch), must support ARI. diff --git a/source/documentation/common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc b/source/documentation/common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc index 8f17c2f46c5..80998118af5 100644 --- a/source/documentation/common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc +++ b/source/documentation/common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc @@ -1,7 +1,7 @@ [id='Changing_Virtual_Machine_Cluster_Compatibility_{context}'] = Changing Virtual Machine Cluster Compatibility -After updating a cluster's compatibility version, you must update the cluster compatibility version of all running or suspended virtual machines by rebooting them from the Administration Portal, or using the REST API, instead of from within the guest operating system. Virtual machines that require a reboot are marked with the pending changes icon (image:../common/images/pendingchanges.png[]). +After updating a cluster's compatibility version, you must update the cluster compatibility version of all running or suspended virtual machines by rebooting them from the Administration Portal, or using the REST API, instead of from within the guest operating system. Virtual machines that require a reboot are marked with the pending changes icon (image:common/images/pendingchanges.png[]). ifdef::SHE_upgrade[The {engine-name} virtual machine does not need to be rebooted.] diff --git a/source/documentation/common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc b/source/documentation/common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc index 3fc78fcd204..0dc7bcf5103 100644 --- a/source/documentation/common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc +++ b/source/documentation/common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc @@ -26,7 +26,7 @@ An error message might warn that some virtual machines and templates are incorre ==== ifdef::admin[] -After updating a cluster's compatibility version, you must update the cluster compatibility version of all running or suspended virtual machines by rebooting them from the Administration Portal, or using the REST API, instead of from within the guest operating system. Virtual machines that require a reboot are marked with the pending changes icon (image:../common/images/pendingchanges.png[]). You cannot change the cluster compatibility version of a virtual machine snapshot that is in preview. You must first commit or undo the preview. +After updating a cluster's compatibility version, you must update the cluster compatibility version of all running or suspended virtual machines by rebooting them from the Administration Portal, or using the REST API, instead of from within the guest operating system. Virtual machines that require a reboot are marked with the pending changes icon (image:common/images/pendingchanges.png[]). You cannot change the cluster compatibility version of a virtual machine snapshot that is in preview. You must first commit or undo the preview. In a self-hosted engine environment, the {engine-name} virtual machine does not need to be restarted. diff --git a/source/documentation/common/upgrade/proc-Updating_Individual_Hosts.adoc b/source/documentation/common/upgrade/proc-Updating_Individual_Hosts.adoc index 55b5df65001..a435bb4a4ab 100644 --- a/source/documentation/common/upgrade/proc-Updating_Individual_Hosts.adoc +++ b/source/documentation/common/upgrade/proc-Updating_Individual_Hosts.adoc @@ -56,7 +56,7 @@ endif::[] . Click menu:Installation[Check for Upgrade] and click btn:[OK]. + -Open the *Notification Drawer* (image:../common/images/EventsIcon.png[]) and expand the *Events* section to see the result. +Open the *Notification Drawer* (image:common/images/EventsIcon.png[]) and expand the *Events* section to see the result. . If an update is available, click menu:Installation[Upgrade]. diff --git a/source/documentation/common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc b/source/documentation/common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc index 79882989eab..ba1b96701cd 100644 --- a/source/documentation/common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc +++ b/source/documentation/common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc @@ -25,7 +25,7 @@ include::snip-Host_update_limitations.adoc[] . Review the summary of the hosts and virtual machines that will be affected. . Click *Upgrade*. -You can track the progress of host updates in the menu:Compute[Hosts] view, and in the *Events* section of the *Notification Drawer* (image:../common/images/EventsIcon.png[]). +You can track the progress of host updates in the menu:Compute[Hosts] view, and in the *Events* section of the *Notification Drawer* (image:common/images/EventsIcon.png[]). You can track the progress of individual virtual machine migrations in the *Status* column of the menu:Compute[Virtual Machines] view. In large environments, you may need to filter the results to show a particular group of virtual machines. diff --git a/source/documentation/data_warehouse_guide/chap-Installing_and_Configuring_Data_Warehouse.adoc b/source/documentation/data_warehouse_guide/chap-Installing_and_Configuring_Data_Warehouse.adoc index 5a35d88027b..ea82cccb128 100644 --- a/source/documentation/data_warehouse_guide/chap-Installing_and_Configuring_Data_Warehouse.adoc +++ b/source/documentation/data_warehouse_guide/chap-Installing_and_Configuring_Data_Warehouse.adoc @@ -5,9 +5,9 @@ include::topics/Overview_of_Configuring_Data_Warehouse.adoc[leveloffset=+1] -include::../common/database/proc-Installing_and_Configuring_Data_Warehouse_on_a_Separate_Machine.adoc[leveloffset=+1] +include::common/database/proc-Installing_and_Configuring_Data_Warehouse_on_a_Separate_Machine.adoc[leveloffset=+1] :context: DWH_admin -include::../common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+1] +include::common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+1] include::topics/Changing_the_Data_Warehouse_Sampling_Scale.adoc[leveloffset=+1] diff --git a/source/documentation/data_warehouse_guide/common b/source/documentation/data_warehouse_guide/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/data_warehouse_guide/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/data_warehouse_guide/index.adoc b/source/documentation/data_warehouse_guide/index.adoc index 0422e82d5d4..f48260624a9 100644 --- a/source/documentation/data_warehouse_guide/index.adoc +++ b/source/documentation/data_warehouse_guide/index.adoc @@ -1,5 +1,5 @@ = Data Warehouse Guide -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :imagesdir: images :context: DWH :DWH: @@ -8,7 +8,7 @@ include::../common/collateral_files/ovirt-attributes.adoc[] [discrete] = Data Warehouse Guide -include::../common/database/snip-About_Data_Warehouse.adoc[] +include::common/database/snip-About_Data_Warehouse.adoc[] include::chap-Installing_and_Configuring_Data_Warehouse.adoc[leveloffset=+1] diff --git a/source/documentation/disaster_recovery_guide/common b/source/documentation/disaster_recovery_guide/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/disaster_recovery_guide/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/disaster_recovery_guide/index.adoc b/source/documentation/disaster_recovery_guide/index.adoc index 6e0c0855c73..08b6ff3ea73 100644 --- a/source/documentation/disaster_recovery_guide/index.adoc +++ b/source/documentation/disaster_recovery_guide/index.adoc @@ -1,5 +1,5 @@ = Disaster Recovery Guide -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :imagesdir: images :toclevels: 4 diff --git a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/index.adoc b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/index.adoc index c78a6fe329e..6bc1f40fa7d 100644 --- a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/index.adoc +++ b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/index.adoc @@ -1,5 +1,5 @@ = Installing {virt-product-fullname} as a self-hosted engine using the Cockpit web interface -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :context: SHE_cockpit_deploy :SHE_cockpit_deploy: @@ -17,10 +17,10 @@ A storage domain dedicated to the {engine-name} virtual machine is referred to a See the link:{URL_downstream_virt_product_docs}html/planning_and_prerequisites_guide/[_Planning and Prerequisites Guide_] for information on environment options and recommended configuration. See link:{URL_downstream_virt_product_docs}html-single/planning_and_prerequisites_guide/#self-hosted-engine-recommendations[Self-Hosted Engine Recommendations] for configuration specific to a self-hosted engine environment. -include::../common/arch/con-RHV_key_components.adoc[] +include::common/arch/con-RHV_key_components.adoc[] [discrete] -include::../common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+1] +include::common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+1] [id='Install_overview_SHE_cockpit_deploy'] == Installation Overview @@ -32,7 +32,7 @@ The self-hosted engine installation uses Ansible and the {engine-appliance-name} * Installing and configuring the {virt-product-fullname} {engine-name} on that virtual machine * Configuring the self-hosted engine storage domain -include::../common/install/snip-rhvm-appliance-note.adoc[] +include::common/install/snip-rhvm-appliance-note.adoc[] Installing a self-hosted engine environment involves the following steps: @@ -70,11 +70,11 @@ Keep the environment up to date. Since bug fixes for known issues are frequently ==== -include::../common/prereqs/asm-Requirements.adoc[leveloffset=+1] +include::common/prereqs/asm-Requirements.adoc[leveloffset=+1] -include::../common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] -include::../common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] +include::common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] // Adding context back after assembly :context: SHE_cockpit_deploy @@ -82,29 +82,29 @@ include::../common/install/assembly-Installing_the_self-hosted_engine_deployment == Installing the {virt-product-fullname} {engine-name} :context: install_RHVM -include::../common/she/proc_Manually_installing_the_appliance.adoc[leveloffset=+2] +include::common/she/proc_Manually_installing_the_appliance.adoc[leveloffset=+2] -include::../common/install/proc-Deploying_the_Self-Hosted_Engine_Using_Cockpit.adoc[leveloffset=+2] +include::common/install/proc-Deploying_the_Self-Hosted_Engine_Using_Cockpit.adoc[leveloffset=+2] Enabling the {virt-product-fullname} {engine-name} repositories is not part of the automated installation. Log in to the {engine-name} virtual machine to enable the repositories: -include::../common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] +include::common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] Log in to the Administration Portal, where you can add hosts and storage to the environment: -include::../common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] +include::common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] //end sect // Adding context back after assembly :context: SHE_cockpit_deploy -include::../common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] +include::common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] :numbered!: [appendix] -include::../common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment.adoc[leveloffset=+1] +include::common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment.adoc[leveloffset=+1] [appendix] [id='Migrating_to_remote_servers_SHE_cockpit_deploy'] @@ -112,25 +112,25 @@ include::../common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment. Although you cannot configure remote databases and services during the automated installation, you can migrate them to a remote server post-installation. -include::../common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+2] +include::common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+2] // Adding context back after assembly :context: SHE_cockpit_deploy -include::../common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+2] +include::common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+2] // Adding context back after assembly :context: SHE_cockpit_deploy -include::../common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+2] +include::common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+2] //end sect [appendix] -include::../common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] +include::common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] [appendix] -include::../common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] +include::common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] [appendix] -include::../common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] [appendix] == Legal notice diff --git a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.adoc b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.adoc index a1a4c934405..0ec665a777a 100644 --- a/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.adoc +++ b/source/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.adoc @@ -1,5 +1,5 @@ = Installing {virt-product-fullname} as a self-hosted engine using the command line -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :context: SHE_cli_deploy :SHE_cli_deploy: @@ -15,10 +15,10 @@ A storage domain dedicated to the {engine-name} virtual machine is referred to a See the link:{URL_downstream_virt_product_docs}/planning_and_prerequisites_guide/[_Planning and Prerequisites Guide_] for information on environment options and recommended configuration. See link:{URL_downstream_virt_product_docs}/planning_and_prerequisites_guide/#self-hosted-engine-recommendations[Self-Hosted Engine Recommendations] for configuration specific to a self-hosted engine environment. -include::../common/arch/con-RHV_key_components.adoc[] +include::common/arch/con-RHV_key_components.adoc[] [discrete] -include::../common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+1] +include::common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+1] [id='Install_overview_SHE_cli_deploy'] == Installation Overview @@ -30,7 +30,7 @@ The self-hosted engine installation uses Ansible and the {engine-appliance-name} * Installing and configuring the {virt-product-fullname} {engine-name} on that virtual machine * Configuring the self-hosted engine storage domain -include::../common/install/snip-rhvm-appliance-note.adoc[] +include::common/install/snip-rhvm-appliance-note.adoc[] Installing a self-hosted engine environment involves the following steps: @@ -66,11 +66,11 @@ Keep the environment up to date. Since bug fixes for known issues are frequently ==== -include::../common/prereqs/asm-Requirements.adoc[leveloffset=+1] +include::common/prereqs/asm-Requirements.adoc[leveloffset=+1] -include::../common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] -include::../common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] +include::common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] // Adding context back after assembly :context: SHE_cli_deploy @@ -78,29 +78,29 @@ include::../common/install/assembly-Installing_the_self-hosted_engine_deployment == Installing the {virt-product-fullname} {engine-name} :context: install_RHVM -include::../common/she/proc_Manually_installing_the_appliance.adoc[leveloffset=+2] +include::common/she/proc_Manually_installing_the_appliance.adoc[leveloffset=+2] -include::../common/install/proc-Deploying_the_Self-Hosted_Engine_Using_the_CLI.adoc[leveloffset=+2] +include::common/install/proc-Deploying_the_Self-Hosted_Engine_Using_the_CLI.adoc[leveloffset=+2] Enabling the {virt-product-fullname} {engine-name} repositories is not part of the automated installation. Log in to the {engine-name} virtual machine to enable the repositories: -include::../common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] +include::common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] Log in to the Administration Portal, where you can add hosts and storage to the environment: -include::../common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] +include::common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] //end sect // Adding context back after assembly :context: SHE_cli_deploy -include::../common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] +include::common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] :numbered!: [appendix] -include::../common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment.adoc[leveloffset=+1] +include::common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment.adoc[leveloffset=+1] [appendix] [id='Migrating_to_remote_servers_SHE_cli_deploy'] @@ -108,25 +108,25 @@ include::../common/she/assembly-Troubleshooting_a_self-hosted_engine_deployment. Although you cannot configure remote databases and services during the automated installation, you can migrate them to a separate server post-installation. -include::../common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+2] +include::common/database/proc-Migrating_the_self-hosted_engine_database_to_a_remote_server.adoc[leveloffset=+2] // Adding context back after assembly :context: SHE_cli_deploy -include::../common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+2] +include::common/database/assembly-Migrating_Data_Warehouse_to_a_Separate_Machine.adoc[leveloffset=+2] // Adding context back after assembly :context: SHE_cli_deploy -include::../common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+2] +include::common/admin/proc-Migrating_the_Websocket_Proxy_to_a_Separate_Machine.adoc[leveloffset=+2] //end sect [appendix] -include::../common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] +include::common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] [appendix] -include::../common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] +include::common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] [appendix] -include::../common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] [appendix] == Legal notice diff --git a/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common b/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.adoc b/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.adoc index 0e7625d864e..de9829ef29a 100644 --- a/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.adoc +++ b/source/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.adoc @@ -1,5 +1,5 @@ = Installing {virt-product-fullname} as a standalone {engine-name} with local databases -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :context: SM_localDB_deploy :SM_localDB_deploy: @@ -13,10 +13,10 @@ In a local database environment, the {engine-name} database and Data Warehouse d See the link:{URL_downstream_virt_product_docs}html/planning_and_prerequisites_guide/[_Planning and Prerequisites Guide_] for information on environment options and recommended configuration. -include::../common/arch/con-RHV_key_components.adoc[] +include::common/arch/con-RHV_key_components.adoc[] [discrete] -include::../common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+1] +include::common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+1] [id='Install_overview_SM_localDB_deploy'] == Installation Overview @@ -51,7 +51,7 @@ Keep the environment up to date. See link:https://access.redhat.com/articles/297 ==== -include::../common/prereqs/asm-Requirements.adoc[leveloffset=+1] +include::common/prereqs/asm-Requirements.adoc[leveloffset=+1] [id='Installing_the_Red_Hat_Virtualization_Manager_SM_localDB_deploy'] == Installing the {virt-product-fullname} {engine-name} @@ -74,22 +74,22 @@ This machine must meet the minimum xref:hardware-requirements_SM_localDB_deploy[ By default, the {virt-product-fullname} {engine-name}'s configuration script, `engine-setup`, creates and configures the {engine-name} database and Data Warehouse database automatically on the {engine-name} machine. To set up either database, or both, manually, see xref:Preparing_a_Local_Manually-Configured_PostgreSQL_Database_SM_localDB_deploy[] before configuring the {engine-name}. -include::../common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] +include::common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] -include::../common/install/proc-Configuring_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+2] +include::common/install/proc-Configuring_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+2] Log in to the Administration Portal, where you can add hosts and storage to the environment: -include::../common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] +include::common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] //end sect // Adding context back after assembly :context: SM_localDB_deploy -include::../common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] +include::common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] :numbered!: @@ -97,18 +97,18 @@ include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffs :context: SM_localDB_deploy [appendix] -include::../common/database/proc-Preparing_a_Local_Manually-Configured_PostgreSQL_Database.adoc[leveloffset=+1] +include::common/database/proc-Preparing_a_Local_Manually-Configured_PostgreSQL_Database.adoc[leveloffset=+1] //adding context back :context: SM_localDB_deploy [appendix] -include::../common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] +include::common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] [appendix] -include::../common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] +include::common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] [appendix] -include::../common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] [appendix] == Legal notice diff --git a/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common b/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/index.adoc b/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/index.adoc index daaff7dc0ee..c52053edfe7 100644 --- a/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/index.adoc +++ b/source/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/index.adoc @@ -1,5 +1,5 @@ = Installing {virt-product-fullname} as a standalone {engine-name} with remote databases -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :context: SM_remoteDB_deploy :SM_remoteDB_deploy: @@ -13,10 +13,10 @@ To install the {engine-name} with a remote {engine-name} database, manually crea See the link:{URL_downstream_virt_product_docs}html-single/planning_and_prerequisites_guide/index[_Planning and Prerequisites Guide_] for information on environment options and recommended configuration. -include::../common/arch/con-RHV_key_components.adoc[] +include::common/arch/con-RHV_key_components.adoc[] [discrete] -include::../common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+1] +include::common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+1] [id='Install_overview_SM_remoteDB_deploy'] == Installation Overview @@ -54,7 +54,7 @@ Keep the environment up to date. Since bug fixes for known issues are frequently ==== -include::../common/prereqs/asm-Requirements.adoc[leveloffset=+1] +include::common/prereqs/asm-Requirements.adoc[leveloffset=+1] [id='Installing_the_Red_Hat_Virtualization_Manager_SM_remoteDB_deploy'] == Installing the {virt-product-fullname} {engine-name} @@ -69,34 +69,34 @@ This machine must meet the minimum xref:hardware-requirements_SM_remoteDB_deploy . Install a second {enterprise-linux} machine to use for the databases. This machine will be referred to as the remote server. -include::../common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] +include::common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+2] Before configuring the {virt-product-fullname} {engine-name}, you must manually configure the {engine-name} database on the remote server. You can also use this procedure to manually configure the Data Warehouse database if you do not want the Data Warehouse setup script to configure it automatically. -include::../common/database/proc-Preparing_a_Remote_PostgreSQL_Database.adoc[leveloffset=+2] +include::common/database/proc-Preparing_a_Remote_PostgreSQL_Database.adoc[leveloffset=+2] // Adding context back after assembly :context: install_RHVM -include::../common/install/proc-Configuring_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+2] +include::common/install/proc-Configuring_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+2] Install the Data Warehouse service and database on the remote server: -include::../common/database/proc-Installing_and_Configuring_Data_Warehouse_on_a_Separate_Machine.adoc[leveloffset=+2] +include::common/database/proc-Installing_and_Configuring_Data_Warehouse_on_a_Separate_Machine.adoc[leveloffset=+2] // Adding context back after assembly :context: install_RHVM Log in to the Administration Portal, where you can add hosts and storage to the environment: -include::../common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] +include::common/admin/proc-Connecting_to_the_Administration_Portal.adoc[leveloffset=+2] //end sect // Adding context back after assembly :context: SM_remoteDB_deploy -include::../common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] +include::common/install/assembly-Installing_Hosts_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] -include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffset=+1] :numbered!: @@ -104,16 +104,16 @@ include::../common/storage/assembly-Adding_Storage_Domains_to_RHV.adoc[leveloffs :context: SM_remoteDB_deploy [appendix] -include::../common/install/proc-Installing_the_Websocket_Proxy_on_a_different_host.adoc[leveloffset=+1] +include::common/install/proc-Installing_the_Websocket_Proxy_on_a_different_host.adoc[leveloffset=+1] [appendix] -include::../common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] +include::common/install/appe-Set_up_Cinderlib.adoc[leveloffset=+1] [appendix] -include::../common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] +include::common/install/proc-Configuring_a_Host_for_PCI_Passthrough.adoc[leveloffset=+1] [appendix] -include::../common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/admin/proc-Removing_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] [appendix] == Legal notice diff --git a/source/documentation/introduction_to_the_vm_portal/chap-Accessing_the_VM_Portal.adoc b/source/documentation/introduction_to_the_vm_portal/chap-Accessing_the_VM_Portal.adoc index ca947baa9f9..219010d46bb 100644 --- a/source/documentation/introduction_to_the_vm_portal/chap-Accessing_the_VM_Portal.adoc +++ b/source/documentation/introduction_to_the_vm_portal/chap-Accessing_the_VM_Portal.adoc @@ -3,9 +3,9 @@ include::topics/What_is_the_VM_Portal.adoc[][leveloffset=+1] -include::../common/prereqs/ref-Manager_Browser_Requirements.adoc[leveloffset=+1] +include::common/prereqs/ref-Manager_Browser_Requirements.adoc[leveloffset=+1] -include::../common/prereqs/ref-Manager_Client_Requirements.adoc[leveloffset=+1] +include::common/prereqs/ref-Manager_Client_Requirements.adoc[leveloffset=+1] include::topics/Installing_the_CA_certificate.adoc[leveloffset=+1] diff --git a/source/documentation/introduction_to_the_vm_portal/common b/source/documentation/introduction_to_the_vm_portal/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/introduction_to_the_vm_portal/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/introduction_to_the_vm_portal/index.adoc b/source/documentation/introduction_to_the_vm_portal/index.adoc index cc915f46c5c..d9b96fbc588 100644 --- a/source/documentation/introduction_to_the_vm_portal/index.adoc +++ b/source/documentation/introduction_to_the_vm_portal/index.adoc @@ -1,5 +1,5 @@ = Introduction to the VM Portal -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] :context: VM_portal :VM_portal: diff --git a/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common b/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/index.adoc b/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/index.adoc index 44a588fae1c..415434cc2f8 100644 --- a/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/index.adoc +++ b/source/documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/index.adoc @@ -1,5 +1,5 @@ = Migrating from a standalone {engine-name} to a self-hosted engine -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] // Make sure Jekyll displays a guide title [discrete] @@ -13,10 +13,10 @@ You can convert a standalone {virt-product-fullname} {engine-name} to a self-hos The difference between the two environment types is explained below: [discrete] -include::../common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+2] +include::common/arch/con-Standalone_Manager_Architecture.adoc[leveloffset=+2] [discrete] -include::../common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+2] +include::common/arch/con-Self-hosted_Engine_Architecture.adoc[leveloffset=+2] [id='Migration_overview'] == Migration Overview @@ -56,33 +56,33 @@ This procedure assumes that you have access and can make changes to the original * The management network (*ovirtmgmt* by default) must be configured as a *VM network*, so that it can manage the {engine-name} virtual machine. -include::../common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] +include::common/install/assembly-Installing_the_self-hosted_engine_deployment_host.adoc[leveloffset=+1] // Adding context back after this assembly, which includes its own context. There's probably a better way that assemblies within assemblies is meant to be done. :context: migrating_to_SHE Although the existing storage domains will be migrated from the standalone {engine-name}, you must prepare additional storage for a self-hosted engine storage domain that is dedicated to the {engine-name} virtual machine. -include::../common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] +include::common/storage/assembly-Preparing_Storage_for_RHV.adoc[leveloffset=+1] Before backing up the {engine-name}, ensure it is updated to the latest minor version. The {engine-name} version in the backup file must match the version of the new {engine-name}. -include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/backup-restore/proc-Backing_up_the_Original_Manager.adoc[leveloffset=+1] +include::common/backup-restore/proc-Backing_up_the_Original_Manager.adoc[leveloffset=+1] After backing up the {engine-name}, deploy a new self-hosted engine and restore the backup on the new virtual machine. -include::../common/backup-restore/proc-Restoring_the_Backup_on_a_New_Self-hosted_Engine.adoc[leveloffset=+1] +include::common/backup-restore/proc-Restoring_the_Backup_on_a_New_Self-hosted_Engine.adoc[leveloffset=+1] When the deployment is complete, log in to the new {engine-name} virtual machine and enable the required repositories. -include::../common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+1] +include::common/install/proc-Enabling_the_Red_Hat_Virtualization_Manager_Repositories.adoc[leveloffset=+1] The {virt-product-fullname} {engine-name} has been migrated to a self-hosted engine setup. The {engine-name} is now operating on a virtual machine on the new self-hosted engine node. The hosts will be running in the new environment, but cannot host the {engine-name} virtual machine. You can convert some or all of these hosts to self-hosted engine nodes. -include::../common/install/proc-Reinstalling_an_Existing_Host_as_a_Self-Hosted_Engine_Node.adoc[leveloffset=+1] +include::common/install/proc-Reinstalling_an_Existing_Host_as_a_Self-Hosted_Engine_Node.adoc[leveloffset=+1] After reinstalling the hosts as self-hosted engine nodes, you can check the status of the new environment by running the following command on one of the nodes: diff --git a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-0.adoc b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-0.adoc index b55cb937268..f22f4b55545 100644 --- a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-0.adoc +++ b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-0.adoc @@ -41,7 +41,7 @@ Upgrading your environment from 4.0 to 4.3 involves the following steps: . xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-0_remote_db[Replace SHA-1 certificates with SHA-256 certificates] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.0/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.0. @@ -49,19 +49,19 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_Remote_Databases.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_Remote_Databases.adoc[leveloffset=+1] You can now upgrade the {engine-name} to 4.2. -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] You must now update the hosts before you can update the cluster and data center compatibility versions. -include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] :4-0_remote_db!: @@ -70,38 +70,38 @@ include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1 You can now change the cluster compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] :4-0-4-2_remote_db!: :context: 4-0_remote_db :4-0_remote_db: -include::../../common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] You can now upgrade the {engine-name} to 4.3. -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now change the cluster compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.1 or earlier only -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-0_remote_db!: diff --git a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-1.adoc b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-1.adoc index e47ee21b0e3..0c45c044b78 100644 --- a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-1.adoc +++ b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-1.adoc @@ -33,7 +33,7 @@ ifdef::rhv-doc[] endif::[] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.1/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.1. @@ -41,38 +41,38 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/upgrade/proc-Upgrading_Remote_Databases.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_Remote_Databases.adoc[leveloffset=+1] You can now update the {engine-name} to the latest version of 4.1. -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] You can now upgrade the {engine-name} to 4.2. -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] You can now upgrade the {engine-name} to 4.3. -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now update the hosts. -include::../../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.1 or earlier only -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] // Upgrades from 4.1 only -include::../../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] :4-1_remote_db!: diff --git a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-2.adoc b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-2.adoc index d1c4bf8c679..2b9bb8a52a9 100644 --- a/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-2.adoc +++ b/source/documentation/upgrade_guide/assembly-Remote_Upgrading_from_4-2.adoc @@ -29,41 +29,41 @@ endif::[] . If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-2_remote_db[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.2/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.2. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] endif::[] -include::../common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_Remote_Databases_to_PG10.adoc[leveloffset=+1] You can now update the {engine-name} to the latest version of 4.2. -include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] You can now upgrade the {engine-name} to 4.3. -include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now update the hosts. -include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.2 or earlier only If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-2_remote_db!: diff --git a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-0.adoc b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-0.adoc index af975b5e36e..400243e3f00 100644 --- a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-0.adoc +++ b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-0.adoc @@ -45,7 +45,7 @@ Upgrading your environment from 4.0 to 4.3 involves the following steps: . xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-0_SHE[Replace SHA-1 certificates with SHA-256 certificates] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.0/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.0. @@ -53,54 +53,54 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] :4-0_SHE!: :context: 4-0-4-2_SHE :4-0-4-2_SHE: -include::../../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] You must now update the hosts before you can update the cluster and data center compatibility versions. Update the self-hosted engine nodes first, and then any standard hosts. The procedure is the same for both host types. -include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] You can now change the cluster compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] :4-0-4-2_SHE!: :context: 4-0_SHE :4-0_SHE: -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here -include::../../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.1 or earlier only -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-0_SHE!: diff --git a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-1.adoc b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-1.adoc index 944cfc42dee..6dc3b088488 100644 --- a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-1.adoc +++ b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-1.adoc @@ -33,7 +33,7 @@ endif::[] . xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-1_SHE[Replace SHA-1 certificates with SHA-256 certificates] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.1/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.1. @@ -41,32 +41,32 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here -include::../../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] You can now update the self-hosted engine nodes, and then any standard hosts. The procedure is the same for both host types. -include::../../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.1 only -include::../../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] // Upgrades from 4.1 or earlier only -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-1_SHE!: diff --git a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-2.adoc b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-2.adoc index 45311e8fc12..dad6a20484f 100644 --- a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-2.adoc +++ b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-2.adoc @@ -31,39 +31,39 @@ endif::[] . If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-2_SHE[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.2/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.2. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] endif::[] -include::../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] -include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here -include::../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] You can now update the self-hosted engine nodes, and then any standard hosts. The procedure is the same for both host types. -include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Can be removed in 4.4 If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-2_SHE!: diff --git a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-3.adoc b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-3.adoc index ae3ef24f1a6..b24554f0c48 100644 --- a/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-3.adoc +++ b/source/documentation/upgrade_guide/assembly-SHE_Upgrading_from_4-3.adoc @@ -31,40 +31,40 @@ Upgrading a self-hosted engine environment from version 4.3 to 4.4 involves the . If you previously upgraded to 4.3 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-3_SHE[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.3/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.3. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] -include::../common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::common/she/snip-Enabling_Global_Maintenance_Mode.adoc[leveloffset=+1] -// include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +// include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_the_Manager_to_4-4.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_the_Manager_to_4-4.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here -include::../common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] +include::common/she/snip-Disabling_Global_Maintenance_Mode.adoc[leveloffset=+1] You can now update the self-hosted engine nodes, and then any standard hosts. The procedure is the same for both host types. -include::../common/upgrade/proc-Upgrading_hosts_to_4-4.adoc[leveloffset=+1] -// include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_hosts_to_4-4.adoc[leveloffset=+1] +// include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_hypervisor_preserve_local_storage.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_hypervisor_preserve_local_storage.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Can be removed in 4.4 If you previously upgraded to 4.3 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :context!: 4-3_SHE :4-3_SHE!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0.adoc index 544474eb517..607e2ecfda4 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0.adoc @@ -37,7 +37,7 @@ Upgrading your environment from 4.0 to 4.3 involves the following steps: . xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-0_local_db[Replace SHA-1 certificates with SHA-256 certificates] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.0/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.0. @@ -45,17 +45,17 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-1.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You must now update the hosts before you can update the cluster and data center compatibility versions. -include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] :4-0_local_db!: @@ -64,31 +64,31 @@ include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1 You can now change the cluster compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] :4-0-4-2_local_db!: :context: 4-0_local_db :4-0_local_db: -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] You can now change the cluster compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-0_local_db!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0_ff.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0_ff.adoc index 1b56afb1a81..a5279bad013 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0_ff.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-0_ff.adoc @@ -33,7 +33,7 @@ Upgrading your environment from 4.0 to 4.3 involves the following steps: . xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-0_local_db_ff[Replace SHA-1 certificates with SHA-256 certificates.] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] //// THIS IS DONE AUTOMATICALLY BY ovirt-fast-forward-upgrade @@ -57,7 +57,7 @@ If you try to continue without upgrading the cluster compatibility version to at You must now update the hosts before you can update the cluster and data center compatibility versions. -include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] :4-0_local_db_ff!: @@ -66,13 +66,13 @@ include::../../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1 You can now change the cluster compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.2. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] :4-0-4-2_local_db_ff!: @@ -84,14 +84,14 @@ Return to `ovirt-fast-forward-upgrade` and continue the process. The tool upgrad You can now change the cluster compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now change the data center compatibility version to 4.3. -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-0_local_db_ff!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1.adoc index 225afe9c162..f815c7afde9 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1.adoc @@ -29,7 +29,7 @@ ifdef::rhv-doc[] endif::[] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.1/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager[Subscribing to the Required Entitlements] for {virt-product-fullname} 4.1. @@ -37,27 +37,27 @@ For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{ // review above endif::[] -include::../../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-2.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now update the hosts. -include::../../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] // Upgrades from 4.1 only -include::../../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] :4-1_local_db!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1_ff.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1_ff.adoc index 5b415750908..6214ad11c73 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1_ff.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-1_ff.adoc @@ -25,7 +25,7 @@ ifdef::rhv-doc[] endif::[] // Prerequisites -include::../../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] //// THIS IS DONE AUTOMATICALLY BY ovirt-fast-forward-upgrade @@ -38,17 +38,17 @@ include::topics/Upgrading_with_ovirt-fast-forward-upgrade.adoc[leveloffset=+1] You can now update the hosts. -include::../../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] -include::../../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] // Upgrades from 4.1 only -include::../../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] +include::../common/upgrade/proc-Updating_OVN_Providers.adoc[leveloffset=+1] :4-1_local_db_ff!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2.adoc index 2ae9577070d..6a8b66ba92a 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2.adoc @@ -27,36 +27,36 @@ endif::[] . If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-2_local_db[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.2/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.2. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] endif::[] -include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_the_Manager_to_4-3.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now update the hosts. -include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.2 or earlier only If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-2_local_db!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2_ff.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2_ff.adoc index f430b669b64..4abc7956419 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2_ff.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-2_ff.adoc @@ -25,14 +25,14 @@ endif::[] . If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-2_local_db_ff[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. ifdef::rhv-doc[] For the list of required repositories, see link:{URL_customer-portal}{URL_docs}{URL_lang-locale}{URL_product_rhv}4.2/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.2. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] endif::[] include::topics/Upgrading_with_ovirt-fast-forward-upgrade.adoc[leveloffset=+1] @@ -40,18 +40,18 @@ include::topics/Upgrading_with_ovirt-fast-forward-upgrade.adoc[leveloffset=+1] You can now update the hosts. -include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.2 or earlier only If you previously upgraded to 4.2 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-2_local_db_ff!: diff --git a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-3.adoc b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-3.adoc index a02b793df8b..e5bb82c6c02 100644 --- a/source/documentation/upgrade_guide/assembly-Upgrading_from_4-3.adoc +++ b/source/documentation/upgrade_guide/assembly-Upgrading_from_4-3.adoc @@ -22,43 +22,43 @@ Upgrading your environment from 4.3 to 4.4 involves the following steps: . If you previously upgraded to 4.3 without replacing SHA-1 certificates with SHA-256 certificates, xref:Replacing_SHA-1_Certificates_with_SHA-256_Certificates_4-3_local_db[you must replace the certificates now]. // Prerequisites -include::../common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] +include::common/upgrade/snip-RHV_upgrade_prerequisites.adoc[leveloffset=+1] * Ensure the {engine-name} has the correct repositories enabled. For the list of required repositories, see link:{URL_virt_product_docs}{URL_format}/installing_{URL_product_virt}_as_a_standalone_manager_with_local_databases/index#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM[Enabling the {virt-product-fullname} {engine-name} Repositories] for {virt-product-fullname} 4.4. // This link must always be for the starting version of this assembly. // review above -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] -// include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +// include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_the_Manager_to_4-4.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_the_Manager_to_4-4.adoc[leveloffset=+1] // Add new {engine-name} upgrade versions here You can now update the hosts. -include::../common/upgrade/proc-Upgrading_hosts_to_4-4.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_hosts_to_4-4.adoc[leveloffset=+1] -include::../common/upgrade/proc-Upgrading_hypervisor_preserve_local_storage.adoc[leveloffset=+1] +include::common/upgrade/proc-Upgrading_hypervisor_preserve_local_storage.adoc[leveloffset=+1] -// include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +// include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] You can now update the cluster compatibility version. -include::../common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Cluster_Compatibility_Version.adoc[leveloffset=+1] You can now update the cluster compatibility version for virtual machines in the cluster. -include::../common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_Virtual_Machine_Cluster_Compatibility.adoc[leveloffset=+1] You can now update the data center compatibility version. -include::../common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] +include::common/upgrade/proc-Changing_the_Data_Center_Compatibility_Version.adoc[leveloffset=+1] // Upgrades from 4.3 or earlier only If you previously upgraded to 4.3 without replacing SHA-1 certificates with SHA-256 certificates, you must do so now. -include::../common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] +include::common/upgrade/proc-Replacing_SHA-1_Certificates_with_SHA-256_Certificates.adoc[leveloffset=+1] :4-3_local_db!: diff --git a/source/documentation/upgrade_guide/chap-Red_Hat_Virtualization_Upgrade_Overview.adoc b/source/documentation/upgrade_guide/chap-Red_Hat_Virtualization_Upgrade_Overview.adoc index 4d271e8787c..07b66a83bfd 100644 --- a/source/documentation/upgrade_guide/chap-Red_Hat_Virtualization_Upgrade_Overview.adoc +++ b/source/documentation/upgrade_guide/chap-Red_Hat_Virtualization_Upgrade_Overview.adoc @@ -1,5 +1,5 @@ [id="Red_Hat_Virtualization_Upgrade_Overview"] -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] = {virt-product-fullname} Upgrade Overview This guide explains how to upgrade the following environments to {virt-product-fullname} 4.3: diff --git a/source/documentation/upgrade_guide/chap-Updates_between_Minor_Releases.adoc b/source/documentation/upgrade_guide/chap-Updates_between_Minor_Releases.adoc index e6309c05f8c..eef389b71cf 100644 --- a/source/documentation/upgrade_guide/chap-Updates_between_Minor_Releases.adoc +++ b/source/documentation/upgrade_guide/chap-Updates_between_Minor_Releases.adoc @@ -1,7 +1,7 @@ [id='Updates_between_Minor_Releases'] = Updates between minor releases -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] ifdef::context[:parent-context: {context}] :context: minor_updates @@ -10,26 +10,26 @@ ifdef::context[:parent-context: {context}] To update from your current version of 4.4 to the latest version of 4.4, update the {engine-name} and then update the hosts. ifdef::rhv-doc[] -include::../common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] +include::common/upgrade/proc-Analyzing_the_Environment.adoc[leveloffset=+1] endif::[] To update a standalone {engine-name}, follow the standard procedure for minor updates: -include::../common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_the_Red_Hat_Virtualization_Manager.adoc[leveloffset=+1] -include::../common/upgrade/assembly-Updating_a_self-hosted_engine.adoc[leveloffset=+1] +include::common/upgrade/assembly-Updating_a_self-hosted_engine.adoc[leveloffset=+1] //Adding context back after assembly :context: minor_updates -include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1] You can also update hosts individually: -include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] +include::common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1] You should update the hosts from the Administration Portal. However, you can update the hosts using `yum update` instead: -include::../common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+1] +include::common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+1] ifdef::parent-context[:context: {parent-context}] ifndef::parent-context[:!context:] diff --git a/source/documentation/upgrade_guide/common b/source/documentation/upgrade_guide/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/upgrade_guide/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/upgrade_guide/index.adoc b/source/documentation/upgrade_guide/index.adoc index 67f220297b6..6eb51a36379 100644 --- a/source/documentation/upgrade_guide/index.adoc +++ b/source/documentation/upgrade_guide/index.adoc @@ -1,5 +1,5 @@ = Upgrade Guide -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] // Make sure Jekyll displays a guide title [discrete] diff --git a/source/documentation/virtual_machine_management_guide/assembly-Installing_Red_Hat_Enterprise_Linux_Virtual_Machines.adoc b/source/documentation/virtual_machine_management_guide/assembly-Installing_Red_Hat_Enterprise_Linux_Virtual_Machines.adoc index a7489262bd2..d31cb5c8c3d 100644 --- a/source/documentation/virtual_machine_management_guide/assembly-Installing_Red_Hat_Enterprise_Linux_Virtual_Machines.adoc +++ b/source/documentation/virtual_machine_management_guide/assembly-Installing_Red_Hat_Enterprise_Linux_Virtual_Machines.adoc @@ -26,7 +26,7 @@ Installing a {enterprise-linux} virtual machine involves the following key steps . xref:Installing_Guest_Agents_and_Drivers_Linux[Install guest agents and drivers] for additional virtual machine functionality. -include::../common/install/proc-Creating_a_virtual_machine.adoc[leveloffset=+1] +include::common/install/proc-Creating_a_virtual_machine.adoc[leveloffset=+1] [[Starting_the_Virtual_Machine]] == Starting the Virtual Machine @@ -45,7 +45,7 @@ include::topics/Enabling_the_Required_Repositories.adoc[leveloffset=+1] [[Installing_Guest_Agents_and_Drivers_Linux]] == Installing Guest Agents and Drivers -include::../common/install/ref-Red_Hat_Virtualization_Guest_Agents_and_Drivers.adoc[leveloffset=+2] +include::common/install/ref-Red_Hat_Virtualization_Guest_Agents_and_Drivers.adoc[leveloffset=+2] include::topics/Installing_the_Guest_Agents_and_Drivers_on_Red_Hat_Enterprise_Linux.adoc[leveloffset=+2] diff --git a/source/documentation/virtual_machine_management_guide/chap-Installing_Windows_Virtual_Machines.adoc b/source/documentation/virtual_machine_management_guide/chap-Installing_Windows_Virtual_Machines.adoc index 3ad0bac8188..62f5bbd1fee 100644 --- a/source/documentation/virtual_machine_management_guide/chap-Installing_Windows_Virtual_Machines.adoc +++ b/source/documentation/virtual_machine_management_guide/chap-Installing_Windows_Virtual_Machines.adoc @@ -15,7 +15,7 @@ Installing a Windows virtual machine involves the following key steps: When all of these steps are complete, the new virtual machine is functional and ready to perform tasks. -include::../common/install/proc-Creating_a_virtual_machine.adoc[leveloffset=+1] +include::common/install/proc-Creating_a_virtual_machine.adoc[leveloffset=+1] [[sect-Starting_the_Virtual_Machine_Using_the_Run_Once_Option]] == Starting the virtual machine using Run Once @@ -27,7 +27,7 @@ include::topics/Opening_a_Console_to_a_Virtual_Machine.adoc[leveloffset=+2] [[Installing_Guest_Agents_and_Drivers_Windows]] == Installing guest agents and drivers -include::../common/install/ref-Red_Hat_Virtualization_Guest_Agents_and_Drivers.adoc[leveloffset=+2] +include::common/install/ref-Red_Hat_Virtualization_Guest_Agents_and_Drivers.adoc[leveloffset=+2] include::topics/Installing_the_Guest_Agents_and_Drivers_on_Windows.adoc[leveloffset=+2] diff --git a/source/documentation/virtual_machine_management_guide/common b/source/documentation/virtual_machine_management_guide/common new file mode 120000 index 00000000000..60d3b0a6a8f --- /dev/null +++ b/source/documentation/virtual_machine_management_guide/common @@ -0,0 +1 @@ +../common \ No newline at end of file diff --git a/source/documentation/virtual_machine_management_guide/index.adoc b/source/documentation/virtual_machine_management_guide/index.adoc index 76129383a78..1f877ccc8e0 100644 --- a/source/documentation/virtual_machine_management_guide/index.adoc +++ b/source/documentation/virtual_machine_management_guide/index.adoc @@ -1,5 +1,5 @@ = Virtual Machine Management Guide -include::../common/collateral_files/ovirt-attributes.adoc[] +include::common/collateral_files/ovirt-attributes.adoc[] // Make sure Jekyll displays a guide title [discrete] diff --git a/source/documentation/virtual_machine_management_guide/topics/Canceling_ongoing_virtual_machine_migrations.adoc b/source/documentation/virtual_machine_management_guide/topics/Canceling_ongoing_virtual_machine_migrations.adoc index 3a6c66a7129..4e43b471725 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Canceling_ongoing_virtual_machine_migrations.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Canceling_ongoing_virtual_machine_migrations.adoc @@ -7,6 +7,6 @@ A virtual machine migration is taking longer than you expected. You'd like to be *Canceling Ongoing Virtual Machine Migrations* . Select the migrating virtual machine. It is displayed in menu:Compute[Virtual Machines] with a status of *Migrating from*. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Cancel Migration*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Cancel Migration*. The virtual machine status returns from *Migrating from* to *Up*. diff --git a/source/documentation/virtual_machine_management_guide/topics/Changing_the_CD_for_a_Virtual_Machine.adoc b/source/documentation/virtual_machine_management_guide/topics/Changing_the_CD_for_a_Virtual_Machine.adoc index 40fba46614d..ae88188e0ca 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Changing_the_CD_for_a_Virtual_Machine.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Changing_the_CD_for_a_Virtual_Machine.adoc @@ -6,7 +6,7 @@ You can change the CD accessible to a virtual machine while that virtual machine *Changing the CD for a Virtual Machine* . Click menu:Compute[Virtual Machines] and select a running virtual machine. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Change CD*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Change CD*. . Select an option from the drop-down list: * Select an ISO file from the list to eject the CD currently accessible to the virtual machine and mount that ISO file as a CD. * Select *[Eject]* from the list to eject the CD currently accessible to the virtual machine. diff --git a/source/documentation/virtual_machine_management_guide/topics/Cloning_a_Virtual_Machine.adoc b/source/documentation/virtual_machine_management_guide/topics/Cloning_a_Virtual_Machine.adoc index 823e8349b5d..67013652a13 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Cloning_a_Virtual_Machine.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Cloning_a_Virtual_Machine.adoc @@ -12,6 +12,6 @@ The *Clone VM* button is disabled while virtual machines are running; you must s *Cloning Virtual Machines* . Click menu:Compute[Virtual Machines] and select the virtual machine to clone. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Clone VM*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Clone VM*. . Enter a *Clone Name* for the new virtual machine. . Click btn:[OK]. diff --git a/source/documentation/virtual_machine_management_guide/topics/Creating_a_template_from_an_existing_virtual_machine.adoc b/source/documentation/virtual_machine_management_guide/topics/Creating_a_template_from_an_existing_virtual_machine.adoc index 89471a1ef87..19b7ce957d0 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Creating_a_template_from_an_existing_virtual_machine.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Creating_a_template_from_an_existing_virtual_machine.adoc @@ -16,7 +16,7 @@ When you create a template, you specify the format of the disk to be raw or QCOW . Click menu:Compute[Virtual Machines] and select the source virtual machine. . Ensure the virtual machine is powered down and has a status of `Down`. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Make Template*. For more details on all fields in the *New Template* window, see xref:Explanation_of_Settings_in_the_New_Template_and_Edit_Template_Windows[]. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Make Template*. For more details on all fields in the *New Template* window, see xref:Explanation_of_Settings_in_the_New_Template_and_Edit_Template_Windows[]. . Enter a *Name*, *Description*, and *Comment* for the template. . Select the cluster with which to associate the template from the *Cluster* drop-down list. By default, this is the same as that of the source virtual machine. . Optionally, select a CPU profile for the template from the *CPU Profile* drop-down list. diff --git a/source/documentation/virtual_machine_management_guide/topics/Editing_Virtual_Machine_Properties.adoc b/source/documentation/virtual_machine_management_guide/topics/Editing_Virtual_Machine_Properties.adoc index e2a667f2982..be937777929 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Editing_Virtual_Machine_Properties.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Editing_Virtual_Machine_Properties.adoc @@ -47,4 +47,4 @@ Changes to the following settings are applied immediately: . If the *Next Start Configuration* pop-up window appears, click btn:[OK]. -Some changes are applied immediately. All other changes are applied when you shut down and restart your virtual machine. Until then, the pending changes icon (image:../common/images/pendingchanges.png[]) appears as a reminder to restart the virtual machine. +Some changes are applied immediately. All other changes are applied when you shut down and restart your virtual machine. Until then, the pending changes icon (image:common/images/pendingchanges.png[]) appears as a reminder to restart the virtual machine. diff --git a/source/documentation/virtual_machine_management_guide/topics/Exporting_a_virtual_machines_to_a_host.adoc b/source/documentation/virtual_machine_management_guide/topics/Exporting_a_virtual_machines_to_a_host.adoc index ad3054aad06..00f7b1b2887 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Exporting_a_virtual_machines_to_a_host.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Exporting_a_virtual_machines_to_a_host.adoc @@ -11,7 +11,7 @@ The virtual machine must be shut down before being exported. *Exporting a Virtual Machine to a Host* . Click menu:Compute[Virtual Machines] and select a virtual machine. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Export to OVA*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Export to OVA*. . Select the host from the *Host* drop-down list. . Enter the absolute path to the export directory in the *Directory* field, including the trailing slash. For example: [filename]`/images2/ova/` . Optionally change the default name of the file in the *Name* field. diff --git a/source/documentation/virtual_machine_management_guide/topics/Exporting_individual_virtual_machines_to_the_export_domain.adoc b/source/documentation/virtual_machine_management_guide/topics/Exporting_individual_virtual_machines_to_the_export_domain.adoc index 8289f8c400f..b0d4c39ce61 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Exporting_individual_virtual_machines_to_the_export_domain.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Exporting_individual_virtual_machines_to_the_export_domain.adoc @@ -11,7 +11,7 @@ The virtual machine must be shut down before being exported. *Exporting a Virtual Machine to the Export Domain* . Click menu:Compute[Virtual Machines] and select a virtual machine. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Export to Export Domain*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Export to Export Domain*. . Optionally, select the following check boxes in the *Export Virtual Machine* window: * *Force Override*: overrides existing images of the virtual machine on the export domain. diff --git a/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_Virtual_Memory.adoc b/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_Virtual_Memory.adoc index d5c4c394b93..38215d556fe 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_Virtual_Memory.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_Virtual_Memory.adoc @@ -14,7 +14,7 @@ This feature is currently not supported for the self-hosted engine {engine-name} . Click menu:Compute[Virtual Machines] and select a running virtual machine. . Click btn:[Edit]. . Click the *System* tab. -. Increase the *Memory Size* by entering the total amount required. Memory can be added in multiples of 256 MB. By default, the maximum memory allowed for the virtual machine is set to 4x the memory size specified. Though the value is changed in the user interface, the maximum value is not hot plugged, and you will see the pending changes icon (image:../common/images/pendingchanges.png[]). To avoid that, you can change the maximum memory back to the original value. +. Increase the *Memory Size* by entering the total amount required. Memory can be added in multiples of 256 MB. By default, the maximum memory allowed for the virtual machine is set to 4x the memory size specified. Though the value is changed in the user interface, the maximum value is not hot plugged, and you will see the pending changes icon (image:common/images/pendingchanges.png[]). To avoid that, you can change the maximum memory back to the original value. . Click btn:[OK]. + This action opens the *Pending Virtual Machine changes* window, as some values such as *maxMemorySizeMb* and *minAllocatedMem* will not change until the virtual machine is restarted. However, the hot plug action is triggered by the change to the *Memory Size* value, which can be applied immediately. diff --git a/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_a_Virtual_Disk.adoc b/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_a_Virtual_Disk.adoc index 806e8fedc01..06f7153d335 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_a_Virtual_Disk.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Hot_Plugging_a_Virtual_Disk.adoc @@ -14,5 +14,5 @@ The guest operating system must support hot plugging virtual disks. . Click menu:Compute[Virtual Machines]. . Click a virtual machine name to go to the details view. . Click the *Disks* tab and select the virtual disk to hot plug. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Activate* to enable the disk, or *Deactivate* to disable the disk. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Activate* to enable the disk, or *Deactivate* to disable the disk. . Click btn:[OK]. diff --git a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_KVM.adoc b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_KVM.adoc index 7bc69e07cad..a35b106dde4 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_KVM.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_KVM.adoc @@ -45,7 +45,7 @@ If the import fails, refer to the relevant log file in */var/log/vdsm/import/* a + . Log in to the Administration Portal. . Click menu:Compute[Virtual Machines]. -. Click *More Actions* (image:../common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. +. Click *More Actions* (image:common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. . Select the *Data Center* that contains the proxy host. . Select *KVM (via Libvirt)* from the *Source* drop-down list. . Optionally, select a KVM provider *External Provider* from the drop-down list. The URI will be pre-filled with the correct URI. See link:{URL_virt_product_docs}administration_guide/index.html#Adding_KVM_as_an_External_Provider[Adding a KVM Host as a Virtual Machine Provider] in the _Administration Guide_ for more information. diff --git a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_Xen.adoc b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_Xen.adoc index b0f2dcef528..caab858da7d 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_Xen.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_Xen.adoc @@ -59,7 +59,7 @@ To import a virtual machine from RHEL 5 Xen, follow these steps: + . Log in to the Administration Portal. . Click menu:Compute[Virtual Machines]. -. Click *More Actions* (image:../common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. +. Click *More Actions* (image:common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. . Select the *Data Center* that contains the proxy host. . Select *XEN (via RHEL)* from the *Source* drop-down list. . Optionally, select a RHEL 5 Xen *External Provider* from the drop-down list. The URI will be pre-filled with the correct URI. See link:{URL_virt_product_docs}administration_guide/#Adding_Xen_as_an_External_Provider[Adding a RHEL 5 Xen Host as a Virtual Machine Provider] in the _Administration Guide_ for more information. diff --git a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_a_VMware_Provider.adoc b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_a_VMware_Provider.adoc index a8e07b7b599..adaf317003f 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_a_VMware_Provider.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Importing_a_Virtual_Machine_from_a_VMware_Provider.adoc @@ -31,7 +31,7 @@ If the import fails, refer to the relevant log file in */var/log/vdsm/import/* a *Importing a Virtual Machine from VMware* . Click menu:Compute[Virtual Machines]. -. Click *More Actions* (image:../common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. +. Click *More Actions* (image:common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. . Select *VMware* from the *Source* list. . If you have configured a VMware provider as an external provider, select it from the *External Provider* list. Verify that the provider credentials are correct. If you did not specify a destination data center or proxy host when configuring the external provider, select those options now. . If you have not configured a VMware provider, or want to import from a new VMware provider, provide the following details: diff --git a/source/documentation/virtual_machine_management_guide/topics/Importing_an_OVA_file_from_a_host.adoc b/source/documentation/virtual_machine_management_guide/topics/Importing_an_OVA_file_from_a_host.adoc index 228d534a795..ba213fd98d4 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Importing_an_OVA_file_from_a_host.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Importing_an_OVA_file_from_a_host.adoc @@ -27,7 +27,7 @@ The location can be a local directory or a remote nfs mount, as long as it has s ---- + . Click menu:Compute[Virtual Machines]. -. Click *More Actions* (image:../common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. +. Click *More Actions* (image:common/images/moreactions.png[]) and select *Import*. This opens the *Import Virtual Machine(s)* window. .. Select *Virtual Appliance (OVA)* from the *Source* list. .. Select a host from the *Host* list. .. In the *Path* field, specify the absolute path of the OVA file. diff --git a/source/documentation/virtual_machine_management_guide/topics/Importing_an_Unregistered_Disk_Image.adoc b/source/documentation/virtual_machine_management_guide/topics/Importing_an_Unregistered_Disk_Image.adoc index 6491b49e11c..b7c067033d6 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Importing_an_Unregistered_Disk_Image.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Importing_an_Unregistered_Disk_Image.adoc @@ -13,7 +13,7 @@ Only QEMU-compatible disks can be imported into the {engine-name}. *Importing a Disk Image* . Click menu:Storage[Domains]. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Scan Disks* so that the {engine-name} can identify unregistered disks. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Scan Disks* so that the {engine-name} can identify unregistered disks. . Select an unregistered disk name and click *Disk Import*. . Select one or more disk images and click *Import*. This opens the *Import Disk(s)* window. . Select the appropriate *Disk Profile* for each disk. diff --git a/source/documentation/virtual_machine_management_guide/topics/Live_migration_prerequisites.adoc b/source/documentation/virtual_machine_management_guide/topics/Live_migration_prerequisites.adoc index ba26b649b5b..4c8c0ddd0dd 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Live_migration_prerequisites.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Live_migration_prerequisites.adoc @@ -1,7 +1,7 @@ [[Live_migration_prerequisites]] ==== Live Migration Prerequisites -include::../../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] +include::../common/sriov/conc-Set_Up_and_Configure_SR-IOV.adoc[] You can use live migration to seamlessly move virtual machines to support a number of common maintenance tasks. Your {virt-product-fullname} environment must be correctly configured to support live migration well in advance of using it. diff --git a/source/documentation/virtual_machine_management_guide/topics/Removing_Virtual_Disks_From_Virtual_Machines.adoc b/source/documentation/virtual_machine_management_guide/topics/Removing_Virtual_Disks_From_Virtual_Machines.adoc index bde17ddb125..17e4a497ce8 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Removing_Virtual_Disks_From_Virtual_Machines.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Removing_Virtual_Disks_From_Virtual_Machines.adoc @@ -6,7 +6,7 @@ . Click menu:Compute[Virtual Machines]. . Click a virtual machine name to go to the details view. . Click the *Disks* tab and select the virtual disk to remove. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Deactivate*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Deactivate*. . Click btn:[OK]. . Click btn:[Remove]. . Optionally, select the *Remove Permanently* check box to completely remove the virtual disk from the environment. If you do not select this option - for example, because the disk is a shared disk - the virtual disk will remain in menu:Storage[Disks]. diff --git a/source/documentation/virtual_machine_management_guide/topics/Virtual_Machine_System_Settings_Explained.adoc b/source/documentation/virtual_machine_management_guide/topics/Virtual_Machine_System_Settings_Explained.adoc index 046010e873e..f4ef56fda79 100644 --- a/source/documentation/virtual_machine_management_guide/topics/Virtual_Machine_System_Settings_Explained.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/Virtual_Machine_System_Settings_Explained.adoc @@ -2,7 +2,7 @@ ==== Virtual Machine System Settings Explained :context: vm_sys_settings -include::../../common/admin/snip-CPU-Considerations.adoc[] +include::../common/admin/snip-CPU-Considerations.adoc[] The following table details the options available on the *System* tab of the *New Virtual Machine* and *Edit Virtual Machine* windows. [[New_VMs_Initial_Run-226]] diff --git a/source/documentation/virtual_machine_management_guide/topics/proc_Exporting_individual_virtual_machines_to_a_data_domain.adoc b/source/documentation/virtual_machine_management_guide/topics/proc_Exporting_individual_virtual_machines_to_a_data_domain.adoc index 4e2838e48ef..48708d82ce7 100644 --- a/source/documentation/virtual_machine_management_guide/topics/proc_Exporting_individual_virtual_machines_to_a_data_domain.adoc +++ b/source/documentation/virtual_machine_management_guide/topics/proc_Exporting_individual_virtual_machines_to_a_data_domain.adoc @@ -19,7 +19,7 @@ The data domain is attached to a data center. . Click menu:Compute[Virtual Machines] and select a virtual machine. . Click the *Disks* tab. . Select all disks belonging to the virtual machine. -. Click *More Actions* (image:../common/images/moreactions.png[]), then click *Move*. +. Click *More Actions* (image:common/images/moreactions.png[]), then click *Move*. . Under *Target*, select the domain. . Click btn:[OK]. From a59b5bcbb5aed458fe82b3a4fefcb315c1b907f0 Mon Sep 17 00:00:00 2001 From: Sandro Bonazzola Date: Thu, 27 May 2021 15:45:54 +0200 Subject: [PATCH 2/3] address comments in PR review Signed-off-by: Sandro Bonazzola --- CONTRIBUTING.md | 14 ++++++++++++++ _config.yml | 15 ++------------- 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e99672c1c9c..5acb22b1358 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,6 +96,20 @@ rvm use 2.5 ./setup.sh && ./run-server.sh ``` +Please note that due to symlinks in documentation directories you may see errors like: + +``` + ** ERROR: directory is already being watched! ** + + Directory: /ovirt-site/source/documentation/administration_guide/common + + is already being watched through: /ovirt-site/source/documentation/common + + MORE INFO: https://github.com/guard/listen/blob/master/README.md +``` + +These errors can be safely ignored. + If the site builds successfully, you will see this message: The Jekyll web server is standing watch at http://\[address\]:4000 (the exact URL is given on the terminal when Jekyll is ready) diff --git a/_config.yml b/_config.yml index 4d4ba9ae78f..7b6f1d472c9 100644 --- a/_config.yml +++ b/_config.yml @@ -139,36 +139,25 @@ exclude: - CODEOWNERS # avoid generating paginated asciidoc content - documentation/common/**/* - - documentation/administration_guide/appe* + - documentation/**/appe* + - documentation/**/common/**/*.adoc - documentation/administration_guide/chap* - - documentation/administration_guide/common/**/*.adoc - documentation/administration_guide/part* - documentation/administration_guide/topics - documentation/data_warehouse_guide/chap* - documentation/data_warehouse_guide/topics - - documentation/data_warehouse_guide/common/**/*.adoc - documentation/disaster_recovery_guide/assembly - documentation/disaster_recovery_guide/concept - documentation/disaster_recovery_guide/reference - documentation/disaster_recovery_guide/task - - documentation/disaster_recovery_guide/common/**/*.adoc - - documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/common/**/*.adoc - - documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/common/**/*.adoc - - documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/common/**/*.adoc - - documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/common/**/*.adoc - documentation/introduction_to_the_vm_portal/topics - documentation/introduction_to_the_vm_portal/chap* - - documentation/introduction_to_the_vm_portal/common/**/*.adoc - - documentation/migrating_from_a_standalone_manager_to_a_self-hosted_engine/common/**/*.adoc - documentation/upgrade_guide/assembly* - documentation/upgrade_guide/chap-* - documentation/upgrade_guide/topics - - documentation/upgrade_guide/common/**/*.adoc - - documentation/virtual_machine_management_guide/appe* - documentation/virtual_machine_management_guide/chap* - documentation/virtual_machine_management_guide/topics - documentation/virtual_machine_management_guide/assembly* - - documentation/virtual_machine_management_guide/common/**/*.adoc sass: add_charset: true style: :compressed From 6d1cd05ae6d3e31c024259d8935f8c8698cc5702 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc=20Dequ=C3=A8nes=20=28Duck=29?= Date: Mon, 31 May 2021 18:23:58 +0900 Subject: [PATCH 3/3] Add workaround to silence watch errors about symlinks pointing to the same location --- CONTRIBUTING.md | 14 -------------- source/_plugins/jekyll_watch_symlink_workaround.rb | 14 ++++++++++++++ 2 files changed, 14 insertions(+), 14 deletions(-) create mode 100644 source/_plugins/jekyll_watch_symlink_workaround.rb diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5acb22b1358..e99672c1c9c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,20 +96,6 @@ rvm use 2.5 ./setup.sh && ./run-server.sh ``` -Please note that due to symlinks in documentation directories you may see errors like: - -``` - ** ERROR: directory is already being watched! ** - - Directory: /ovirt-site/source/documentation/administration_guide/common - - is already being watched through: /ovirt-site/source/documentation/common - - MORE INFO: https://github.com/guard/listen/blob/master/README.md -``` - -These errors can be safely ignored. - If the site builds successfully, you will see this message: The Jekyll web server is standing watch at http://\[address\]:4000 (the exact URL is given on the terminal when Jekyll is ready) diff --git a/source/_plugins/jekyll_watch_symlink_workaround.rb b/source/_plugins/jekyll_watch_symlink_workaround.rb new file mode 100644 index 00000000000..ae8ac19faa0 --- /dev/null +++ b/source/_plugins/jekyll_watch_symlink_workaround.rb @@ -0,0 +1,14 @@ +# see https://github.com/oVirt/ovirt-site/pull/2505 +# borrowed from https://github.com/guard/listen/issues/339#issue-101785791 +require 'listen/record/symlink_detector' +module Listen + class Record + class SymlinkDetector + def _fail(_, _) + # don't warn, noisy + # keep the exception to skip listing on the symlink target in _fast_build_dir() + raise ::Listen::Error::SymlinkLoop, 'Failed due to looped symlinks' + end + end + end +end