In-Guest High Availability Configuration in OpenStack Using InfoScale Availability Agents

Transcription

1 In-Guest High Availability Configuration in OpenStack Using InfoScale Availability Agents Solution Brief Last updated:

2 Table of Contents INTRODUCTION... 3 USE CASE... 3 REQUIREMENTS... 5 CONFIGURATION OVERVIEW... 5 SOFTWARE LIMITATIONS... 6 SAMPLE CONFIGURATION... 6 TESTED CONFIGURATIONS... 9 REFERENCES

3 Introduction Veritas InfoScale Availability (formerly known as Veritas Cluster Server VCS lets you configure applications for high availability (HA in an OpenStack environment. An HA configuration in OpenStack guests needs to support the underlying network resources as well. InfoScale Availability provides the following agents to support the configurations for these resources: OpenStackIP: The OpenStackIP agent lets you fail over an IP between compute instances by adding IP addresses to and removing IP addresses from the OpenStack device ports. OpenStackAuth: The OpenStackAuth agent enables communication between the OpenStackIP agent and other OpenStack components. The OpenStackAuth agent generates and validates the tokens and endpoint URLs that the OpenStackIP agent needs to communicate with the OpenStack components. Use case To illustrate the InfoScale solution, this document uses the example of an Oracle application that is installed on OpenStack VMs with the Oracle database data stored over an NFS location. To automatically respond to database failures, clients must be smart enough to reconnect to the database and connect to a virtual IP address that is configured on the active database node. This virtual IP address must be available at the Neutron port of the active host. 3

4 To enable the failover of an IP to other available host in case of a database or instance failure, we need to use the OpenStackIP agent along with the IP agent in an InfoScale configuration. The OpenStackIP agent works with the Neutron port and it updates the port definition of the device while bringing the resource online or taking it offline. The following graphics depict an application that is configured for in-guest HA in Red Hat OpenStack using InfoScale Availability: Figure 1: Application and OpenStackIP service group online on Node 1 Figure 2: Application or instance faulted on Node 1; service group failed over to Node 2 4

5 Requirements The operating system-provided curl rpm must be present on each cluster node. Configuration overview Configure a parallel service group for the OpenStackAuth agent, and make it a child of the service group for the OpenStackIP agent. The following figure depicts the resource dependencies in the OpenStackIP or the application service group: 5

6 Software limitations When PrivateIP is specified and the value of the UseNewPort attribute is set to 0 (zero, the following limitations apply: The agent appends the value of PrivateIP to the --fixed_ips field of the device port. By default, -- fixed_ips can accommodate only five IP addresses. It already has one address, which is the base address of the device. The number of IP address per port can be changed in a Neutron configuration. For details, see the value of max_fixed_ips_per_port in the /etc/neutron/neutron.conf file. Workaround: If the cluster configuration has more than four OpenStackIP resources for the same device, from the fifth OpenStackIP resource onwards, set the UseNewPort attribute to 1. The base IP address of the device in the instance network configuration must be static. If it is set to DHCP, the virtual IP address may be set as the base IP of the device after reboot. Sample configuration include "OracleASMTypes.cf" include "types.cf" include "Db2udbTypes.cf" include "OracleTypes.cf" include "OpenStackTypes.cf" include "SybaseTypes.cf" cluster nfsoracle ( SecureClus = 1 UseFence = SCSI3 system vcs1 ( system vcs3 ( group OpenStackAuth_Grp ( SystemList = { vcs1 = 0, vcs3 = 1 } Parallel = 1 AutoStartList = { vcs1, vcs3 } OpenStackAuth OpenStackAuth_Res ( Tenant = Infoscale 6

7 Username = admin Password = BPHnEPeHChDHe KeystoneEP = " Region = RegionOne // resource dependency tree // // group OpenStackAuth_Grp // OpenStackAuth OpenStackAuth_Res group OracleDB_Grp ( SystemList = { vcs1 = 0, vcs3 = 1 } AutoStartList = { vcs1, vcs3 } IP IP_Res ( Device = eth0 Address = " X.X" NetMask = " " Mount Mount_Res ( Critical = 0 MountPoint = "/data" BlockDevice = "vcs4:/oradata" FSType = nfs4 MountOpt = rw NIC NIC_Res ( Device = eth0 Netlsnr Listener_Res ( Owner = oracle Home = "/oracle/12102/dbbase/dbhome" OpenStackIP OpenStackIP_Res ( PrivateIP = " X.X" 7

8 FloatingIP = " X" Device = eth0 UseNewPort = 0 Oracle OracleDB_Res ( Sid = oradb Owner = oracle Home = "/oracle/12102/dbbase/dbhome" requires group OpenStackAuth_Grp online local firm IP_Res requires OpenStackIP_Res Listener_Res requires IP_Res OpenStackIP_Res requires NIC_Res OracleDB_Res requires Listener_Res OracleDB_Res requires Mount_Res // resource dependency tree // // group OracleDB_Grp // Oracle OracleDB_Res // Netlsnr Listener_Res // IP IP_Res // OpenStackIP OpenStackIP_Res // NIC NIC_Res // Mount Mount_Res group vxfen ( SystemList = { vcs1 = 0, vcs3 = 1 } AutoFailOver = 0 Parallel = 1 8

9 CoordPoint coordpoint ( ActionOnCoordPointFault = RefreshRegistrations Phantom RES_phantom_vxfen ( // resource dependency tree // // group vxfen // Phantom RES_phantom_vxfen // CoordPoint coordpoint Tested configurations The following configurations have been tested: OpenStack version Guest operating system version InfoScale Availability version RHOSP 10 RHEL 6.x, RHEL 7.x, SLES 11, SLES 12 InfoScale Availability 7.x RHOSP 11 RHEL 6.x, RHEL 7.x, SLES 11, SLES 12 InfoScale Availability 7.x Mirantis 9 RHEL 6.x, RHEL 7.x, SLES 11, SLES 12 InfoScale Availability 7.x Neutron Networking API v2.0 References For information on installing the agents and configuring the service groups for OpenStack, see the InfoScale Availability Agents for OpenStack Installation and Configuration Guide. You can find the document by filtering through the agents at: Additionally, refer to the following documents at: age%20foundation For information on the InfoScale bundled agents, see the Cluster Server Bundled Agents Reference Guide. For general information on administering a cluster and monitoring resources, see the Cluster Server Administrator s Guide. 9

10 About Veritas Technologies LLC Veritas Technologies LLC enables organizations to harness the power of their information, with solutions designed to serve the world s largest and most complex heterogeneous environments. Veritas works with 86 percent of Fortune 500 companies today, improving data availability and revealing insights to drive competitive advantage. For specific country offices and contact numbers, please visit our website. Veritas World Headquarters 500 East Middlefield Road Mountain View, CA ( Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. 10