oVirt DR Site to-site using ansible
Download as ODP, PDF•1 like•993 views
This document discusses disaster recovery for oVirt virtualization environments. It describes how oVirt has evolved to support disaster recovery through exporting and importing storage domains. However, this process was manual. oVirt 4.2 added more attributes to OVF files to support automatic registration of VMs and templates between sites. Ansible roles are now available to automate failover and failback between primary and secondary oVirt sites using mapping files. The roles generate mappings, import storage domains, register VMs and templates, and start VMs to recover the secondary site or restore the primary site.
oVirt DR Site to-site using ansible
- 1. This presentation is licensed under a Creative Commons Attribution 4.0 International License Ansible Makes oVirt DR a Piece of Cake Maor Lipchuk Senior Software Engineer Red Hat Israel January 2018
- 2. Can a Disaster be Avoided? 2 Disasters In Our Day To Day
- 3. 3 ● Amazon explains big AWS outage, says employee error took servers offline, promises changes ● Microsoft: Overheating caused Outlook and Hotmail shutdown ● Google goes down for 5 minutes, Internet traffic drops 40% ● WhatsApp panic hits after messaging app suffers worldwide outage Disasters In Our Day To Day
- 5. 5 oVirt Disaster Recovery Evolution
- 6. Pros ● Simple file storage domain ● Provides a backup solution for VMs and Templates Cons ● Not suitable for backing up the entire setup ● Long copy operations 6 Export Storage Domain
- 7. ● OVF_STORE Disk ● Import Storage Domain 7 oVirt 3.5 - Import Storage Domain Metadata OVF_STORE OVF OVF OVF OVF OVF
- 8. Improvements ● Recover process is faster ● No copy operations are needed ● All VMs and templates In the setup are recoverable 8 oVirt 3.5 - Import Storage Domain
- 9. Known Issues ● Not a fully fledged, end to end solution for the entire oVirt setup ● The recovery process is done manually ● Entities’ properties are not fully covered in OVF 9 oVirt 3.5 - Import Storage Domain
- 10. What Is New With oVirt 4.2 10
- 11. Adding missing attributes to the OVF 11 oVirt 4.2 - Fill In The Gaps Cluster Name External LUN Disk Affinity Group Affinity Label Permissions Vnic Profile
- 12. ● OVF_STORE disk includes “extra data” file ● VM Statuses supported 12 oVirt 4.2 - Fill In The Gaps DOW N UP
- 13. ● Define a way to support a recovery process for oVirt setup to a separate site 13 oVirt 4.2 – DR site to site
- 14. Site To Site: Pre Requirements 14
- 15. Storage replication should be configured for the storage domains to be recovered 15 Step 1 - Storage Replication
- 16. A pre configured secondary setup that contains hardware properties such as networks, clusters and hosts 16 Step 2 - Prepare “Just In Case” Setup Secondary Site PrimarySite
- 17. On recovery, the secondary setup will be used for recovery. The recovery process includes 1. Import the replicated storage domains 2. Register all the VMs and Templates 3. Run all the VMs which were running in the original site 17 Step 2 - Prepare “Just In Case” Setup
- 18. 18 How To Mix And Match?
- 19. Define a mapping file to map between primary site and secondary site attributes. Will be used on register entities 19 Step 3 - Mapping File
- 20. 20 Step 3 - Mapping File
- 21. http://1.bp.blogspot.com/- yPK9sZFw7qU/TqBDueEHcJI/AAAAAAAAB6I/34HinboIM ao/s1600/Exhaustion.jpg Warning! Writing mapping files might be exhausting
- 22. oVirt Ansible Disaster Recovery 22
- 23. ● Part of ansible galaxy https://galaxy.ansible.com/oVirt/disaster-recovery/ ● A role which is part of the ovirt-ansible repository ● oVirt-ansible maintains multiple Ansible roles that can be deployed to easily configure and manage various parts of the oVirt infrastructure. ● oVirt ansible is maintained by Ondra Machacek 23 oVirt Ansible Disaster Recovery
- 24. ● Generate Mapping ● Failover ● Failback 24 oVirt Ansible Disaster Recovery
- 25. ● Go over the entire primary setup and creates a mapping template automatically ● Admin needs to fill in the missing parts of the secondary site 25 Mapping Generator
- 26. --- - name: Generate mapping hosts: localhost connection: local vars: site: http://localhost:8080/ovirt-engine/api username: admin@internal password: my_password ca: /pki/ovirt-engine/ca.pem var_file: my_var_file.yml vars_files: - passwords.yml roles: - ovirt-ansible-disaster-recovery 26 Mapping Generator – Define a Play
- 27. 27 Mapping Generator – Simple as it gets
- 28. 28 Mapping Generator – Output Example --- dr_sites_primary_url: http://localhost:8080/ovirt-engi-ne/api dr_sites_primary_username: admin@internal dr_sites_primary_ca_file: /home/mlipchuk/ovirt- share/etc/pki/ovirt-engine/ca.pem # Please fill in the following properties for the secondary site: dr_sites_secondary_url: dr_sites_secondary_username: dr_sites_secondary_ca_file: dr_import_storages: my_var_file.yml
- 30. ● Recover the secondary setup automatically using the a mappings var file 30 Ansible Failover
- 31. ● Automation process - Import master storage domains - Import all other storage domains - Register Templates (with mapping) - Register VMs (with mapping) - Run HA VMs - Run other VMs 31 Ansible Failover - Automation
- 32. --- - name: Failover oVirt setup hosts: localhost connection: local vars: dr_target_host: secondary dr_source_map: primary vars_files: - passwords.yml roles: - ovirt-ansible-disaster-recovery 32 Ansible Failover – Define a Play
- 33. 33 Failover – Simple as it gets
- 34. Automation Process (Failback) ● Restoring the primary site back again after it has been shifted to a secondary site 34 Ansible Failback
- 35. Automation Process (Failback) - Get the primary setup ready for import - Clean the secondary site from its storage domains - Notice the admin to switch the replication process - Import replicated storage domains to the primary - Register all Templates and VMs - Run all VMs which ran before (HA first and then all other VMs) 35 Ansible Failback
- 36. Summary 36
- 37. ● Filled in the gaps in the VM’s and template’s OVF ● VMs statuses were added in the OVF_STORE disk ● Recovery process is now automatically thanks to Ansible ● User is able to failover and failback the environment 37 Summary
- 38. - Ansible galaxy https://galaxy.ansible.com/oVirt/disaster-recovery/ - oVirt ansible repo https://github.com/oVirt/ovirt-ansible.git - oVirt ansible disaster recovery repo: https://github.com/oVirt/ovirt-ansible-disaster-recovery 38 Links
- 39. This presentation is licensed under a Creative Commons Attribution 4.0 International License THANK YOU http://www.ovirt.org [email protected] [email protected]
Editor's Notes
- #2: Hello, My name is Maor Lipchuk I’m a senior Software Engineer in the oVirt storage team I work in Red Hat Israel and Today I would like to talk with you about oVirt solution for Disaster Recovery and what we introduced in oVirt 4.2
- #3: I would like to start with a retorical quesiton, Can we avoid a disaster?
- #4: So, as you can see even the most known and biggest companies encountered one way or another a disaster. The truth is no matter how much money and resources a company will invest to avoid a disaster, no one can guarantee a disaster will be avoided. Which basically has some positive relief , because that means that a disaster is something that in some terms can be understandable by customers. But what is crucial for the costumer, and what really makes a company reliable is that the customer’s data will recovered with minimum data lost in the most fastest and efficient way. Which brings me to the Disaster Recovery Solution
- #5: So, after saying that, how does oVirt supports Disaster Recovery
- #6: Through the course of time, oVirt introduced several ways for backup and recovery solutions, I would like to go on some of them to get the concept of the invention which was introduced in oVirt 4.2
- #7: Export Storage Domain is one solution which was part of oVirt all along. It gave the ability for the admin to backup its VMs and Templates into a file storage domain which was attached to the Data Center. The backup process basically copied the disks and the VM’s or Template’s OVF and once the user desired to recover that VM one only needed to import that entity and uwalla, it has his VM back The problem wuth
- #8: In oVirt
- #13: Elaborate more what the admin needs to do
- #14: Elaborate more what the admin needs to do