Fedora Account System
Red Hat Associate
Red Hat Customer
Describe the issue: ------------------- Information regarding DR needs to be improved. 1. change#1 Chapter 3, 'section 3.1.2. Prerequisites for failover and failback configuration' - mentions "Execute Ansible playbooks manually from a separate master node". This title should replaced with "Execute Ansible playbooks manually from a separate machine" and contents under that should be: <snip> Generate and execute Ansible playbooks manually from a separate machine that acts as an Ansible controller node. This node needs the package ovirt-ansible-collection that has all the required disaster recovery ansible roles. NOTE: By default, this package is installed with Hosted Engine Virtual Machine. In the case of disaster, the primary site may be broken which would result in Hosted Engine VM down. So its safe to use separate machine outside of primary site to maintain and run this playbook, but for testing purpose these playbooks can be triggered from Hosted Engine Virtual Machine </snip> 2. change#2 Section 3.3.1.1 - replace mounted at /var/run/gluster/shared_storage with /run/gluster/shared_storage 3. Change#3 Section 3.4.2 - under the first point 'create playbook to generate the mapping file', remove this statement - "Red Hat recommends creating this file in the /usr/share/ansible/roles/oVirt.disaster-recovery directory of the server that provides ansible and manages failover and failback." This location is no longer available, user can create the playbook in any location in the machine 4. Change#4 Section 3.4.2 Update - "Example playbook file: dr-ovirt-setup.yml", update the last line of the playbook as: <snip> roles: - ovirt.ovirt.disaster_recovery </snip> 5. Change#5 The above change#4 applies to playbook example - "Example playbook file: dr-rhv-failover.yml" in the section "3.4.3. Creating a failover playbook between source and target clusters" 6. Change#6 The change#4 applies to playbook example -"Example playbook file: dr-cleanup.yml" in the section "3.4.4. Creating a failover cleanup playbook for your primary cluster" 7. Change #7 The change #4 applies to the playbook example - "Example playbook file: dr-rhv-failback.yml" in the section "3.4.5. Create a failback playbook between source and target clusters" 8. Change #8 - Section "Appendix A. Mapping File Attributes" For "Storage domain details" row , in addition to the existing value, add a note: "make sure to mention only the storage domains that has its data sync configured to the secondary site" Describe the task you were trying to accomplish: ------------------------------------------------- Updates to the document with the latest RHV 4.4.3 Document URL: ------------- https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/maintaining_red_hat_hyperconverged_infrastructure_for_virtualization/config-backup-recovery Product Version: ------------------- RHHI-V 1.8
Just noticed that change#8 mentioned in comment0, is actually referring to Appendix section in RHV guide. Instead, the same information[1] can be added as NOTE in RHHI-V Maintenance guide, under the section 3.4.2. Creating a mapping file between source and target clusters, under the content: <snip> See Appendix A: Mapping File Attributes in the Red Hat Virtualization Disaster Recovery Guide for detailed information about attributes used in the mapping file </snip> [1] - Make sure to mention only the storage domain in the mapping file, that has data sync configured to the secondary site. The mapping block for the other storage domains without data sync, for example hosted-engine storage domain, section can be removed from the mapping file.
Also section-6.1 Creating a shutdown playbook, needs the playbook to be corrected. Example playbook file: shutdown_rhhi-v.yml This is a one word change. existing content: --- - name: oVirt shutdown environment hosts: localhost connection: local gather_facts: false vars: engine_url: https://ovirt-engine.example.com/ovirt-engine/api engine_user: admin@internal engine_password: 123456 engine_cafile: /etc/pki/ovirt-engine/ca.pem roles: - ovirt.shutdown_env Expected content: --- - name: oVirt shutdown environment hosts: localhost connection: local gather_facts: false vars: engine_url: https://ovirt-engine.example.com/ovirt-engine/api engine_user: admin@internal engine_password: 123456 engine_cafile: /etc/pki/ovirt-engine/ca.pem roles: - ovirt.ovirt.shutdown_env
change#10 Add the following content to section 3.4.3 before the existing example snippet <content> You can define a password file (for example passwords.yml) to store the Manager passwords of the primary and secondary site. For example: --- # This file is in plain text, if you want to # encrypt this file, please execute following command: # # $ ansible-vault encrypt passwords.yml # # It will ask you for a password, which you must then pass to # ansible interactively when executing the playbook. # # $ ansible-playbook myplaybook.yml --ask-vault-pass # dr_sites_primary_password: primary_password dr_sites_secondary_password: secondary_password Note For extra security you can encrypt the password file. However, you will need to use the --ask-vault-pass parameter when running the playbook. See Using Ansible Roles to Configure Red Hat Virtualization in the Administration Guide for more information. </content> This is the information available with RHV DR guide https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/disaster_recovery_guide/index#create_failover_failback
Verified with the doc link and required changes are implemented in the doc
*** Bug 1894463 has been marked as a duplicate of this bug. ***
changes are already published