The E2E Gaming Deployment only has one front end Server built out by the shared macro. In production, we recommend having two front end Servers for failover and load balancing. This tutorial will walk you through the basic steps to get an additional front end Server up and running in your Deployment, each with its own Elastic IP (EIP).
Note: Please consult the referenced tutorials for additional details (if needed).
A Deployment that is up and operational as a result of executing the E2E Gaming macro. You should have (at a minimum) a running master and slave database Server, and a front end Server.
Note: Although this tutorial was created to supplement the E2E Gaming macro/tutorial, the steps can be used for guidelines in other Deployments.
Note that even though the second FE Server is operational, if you navigate to its public URL in our phpBB application example, you will see the Introduction page (not the bulletin board application itself). This is the page where you can start the installation process. Normally, you would update your ServerTemplate to include the installation of your application. In our phpBB example, this is still a manual operation.
Note: If you refresh your browser several times on the phpBB bulletin board example, you might expect to alternate between the phpBB application (which was installed and running on FE1) and the Introduction page (on FE2). However, this is not the case because of the TTL. The default TTL on your A Records in DME is 1800 seconds (30 minutes). You can of course force going to FE2 by using the EIP or the EC2 Public DNS URL in your browser address bar.
© 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.