Home > Guides > Dashboard Users Guide > Clouds > AWS Regions > EC2 Elastic IPs > Actions > Switch my frontends to use EIastic IPs

MindTouch
Copyright (c) 2006-2014 MindTouch Inc.
http://mindtouch.com

This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).

At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.

A complete copy of the MSA is available at http://www.mindtouch.com/msa

Switch my frontends to use EIastic IPs

Objective

To switch running front-end servers using dynamic assigned IPs to using Elastic IPs.

Overview

If you have running frontend servers that are using a DNS Provider for configuring their dynamic IP addresses and wish to switch to using an Elastic IP instead, you will need to follow the migration instructions below in order to ensure that your visitors do not experience any problems connecting to your site.  If you do not take the necessary steps when changing the IP addresses of running frontend servers, your users could experience a sudden interruption of service and bad server requests as you suddenly switch to using Elastic IP addresses.

Migration Instructions - Summary

In order to follow best practices when switching to Elastic IP addresses you must follow the necessary precautionary steps. 

  1. Create Elastic IPs for your frontend servers.  See Create Elastic IPs (EIP).
  2. Launch new servers using the appropriate frontend ServerTemplate that is using the latest RightImageTM
  3. Connect the new EIP frontend servers to the running application servers.
  4. Connect the new EIP frontend servers to each other. 
    NOTE:  This step only applies to Basic Setups because in this scenario, frontends are also running application servers.
  5. Change the DNS A records for your two frontends to point to the new EIP frontend servers.
  6. Once no more requests are being served from the old frontend servers, terminate them.

Sample Setup Diagrams

Below are diagrams of two common setups.  The Basic Setup is a 4-instance deployment where the frontends serve as both the load balancer and application server.  In the Advanced Setup, the frontends are strictly load balancers that point to all of the application servers.

01-switch_eip_setup.gif

Steps

Step 1: Create two Elastic IPs for your frontend servers.

If you have not reserved Elastic IP (EIP) addresses that you can later assign to your frontend servers, follow the Create Elastic IPs (EIP) tutorial and register two Elastic IPs.  You will need an EIP for each frontend server.

Step 2:  Launch new frontend servers using the most recent frontend ServerTemplates

Select the appropriate RightScale frontend ServerTemplate (PHP FrontEnd, Rails FrontEnd, etc.).

  1. Add a Server to your Deployment with the appropriate server information.  Select the first Elastic IP (e.g. fe-1) that you want to associate with the first frontend.  Click Add.
    screen-AddServerEIP1-v1.png
     
  2. Repeat the process for the second frontend server and select the other Elastic IP (e.g. fe-2).
  3. Launch the new servers. 
  4. Once the servers are operational, continue to the next step.

Step 3: Connect the new EIP frontend servers to the running application servers

The next step it to connect the new EIP frontend servers to the running application servers by executing the LB get HA proxy config operational RightScript.  The new frontend servers will try to get the configuration file from the running frontend servers.  Once they get the configuration file, they can route traffic to the application servers.

02-switch_eip_config2.gif

 

 

03-switch_eip_connect2.gif

 

 

Step 4: Connect the new frontends to each other

NOTE: This step only applies to the Basic Setup.  For Advanced Setups, skip to the next step.

Since the frontend instances are also running the application servers, you'll need to associate the new frontends together by running the LB mongrels to HA proxy connect RightScript.

03-switch_eip_connect.gif

 

Step 5: Change the DNS A records to point to the Elastic IPs

The new EIP frontend servers are now ready to serve traffic.  With your DNS provider, lower the TTL on the A records that point to your frontend servers so that the change will be propagated more quickly.  Wait a couple of minutes and then change the DNS A records to point to the new EIP frontend servers so incoming traffic will be routed to the frontends.  

 

04-switch_eip_dns2.gif

 

 

Step 6: Terminate old frontend servers

Once no more requests are being handled by the old frontend servers (FE-1, FE-2), you can safely terminate the instances.  You can find information about HAproxy and Apache activity in the monitoring graphs.  We recommend leaving the old frontend servers running for a couple of days to make sure everything is running properly, because if you experience any problems, it will be easy to switch back to the old frontends.

 

05-switch_eip_terminate2.gif

You must to post a comment.
Last Modified
22:16, 16 May 2013

Tags

Classifications

This page has no classifications.

Announcements

None

Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.