Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Disaster Recovery Strategies Using oVirt's new Storage Connection Management Features (DevConf.cz 2014)

4,469 views

Published on

A short overview of oVirt 3.3's Storage Connection Management feature, and several examples how this feature can be used in Disaster Recovery strategies.

Published in: Technology, Business

Disaster Recovery Strategies Using oVirt's new Storage Connection Management Features (DevConf.cz 2014)

  1. 1. Disaster Recovery Strategies Using oVirt's new Storage Connection Management Features Allon Mureinik Team Lead, Cloud Storage, Red Hat amureini@redhat.com / @mureinik February 2014 Allon Mureinik - oVirt 3.3 Storage DR Features 1
  2. 2. Agenda ● Storage concepts in oVirt ● ● Storage Domain vs. Storage Server Connection oVirt 3.3's new APIs and capabilities ● ● ● GUI REST Putting it all together ● DR me, please! Allon Mureinik - oVirt 3.3 Storage DR Features 2
  3. 3. Terminology “Language is the means of getting an idea from my brain into yours without surgery” - Mark Amidon Allon Mureinik - oVirt 3.3 Storage DR Features 3
  4. 4. Terminology ● Disk – A virtual disk used by a VM (or template) ● ● VDSM terminology: Image Storage Domain – A large storage area monitored and managed by oVirt. ● Main usage: Provisioning disks ● Supported storage types: ● File Storage: NFS, GlusterFS, POSIX, local FS ● Block Storage: iSCSI, FCP Allon Mureinik - oVirt 3.3 Storage DR Features 4
  5. 5. So what’s a Storage Server Connection? ● The “physical” properties where the “virtual” Storage Domain can be found ● ● ● For file storage – a [mount] path For iSCSI – target details – iqn, port, username, password, etc. For FCP – not available Allon Mureinik - oVirt 3.3 Storage DR Features 5
  6. 6. Terminology – a visual representation Allon Mureinik - oVirt 3.3 Storage DR Features 6
  7. 7. What’s the problem? (pre 3.3) ● ● ● Users aren’t aware of Storage Server Connections Users aren’t aware of the distinction between them and Storage Domains GUI: ● ● ● One screen to add Part of Storage Domains management REST: ● No such entity ● Queried and added via Storage Domain operations Allon Mureinik - oVirt 3.3 Storage DR Features 7
  8. 8. What’s the problem – GUI (NFS) Allon Mureinik - oVirt 3.3 Storage DR Features 8
  9. 9. The Problem – GUI (iSCSI) Allon Mureinik - oVirt 3.3 Storage DR Features 9
  10. 10. What’s the problem - REST Allon Mureinik - oVirt 3.3 Storage DR Features 10
  11. 11. What’s new in oVirt 3.3? ● Storage Server Connections are an entity ● ● They can be queried, added and updated independently of the Storage Domains ... And as such can be edited ● Supported for NFS, POSIX, local FS and iSCSI ● Both via the GUI and via REST ● Some advanced operations only available in REST Allon Mureinik - oVirt 3.3 Storage DR Features 11
  12. 12. GUI – File based Storage Domains Allon Mureinik - oVirt 3.3 Storage DR Features 12
  13. 13. REST – The main collection Allon Mureinik - oVirt 3.3 Storage DR Features 13
  14. 14. REST – A property of a Storage Domain Allon Mureinik - oVirt 3.3 Storage DR Features 14
  15. 15. Is there a DR in the house? Allon Mureinik - oVirt 3.3 Storage DR Features 15
  16. 16. Approach 1 – Network trickery only Allon Mureinik - oVirt 3.3 Storage DR Features 16
  17. 17. Approach 1 – Network trickery only (2) ● ● When the DR site comes up, oVrit Engine sends the same connection details to the new hosts Luckily, the DR site has its own DNS server, and the old connection details just point to the replicated storage ● ● Extremely dangerous Not flexible – requires similar (if not identical) hardware configuration on both sites Allon Mureinik - oVirt 3.3 Storage DR Features 17
  18. 18. Approach 2 – Update the connection Allon Mureinik - oVirt 3.3 Storage DR Features 18
  19. 19. Approach 2 – Update the connection (2) Allon Mureinik - oVirt 3.3 Storage DR Features 19
  20. 20. Approach 2 – Update the connection (3) ● ● When switching over to the DR site, use the REST API to edit the connection details for all storage domains Applicable for NFS, POSIX and iSCSI ● ● ● Redundant for FCP, of course Advantage: Relatively simple Disadvantage: another step in an already elaborate process Allon Mureinik - oVirt 3.3 Storage DR Features 20
  21. 21. Approach 3 – Redundant Connections Allon Mureinik - oVirt 3.3 Storage DR Features 21
  22. 22. Approach 3 – Redundant Connections (2) ● ● ● ● User REST API to add connection to all the storage servers, including the DR site, when the site is established Make sure, via network configuration, that each host can only access one storage server, so there aren’t any “collisions” Advantage: Preemptive, less steps when switching over to a DR site Disadvantage: Additional “useless” information in the production site Allon Mureinik - oVirt 3.3 Storage DR Features 22
  23. 23. Looking forward Allon Mureinik - oVirt 3.3 Storage DR Features 23
  24. 24. Looking forward (no commitment) ● Support for GlusterFS ● Connection redundancy for file domains ● ISCSI multipathing (oVirt 3.4) ● Integrations ● ● E.g. Symantec Cluster Server Patches are welcome! Allon Mureinik - oVirt 3.3 Storage DR Features 24
  25. 25. Where now? ● oVirt homepage: ● ● Feature page: ● ● http://www.ovirt.org/Features/Manage_Storage_Connections Lists: ● ● http://www.ovirt.org users@ovirt.org Feedback: ● http://devconf.cz/f/117 Allon Mureinik - oVirt 3.3 Storage DR Features 25

×