4.6. Setting up IP address resources on AWS

Procedure

1. Add the two resources to the same group that you have already created to enforce order and colocation constraints.

2. Install the resource-agents package:

   # dnf install resource-agents

3. Create an elastic IP address:

   [root@ip-10-0-0-48 ~]# aws ec2 allocate-address --domain vpc --output text

   eipalloc-4c4a2c45   vpc 35.169.153.122

4. Optional: Display the description of awseip. This shows the options and default operations for this agent.

   # pcs resource describe awseip

5. Create the Secondary Elastic IP address resource with the allocated IP address in the 2nd step:

   # pcs resource create <resource_id> awseip elastic_ip=<elastic_ip_address> allocation_id=<elastic_ip_association_id> --group networking-group

   Example:

   # pcs resource create elastic awseip elastic_ip=35.169.153.122 allocation_id=eipalloc-4c4a2c45 --group networking-group

Verification

1. Verify the cluster status to ensure resources are available:

   [root@ip-10-0-0-58 ~]# pcs status

   Cluster name: newcluster
   Stack: corosync
   Current DC: ip-10-0-0-58 (version 1.1.18-11.el7-2b07d5c5a9) - partition with quorum
   Last updated: Mon Mar  5 16:27:55 2018
   Last change: Mon Mar  5 15:57:51 2018 by root via cibadmin on ip-10-0-0-46
   
   3 nodes configured
   4 resources configured
   
   Online: [ ip-10-0-0-46 ip-10-0-0-48 ip-10-0-0-58 ]
   
   Full list of resources:
   
    clusterfence   (stonith:fence_aws):    Started ip-10-0-0-46
    Resource Group: networking-group
        vip (ocf::heartbeat:IPaddr2): Started ip-10-0-0-48
        elastic (ocf::heartbeat:awseip): Started ip-10-0-0-48
   
   Daemon Status:
     corosync: active/disabled
     pacemaker: active/disabled
     pcsd: active/enabled

   In this example, newcluster is an active cluster where resources such as vip and elastic are part of the networking-group resource group.

2. Launch an SSH session from your local workstation to the elastic IP address that you have already created:

   $ ssh -l ec2-user -i ~/.ssh/cluster-admin.pem 35.169.153.122

3. Verify that the SSH connected host is same as the host with the elastic resources.