Red Hat Enterprise Virtualization Disaster Recovery

Transcription

1 Red Hat Enterprise Virtualization Disaster Recovery John Herr, RHCA Senior Software Engineer, Red Hat Aaron Weitekamp Senior Software Engineer, Red Hat

2 What is this session about?

3 This session is about Disaster Recovery An overview of the failover process. The methods available to create a failover. The Red Hat Enterprise Virtualization 3.3 REST API. Automating the failover process.

4 Presenters John Herr Senior Software Engineer, Red Hat Aaron Weitekamp Senior Software Engineer, Red Hat Both work in the Systems Engineering Team at Red Hat. This team identifies high-value solution stacks based on input from Sales, Marketing, and Engineering teams and develops reference architectures for customers.

5 Failover Environment No two environments are the same

6

7 Environment Description Required Mirrored Storage Red Hat Enterprise Virtualization Manager Data Domain Optional Mirrored Storage ISO Domain Export Domain Non-Mirrored Storage DNS/DHCP server

8 Failing Over The Process

9 Failover Steps 1.Ensure storage domain data is available 2.Ensure name resolution for the RHEV Manager host name 3.Bring up RHEV Manager at second site 4.Add second sites hypervisors to the datacenter 5.Modify the storage configuration 6.Bring up VMs

10 Preparing Move storage domain data Mirrored data storage (Ideal Solution) Name resolution

11 Interfaces to Control Failover

12 Failover Methods Web User Interface (partial) REST API rhevm-shell rhevm-sdk-python rhevm-sdk-java Third Party Applications

13 Web User Interface (portal)

14 RHEVM-Shell Wrapper around the REST API calls Data is passed and returned in a human readable format Uses either UUIDs or Common Names to access resources Scriptable

15 RHEVM-Shell Setup $ cat /root/.rhevmshellrc [cli] autoconnect = True autopage = True [ovirt-shell] username = admin@internal timeout = -1 extended_prompt = False url = insecure = False filter = False session_timeout = -1 ca_file = /root/ca.crt dont_validate_cert_chain = False key_file = None password = password cert_file = None

16 RHEVM-Shell Example Interactive use of shell $ rhevm-shell [RHEVM shell (connected)]# add datacenter --name DC-iSCSI --storage_type iscsi --version-major 3 --version-minor 3 Non-Interactive use of shell $ rhevm-shell <<< "add datacenter --name DC-iSCSI --storage_type iscsi --version-major 3 --version-minor 3 --expect '201-created'"

17 RHEVM-Shell Example - Output id name status-state storage_type : ecd6d eb-808d-66ad12126c5e : DC-iSCSI : uninitialized : iscsi supported_versions-version-major: 3 supported_versions-version-minor: 3 version-major : 3 version-minor : 3

18 REST API Calls are made through a web portal as GET, PUT, POST, etc requests. Data is passed and returned in XML format Uses UUIDs to access resources Curl can be used to submit API requests Scriptable

19 REST API Example $ wget --no-check-certificate $ curl --cacert ca.crt --user 'admin@internal:password' \ --header "Accept: application/xml" \ --header "Content-type: application/xml" \ --request "POST" \ --data '<data_center> <name>dc-iscsi</name> <storage_type>iscsi</storage_type> <version minor="1" major="3"/> </data_center>' \

20 REST API Example - Output <?xml version="1.0" encoding="utf-8" standalone="yes"?> <data_center href="/api/datacenters/1727e963-bd5c-4e43-99c5- d79fd " id="1727e963-bd5c-4e43-99c5-d79fd "> <name>dc-iscsi</name> <storage_type>iscsi</storage_type> <version major="3" minor="1"/> <supported_versions> <version major="3" minor="2"/> <version major="3" minor="1"/> <version major="3" minor="3"/> </supported_versions> <status> <state>uninitialized</state> </status> </data_center>

21 RHEVM software development kits rhevm-sdk-python, rhevm-sdk-java Libraries for interacting with the REST API

22 API Methods

23 Disaster Recovery APIs /api/storageconnections/connection_uuid path, iqn, address, port, user, password /api/networks/network_uuid name, description, ip, vlan, stp and display /api/hosts /api/hosts/host_uuid/nics/nic_uuid network, ip and boot_protocol

24 Update iscsi Storage Connection rhevm-shell [RHEVM shell (connected)]# update storageconnection e545772d-0e34-4db6-8e6f-db076ef8a139 --target iqn com.equallogic:0-1cb196-7de60c201-2e19b5f809c5310b-rdriscsi-b id : e545772d-0e34-4db6-8e6f-db076ef8a139 address: port : 3260 target : iqn com.equallogic:0-1cb196-7de60c201-2e19b5f809c5310b-rdr-iscsi-b type : iscsi

25 Update iscsi Storage Connection REST API curl --silent --cacert rhevm.cer \ --user "admin@internal:2bor!2b" \ --header "Accept: application/xml" \ --header "Content-type: application/xml" \ --request "PUT" \ 1cb196-7c160c201-08f9b5f b-rdr-iscsi-a</target> </storage_connection>" \ --data "<storage_connection> <target>iqn com.equallogic:0- 0e34-4db6-8e6f-db076ef8a139

26 Disaster Recovery Process

27 Failover Steps Bring up RHEV Manager Fix networking Keep original hostname Prevents need to recreate certificates Add hypervisors to RHEV Manager and approve them Modify storage connection using API Start the Vms Test for functionality

28 Mirror Data from Primary Site to Backup Site This is hopefully already done using mirroring If not, the data domain needs restored to the backup site Could take a while

29 Name Resolution Create a dns entry for the RHEV Manager This entry should resolve the original FQDN to an address on the backup site's network Will require zone for original site

30 Bring up the RHEV Manager Fix networking New IP Address (can be automatically taken care of with DHCP) May need to edit /etc/udev/rules.d/70-persistent-net.rules Keep original hostname to prevent the need to re-create certificates

31 Hypervisors Add the new hypervisors to RHEV Manager Add configure hypervisor nics if needed Power on the Vms Test the Vms for functionality

32 New Backup API Methods

33 Backup APIs /api/vms/vm_uuid/snapshots /api/vms/vm_uuid/snapshots/snap_uuid/disks /api/vms/vm_uuid/disks

34 Backup Process Create a snapshot of the VMs disk Attach the snapshot onto a backup appliance VM Backup the data on the disk Detach the snapshot from the appliance With the API, all this can be controlled via the appliance VM

35 Resources

36 Summit Sessions of Interest Configuring a disaster-resilient Red Hat Enterprise Virtualization environment Wednesday, 2:30-3:30 Red Hat Enterprise Virtualization: Overview & roadmap Wednesday, 3:40 4:40 Red Hat Enterprise Virtualization Hypervisor roadmap Thursday, 9:45 10:45 Red Hat Enterprise Virtualization deep dive Wednesday, 4:50 5:50

37 Summit Demos Symantec Tintri

38 Reference Architectures Red Hat Customer Portal Provides tar balls of scripts used in reference architecture if available Support -> Knowledgebase -> Reference Architectures Red Hat Resource Library No scripts available

39 Thanks Please complete the session survey