You can create two types of server arrays. Depending on which one you create (alert-based or queue-based) the configuration options will change accordingly.Manage > Arrays > New
A server array consists of mostly identical EC2 instances where the number of instances varies over time in response to changing factors. For example, the number of instances can go up based on high CPU usage, or go back down with low CPU usage. A series of alert specifications and escalations are used to define the conditions under which the server array will change, such as launching or terminating servers.
There are two types of server arrays:
Select the New action button to create a new Server Array.Manage > Arrays > Index
View basic information about the server array including its status, which deployment it's a part of, as well as any current scaling stats.
The Statistics tab is only visible for queue-based arrays that have statistics enabled. To view statistics, enable the "Audit entry analysis" option under the array's Info tab.Manage > Arrays > Show > Statistics tab
The Volumes tab lists all of the EBS volumes that are currently attached to instances in the server array.
The Inputs tab shows the input values that will be inherited by all new servers that are launched into the server array. In most cases, new servers will inherit these values from the ServerTemplate and/or Deployment that it's attached to. Similar to a server's Next Inputs tab, any inputs that are defined at the Server Array level (under this tab) will overwrite any values that are defined at the ServerTemplate or Deployment levels. Remember, since servers in an array may have been launched at different times, this tab is not designed to be an accurate description of the input configurations for each server in the array.
Note: When you execute a script under a server array's Scripts tab, the inputs that are defined under this tab will be used.Manage > Arrays > Show > Inputs tab
The Info tab shows basic information about the server array including its status (enabled/disabled), the array type, associated deployment, autoscaling parameters, etc. If you can click the Edit icon to change the revision of the array's ServerTemplate, new servers will use the new revision specified while any existing (running) servers will inherit the input values of the new revision (input hierarchy rules apply). If you enable an array, new servers can be launched into the array. If you disable the array, no new server instances can be launched, but any active servers in the array will continue to run normally. The Scaling Stats section describes recent scaling activity.
If you are using an alert-based server array and have predictable traffic patterns, you might want to use the Schedule alert option to define a weekly scaling schedule.Manage > Arrays> Show > Info tab
The Current Alerts tab shows each running server that's in the array along with the status of its alerts. A green ball denotes that there are no triggered alerts, whereas a red ball denotes a triggered alert condition on the server. A red ball will be shown for each triggered alert specification.
Alert specifications cannot be edited under this tab. To modify alerts on the current running servers in the array you must modify them at the individual server level. To modify alerts on future servers that are launched into the array, use the array's "Next Alerts" tab.Manage > Arrays > Show > Current Alerts tab
The Scripts tab shows a list of RightScripts that can be run on server instances in the array. When you run a script on server instance(s) in the array using one of the options below, you will be prompted to verify input parameters and confirm the execution of the script. When you attempt to run a script, you will see a list of all ServerTemplates in the array that contain that script. You can only run a script on a server instance where its ServerTemplate contains the script. For example, there may be situations where you have server instances in the array that were created with different ServerTemplates or different revisions of the same ServerTemplate.
The Instances tab allows you to sort by the state of the active instances in the array (all, stranded, pending, operational, terminating). You cannot 'lock' an instance in a server array to prevent it from being terminated. Server arrays are designed to either grow or shrink based on the defined alert conditions. Instances will automatically be launched and terminated as necessary. You can only control the minimum number of instances that should remain active in a server array. However, you cannot control which ones should remain active. If you want a particular server instance to persist and not be termianted, you must add it to your deployment. You cannot move a particular server instance from a server array into your deployment or vice-versa.Manage > Arrays > Show > Instances tab
The Next Alerts tab shows the alert specifications that will be inherited by any new servers that are launched into the server array. By default, instances will inherit these alert specifications from the array's ServerTemplate. However, you can also add additional alert specifications at the server array level. Existing instances that are already running will remain unaffected and will not inherit any additional alert specifications.
© 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.